Ratfink

I couldn't figure out how to stop it upgrading back to V76 after rolling back to V74 - do you know if there's a way to force it to stay at a certain version?

I upgraded the Qpro firmware to the latest V76 using the advice in this video and eye tracking restored - Thanks for sorting that, I don't see the newer version available but using adb sideload to force V76 into the headset has fixed it for now

Rolling Quest Link back to V74 as per the link I included restores eye tracking I've turned off auto updates, and will stick to V74 until forced to upgrade

Hi All First time flying with QPro in a few weeks and noticed quad view eye tracking not working. Long story short, it seems Meta is the issue with a new update that breaks eye tracking using Link (USB in my case) https://communityforums.atmeta.com/t5/Get-Help/Latest-Meta-Update-Breaks-eye-tracking-and-avatars-for-QUEST-PRO/m-p/1311837#M363318 Rolling back to V74 could be a slolution according to the link above, but I'm happy to sit tight for a fix Anyone else having this issue?

I'd like to see a decent AI WSO in F-15E and just to offer an objective opinion, Jester is well suited to the USN F-14 calling out bogey position, speed and alt, etc in the dogfight. George in the US Army AH-64 is a bit dull and needs more work. F-15E is USAF and don't see another AI compadre engine as an issue if it helps with immersion. I like Jester more than George, especially the banter and quips he makes, and would like similar in the Eagle. I've heard a 494th FS pilot say in regards crew co-ordination - "I row the boat, WSO shoots the ducks!" So any AI WSO would need to be fairly autonomous to allow the pilot to get the jet where it needs to be to allow the pointing of AG weapons and Jester may not allow for that.

I have the Quest Pro now (upgrade from Rift S and Quest 2), and think it's a great headset for DCS over link cable. I prefer to use the Quest hand controllers for clicking around the cockpit, but with DCS the right controller keeps disappearing and a message pops up from Quest saying controller cannot be tracked. A brief nudge, and it's back. Sometimes the right hand appears floating by right hand side of cockpit for no reason, which I thought may be as I have the Quest pro set to use hand tracking and it seems to match the physical position of my hand on the TM WH F-18 joystick I have. I have turned off hand tracking but it still does it. I have no other issues with the tracking of the controllers otherwise, this only happens in DCS

Yes, a bit of ripped post it note over the sensor is my solution I did notice DCS MT wouldn’t load unless the headset was active (on head prior to post it note solution) and have concluded the Open XR runtime must have the headset active to allow DCS to function, whereas using ST or forcing Oculus API using reg edit fix it’s fine. Sent from my iPhone using Tapatalk

According to https://registry.khronos.org/OpenXR/specs/1.0/man/html/XrResult.html Error code from my dcs.log XR_ERROR_SESSION_LOST The XrSession was lost. It will need to be destroyed and optionally recreated. How can the cause of the lost XrSession be determined? It's clearly linked to removal of the headset making the device sleep, but I can't find a way to stop that happening. It's happening 9/10 times, and is really quite frustrating as though it doesn't happen with native Oculus API on my system, OpenXR performance is much better for me. Enabling Turbo mode in OXR smooths out all the sticky/stutter menus at load time which I haven't found a solution for with OTT or any other setting. (Only an issue in MT) Hoping this can be fixed soon.

OK so DCS MT crash after remove/replace headset DOES NOT occur when forcing Oculus API by setting registry key Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1 ActiveRuntime="None" Ran DCS MT forced in Oculus Later confirmed using Oculus API not OpenXR 2023-05-03 17:35:25.405 ERROR VISUALIZER (Main): OpenXR exception: XrResult failure [XR_ERROR_RUNTIME_UNAVAILABLE] Origin: xrEnumerateInstanceExtensionProperties(nullptr, 0, &instanceExtensionCount, nullptr) Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:163 2023-05-03 17:35:25.536 INFO VISUALIZER (Main): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S So issue seems to be related to OpenXR crashing causing DCS to crash when remove/replace headset

Oculus app updated today to Oculus app version 53.0.0.105.132 (53.0.0.105.132) but DCS MT still crashes on pause (tested with F-18 free flight on Caucasus - flew for 20 secs or so, pause game, remove headset, wait 10 secs replace headset - hang then CTD) I opened the log from OpenXR Toolkit Companion, pasted below. Maybe I will try the registry hack to disable OpenXR and force Oculus API [OXRTK] 2023-05-03 17:43:06 +0100: OpenXR Toolkit - GA-2 (v1.2.4) [OXRTK] 2023-05-03 17:43:06 +0100: dllHome is "C:\Program Files\OpenXR-Toolkit" [OXRTK] 2023-05-03 17:43:06 +0100: OpenXR-Toolkit layer is active [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_D3D11_enable [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_D3D12_enable [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_opengl_enable [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_vulkan_enable [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_vulkan_enable2 [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_depth [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_win32_convert_performance_counter_time [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_convert_timespec_time [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_cube [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_cylinder [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_equirect [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_visibility_mask [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_color_scale_bias [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_EXT_win32_appcontainer_compatible [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_EXT_debug_utils [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_OCULUS_recenter_event [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_OCULUS_audio_device_guid [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_color_space [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_display_refresh_rate [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_META_performance_metrics [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_META_headset_id [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_OCULUS_ovrsession_handle [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_haptic_amplitude_envelope [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_haptic_pcm [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_touch_controller_pro [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_touch_controller_proximity [OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_OCULUS_external_camera [OXRTK] 2023-05-03 17:43:06 +0100: Application name: 'DCS World', Engine name: '' [OXRTK] 2023-05-03 17:43:06 +0100: Using OpenXR runtime Oculus 1.85.0 [OXRTK] 2023-05-03 17:43:06 +0100: Using OpenXR system Oculus Rift S [OXRTK] 2023-05-03 17:43:06 +0100: Overriding OpenXR resolution: 2250x2424 [OXRTK] 2023-05-03 17:43:06 +0100: Using OpenXR resolution (no upscaling): 2250x2424 [OXRTK] 2023-05-03 17:43:06 +0100: Using OpenXR resolution (no upscaling): 2250x2424 [OXRTK] 2023-05-03 17:43:09 +0100: Using Direct3D 11 on adapter: NVIDIA GeForce RTX 3080 [OXRTK] 2023-05-03 17:43:09 +0100: MipMap biasing for upscaling is: -0.000 [OXRTK] 2023-05-03 17:43:10 +0100: Open menu with CTRL+F2 [OXRTK] 2023-05-03 17:43:10 +0100: Creating swapchain with dimensions=2252x2424, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21 [OXRTK] 2023-05-03 17:43:10 +0100: Creating swapchain with dimensions=2252x2424, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21 [OXRTK] 2023-05-03 17:43:13 +0100: Projection calibration: -0.06915, 0.06993 | 0.06915, 0.06993 [OXRTK] 2023-05-03 17:43:19 +0100: Late initializeInterceptor() call [OXRTK] 2023-05-03 17:44:50 +0100: xrEndFrame: XrResult failure [XR_ERROR_SESSION_NOT_RUNNING] Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr) Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_NOVENDOR_toolkit\layer.cpp:3254 [OXRTK] 2023-05-03 17:45:34 +0100: D3D11Device destroyed [OXRTK] 2023-05-03 17:45:34 +0100: Session destroyed

I get this happen most times when I pause the flight, remove headset, wait a while, put headset back on in MT with Rift S. I don't recall this being an issue until now, and seems entirely repeatable. [Edit - does not occur in ST which uses Oculus API and not OpenXR] I can see the paused image, though mainly missing, and the spinning hour glass before it CTD Log attached. Guessing this is the crucial bit 2023-05-02 21:29:31.669 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST 2023-05-02 21:29:31.677 INFO EDCORE (Main): (dDispatcher)enterToState_:5 2023-05-02 21:29:31.678 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST 2023-05-02 21:29:31.684 WARNING LOG (10996): 1 duplicate message(s) skipped. 2023-05-02 21:29:31.684 INFO APP (Main): application shutdown dcs.log

Thanks Reflected, has this been changed by yourself for the newest release? It's not in the changelog. I noticed there's a base change too. Hopefully I can change that setting and run it because that mission is visually stunning and you Sir, deserve the equivalent of an Oscar for DCS cinematography with that

Hi All Last night (Tuesday) I paid for the N2.0 update and updated DCS OB to very latest DCS 2.8.4.39313 I ran Mission 3 again to marvel at the B-17s and the new N2.0 scenary. Now when I hit F2 for external views, I only see my own Spit each time I hit F2. It only happens in this campaign. Spit in N2.0 free flight, dogfight, etc F2 switches between all a/c in the map at the time. I'm not suggesting this is a campaign bug, but has anyone else experienced this? Just to add, with DCS OB MT version 2.8.4.38947 as per 2 weeks ago with original Normandy map, F2 in same mission switched between all a/c in the map and the B-17s looked stunning and had no noticable impact on my rigs performance with Rift S VR. Suffice to say, the campaign in MT runs smooth as butter for me whereas when I first ran it a year or so ago I needed to use F10 option to remove a/c and improve performance

Hi Baltic, I'm replaying this campaign and also suffered the missing tanker though I didn't check its activities like escanaer. The tanker wasn't on comms menu, but was showing on Tacan 33X at the same distance as the carrier, so I can only assume it's the same issue. Still a great campaign, and I know releases of DCS updates can cause issues you need to fix, but I can just skip it for now as I did complete the campaign once before without tech issues

Just to add, I have now enabled Turbo Mode in OpenXr and the strange stuttering and 'head following' and snapping of the view when moving head in MT is gone. I can still enable ASW using Ctrl+F3 and it's all fine. Though I found it's not needed as I'm hitting 80fps or near as now in most scenarios

Yes, just made my res settings in OXR toolkit and left OTT running but set to apply ASW 45Hz

I'm a Rift S user and here's what I've done with OpenXR Toolkit for MT. Sorry no screenshot. But I use the Apache Syria hot start as a benchmark and have it performing pretty decent in MT. I haven't tried forcing it to use Oculus API yet to see what effect that has, but in hangar menu with OpenXR it stutters and glitches like mad. If I look about, the image follows me (like VR is a monitor) then snaps to where it should be. Once in the pit, it's pretty decent

Thanks for the replies guys. In MT I have OpenXR res override at 2250x2600 or something like that (don't exactly recall 2nd number but 1st is 2250) and upscaling on 100% and sharpening 20% and it's very decent. Apache hot start Syria 50-70 fps and looking pretty sharp in the displays. MSAA off. BTW OTT is running but ss=1.0 and just applying a default 45hz asw which I'm overring with ctrl-1 and ctrl-3 for off/on Should add, that occasional stuttering especially in main loading hangar screen is a massive issue, flying is not as much. When it stutters, it's slide show. But in flight for most of the time, it's a smooth and pleasant experience. I think this is a known issue so not bothered. I've also noticed CPU0 is 100% and core temps are about 10 deg C up (HW Monitor shows nominal 55-60 deg in ST to 60-65 in MT) I'm interested to know this too, but don't want to wreck my ST

For those with Rift S, can anyone verify what I'm seeing in OPenXR with DCS-MT? As we know, MT uses OpenXR only - of which I have no experience as normally DCS-ST uses Oculus direct I have always used OTT to tweak my ASW=45Hz and SS=1.7 and have a decent experience and FPS on the whole. I have downloaded the OPenXR toolkit and left everything at default. WIth OTT running with SS=1.7 in MT my performance was terrible, CPU0 at 100% and fps around 20 for Apache Syria hot start IA mission. If it set SS=1.0 in OTT, performance is 60-80fps but looks terrible. SS=1.3 is 40-60fps and looks OK (but not as clear as Oculus API and SS=1.7). So my lack of experience with OpenXR is showing, but when I open the toolkit and allow to override resolution it has approx 1500x1300 per eye pixels (I am not on the DCS pc to get exact numbers) but around there. Where does OpenXR get these pixel numbers from? Rift S is 1280x1440 per eye, and I can't set this combination in the toolkit. I'm guessing the combination of OpenXR setting and OTT are causing issues on my system, but don't know what to set in OpenXR to get the same output as from Oculus API visually. Upscaling % setting seems to cause a random pixel from what I can tell, it makes no sense. Anyone with a Rift S and similar rig found this?

I have v50.0.0.165.257 and Rift S and not aware I had it

If MT wants to run with OpenXR for Oculus Rift S, should I be looking to OpenXR Toolkit for making optimisations to improve performance? As I'm only used to DCS using Oculus API directly, I have no experience with OpenXR

Yes, Rift S here. I notice lots of stutter and lag, CPU bound in FPS meter. Seems to be using OPenXR not native Oculus client, that seems to be the issue

I have a Rift S and see that line in dcs.log but with "VISUALIZER (Main): LAUNCH IN VR OpenXR: Oculus Rift S" for MT The loading hangar page stutters and lags like crazy. I do see better fps overall in flight, but with a lot of lag and "CPU bound (Main Thread)". CPU0 is running 100%, CPU1-7 high but not max

So with my setup, I'm seeing this bin-mt\DCS.exe - CPU0 = 100%, CPU1-7 60-70% DCS.exe - CPU0 = 60-70%, CPU1-7 60-70% both cases 3080 near max 12GB VRAM use, GPU 90+% stable bin-mt\DCS.exe stutters and lags Normal DCS.exe seems to be MT Closing DCS either case all CPUs go to idle WTF???

I'm seeing similar with no change to my settings with Rift S. No load screen, just black. I tried SP instant action AH64 Syria Hot Start mission and stuttering is far worse in MT than ST