why is everything so difficult now?
#1

for the last 18 months I've been manually installing all the mods as they came out...with hardly any of the problems other people have...

now all the new stuff will only work with the UI install and is not backwards compatible with the 0.93 soundmod... (new a/c and buttons files)

so does that mean i have to start again and reinstall the lot from scratch using the UI???

getting like microsoft here :roll:
Reply
#2

Should be okay. I found it necessary lately to start using UI buttons files instead of 9.3 type in my custom install, plus I picked a few objects from the UI1.1. Apart from that though it's fairly easy to keep current if you know the drill. You've been in on the process since the earliest days of modding, so you should be alright. :wink:
Reply
#3

I only use the UI version for online flying.. Everything else I install I do manualy into my main original modded version, (0.93) for when I'm flying offline.. everything is totaly compatible at the moment.. As stated, if you know your way around the basic file structure in the modded game it's relatively easy to manualy install stuff.
Minor problems encountered are usualy sorted by chatting in the relevant threads, so touch wood it will continue to do so..
One thing to remember though is if you want to fly online as well, the days of just having one install for everything are long gone.. the game has moved on, so its a matter of dealing with that fact and getting used to having another install on your system, (or more)..
Reply
#4

well I'm almost 100% off-line....but i've not been able to install any of the last crop of a/c with new buttons files...they just CTD at 60% Cry

so does that mean that if I choose UI install during the a/c installer instead of 9.3...it gives me a completely different file?
Reply
#5

fabianfred Wrote:well I'm almost 100% off-line....but i've not been able to install any of the last crop of a/c with new buttons files...they just CTD at 60% Cry

I'm pretty conversant with file structures and mods and making stuff, but I have the same problem with all the latest new aircraft requiring new 'buttons' - no matter what i do I cannot get them installed. I too have the dreaded 60% crash ...
Reply
#6

I had the same problem with new aircrafts until I tried to install them manually and not with their installer.
So now I unzip the files of the installer with winrar or tugzip and then I place them in the folders to which they are destinated, and, the most important, I add the lines for air.ini, plane_ru.properties and weapons_ru.properties at THE END of the files and NOT in alphabetical order. As result in the QMB I have the new planes at the end of the list, but they work!
With the new AC 3.5, all new planes fly well.
Maybe it works only for me, I don't know, because other members put new entries in alphabetical order and have no problems, but if I do so, my Il2 crash at 60%. Bizarre.

PS
If the installer is not "unzippable" (the ones with a hard disk icon) I run it and choose as destination
a 'fake' Il2 with the same folders structure, so later I know where to put the new items manually)

I hope that this can help you
Reply
#7

I can only understand this partly.

it is not so hard removing files and Mods folder and installing UI and then from there build in all teh stuff you wand on top.
works pretty straight forward I think and the compatibility issues where part of the reason why a UI came and why it makes sense.

it is supposed to be a common plattform to build on.

actually I think not this but the other way around is complicated.

try it, you will find it not so hard. i know that you know your way around the files a bit and this makes it even easier. Smile
Reply
#8

I've pretty much given up on the new beta aircraft until they become official in the next installment of AAA UI. The Spifire XIV mod completely porked my install for some reason, whilst it worked when I tried to uninstall it for online purposes I got CTDS at 60 despite having the latest AC installer. Bizarre, but not to worry, I can wait. Smile
Reply
#9

Guys, the 60% crash is due to an inconsistenci between what the Buttons file expect to find FM wise and what it actually finds. UI 1.1 is the safe way to go in this respect becouse the "other aircrafts" buttos file are probably built taking the latest Aircraft intall version and adding the "beta plane" in question.

So if you have a current U.I. + Air.Inst. you should have no problems, unless you ahve any planes outside AAA.

Bottom line. You may have lots of planes installed, that are not called by the buttons file. What you can
Reply
#10

[quote="Baco1170"]
Bottom line. You may have lots of planes installed, that are not called by the buttons file. What you can
Reply
#11

No.

The buttons file contains the flight models for the aircraft in the game. The class file of any installed aircraft (i.e. listed in air.ini) calls for the relevant flight model from the buttons file when the game loads.

If you have an aircraft in your air.ini that doesn't have the flight model in the buttons file you are using, the game crashes at 60%. However, you can have flight models in the buttons file that aren't used, and it will still work. The buttons file could have a thousand different flight models of aircraft you don't have, and it will still work. But have just one aircraft listed in your air.ini that doesn't have the flight model in your buttons and it will crash.

So, the way to not get crashes is to ensure that the buttons you are using has been updated for the aircraft you want to install in air.ini. I'm using Muas' 'All Mighty'. This features almost every flight model except some of the recent things (like the Battle, new Spits and the Typhoon). So, using this buttons file I can't use those aircraft. However, if the buttons gets updated, I can.

People have problems when they have a set of aircraft installed and then copy over their buttons with a new one because they've installed a new plane. If that buttons doesn't feature the planes you've already installed, it will crash.

Let's make up an example. You've got Muas' new Bf 109s and it works. You've got the 'All Mighty' buttons that has the new Bf109 flight models and they're listed in air.ini. Everything's perfect.
Then you install a new aircraft, for example the Battle. You copy over the 'All Mighty' buttons with a new one that came with the Battle. Crash.

Why? because you've still got the new Bf109s installed and you've removed the buttons file that has their flight model. The only way is to remove all traces of the Bf 109s and use aicraft that you know are on the buttons.

So, basically, you just need to be mindful of what you've installed, and understand that you can't have every plane if you don't have the right buttons file. Buttons files really aren't that mysterious, or confusing - the 60% crash is saying the game can't find what it needs in the buttons.

Joe
Reply
#12

Thanks for the calrification Cannon!
Reply
#13

Well this last makes sense ... at least you don't need to install all new aircraft, even if you don't care for them.

But, if so, how come when I (try to) install a new aircraft like the PZL-24 or Miles Magister and when I use the very latest buttons file, the game will still crash?

I still wonder if there isn't something else interfering with new plane installs.

In the past I used to be able to install new aircraft with new buttons and they worked quite fine ... but then, and I can't pinpoint when, no new aircraft will install correctly anymore.

It's a bit mystifying but ultimately not anything that I am worried about ... I doubt I've flown a full mission these last months, being occupied with other Il-s related matters.

Perhaps it also annoys on a personal level - I keep on wondering what I have done incorrectly ...
Reply
#14

How many different people are authoring these Buttons files?

I read somewhere that the UI uses a different file structure/names for the sound files...could this cause a problem?
Reply
#15

Quote:How many different people are authoring these Buttons files?

I read somewhere that the UI uses a different file structure/names for the sound files...could this cause a problem?

As I understand the rules were changed about a month ago, so only official AAA buttons files may be released/posted on the site. This makes good sense as the buttons file is the tree of the knowledge of good and evil for this game.

However, it seems that the powers that be on this site don't seem to have the time to add certain aircraft (or WIP/Beta) or veto certain aircraft that appear on here, so not every aircraft on this site is included in the buttons file as far as I can see.

To work in the game, any aircraft with an entry in air.ini must have a corresponding FM in the buttons file. Obviously FMs are the holy of holies for all stock A/c and must not be altered. As you can hopefully deduce, if all sorts of people start putting out random buttons files then there is the scope to insert ones own nefarious code and datum for even stock aircraft.

Although this all makes sense, imho the baby was somewhat thrown out with the bathwater as Muas and Karaya were putting out 'almighty' buttons files with all know a/c and these worked a treat. However, this was stopped and now only UI related buttons files are put out which seem to be much less comprehensive and indeed problematic for some, at times.

Unfortunately, in order to protect the integrity of the game, some seemingly draconian measures must be enforced. They are of course meant for your and the games' protection. If you use AAA then you accept that AAA know best what this means for both them and you.
Reply


Forum Jump:


Users browsing this thread: 9 Guest(s)