• 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 Crash to desktop

kevinmdavis2010

kevinmdavis2010

Messages
173
Country
unitedstates
Hey all,
I changed the compile path in ADE to FSX's Addon Scenery folder to make it load properly in my simulator. However, now my simulator crashes to the desktop immediately after I try to load one of the airports I made changes to along with the one I created from scratch. I experimented and loaded an airport that I didn't make changes to, and the crash didn't occur. Should I change the compile path in ADE? What's weird here is that the path I put it in is the only one that applies the changes to the simulator. All I really did was change the gate and parking spot names.
Please help!
Kevin Davis
 
It found three errors at KMKE. I didn't check the other three. Should I run the fault finder for all of the malfunctioned airports and paste the results here? Would "Orphan Parking" cause a CTD? I've never heard that term before.
Regards,
Kevin Davis
 
Orphan parking is the leading cause of CTDs.
No, you should run fault finder then fix the faults :eek:
 
I would go as far as to say that orphan parking is the leading cause of CTDs
 
Hi Chris and Jon,
Of the three errors Fault Finder found, one had to do with "Orphan Parking," and the other two had to do with "Orphan Taxi Links." Chris, when you say, "Fix the faults," do you mean to delete the affected parking spots and taxi links? I didn't even create a taxi link! Should I post the rest of the ad4 files for the other airports I've had problems with? As I mentioned on post #1 on this thread yesterday at 10:40, I loaded an airport in FSX that I didn't edit in ADE, and the error didn't occur. Would a screenshot of the errors listed help?
Regards,
Kevin Davis
 
If you remove the orphan parking spots can you load it in FSX? You can have orphan taxi links - they don't cause a compiler error and are sometimes deliberately used. The Fault Finder does not only identify fatal errors that will cause a CTD.

Sounds like you added the orphan parking which is the cause of the problem. Clear them first. Either delete them or attach them to the taxiway network. Then we can talk about other 'faults'
 
Hi Jon,
I deleted the orphan parking spots and taxi links, compiled the airport, and still had a CTD when I tried to load it in FSX.
Thanks,
Kevin Davis
 
Please attach the project file as it is now after you removed the orphans
 
kevinmdavis2010 said:
I changed the compile path in ADE to FSX's Addon Scenery folder to make it load properly in my simulator.
Click to expand...
Hi Kevin, which is the target of your compile path?
I tried for instance your KMMK_ADE_KD.ad4 and had no CTD. Yes, the parking indeed is "orphan" and two links are "orphan" but this can't cause the CTD. The orphans can not be used but cause no CTD! There must be an other issue.
Edit: I tried the other two too, there are noch changes, they look like stock airports! - and no CTD in my sim.
 
Last edited:
Flattermann said:
Hi Kevin, which is the target of your compile path?
I tried for instance your KMMK_ADE_KD.ad4 and had no CTD. Yes, the parking indeed is "orphan" and two links are "orphan" but this can't cause the CTD. The orphans can not be used but cause no CTD! There must be an other issue.
Edit: I tried the other two too, there are noch changes, they look like stock airports! - and no CTD in my sim.
Click to expand...
Hey Christian,
Thanks for looking! The path is: C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery. Is that what you mean by "Target?"
I also tried loading an aircraft at a nearby airport that I didn't edit - KMWC - which is 11.5 miles northwest of KMKE, and the crash occurred again. When I click Fly Now, and the loading bar appears, the Simulator immediately crashes to the desktop when it reaches 100%. Could it be an error with the locations in the Scenery Library in FSX? Out of curiosity, would the fact that the airports are stock ones have an impact if I edited them? The only one that wasn't a stock airport was WS03. I made that one from scratch. Hopefully this is an easy fix. The above path is not the default one that ADE uses - I manually adjusted it.
Regards,
Kevin Davis
Edit: If it helps, this is the Event Viewer report from the last time FSX crashed
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: g3d.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x000191ce
Faulting process id: 0x1e9c
Faulting application start time: 0x01d3f17bd9c92455
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\g3d.dll
Report Id: 5ddb1ae0-b2d9-48d2-91f3-a585856af8f7
Faulting package full name:
Faulting package-relative application ID:
 
Last edited:
Kevin

Load the problem file. Then go to Tools>File Priority Analyser. Run it and make sure that you don't have a rogue copy of your Airport project loading before your revised one.
 
Hi Kevin,
it is not so easy to answer,
First I am not a native English speaker so I used the word "target", perhaps it is wrong but you understand me;)
Normally the path over C:\Program Files (x86) is not the best one at least for FSX Gold, which I am using. Steam I doesn't know if it is the same problem caused by Win 10.
Better would be C:/FSX..... perhaps C:\Steam\steamapps\common\FSX\Addon Scenery\scenery I really don't know more accurate.

Quote: Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\g3d.dll.
This is a serious problem. The g3d.dll often makes difficulties. I myself had a problem with this file a week ago. I solved it but don't ask me how:rolleyes:
Sometimes it occurs at overload.

What addons have you in this region? In my case I suspected ORBX. I have some freeware airports there and some mesh and GP (groundpoly) problems.
Can you load FSX in other regions?

EDIT: I wrote before Jon's answer. Perhaps his way is better.
 
No problems loading for me either.
If it's a g3d.dll problem, I seem to remember that fsuipc by Pete Dowson is recommended.
 
You must log in or register to reply here.
Back
Top