Crash in some modules with MSAA Off

[ripper253]

As per the title, I found that in OpenXR VR and MT, having MSAA set to off in certain modules (List so far is Mi-8, Mi-24, Ka-50 and AH-64) causes crashes upon loading their instant action missions, which is immediately fixed upon turning MSAA to 2x

in 2D and ST VR, they all work fine, so presumably something is up with the bitwise && going on with the MSAA setting as it's crashing with a depth buffer mismatch and a shadowmap function in the backtrace

System is a 5900X, 64gb, 6900XT running Windows 10 and a Pimax 5KS headset using PimaxXR 0.3.2, let me know if you need anything else!

dcs.log DxDiag.txt

[Flappie]

Hi. Maybe you've already solved your problem, but in case you haven't:

1. Try the MSAA x4 setting ingame and see if it DCS keeps crashing.
2. No crash? Then try MSAA x2.
3. No crash? Then try no MSAA again.

[ripper253]

I've "solved" the problem by just not using MT, so I've had to check, and yeah

4x, fine

2x, fine

Off, crash

Weirdly it seems to only be rotorcraft but it happens even if I just simply get near them in MP, so I've had many a sortie end by just buzzing an AH-64

Repair is ineffective

Having the MSAA overridden causes even weirder behaviour as setting it to 2x and overriding it to off in the driver allows it to run but causes visual artifacts

The bitwise and is seemingly still the issue, but in the intervening month I've just given up on MT as MSAA seems to take up more CPU frame time than I "get back" by switching to it, and "don't go near certain aircraft" isn't exactly a comfortable solution in MP scenarios, less so in SP

[Flappie]

Thanks for trying. Devs are still working on this issue by the way.

[Rapierarch]

On 4/23/2023 at 3:10 PM, ripper253 said:

I've "solved" the problem by just not using MT, so I've had to check, and yeah

4x, fine

2x, fine

Off, crash

Weirdly it seems to only be rotorcraft but it happens even if I just simply get near them in MP, so I've had many a sortie end by just buzzing an AH-64

Repair is ineffective

Having the MSAA overridden causes even weirder behaviour as setting it to 2x and overriding it to off in the driver allows it to run but causes visual artifacts

The bitwise and is seemingly still the issue, but in the intervening month I've just given up on MT as MSAA seems to take up more CPU frame time than I "get back" by switching to it, and "don't go near certain aircraft" isn't exactly a comfortable solution in MP scenarios, less so in SP

Hi, I had the same problem but when I put nvida DLSS dll in bin and bin-mt folders it stopped crashing when I turn off MSAA. (I use supersampling instead of MSAA)

I was doing a lot more things than that meantime so I'm not 100% sure if this solves it but would you mind trying it?

Just download latest dll from here https://www.techpowerup.com/download/nvidia-dlss-dll/ and paste it both in bin and bin-mt folders and tell us if this solves the problem.