Jump to content

MT OB crash on launch


TAW_Impalor

Recommended Posts

Tried to test the new MT version. DCS did not launch, no error messages, just crash and dump files in the logs folder. Attached. 

Update: both VR and non-VR. I have HT and E-cores disabled...

dcs.20230310-154812.zip


Edited by TAW_Impalor

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Link to comment
Share on other sites

  • TAW_Impalor changed the title to MT OB crash on launch

Looks the same C0000005 ACCESS_VIOLATION error as this one:

 

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Link to comment
Share on other sites

21 hours ago, Flappie said:

@TAW_Impalor The files you attached are not complete. Please replicate the issue, then attach your dcs.log file.

I replicated and attached the log. It is indeed the C0000005 ACCESS_VIOLATION. Enabling HT did not help. I don't want to enable E-cores because I overclock all cores to 54 and it does not post with e-cores enabled (and I don't need them for anything else). I already get stable 90 FPS in VR, not sure if MT can make it any better. 

dcs.log

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Link to comment
Share on other sites

  • 2 weeks later...

One of the last updates fixed the crash. I see only two threads (Main and Rendering) at 100% with others much lower. DCS says "CPU bound". So not really sure why the advice is to have HT and E-cores on (mine are off). 

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...