MSFS - origin airport

[gfxlover]

Hi,

I have a really strange problem with MSFS when using FCDU.exe (both 1.8.3 and 1.8.4.) and flying Asobo´s B747 or B787 (there may be more aircrafts with that problem). If I choose e.g. YBBN or YSSY as origin airport, FCDU states NFRO as origin and close itself as soon as I try to add destination airport to FCDU. I even tried to remove NFRO from cfg files, but it just stated another one, not the real origin airport I was in.

BUT If I choose e.g. EDDF as origin, everything is ok. OR If I am in nearly any other aircraft (e.g. INI A310), it works flawlessly everywhere.


Thank you

We all need FSCaptain in MSFS. I tried SLC and some others and no no no..FSCaptain is the way:)

Regards,
gfx

[peter]

Hello Gfx,

thanks for your kind words. Note that FSCaptain for MSFS is still in Alpha, so you have to expect some problems. However, I was unable to follow the procedure you describe: when the simulator is not running, FCDU.exe closes automatically. And when I am on the ground at YSSY, the FCDU automatically enters YSSY as origin, and I can enter YBBN as destination without issues. Can you explain exactly what sequence of actions you take?

Best regards,
Peter

[gfxlover]

WMKK airport
Asobo B747-8 (or B787-10)






When I try to add NZAA to destination, FCDU just disappear.

And the very same situation in INI A310.

[Travis]

We have not released FSCaptain for MSFS, so there is no real support available.

But....

If you would kindly ZIP and email me your /FSCaptain/Config/ folder, along with a recent ADMIN log file, plus an FCDU log file from one of your failed attempts, I will look to see where you may be going wrong.

I will respond in several days.

Best,

[peter]

OK, I followed exactly what GFX did and could reproduce the crash with the default 747-800. I then started with the Fenix A320 at WMKK and also entered NZAA in the FCDU, and it worked fine. Hence, the problem is somehow related to the specific airplane. Thanks for reporting this, we'll try to find the cause of it.

Peter

[Travis]

After a very long sim update, I can crash the FCDU just as easily as you two!

I will enjoy figuring out what's happening. (??)

Details to come, once I know something.

Needless to say, log files are not needed.

Best,

[Travis]

Found and fixed both problems - not knowing where the a/c launched at, and the annoying CTD.

The original airport database had a hard limit of 32000 airports.  I noticed my airports.cfg file has over 39000 airports.

I'll fiddle with this for a while, and once I make a dedicated MSFS build, I'll have a larger limit (perhaps 47K or some such).

Best,

[Travis]

It wasn't the aircraft themselves, rather the range of the aircraft.  B7x7 > A320.

Having a longer range means there was more "reading of airports," until eventually BOOM.

Until I can get a final fix out, you would have to cull some airports from your airports.cfg file that you normally wouldn't use.

If you're interested in trying this, let me know and I'll write up a few suggestions.

And I'll make a TODO to add such limits to a SceneryScanner ini file... for future usage.

Best,

[gfxlover]

I would never have imagined that reason:) So the easiest way is probably to make a backup of airports.cfg and just use those airports needed for my flight.

A blank line needs to be placed after last entry I suppose? Otherwise it won´t find that last airport.


Thank you very much:)

[Travis]

GFX,

When I read your initial post, I had no idea what might have happened! 

(And thank you warmly for your kind words there!!!)

When Peter indicated that I should be able to replicate the CTD... I did so and then looked at my log file and finally ran a "tracepoint test" that pointed me to where the crash happened.

It was Easy Peasy from there to suss out the problem....
------------

Now, as to the culling of your aircraft.cfg file, I have an idea for you that might keep you from having to update it on every flight....

First, I will assume that most of your flights are done in airliners, or at least in aircraft that would benefit from a "hard" runway.  If that's an incorrect assumption, ignore the rest of this message and let me know. 

But if I am correct, I would propose that you "filter" (or remove) all "soft" runways.  When I did this to my MSFS Standard airports.cfg file, I was able to immediately take my airports count from 39975 to 17427.

I used my spreadsheet to test this, so if you are confident in your spreadsheet usage, make a backup of your airports.cfg file and import it as CSV into your spreadsheet.  Then just go to Column F (the Column Name is "Hard") and remove all rows with "0".

There are lots of other possible "filters" that you can use if this isn't beneficial for you.  Just let me know and I'll offer up some other suggestions, such as "remove all airports with the Country of 'ABC.'"

If you would rather skip all that grunt work, you can email me your current airports.cfg file along with your preferred filters, and I would be happy to make the file for you.

Best,

[gfxlover]

It´s a great idea to remove all soft rwy airports. I can do it myself.

Thank you once again:)