alfred2704

Try to disable turbo mode in settings.cfg file, turbo_mode=0

@mbucchia could you explain which table is to be applied ? https://varjo.com/use-center/get-to-know-your-headset/getting-the-perfect-image-quality/ 4. Varjo Aero running a Varjo native application with foveated rendering (eye tracking calibrated) or 5. Varjo Aero running a Varjo native application in quad view mode Number 4 right? Thank you.

Found option 'peripheral_multiplier=1.25' Found option 'focus_multiplier=1.25' Found option 'turbo_mode=1' Found option 'no_eye_tracking=0' Peripheral resolution: 2740x2350 (multiplier: 1.250) Focus resolution 1500x1500 (multiplier: 1.250) Peripheral resolution: 2740x2350 (multiplier: 1.250) Focus resolution 1500x1500 (multiplier: 1.250) Creating swapchain with resolution: 2740x2350 Creating swapchain with resolution: 2740x2350 Creating swapchain with resolution: 1500x1500 Creating swapchain with resolution: 1500x1500 Still playable but at the limit

This what I see with 1.25 multiplier: 2023-03-19 16:38:18 +0100: Found option 'peripheral_multiplier=1' 2023-03-19 16:38:18 +0100: Found option 'focus_multiplier=1.25' 2023-03-19 16:38:18 +0100: Found option 'turbo_mode=1' 2023-03-19 16:38:18 +0100: Found option 'no_eye_tracking=0' 2023-03-19 16:38:18 +0100: Peripheral resolution: 2192x1880 (multiplier: 1.000) 2023-03-19 16:38:18 +0100: Focus resolution 1500x1500 (multiplier: 1.250) 2023-03-19 16:38:18 +0100: Peripheral resolution: 2192x1880 (multiplier: 1.000) 2023-03-19 16:38:18 +0100: Focus resolution 1500x1500 (multiplier: 1.250) 2023-03-19 16:38:22 +0100: Creating swapchain with resolution: 2192x1880 2023-03-19 16:38:22 +0100: Creating swapchain with resolution: 2192x1880 2023-03-19 16:38:22 +0100: Creating swapchain with resolution: 1500x1500 2023-03-19 16:38:22 +0100: Creating swapchain with resolution: 1500x1500 Ps. I also can reproduce double cursor for F-18.

I prefer visuals to FPS. Did some other test, setting focus_multiplier=1.25 which is 2740 just to get closer to what I had with toolkit 2800. The cost is 5-8 FPS but quality in the focused area improved. PS. did not change peripheral_multiplier so maybe reducing it a little could increase overall FPS.

Did some tests: Ka-50 III Gulf free flight, F-18 Syria free flight, F-14 SC Quals and improvements are there and you really can see them. With VB 39 I got 60-80 FPS and mostly smooth pic. Before in the same test scenarios my FPS were 50-65. Thank you @mbucchia.

I solved it by enabling E-cores in BIOS. If they are disabled MT version won't start.

NineLine, I just enabled E-Cores in BIOS and it solved the problem Intel CPU. So I think the bug is that the app is trying to access cores that are not available(disabled in BIOS) although informed by OS that this CPU type has X cores but available only cores= X - disabled.

No, it is not working. As I said it is the bug(access violation) that should be fixed by devs.dcs.20230312-093050.crashwindows_log.txtdcs.log

Could you check your DCS log and see if it is about an access violation? If so there is other discussion in this same MT bug forum.

OpenXR. We just have to wait till it is fixed by devs. Since this access violation is only for MT version(DCSThreadManager).

same here: C0000005 ACCESS_VIOLATION at 00007ffc3c7139b4 00:00000000

I get much more VRAM usage with SteamVR that's why I switched to OpenXR.

You should look for online shops with configurator functionality if you don't want to build it by yourself. In Spain we have: https://www.wipoid.com/configurar-pc/ https://www.ldlc.com/es-es/configurador-pc/ https://www.pccomponentes.com/configurador I'm sure there are some in your country also.

With Intel 13th gen I'd rather go with DDR5 at least 6400.