• 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 closes with exeptional error on airport selection

Messages
198
Country
germany
Hi all,

I have a problem which comes out of nowhere.

yesterday FSX closes with an exeption error on my two airports EDJA and EDMT. I have no clue so far, what this is. I found out, that only my selfmade airports force FSX to quit with an error: FSX has to be closed. Please restart bla bla... no errornumber, nothing.

I tried this so far:
renewing the fsx.cfg -> no effect
recompiled all BGL's for both airports, meaning from ADX ->Airport.bgl no luck
and the libraryCreator from Arno -> no luck

That means that recompiling the source.xml into bgl didn't kill the error.
I haven't done anything which would explain, that FSX sends an error message. I shut down the computer, next day I started it to fly a boit around and EDJA was my start airport. After the loadingscreen I got the error imidiatly. Than i reset the fsx.cfg with flusifix and I got to the main menue. Than I have choosen EDJA and BANG...exceptional error, please close fsx and restart.... same with EDMT. So I guess it is something in the airport files....

Anyone any clue?!

Thanks in advance

Cheers, Demon
 
Have you run the Fault Finder in ADE? There are some errrors that it might catch that are not caught by the compiler
 
Hi Scruffyduck,

as i said, i haven't touched edja since a long time. So there actually can't be an error in the sceenery. Weird is, that only those two airports cause the crash. I still will try to run the fault finder. I just remember I did change the frequencies for edja. Could that be the fault?

Thanks for taking the time to help me with this.

Greets,

Demon
 
Perhaps you can post the bgl file causing to problem or email it to me - jon AT fsdeveloper.com - and we can take a look at it also. If it causes a crash here then that might tell us something.....
 
Many thanks scruffduck. I will send you the bgl on monday, since the files are on my other computer, which is in Munich. Thanks again

cheers,

Demon
 
Perhaps you can post the bgl file causing to problem or email it to me - jon AT fsdeveloper.com - and we can take a look at it also. If it causes a crash here then that might tell us something.....

Hi ScruffyDuck,

I ve just sent you an email with all files to look at. Thanks again for the kind offer!!

cheers,

Demon
 
Well I am not going to be much help. I loaded the bgl files that you sent me into FSX and the airport loaded fine. Now I do have the basic version of FSX without Accel or SP1/SP2 so it is possible that one of the updates is causing the problem. The only thing I noticed is that some of the objects do not seem to draw properly.
 
hmm, well could be that is sp2 causing the probs...isnt there a way to find out, at what statge the programm is causing the error? like : loading *.bgl -> error no such object found... just as an example

But thanks for trying...I need to find out, what else could has happened...

cheers,

Demon
 
hmm, well could be that is sp2 causing the probs...isnt there a way to find out, at what statge the programm is causing the error? like : loading *.bgl -> error no such object found... just as an example

But thanks for trying...I need to find out, what else could has happened...

cheers,

Demon

Well maybe someone else can take a look. I am updating my version of FSX on my development machine so maybe I will see this problem when I get everything installed
 
hi Jon,

I found out, that the error must be in the new EDMT file...I deletet that file out of the scenery.cfg, eversince my EDJA, what I sent to you, is working again...but if I also add EDMT, the new Airfield, EDJA strikes again...that makes me wonder, because those two airports should not be connected to eachother, should they?

cheers,

Demon
 
As it seems it was an orphant parkingslot in EDMT the new airstrip I made. Since I deleted that parking slot, all runs fine again. But how could that airstrip influence EDJA? Is it, because it reads all surrounding airstrips and airports, and as EDJA was selected in Main Menue from FSX, it automaticaly loaded the EDMT which is jsut around 16 miles away and gave that error? Is that possible?:eek:

thanks so far and cheers,

Demon
 
Hi,

for sure is that possible. I think when starting, FSX loads all scenery which is active in scenery.cfg and could be visible (up to a not known radius and maybe more) from the geografic starting point. So a ~16nm near visible scenery clearly can influence the behaviour of your starting in Memmingen.

I recommend you give your work in EDMT an extra (higher) entry in the scenery.cfg and put all new bgl files and textures in there.

If you have problems, de-activate the EDMT entry and you can see, if there is an isolated error which ever can happen while evaluation is in progress.

Normally none of the former actions should be done, because these can produce side-effects which make the search for the reason of CTDs more complicated.

Regards
Hans
 
Last edited by a moderator:
Hi again :)

I already sorted out the error. As i wrote, it was an orphant parking slot. Now fsx runs smooth again!!! But thanks a lot for taking the time to explain it to me in detail. Very interesting.

Cheers,
Demon
 
Last edited:
Back
Top