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

Some FSX aircraft show, others don't

First off, AIFP is a great improvement over the FSX SDK traffic tool. After sorting through the problem of FS9 traffic.bgl's "poisoning" the FSX compiled files, Ive run into a problem I'm stumped by. I have created several working flightplans with some FSX default planes but others simply won't show up, no matter what. The ones that I have tried and can't get to "show" are the C-172, Maule, Goose and DC-3. Any ideas as to what would cause this?
 

gadgets

Resource contributor
Woodart, from the names, I assume these are default aircraft. If at some point you used an early version of AIFP to access these aircraft, you may have done some (easily correctable) damage to their aircraft.cfg files. Please see this thread. It contains a description of the problem, describes a manual fix and contains a link to a small utility I wrote to fix it.

Don
 
Hi Don, thanks for the speedy response. Yes, these are all default FSX planes. I took a look at the .cfg files of using Cygnus but found no anomalies at the beginning of any of the files. I also used your "BOM removal" utility with the same result. Is it possible that there is a problem with cruise speeds that could cause this? Thanks!
 
Last edited:

gadgets

Resource contributor
Possibly. Do other aircraft perform properly?

Please send me an example of the flight plan, airport and aircraft files that cause this. Please also include the compiled traffic file.

Incidentally, what version of
Don
 
Most aircraft work fine but I have encountered the problem with a few add-on craft as well but since they were old FS9 models, I thought it might be a FSX compatability issue. I just tried loading them ss user aricraft and they do appear in FSX. I'm using v1.3
 
Last edited:

gadgets

Resource contributor
Sorry woodart. All the files look fine as do the cruise speeds - both in the aircraft.cfg file and the aircraft.txt file. I assume the arrival times are realistic in the context of the distances involved and the cruise speeds.

Have you tried substituting in a given flight plan file an aircraft that works for one that doesn't. If the second aircraft shows up, it's almost certainly not the flightplan.

Since you've checked that it's not the BOM problem, at the moment I can't think of anything else it could be except something to do with the aircraft. Perhaps you could restore those aircraft and see if that makes a difference

If I do think of anything else, I'll let you know.

Don
 

gadgets

Resource contributor
Woodart, just had a thought.

Two of the airports involved in the flght plan file are add-ons. Have you checked that there's adequate parking - for both originating and departing flights?

Don
 
Top