CTD after take off, Fenix A319, KDCA

User Support Hub Crashes (CTDs)
,
1

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

Disabled custom KDCA scenery

Brief description of the issue:

Fenix A319 IAE, taking off from KDCA rw 19, at around 1140 feet AGL, sim stutters then CTDs.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Same CTD when using custom KDCA scenery
Start flight at gate, preflight, pushback, taxi, takeoff then CTD happens during initial climb around the time switching to CLB throttle setting.

Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):

AMD 7900XT with latest driver (24.20.01.02)

PC specs and peripheral set up:

Asus Prime X470 Pro, AMD 5800X3D, 64GB RAM; two monitors, VKB stick and throttle, rudders

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

1973702074511972283, type 5

Build Version # when you first started experiencing this issue:

1.37.19.0

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

2

Moved to Crashes (CTDs) given this report is specific to the 3rd party Fenix A319 :+1:

1 Like
3

Do you have the same issue if you follow the OP’s steps to reproduce it?

NO

Provide extra information to complete the original description of the issue:

I started the default Cessna 172 from a cold and dark state. Take-off from the default KDCA airport RWY 19 without a flight plan. I didn’t encounter any issues - the test went smoothly.

PC Specs and peripherals:

Windows 11 pro, MSI MAG X670E TOMAHAWK WIFI, Ryzen 7 8700x3D, ALF III 360, 32GB DDR5 tweaked, RTX 4090 driver ver. 560.81

  • VKB Gladiator NXT EVO Space Combat Edition joystick
  • Alpha Flight Controls XPC yoke
  • X56 throttle
  • Logitech rudder pedals
  • EFIS by Coreflight
  • MCP by Coreflight
    // SpadneXt was running in the backround.

If relevant, provide additional screenshots/video:

Screenshot (12)
Screenshot (12)1920Ă—1080 150 KB

Screenshot (13)
Screenshot (13)1920Ă—1080 121 KB

Screenshot (14)
Screenshot (14)1920Ă—1080 120 KB

Screenshot (16)
Screenshot (16)1920Ă—1080 119 KB

Screenshot (17)
Screenshot (17)1920Ă—1080 140 KB

Screenshot (19)
Screenshot (19)1920Ă—1080 155 KB

Edit
@iborg1979
Please test the game without any modifications or add-ons. To do this rename community folder to community_copy and create a new empty community folder. Then launch MSFS.
Select Cessna 172 Skyhawk aircraft and test the game without any add-ons.

FYI

The driver you currently have installed is a preview version. The latest stable release is driver version 24.10.29.01

4

Just tested as indicated: C172, empty community folder, nothing else running (no Couatl or FScrew, only TrackIR).
Took off from rw19, CTD’d at about 900’ flying runway heading.
Now, I’ll try the same after disabling photogrammetry.

5

Also, if you have your rolling cache enabled, disable or delete it.

6

Delete game cache.

1 Start your PC in safe mode

  • Click start
    1start
  • Click power icon
    image
  • Press and hold left SHIFT key and click restart
    image
  • Select Troubleshoot > advanced options > startup settings > restart
  • Select 4 - Enable safe mode

2 Click start and type

%localappdata%\D3DSCache

Press Enter
Delete all folders

3 Click start and type

%APPDATA%\..\LocalLow\Nvidia\PerDriverVersion\DXCache

Press enter
Delete all files

4 Go to
C:\Users\YourUserName\AppData\Local\AMD

In safe mode delete

  • OglCache
  • DxCache
  • DX9Cache
  • DxcCache

5 type

%localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes

Delete all files

Restart PC

6 Click “start” and type storage settings - press enter
7 Click temporary files > scroll down > check box DirectX Shader Cache
8 scroll up > click Remove Files

9 Restart PC.

10 Launch MSFS. Delete and turn off rolling cache.

Source https://forums.flightsimulator.com/t/stutterfest-with-world-update-17/650355/3?u=tenpatrol

7

2nd run: this time booted MSFS in “secure” mode, PG disabled, rolling cache off and deleted: no CTD.
Landed, re-enabled PG, took off again: no CTD.
Next, rebooting MSFS in “normal” mode, PG on, rolling cache off.

8

Test 3 : MSFS started in normal mode, PG on, rolling cache off: no CTD.
Beginning to suspect it might have been a rolling cache issue…
I’ll start MSFS again in “full” config, keep the cache disabled, and see how it goes.

1 Like
9

Well, I’m pleased to report that the steps advised did work. I was able to resume flying the A319 out of KDCA.
Must have been the cache.

3 Likes
10

Great ! Happy flights :slight_smile:

1 Like
11

Fly safe capt!

1 Like