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

FS2004 FS Crash with AFLT Approach

tgibson

Resource contributor
Messages
11,338
Country
us-california
Hi Don,

Using the latest 4.5.3.5, but this happened with the previous version as well. This crash is occurring when the loading airport progress bar appears, at 0%.

I am using my usual classic KLAX AFLT file. When I place a Left Edge classic approach, FS crashes with the following:

Problem signature:
Problem Event Name: APPCRASH
Application Name: fs9.exe
Application Version: 9.1.0.40901
Application Timestamp: 4135a208
Fault Module Name: UxTheme.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdb3c
Exception Code: c0000005
Exception Offset: 00017b7b
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: a423
Additional Information 2: a4234bc6f3093e8702d9477387ccf1bc
Additional Information 3: 67a3
Additional Information 4: 67a3db63c599a188d07580a8adc15520

If I change it to a Funnel approach (for example), there is no crash and FS9 loads normally.

I then decided I better start from the beginning, so I loaded my usual KLAX BGL file into AFLT, as a new project. Without making any changes, I then compiled it. FS crashed with the following:

Problem signature:
Problem Event Name: APPCRASH
Application Name: fs9.exe
Application Version: 9.1.0.40901
Application Timestamp: 4135a208
Fault Module Name: G3D.DLL
Fault Module Version: 9.0.0.30612
Fault Module Timestamp: 3ee946b8
Exception Code: c0000005
Exception Offset: 000156b0
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

I then restarted FS and tried to load at KLAX again. This time FS9 hung with the following after ending it using the Task Manager:

Problem signature:
Problem Event Name: AppHangB1
Application Name: fs9.exe
Application Version: 9.1.0.40901
Application Timestamp: 4135a208
Hang Signature: 8544
Hang Type: 2048
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Hang Signature 1: 8544aa52f903e1c7766296900e9f20f6
Additional Hang Signature 2: bfea
Additional Hang Signature 3: bfeab575bd4cb2ba986e160900056927
Additional Hang Signature 4: 8544
Additional Hang Signature 5: 8544aa52f903e1c7766296900e9f20f6
Additional Hang Signature 6: bfea
Additional Hang Signature 7: bfeab575bd4cb2ba986e160900056927

KLAX BGL file attached.

I then went back to my old project and as long as Funnel is chosen, FS loads fine. With Left Edge, it crashes again.

Hope this helps,
 

Attachments

  • KLAX_ADE9_62.bgl
    64.4 KB · Views: 87

tgibson

Resource contributor
Messages
11,338
Country
us-california
Hi again,

Don't worry about this, I doubt anyone else uses FS2004. I can just use a previous version I have saved if I need anything for FS9.
 

gadgets

Resource contributor
Messages
9,388
Country
ca-britishcolumbia
We've had company for most of the past week. So haven't had a chance to investigate. It sounds like a data initialization issue. The error data you sent isn't meaningful to me, but it should be relatively easy to spot. I'll take a look AsAP
 
Top