solved MSFS 2024 crash when using A340-300

[ChristerH]

I have just purchased it for MSFS 2024 have crashed two times when going into outside views.

I dont have a bad system, I have a NVIDIA 3080 video card and have had no issues with any other airliners.

Is there something I can do or was this a misstake to purchase ?

Edited October 9 by ChristerH
Added graphic

[ChristerH]

SOLVED by reducing DLSS.

[sgb478]

I was using iniBuilds' first edition of the 340-300 with no issues.  Then, iniBuilds updated it, and my flights were over.  Every time I tried to fly the update, MSFS 2024 would crash at either the gate, the taxi way, the run way, or mid flight.

Then, I found your post, ChristerH, and my problem is solved!!!  Thank you.

Note to iniBuilds: After Version 2, I had to change all my graphics settings.  The only one that solved the CTD problem was this solution.

[richboy2307]

Hi,

That sounds like a potential driver or shader cache issue. I would recommend clearing your GPU Shader Cache if you haven't done so for a while. There are plenty of video guides online, such as this that can help. Use the appropriate method for your particular brand of GPU (AMD or Nvidia).

Thanks!

[ChristerH]

My problems did not completely end with this. When starting outside the aircraft a message still came up about my video card.

i ended up taking down my resolution from full 4K to 1440 and all issues were solved.

i think this plane really tax the GPU. Hopefully it will be optimized.

 

[ChristerH]

1 hour ago, richboy2307 said:

Hi,

That sounds like a potential driver or shader cache issue. I would recommend clearing your GPU Shader Cache if you haven't done so for a while. There are plenty of video guides online, such as this that can help. Use the appropriate method for your particular brand of GPU (AMD or Nvidia).

Thanks!

I will try this.

[richboy2307]

23 minutes ago, ChristerH said:

i think this plane really tax the GPU. Hopefully it will be optimized.

The aircraft is already highly optimized, so I'm not sure what else can be done to meet that expectation? For context we have testers using it across a spectrum of hardware, from mid-tier 20-series cards all the way up to the latest high-end 50-series, not to mention the same aircraft is available for use on Xbox.  So while we are open to suggestions, do note that no effort has been spared to optimize performance already - be it code or art side and the resultant product is the best that can be achieved based on current knowledge and sim conditions.

I'm sure you're aware but for the benefit of anyone else reading this - some things you should take into account:

Hardware: you do have to be mindful of your hardware in adjusting your sim settings, especially when running at high resolutions (like 4K) with many addons. Render Resolution, Texture Resolution, Object & Terrain LOD settings will have a huge impact on your experience. Especially when you set it at the edge of your hardware capability such that there is little headroom for the smallest overrun in certain conditions (e.g. larger amounts of ai traffic models spawned than anticipated).

For 4K at native render res with TAA, at High Texture Resolution, Terrain & Object LODs above 120, in excess of 16GB VRAM is recommended. Anything less, you should adjust accordingly.

Liveries or any texture modification packs:  The official liveries on the iniManager (or marketplace livery packs) are using the decal-painting method that allows for dynamic-scaling depending on your distance from the aircraft all the while keeping texture resolutions to a bare minimum (less than 2K even). By comparison, many 3rd Party Liveries still use the traditional method of painting on model textures directly, then exporting at extremely high resolutions (8K/4K) which will cause VRAM usage to spike unnaturally so you should take that into consideration.

This method is used throughout the aircraft texturing process, inside out, as well as strict adherence to node/bone limits on models, and extensive use of FS24 LODs system to achieve the performance this aircraft currently has.

Thanks!

[ChristerH]

Understood. I appreciate the explanation. I will address the cache and a clean driver install.

i have to say that with the settings I use now it’s a great experience.

keep up the good work.

 

ch

[sgb478]

Hi richboy2307!  Thank you so much for the explanation.  In my particular case, I had issues mirroring ChristerH's that began after the updates.

I bought the A340-300 that day it became available, and I actually downloaded it instead of streaming it.  I was enjoying the A340-300 tremendously.  Whether I was flying from KMDT to KCLT or KLAX to LIRF, the flights were unmatched.  Then, I upgraded to version 2 and have had issues since - autopilot not engaging, nose-dive crashes in rare instances where the autopilot did engage; CTDs mid-flight, autoland ignoring the ILS signal.  I wish I would get back to the original version.  

[richboy2307]

20 minutes ago, sgb478 said:

Then, I upgraded to version 2 and have had issues since - autopilot not engaging, nose-dive crashes in rare instances where the autopilot did engage; CTDs mid-flight, autoland ignoring the ILS signal.  I wish I would get back to the original version.

Hi @sgb478

That is very odd and not normal. Not seeing any widespread reports of any of the listed issues, nor have we seen that in our own testing. Additionally, there are no drastic changes implemented in the updates that would cause such a vastly different experience compared to release either. So something else has to be amiss here.

CTDs are very likely related to unstable GPU driver or corrupted shader caches if you're receiving DXGI_Hung errors shown above. For everything else it could be a result of bad update or cached files. Not all driver versions are created equally, and not all of them work stably across the spectrum of GPUs. Try the latest first, but it may not always be the best so try to google for last known "stable" version for your particular GPU. 

Can you also please try the following

• Close the sim and manually delete the A340 (fs24-inibuilds-aircraft-a340) from your Streamed Packages folder. When you relaunch the sim next, it will initiate a fresh download/streaming of the package.
  
  The paths will be as follows: 
  Steam: %APPDATA%\Microsoft Flight Simulator 2024\StreamedPackages\fs24-inibuilds-aircraft-a340
  MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\StreamedPackages\fs24-inibuilds-aircraft-a340
   
• Set Turbulence to LOW via Settings > Assistances menu.
  This is to avoid AP Disconnection due to exaggerated turbulence effect on CFD aircraft like the A340.
• Ensure control profiles have not reset during any sim update, and the correct ones are still applied to the A340.
• Increase your Rolling Cache size to atleast 2x your installed physical RAM (i.e. 32GB Rolling cache if you have 16GB RAM).
  This will flush the cache initially to rid of any out of date data, and also help ensure a smoother experience when dealing with streamed packages.
• Try conducting ILS approaches at different airports to rule out any airport specific issues. Again, there have been no changes implemented amongst the updates that would have any bearing on this part of the simulation, so it doesn't make much sense for it to stop working after an update due to anything in the update itself.
  
  If you still are having issues, please post a video along with detailed reproduction steps (airport, approach, variant, navdata method used, sceneries used) that would allow further investigation.

Thanks!