daddio007

Sorry to post continuously but I have an update. I rolled Varjo Base back to the previous 3.9.0.10 version and DCS build 2.8.7.42583 works fine in VR. I then upgraded back to the latest Varjo Base of 3.10.1.14 and it hung and had the message in the log: ERROR VISUALIZER (Main): OpenXR exception: runtime is not available Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:322 Subsequent attempts to load DCS defaulted to 2d with the same message, as before. Rolled back again to Varjo Base 3.9.0.10 and 3d works again. Loaded consistently at least 6 times. At least on my system, the incompatibility is between the latest builds of DCS and Varjo Base. Older build of either will work with the newer of the other (DCS 2.8.6.41066 works with Varjo Base 3.10.1.14 but DCS 2.8.7.42583 only works with Varjo Base 3.9.0.10 (or earlier presumably). If anyone else having the issue wants to try this please let me know if it works or not and I will update the ticket I have open with ED and Varjo. Thanks!

@dburne Hi! I believe you stated somewhere that you are not having any issues with the latest DCS OB build and the Aero in VR correct? I have a ticket open with ED and mentioned that some folks were running fine and they asked if I could compare settings with those not having an issue. If you don't mind, can you tell me what video card you are running and if a 4090 what driver version? I've tried several, currently on 536.67. Also I'm presuming you are on the latest Varjo Base and firmware (3.10.1.14 & 0.17.0.486)? Are you running Varjo Foveated 0.2.0 or OXR toolkit etc? Finally, presuming you are DCS MT, and starting with --force_enable_VR --force_OpenXR and or VR checked in settings? Appreciate any answers you can provide! Thanks!

Yeah that was me. Just opened a new one for the latest build. Still doesn't work though it did just once a few minutes ago when I deleted the saved game folder in users. That only worked once though. Just weird. It's possibly some kind of buffer issue based on the info that Matthieu B gave me back when I was troubleshooting the last build. Really frustrating. To open a ticket, go to the main site under support. Make sure you are logged in. Trouble tickets (digitalcombatsimulator.com)

Unfortunately, checking the "Enable Virtual Reality Headset" option in VR does not fix it for me. @BIGNEWYI had Ticket # 141742 but it was auto closed since the devs were on break and no one has responded to it in several weeks. The log is in that ticket if you can get someone to address it. Happy to play tester if you don't have an Aero on the team. I had to roll back to 2.8.6.41066. That fortunately still works. Thanks for the suggestion though! Glad it works for you!

Also working with Matthieu on this and the error I get in dcs.log is: 2023-06-27 01:56:40.764 ERROR VISUALIZER (Main): OpenXR exception: runtime is not available Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:322 MSFS2020 works fine. Previous 41066 build works just fine consistently (rolled back 4 times so far during testing). 41363 build fails consistently with the above error. Appears that some have this error inconsistently out on Varjo Discord. We ran OpenXR debug and Fred Demotts OpenXR Tracing tool. From what we can tell it is not even trying to load OpenXR on my system at all. I opened a support ticket. I would love to know what and where that source path is. I have yet to find it.

Same issue here. The latest update has broken VR in Varjo Open XR.

Hey guys! I have had pretty good success following this guide but there are places in some of the maps that cause some serious interrupts. One of these is over Guam so this post caught my eye. This is what I get over certain parts of Guam: It's enough that sometimes Steam VR will crash with this in the Steam vr logs: Closing pipe VR_ServerPipe_5704 because it was broken from the other end Any ideas troubleshooting this? I've seem everything from rolling back drivers to disable motion repro to re-install Steam. Mostly it is fine and there are places where I'm running at 90fps with under 10ms frametimes on GPU and CPU. But certain places where there might be a lot of certain objects it nose dives in a hurry! Core I9-9900KF, 32 gb ram, NVM drives, RTX 3090, almost same specs as SOH except still W10. Thanks in advance for any suggestions!

Hey Speed! Once again thanks for testing and posting all this. I'm trying to follow along and it's been about a month so just catching up on all the changes. After reading through the main post just now I wasn't sure if you were sticking with your Clear Water shaders or going to the Simplex 2.0. Also are you using Reshade or this new Open-VR FSR thing? EDIT* Scratch that last question... just read back a bit farther to see that you are not using Reshade. I have been using it lately with Steam SS down to around 50%. I'll give this new FSR thingy a go! Thanks! Daddio

Speaking of Steam VR API, I sent you a PM which you can ignore as I started using the updater and finally FINALLY got Oculus to stop loading with DCS! I'd still like to know what switches you throw to default it to the Steam VR API but so long as Oculus does not run unless I tell it to I am happy! Thanks for this SkateZilla! Daddio007

Thanks again guys! Yes RE: export.lua I was (am I guess) a Helios user in 2D so all that got pulled out and there is no export.lua currently. I'll continue to run down these others. Appreciate the help!

First off, thanks to Kegetys and Speed, and everyone else helping to make this mod work. It is a difference maker for me. That said, I still have places where my CPU Frametime just tanks and I am trying to learn why. Can anyone tell me what drives CPU Frametime the most? Is it number of objects like planes? As an example, in Instant Action/FA18/Nevada/Ready on the Ramp as I enter the cockpit my GPU & CPU Frametimes are around 10ms. As I look to the left where all the planes are on the tarmac, the CPU frametime jumps to around 25ms and solid red. Look back to right, goes back to around 10ms. Likewise in the air as I fly over that area CPU just blows up for a few seconds. Of course when that happens the actual framerate goes to around 23 and we get the typical ghosting and stuttering etc... I pretty much use Speed's settings for my machine (i9-9900k at 5.0GHz/Aorus z390/32GB RAM/m.2SSD/EVGA FTW3 Ultra 2080ti hybrid) with an Index and it all works pretty well (mostly 45fps) except these weird CPU Frametime spikes. I've got Process Lasso going with hyperthreading disabled on DCS, this mod, I've reduced most every setting and this one spot (and quite a few others in various missions) always blow up. Is it just me or is it just that spot/mission? Thanks and happy flying!

Also getting this on Free Flight for the Hornet in Persian Gulf. Seems to be since the last update.

Found the issue... all due to duplicates in the bindings. For every button press or release there were 2 of the same actions. Not sure how I managed to get them in there twice but redoing the profile from the original worked. Single action for each binding now and everything so far works the way it should. I still had to manually change the Monitor # in the HPF file but that was easy enough. Of note, with the single binding only half as many Monitor 1 entries in the file to change! Should have been my 1st clue... hey I'm learning! Thanks again for creating this profile. I'm excited to start learning how to fly a Harrier! Merry Christmas and Happy Holidays! :thumbup:

My report on this profile... I managed to get the new AV8BNAv3 profile mostly working by editing the HPF file in Notepad++ and manually replacing "Monitor 1" with "Monitor 2" for my setup (2 monitor top/bottom). Prior to that both monitors showed up as "Monitor 1" in the profile and nothing worked after Resetting Monitors and doing the setup in the interface. Everything appears to work now except the MFCD and UFC Function Mode and keypad keys wont "latch" for lack of a better term. They will work only while you hold them down then revert to the previous state when you let them go. Most other switches and knobs seem ok but the weapon quantity and fuzing switches are not incrementing the same as their in cockpit counterparts. That's my report thus far. If anyone has an idea how to fix those switches please let me know. I'm stumbling around in the dark on this stuff! Love it though! Thanks for doing this profile!

Hi Capt Z, Does the SU27/33 profile still work with the latest 2.5 release and Helios 1.4? I am trying to get it running and dont seem to be exporting from what I can tell. I am using the 20-Jan-16 export.lua but no gauges are moving. I can change HUD/Radar modes by pressing the NAV/BVR buttons on the profile so some stuff is sending but nothing seems to be coming back. I checked the hpf file and have the correct monitor (monitor 2, I only have two) selected. I'm kinda stumped. Any ideas? BTW, I have almost all of your other profiles working and absolutely love them. Thank you so much for what you do. Thanks again!:thumbup: