Bmyers

It happened again. Track file below. I think this one was triggered by decreasing the HSI range but the bug didn't happen right away so hard to tell. That's 2 for 3 games. https://www.dropbox.com/scl/fi/so03vuokec7poz5uhucfq/TNN_release-2.0.66-20231101-180509.trk?rlkey=5xwq4t0mmgnvx8qn6lumqkxb1&dl=0

@Flappie Hi, After watching my replay of the event I found new information and re-wrote the original post. I made a youtube video of the event and added the track file too (both in original post).

(Re-written after reviewing replay) TACAN can stop updating. DME and bearing to the station stops updating. Station position on the HSI becomes inaccurate (it still moves around when you turn but it's no longer correct). It seems this can happen when not interacting with the HSI. If you watch the video below you will see me flying towards the CV and the HUD counting down the DME until it hits 12.3 and stays there. I was just looking around when this happened. It happened again in some minutes later into the flight when I decreased the HSI range from 20 to 5 when at 9 DME, putting the CV outside of the HSI's range. You can see both of these in this video: https://www.youtube.com/watch?v=MA66pKHLJvw Drop box link to the trackfile: https://www.dropbox.com/scl/fi/pxiln9k6ejotp3ftqizs2/TNN_release-2.0.66-20231028-203150.trk?rlkey=mww4m7rhbit8asj4br3dbv67l&dl=0 You'll have to FF a lot to get past all the boom booms =( Once you realize there is a problem you can reset the HSI by changing stations and then returning, or by toggling the TACAN Off/On. Easy but it's a bit more painful because you may have contacted the carrier, gotten the BRC, entered it into the CRS line then losing all that when you toggle the TACAN settings. Not to mention the time wasted figuring out there was a problem in the first place and flying an embarrassing long time in the wrong direction (like I did lol). Here is a list of actions for reference that are also chapters in the video 00:11 TACAN on to settings set before takeoff. Seems to be working 00:50 CRS line set 01:02 HSI dropped from 40 to 20 while Carrier 23.1 DME (still works) 02:30 Notice hud DME goes to 12.3 GWA and stops. 02:47 Notice HSI station also frozen at 12.3 DME. 03:25 HSI dropped from 20 to 5 while still frozen. No change to DME or station position even though it's no longer in front of me. 04:47 More TACAN settings changes to no effect. 05:36 I'm starting to realize there is a problem 06:00 Double checking TACAN settings 07:13 I finally change TACAN station to a random number and back again fixing it. 07:34 I change HSI from 20 to 5 while at 9 DME which immediately breaks it 09:25 I toggle the TCN button on the HSI. Does not fix it. 09:29 I turn TACAN off and ON. This fixes it.

@Glide Nailed it. Man that is the bomb... it's like a whole new DCS. two shortcuts so I can choose VR or not OpenXR with WMR OpenXR tools set to 75% custom render scale and latest OpenXR runtime preview OpenXR toolkit enabled for DCS, set to 90% FOV (any more and I'm tunneling.), World Scale set to 100% to match my narrow ass IPD. No studdering anywhere. Much higher performance. OpenXR added maybe 10%, this probably added another 10%. I saw 55 to 60 fps when I'm used to 35 and it looks fantastic. I wonder if it can help out my Leapmotion performance too... I'll have to look into that.

@Glide @Botik85 @Baldrick33 Hi all, thanks for your inputs. I'm pretty sure this is a SteamVR problem on my system. I uninstalled it and an app I didn't know I had called "Windows Mixed Reality for SteamVR". Maybe I was accidentally using this instead of the usual WMR which was causing the SteamVR persistence? Now DCS launches into VR with WMR running in the background. Is this what I should expect with OpenXR? Or am I still in a composite mode? I did find I had to set force OpenXR for it to work. DCS's performance seems to have gone up.. lots of studdering when there is a window open like in the MiG hangar, or in flight with the briefing open, but it's smoother while flying which is great. I think I'm getting some more frames too. After quitting DCS I reinstalled SteamVR. It cannot detect the headset at all. That's a bit of a bummer but fine for now since I'm not actively using any of it's SteamVR apps at the moment.

@Baldrick33 Here is one from just now with just --force_OpenXR. Thanks for spending your time on this! I see a device unplug at the bottom. That is probably where SteamVR intercepts it. @Botik85 OpenXR set to WMR runtime -check Enable VR in game -check (which is how I've been using it with SteamVR for several months) Can start DCS without parameters. -I can only do that if SteamVR has OpenXR runtime. It will fail just like the other scenarios I tried in my original post if WMR has OpenXR runtime. dcs.log

Hi all, I would really like to get openXR going with my HP Reverb 2. After following all the directions on this thread all I get is the DCS loading screen, then SteamVR kicks in leaving me with nothing. DCS just sits there with no screen, or DCS actually loads with WMR but then Steam VR takes over and DCS quits. I'm using the MT version of DCS (and I've double and triple checked that my shortcut goes to the MT version). I've set Windows MR to be the OpenXR runtime. I've tried each of the two force commands --force_enable_VR --force_OpenXR singly, and together in my shortcut after the shortcut path, just like the instructions. Changing these is what causes the two possible failure modes described up top. With only the force OpenXR, or force both of them, I end up with SteamVR loading and DCS with no screen at all. With only the force enable VR I get DCS loading and see it in VR briefly before SteamVR takes over and DCS quits. I have OpenXR Explorer and OpenXR Toolkit on my system. Explorer does report that WMR is the OpenXR runtime. I am not using the steam version of DCS. I bought DCS directly from ED Any ideas on other things I should look at? thanks Bryan

Hi, When using 2.8 Open Beta with Windows Mixed Reality set to be the active OpenXR runtime (via the OpenXR Tools for Windows Mixed Reality app) I'm getting grey flashes every few seconds in one or the other eyepieces of my HP Reverb G2. It's a bit disorientating so I didn't try to fly with it but it happens right in the app's pre-flight screen. (not sure what you call it... the MIG-29 hangar with the DCS windows up). With SteamVR set to OpenXR Runtime the grey flashes don't appear. I'm on Windows 11.. not sure what other info is helpful. Msg back and I'll help with whatever you need. I could probably also record an eyepiece with my phone so you can see it. thanks