solved MT OB crash on launch

[TAW_Impalor]

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 March 10, 2023 by TAW_Impalor

[Program_Apollo]

Try turning on your E-cores and HT. That's what worked for me and was able to launch it.

[wolkus]

Had the same issue.

Hyperthreading and E-cores were set to "Auto" in BIOS.

After setting Hyperthreading to Enabled and E-cores to 4 (max in my case) i was able to launch.

Thanks guys!

Edited March 11, 2023 by wolkus

[Flappie]

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

[Baldrick33]

Looks the same C0000005 ACCESS_VIOLATION error as this one:

 

[TAW_Impalor]

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

[Flappie]

Thanks. Oh, OK that's the shortest dcs.log file I has ever seen. It crashes from the very beginning.

[TAW_Impalor]

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). 

[Flappie]

Thanks for your feedback.

And I have no idea about CPU magic, sorry. I'm more of a software guy.