WARNING: On FE Aircraft ini files

[+peter01 2]

I posted something about this before, but now that someone else is experiencing these problems, I just want to emphasize:

 

DO NOT MOVE aircraft ini files (planexxx.ini,xxxloadout.ini, and possibly the data.ini's (the FMs) as well) from FE2 to FE1. Do not use aircraft files done for FE2 in FE1.

 

You will have major problems. Things won't work, you may not even be aware of it, and by the time you are, possibly a lot of the plane files will need to be fixed.

 

Generally if you move ini or loadout files from FE2 to FE1, or those done for and/or on a FE2 game, many of these will have a problem. Either you will not see the plane as flyable or there will be no loadout options or both. If you then move them then to FE2, further or even new problems will occur in FE2 as well, as files become even further corrupted! These problems happen as FE1 and FE2 are essentially different.

 

This is true not just of my FMs, but any - stock ones, other peoples FMs, anything. It is hard to be aware of, as not all planes are effected. Not sure why some/many are, and other are not.

 

BUT, it is safe to move FE1 files --> FE2 (if not already corrupted). NOT vice versa.

Edited April 2, 2010 by peter01

[Wrench 9,805]

It should also be mentioned, that 99.9% of the inis AND the lods in NextGen Series games (SF2 & FE2) are in Unicode.

 

Now, in SF2 series, ANSI inis don't seem to have much of a problem, other than increasing game/mission/terrain loading time (sometimes to 5-7 minute range!) You can decrease this time, and probably increas the general smoothness of the sim, by converting ini to Unicode.

 

It's pretty simple ... open the ini (notepad will do, as always), and "SAVE AS..." and select Unicode as the format. Just plane unicode, NOT Unicode BigEndian.

 

Going the other way, from FE2 to FE is NOT (usually) possible, as the 1stGen series game engine cannot read the unicode inis and lods. Inis can be converted down, but LODs cannot (well, not with MAX)

 

A lot of this has been covered in the 'other 3W forums above', and in the SF2 Knowledge Base.

 

wrench

kevin stein

[+peter01 2]

It should also be mentioned, that 99.9% of the inis AND the lods in NextGen Series games (SF2 & FE2) are in Unicode.

 

Now, in SF2 series, ANSI inis don't seem to have much of a problem, other than increasing game/mission/terrain loading time (sometimes to 5-7 minute range!) You can decrease this time, and probably increas the general smoothness of the sim, by converting ini to Unicode.

 

It's pretty simple ... open the ini (notepad will do, as always), and "SAVE AS..." and select Unicode as the format. Just plane unicode, NOT Unicode BigEndian.

 

Going the other way, from FE2 to FE is NOT (usually) possible, as the 1stGen series game engine cannot read the unicode inis and lods. Inis can be converted down, but LODs cannot (well, not with MAX)

 

A lot of this has been covered in the 'other 3W forums above', and in the SF2 Knowledge Base.

 

wrench

kevin stein

 

 

Thanks wrench - explains the mystery (I think!). We're all new to the next gen FE2, and cos' we all have spent a lot of time getting the FE1 game working well I guess many of us never had time or interest to look at developments in SF2.

 

Bit of a learning curve ...

Edited April 2, 2010 by peter01