dburne

No of course not, my discussion was on using hyper threading or not, nothing to do with overclocking. Historically flight sims were not known for making any use of hyper threading so it was common practice to disable that in the PC Bios. This new Multi Threading by DCS changes that line of thinking now. You want more threads to make better use of hyper threading, at least up to 32 threads at which point DCS does not recommend more.

Just an observation on my part that might be helpful for some. I had previously tuned my system overclock to run at 5.1 GHz on 8 cores with no Hyper Threading. This allows for a little less vcore voltage and cooler core temps. Today after installing the patch I went in and enabled Hyper Threading to get that advantage from MT, and my system froze during first couple of flights. Then it dawned on me how I had reduced the voltage , so I went in and increased the vcore slightly and all is well again. And well worth it for this Multi Threading now.

I would also add this tidbit of info in case it helps some others. I have always ran my i9 9900k @ 5.1 GHz with HT disabled cause I really did not need it. Well let me tell ya for Multi Threading you want that enabled,so now I am running 8 cores/16 threads instead of just 8 cores. And it made a signicant difference in my performance. ED stated you don't really want more than 32 threads for MT. But if like me and you have less check and make sure your Hyper Threading is enabled in the bios.

Today's update with MT is absolutely incredible, spent most of the day flying and loving my new found performance in my Varjo Aero. Well done ED!

Spent much of the day today flying campaign in the Spit on Normandy Map, holy cow I am so pleased with the performance I am getting with my Aero in VR now. MT today along with native Open XR support we got on last update are both a big win, especially MT!! Great job ED!! Thank you so much also for still considering VR players in the equations as well!

LOL ain't that the truth, just glad I got mine sorted this morning before the big update drop.

Ok enabled HT and yes saw some slight improvement versus not having it enabled. Reckon though I am going to need a new mb/cpu. Trying to hold off till after first of year 2024. The DCS FPS screen shows I am CPU bound on main thread, both with HT off ( 8 cores) and with HT On ( 16 threads).

Same here. I saw some slight improvement with my i9 9900k at 5.1 GHz all cores (no HT). Runningn in VR with Open XR. Going to enable HT now and see if I see a perceivable difference.

Servers must be very busy. Trying to launch the game and just keep getting login attempting screen...

I am currently downloading but it has slowed to a crawl, not even 50% there yet.

Yes this.

Getting it now - really anxious for MT and how it does in VR for me.

Wohoo!

Yeah now that would be nice!

Ok finally got it - whew!!! Uninstalled OXRTK followed by deleting the Open XR Toolkit reg entry, has now gotten the Toolkit back working for me. At least now I know I will have to delete the reg entry if it happens again so much thanks!! I have absolutely zero idea what I might could have done that caused this issue to start with.

Ugh guess I am going to have to uninstall and try and delete the reg entry. Amazing how deep this thing buries itself in one's system, it has me absolutely pulling my hair out. No idea why it worked fine for about 3 days then blammo with no easy way to get it back.

Nuke option worked in safe mode - however when I take it out of safe mode I am right back to it crashing when launching DCS.

Nope slow repair did not help. Time to try nuke option I think.

Ok much thanks, will have a look when this slow DCS repair gets finished. I am not very hopeful the slow repair will help.

Tried an uninstall ( including appdata folder) and reinstall of Open XR Toolkit , still same issue. With Toolkit active DCS always crashes. Ok will give that a whirl, thanks.

Ok thanks - I ran a standard repair, think I should try slow repair? Even though it works fine without the toolkit active?

Yes, version 1.2.4. I re-enabled toolkit and got the crash again. Here are the contents of the OXRTK log file after this attempt to launch DCS: [OXRTK] 2023-03-10 06:55:48 -0500: OpenXR Toolkit - GA-2 (v1.2.4) [OXRTK] 2023-03-10 06:55:48 -0500: dllHome is "C:\Program Files\OpenXR-Toolkit" [OXRTK] 2023-03-10 06:55:48 -0500: OpenXR-Toolkit layer is active [OXRTK] 2023-03-10 06:55:48 -0500: Using layer: XR_APILAYER_FREDEMMOTT_OpenKneeboard [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_D3D11_enable [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_D3D12_enable [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_opengl_enable [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_win32_convert_performance_counter_time [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_composition_layer_depth [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_EXT_eye_gaze_interaction [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_VARJO_composition_layer_depth_test [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_VARJO_environment_depth_estimation [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_EXT_debug_utils [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_EXT_win32_appcontainer_compatible [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_VARJO_foveated_rendering [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_visibility_mask [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_EXT_hand_tracking [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_VARJO_marker_tracking [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_HTCX_vive_tracker_interaction [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_VARJO_view_offset [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_vulkan_enable [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_vulkan_enable2 [OXRTK] 2023-03-10 06:55:48 -0500: Runtime supports extension: XR_KHR_swapchain_usage_input_attachment_bit [OXRTK] 2023-03-10 06:55:49 -0500: Application name: 'DCS World', Engine name: '' [OXRTK] 2023-03-10 06:55:49 -0500: Using OpenXR runtime Varjo OpenXR Runtime 3.9.0 [OXRTK] 2023-03-10 06:55:49 -0500: Using OpenXR system AERO [OXRTK] 2023-03-10 06:55:49 -0500: Overriding OpenXR resolution: 3240x2777 [OXRTK] 2023-03-10 06:55:49 -0500: Using OpenXR resolution (no upscaling): 3240x2777 [OXRTK] 2023-03-10 06:55:49 -0500: Using OpenXR resolution (no upscaling): 3240x2777 [OXRTK] 2023-03-10 06:55:50 -0500: Using Direct3D 11 on adapter: NVIDIA GeForce RTX 4090 [OXRTK] 2023-03-10 06:55:50 -0500: Early initializeInterceptor() call [OXRTK] 2023-03-10 06:55:51 -0500: Open menu with Down [OXRTK] 2023-03-10 06:55:51 -0500: Creating swapchain with dimensions=3140x2780, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21 [OXRTK] 2023-03-10 06:55:51 -0500: Creating swapchain with dimensions=3140x2780, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21

Ok I disabled Open XR Toolkit with the Open XR Companion App , DCS launched in Open XR this time with no issues. Apparently with using the Open XR Toolkit it is causing DCS to crash for some reason. I am using version 1.2.4 of the app.

Yes, all seems normal with it.

Ok so deleted the log file and tried again, same result DCS crashes. Log file: InstanceExtensionsWrapper.log