Soulflight

DX11 works again. just a heads up :)

I have exactly the same issue with many complex aircraft. Do you use DX12?

581.42 breaks DX11 entirely for me. Ill try the next one once its released. my main problem is that under DX12 i get a lot more CPU load and therefore stuttering, the 5600x is simply not cut out for DX12, but runs DX11 quite fine.

I dont use it (anymore) since a few months already. In general all this flashy shiny gaming marketing stuff stays off my system. For settings there is profile inspector and thats it. ☺️ In general I wouldnt mind using DX12 but its more demanding and I have to reduce certain settings to be able to maintain good FPS. I have a 4060ti with 16GB VRAM and 32 GB system RAM and it gets completely eaten in DX12 in demanding scenery areas. I dont even know why RAM usage for displaying the same image is so much higher in DX12, but I suppose its because of worse optimization.

I just installed the most recent nvidia drivers 581.42 released 3 days ago, and now DX11 doesnt work anymore even with TAA and HAGS off. I guess thats the finger from nvidia regarding this issue. 😅 So, I need to install more system RAM now or ramp down settings compared to what worked well in DX11 to be able to fly smoothly. fml....

Yes, unfortunately. But it makes FS2020 work in DX11 again, dont ask me how. I guess thats a problem between nvidia and microsoft and not really solvable on our level.

Hence the "on my system" i cant claim its a general problem. But after prolonged usage my RAM usage fills up to insane levels ruining FPS usually on landing. With DX11 this doesnt happen to me.

post can be deleted by now.

Ok anyone experiencing crashes with DX11 and later nvidia drivers: turn off hardware accelerated GPU sheduling in windows. That did the trick for me, at least when you are using TAA, otherwise the sim crashes when loading into the flight from the map view. It pains me to say that but TAA combined with selecting a higher resolution (DSR) gives me superior image quality compared to anything that DLSS was doing. There is more contrast and sharpness in the image, better clouds and lights are actually shining at night. TAA seems to have come a long way in 2 years and shimmering issues at light poles etc. are greatly reduced by now. Downsides is that some addon airport terminal buildings are still excessively shimmering, which is due to the way they are designed. Also, frame generation doesnt work, obviously. But i dont use it anyways since its eating more VRAM and causes flickering. ill stick with DX11 and TAA for now.

I have exactly the same issue on DX11. DX12 has memory leak issues on my system, even though it runs well after startup.

So a few months ago I started using DX12 and swapped to DLSS4 using the swapper tool and the required nvidia inspector settings. After some usage time i found out that DX12 in MSFS has memory leak issues. I will attach a screenshot for anyone who doesnt believe me. This was after a longer flight in the FBW A380, i already use the downscaled textures for this aircraft which are available on flightsim.to. My system is mid-range-well equipped with RAM and VRAM, and it still manages to overload it completely after a few hours while FPS are fine when starting up the sim. But this is not the issue i am trying to get solved, its just the reason why I want to actually switch back to DX11 but I cant. MSFS in DX11 mode crashes after the initial loading when usually the main menu should be shown but instead i am getting a CTD. I dont know if this issue is related to DLSS4 or not. For safety I aleady switched back to default in the DLSS swapper utility with no change. Here is the corresponding error log from windows: Fehlerhafter Anwendungsname: FlightSimulator.exe, Version: 1.39.9.0, Zeitstempel: 0x00000000 Fehlerhafter Modulname: nvngx_dlssg.dll_unloaded, Version: 310.2.1.0, Zeitstempel: 0x67d089b2 Ausnahmecode: 0xc0000005 Fehleroffset: 0x00000000008976a0 Fehlerhafte Prozess-ID: 0x184C Fehlerhafte Anwendungsstartzeit: 0x1DC25BFC6761C99 Fehlerhafter Anwendungspfad: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Fehlerhafter Modulpfad: nvngx_dlssg.dll Berichts-ID: 1b6bf1d2-831c-4d6e-adee-5d331708647d Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe Fehlerhafte paketbezogene Anwendungs-ID: App It seems to be an nvidia driver issue. I found some reports of similar issues with latest nvidia drivers and nvidia releasing a hotfix, but on my system the problem still persists with the latest nvidia drivers 581.29. I already dumped the nvidia app from my system as some say this could cause issues and there is no benefit of having it if you use nvidia inspector. GPU is a 4060ti with 16GB VRAM on windows 11. Has anyone dug into that issue with more success than I did? UPDATE: it seems that the crash doesnt happen when Hardware Accelerated GPU Scheduling is turned off in windows settings. However, DLSS4 definitely doesnt work in DX11, since it crashes as soon as you try to load a flight. DX11 with TAA works, however.

Update: its freeware now 😁

The website has been taken down by Dan. Unfortunately no one could convince him to release the sourcecode and find new devs for it.

So I am running a 460ti 16GB on a 1440p Gsync monitor and for years I usually upscale any games, including MSFS, to 3413x1920 for a sharper image. However the latest driver update (done in a clean way with DDU etc.) seems to have broken my DSR capability. I activated DSR and selected resolutions in the nvidia control panel and the upscaled resolutions also show up in any games display options. However, selecting them changes nothing. Even when the games options are showing 1920, the screen noticeably is still running in 1440p. The only workaround is to upscale the whole desktop to 1920, but thats impractical as it makes the whole windows screen too small for working with it. Anyone has a clue what I missed? EDIT: of course windows 11 has a scaling option I first wasnt aware it existed lol. I dont know if thats really a solution or just a workaround though....

Thanks everyone. But I dont use FG at all, as even with good FPS it feels wobblish. Anyways, DX12 in 2020 runs fine now for me and give me amazing image quality with DLSS4. But for this, I had to reduce texture resolution in 2020 from "ultra" to "high", as DX12 mode eats up my 4060ti's 16GB of VRAM easily on ultra. On high, its -5GB VRAM usage and butter smooth even in the middle of big cities with traffic and addon airports. Someone on youtube also mentioned that DLSS4 is not compatible with DX11.

meanwhile a channel admin on youtube confirmed to me that DLSS 4 is not compatible with DX11. But i managed to get DX12 running fine. My bad i was reluctant to lower texture resolution from "ultra" to "high" before. I see no quality difference so far but -5GB VRAM usage. Remarkable that DX12 on with ultra texture resolution brought even my 16GB VRAM to its knees and caused my system RAM to be used in complex scenery areas. It even caused OOM crashes, hello FSX days. 😁

I activated DLSS4 on my 4060ti and it was all done correctly. The DLSSinfo method shows the latest version being used in MSFS too. But i have a stupid question: does DLSS4 now require using DX12 mode? If yes, thats a shame since DX12 doesnt run as well on my system. In areas with dense scenery and high quality aircraft, it is more laggy and has more stutters. For some reason it seems to utilize more system RAM on my rig, so in the past I prefered DX11. I am not using FG, as I dont like the taering effects, but I like the better image quality that DLSS4 delivers. The problem is that DX11 doesnt seem to work with it. After the installation launching MSFS in DX11 mode crashes it after loading the main menu/map. Any ideas?

Noob question: is it normal that enabling DLSS 4 in 2020 breaks DX11 mode? I am only able to use MSFS in DX12 now. Problem is that DX11 runs much smoother as with DX12 my VRAM fills up too much resulting in stutters in dense areas. I dont want to use FG, I just want to improve image quality with DLSS4.

Btw why do they still not allow this? Afaik this is what makes apps like ASFS basically a collection of improvised workarounds. Previously I thought Asobo didnt want to allow creation of a proper 3rd party weather system for MSFS because it could defeat marketing for MSFS 2024. Whats the reason for being so protective with the weather API? I am still on 2020 myself and i am happy with it. Especially since addon compatbility doesnt seem to be as guarranteed as announced. Minor issues with visuals in 2020 could be improved by mods/3rd party apps. The only reason for me to get 2024 would have been more accurate live weather and cloud types, including realistic TS/CB depiction, similar to the way it was done by ActiveSky on FSX/P3D. I decided to wait for reviews and I am glad to see i was right.

After several hours of gradually removing stuff from the community folder and subsequent testing i found out that it seems to have been caused by a navigraph AIRAC I had installed. Weird enough this causes such a crash but its gone when removed.

Got back from work today and did some checking. Updated nvidia driver the usual clean way without any changes. But I can get into safe mode! This is strange because I deactivated my addons already using the addon manager. But there are some which are installed by their own installers and are still present in the community folder. Is there anything else MSFS safe mode changes when activated, except for not loading addons inside the community folder?

memory issues were not really my suspicion as the system itself is very stable with anything except MSFS. Its just something i read that 0xc000005 points towards memory instability. But I just ran a full memtest, which took 4,5 hours and returned 0 errors, so nope...

I just got back from 2 weeks offline and tried to start MSFS, yesterday it worked fine, i downloaded the recent WU and mandatory update. Now I cannot get to the main menu anymore. Loading finishes and then MSFS crashes without any error. Event log shows this: Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.37.19.0, Zeitstempel: 0x00000000 Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.37.19.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000bee81e ID des fehlerhaften Prozesses: 0x0x3120 Startzeit der fehlerhaften Anwendung: 0x0x1DAF4A7B1461F4A Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Berichtskennung: 723bb2d6-1ccb-486d-956d-f02d071da89e Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App I used addon manager already to deactivate all addons, but even plain vanilla MSFS crashes the same way. sfc /scannow also didnt show any corrupted system files. Some threads I found about it online point towards memory timing problems but I didnt change anything recently. I use 2x16GB DDR4-3200 sticks and applied the corresponding preset in my BIOS setup. Other than that I didnt make any changes and didnt OC anything. So nice, you have one day off and you spend it downloading updates and then troubleshooting, fml. 😄

Cope and seethe. I said the symptoms seem to me like there is a memory leak, which, in my case, is most likely caused by SimFX filling up RAM. Since the solution is to not use SimFX at all, I dont see how you come to the conclusion there never was a memory leak either. Unfortunately I didnt do anything else so far anymore. I was away for 2 weeks now and since the recent updates my MSFS isnt launching at all. 😬 I read P42 released updates, so maybe ill give it another try and tell you about it.

Cope and seethe. I said the symptoms seem to me like there is a memory leak, which, in my case, is most likely caused by SimFX filling up RAM. Since the solution is to not use SimFX at all, I dont see how you come to the conclusion there never was a memory leak either. Unfortunately I didnt do anything else so far anymore. I was away for 2 weeks now and since the recent updates my MSFS isnt launching at all. 😬 I read P42 released updates, so maybe ill give it another try and tell you about it. For me it definitely was, as its gone after deactivating simfx. Every system and setup is different however.