• 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.

P3D v4 AIFP reads SODE files

Can anyone please explain how to get rid of this in AIFP? It started to happen after I updated SODE to the latest version.


  • aif1.JPG
    30.7 KB · Views: 120


Resource contributor
Andrew, AIFP attempts to read all sim.cfg and aircraft.cfg.

The SDK (since FSX) says aircraft and helicopters should use "aircraft.cfg" and other vehicles "sim.cfg". However, some time ago it was discovered that a few aircraft developers were using "sim.cfg". So that AIFP could cope (it seems users expect AIFP to adapt instead of having the other developers fix the underlying issue), I added "sim.cfg" to the search list. Consequently, I'm reluctant to now remove it.

So, in the next release, I'll try to avoid the exception you are experiencing (due to Flightsim being installed on the C: drive - I know, that's the default location). In the meantime, if you run AIFP as administrator, the message should not be issued.

Thanks Don, I'm good with using AIFP as Admin for now. My P3D is of course, never installed in the default location, but on a separate FS SSD.


Resource contributor
I misspoke in the previous post. It should have referred to SODE (not Flightsim) being installed on the C: drive.

Please download AIFP Development Release 3.2.15(t) from http://stuff4fs.com and confirm whether or not the exception message is still issued.

Yes, I let SODE install in the default path on the C disk actually. Tested the new AIFP version, all good, no more ned to run as admin. :)