• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX Help - 2.1.24d Texture Install Number Sequence

jordanal

jordanal

Messages
78
Country
us-florida
Hi again, Don.
I've come across a bit of in issue using 2.1.24d when installing zip textures from the AIFP download-install AC window. I'm not sure, but I think there is some character or hidden text being introduced into the aircraft.cfg flltsim.x number sequence.

As you can see in capture1, the last EMB190 livery was fltsim.36 before installing the latest two textures (Lufthansa .37, and NasAir .38) with AIFP.

Then when I run Peter Van der Veen's ACA2007.exe utility, it picks up a sequence error in the aircraft.cfg (the EMB190 for example in this discussion is highlighted in its report).

I then run the FSRenum.exe utility on the aircraft.cfg which has always worked before, and it interpretes the last two installed liveries as .0 and .1 as shown in Capture 3. I've never seen this renum utility not sequence fltsim entries correctly - weird.

Maybe a hidden page break, character, or encoding is being inserted in the aircraft.cfg - I can't find the issue with my text editor. Can you?
 

Attachments

Also of interest, if I copy the preceding livery section header [fltsim.36] and the preceding blank line, and the past that over the corrupt [fltsim.37] and [fltsim.38] headers, and manually renumber accordingly, the aformentioned utilities (ACA2007 and FSRenum) no longer complain about the livery sequencing.

There has to be some kind of hidden charater, or something, being installing by AIFP near the livery seciton headers or preceding whitespace. :confused:
 
I have just installed an aircraft using 2.1.24(d) and checked the resulting aircraft.cfg file with a hex editor. There are no hidden characters (nor are there intended to be).

I have no idea what ACA2007 or FSRenum do or look for. I did notice, however, that in your Capture 3, the [Fltsim.36] header immediately preceeding the [fltsim.0] section has an uppercase "F" while AIFP inserts [fltsim.x] using a lower case "F" (which is quite legal). Perhaps one or the other utility is "tripping over" the lower-case "F".

If you send me the apparently-erroneous aircraft.cfg file, I'll take another look.

In the meantime, have you tried testing whether or not Flightsim has a problem with the file?

Don
 
I haven't been able to replicate the issue using the latest AIG (New Years) round. Chalk it up to one of those days, I guess. :rolleyes:
 
In case anyone else comes across this thread later, it turns out Peter van der Veen's ACA2007-light utility had an issue with mixed capitialization of the 'F' in the [fltsim.x] header. I reported the issue some weeks ago and Peter posted a new version of ACA2007 Light (v1.0.6). http://aifs.pvdveen.net/

BTW Don, I just wanted to let you know, AIFP 2.1.24(q) has been working very well for me - I think it's the most solid version to date. Thanks again for such a great tool! :wave:
 
Last edited:
You must log in or register to reply here.
Back
Top