peachmonkey

hi, all, I'm not sure if I'm doing something wrong or there's a bug. The instrument lights stop working after the a CB breaker "COMPASS LT" is reset (see picture). 1) I turn the #9 instrument light rheostat to the max 2) the COMPASS LT breaker pops. The oil temp gauge goes to 0. 3) I push the breaker back in. The oil temp gauge shows the proper temp reading. 4) instrument lights never illuminate after that... Anyone experiences the same behavior?

@Supmua thank you for doing all the testing! I'm running VB at Medium (33ppd) and my experience is very pleasant on my system. Heck, the DCS VR is so much better that I haven't played IL2 for about a week now, and have no interest in going back to it either... Vsync On = definitely need to maintain 90fps to get rid of the ghosting, but even with it's being Off the smoothness is still very much pleasant compared to openVR. OpenXR with SteamVr = if you figure it out that'd be awesome. In my tests as soon as you disable OpenVR in VarjoBase the SteamVR stops seeing the headset altogether....

1) yup, running it through steamVR framework, however it's using OpenXR renderer instead. For that OpenVR must be disabled in Varjo Base, however the --forceSteamVR makes sure the HMD tracking works through it. It's similar to opencomposite hack that was done for Oculus devices... 2) unfortunately, Reshade 5 won't work with OpenXR. If you want to get that additional color saturation + sharpening you must use the OpenXR Toolkit. Just download the latest v1.0.4 and install it, there's no need to replace DLL's anymore, it's working out of the box. https://mbucchia.github.io/OpenXR-Toolkit/ FFR doesn't really work with DCS in this toolkit version, or if it works it's very wonky, I wouldn't turn it on at all.

the 'mod' portion is replacement of the "openvr_api.dll" that DCS comes with another version (from the opencompositeACC) that performs the intercept of the OpenVR calls and sends it to the openXR framework of Varjo Base. The next DCS update will overwrite the openvr_api.dll so that file needs to be replaced/update after every DCS update. So, technically, you're running DCS using the native's Varjo XR framework, just hacked thru the openvr pipeline. edit: I'll stop replying here as to not highjack the thread.

Remember you were using OpenComposite to replace Oculus's runtime? It's exactly like that. It's not a DCS mod. It's a "replacement of the SteamVR" mod. You're missing out on smoothness. There are no spikes in frame times so the overall performance is very very smooth.

try it with the OpenXR mod. It makes the experience a lot more smoother.

did you try your AERO with OpenXR in DCS yet? It makes the the performance "silky smooth" (Zohan ), gets rid of the jitters.. I made it in to a separate topic in VR forum.

Varjo Aero. nothing beats its clarity and sweet spot. G2 and VP2 (I have both of these as well) are collecting dust, trying to sell them.

@mimikiwi the latest version of OpenXR toolkit works out of the box, no need for any custom dll's.. https://mbucchia.github.io/OpenXR-Toolkit/ (v1.0.4)

(updated: June 10th, 2022) hey, guys, thanks to @mimikiwi on Discord and other super cool guys we figured out how to make OpenXR work for Varjo Aero. The performance gets a serious bump in the 'smoothness' department. There are no jitters/tears, the performance is super smooth. You can still see the blur looking outside the cockpit on left/right at low level, but it beats the jitter mess that OpenVR introduces. To make it work for Varjo Aero: 1) download the mod from https://gitlab.com/Jabbah/open-composite-acc/-/releases (latest version 0.6.1 https://gitlab.com/Jabbah/open-composite-acc/uploads/d802bd460c18ee06e832bb2d6582209c/OCXR_WMR_ACC_v0.6.1.zip) The above links are old, the .zip download still works but it has older files, so I recommend you navigate to the latest release page: https://gitlab.com/znixian/OpenOVR/-/tree/openxr Download file (x64bit): openvr_api.dll (link: https://znix.xyz/OpenComposite/download.php?arch=x64&branch=openxr) This file provides a redirect mod from openVR to OpenXR framework in Varjo application ecosystem. 2) place the downloaded openvr_api.dll in to \bin\ folder in DCS (or use a mod installer): Important: openvr_api.dll is part of the DCS core install (for OpenVR support), hence it already exists in \bin\ and the system will prompt you to over-write it. Back up the existing openvr_api.dll file if you want to revert back to OpenVR/SteamVR support. Then go ahead and over-write it with the downloaded file. Please note that any subsequent updates to the game may/will over-write this file with the ED provided one, hence check after each update whether or not you need to over-write it again. If you forgot to back up the original you can always restore it via Steam file check integrity of the whole DCS game (it'll re-download the original file). 3) create a file called opencomposite.ini in \bin\ folder. Some people need this file, some don't, but on my system I get an error if this file isn't present when launching DCS. Copy/paste the following contents in to the file using the notepad app: ;Mirror mode outputs a shared texture for use by OBS plugin ;mirrorMode=disabled ;Performance stats enables writing of performance stats ; If enabled press F11 to start stats capture to file ; File is currently output to \Program Files (x86)\Steam\steamapps\common\Assetto Corsa Competizione\AC2\Binaries\Win64\teststats.csv ;performanceStats=disabled ;Hidden area mesh fix now is autogenerated you no longer need to put in manual values see changeling V0.6.1 ;enableHiddenMeshFix=enabled ;Use OpenXR layers to handle GUI overlays and HUDs, if set to false will render internally directly onto swap chain before submitting enableLayers=true forceConnectedTouch=disabled renderCustomHands=disabled 4) Open Varjo Base application and make sure OpenXR is enabled 5) make sure OpenVR is DISABLED in VarjoBase (doing so may affect other SteamVR games you play, so remember to switch it back ON if you're playing games that rely on OpenVR) 6) Make sure V-sync is disabled in Varjo Base. Otherwise you'll get a lot of ghosting in-game. 7) run the game with "dcs.exe --force_steam_VR" (create a shortcut, add the --force_steam_VR line at the end. Make sure it's indeed dcs.exe in the shortcut and not dcsupdater.exe or some other file names) Note1: If there are problems with the aspect ratio of the DCS (tilt your head left or right and the whole picture skews to the left or to the right) you may need to re-run the WMR debug tool to resolve the aspect ratio problems. It was necessary to run it when we figured out the support for OpenXR back in March. However, with the latest DCS builds the need to run WMR tool is no longer there. **************IF you need to run /or/ re-run the tool:************** a) delete a single headsetname.lua file from %:\Users\username\SavedGames\DCS\ <-- this file will exist ONLY if you ran the WMR debug tool before. If you never used the correction tool then the file won't be there, so proceed to b) below. Note2: headsetname <-- this could be Quest2, or some HP or Dell in its name, or HEDY.lua (it changes for some reason). You need to have the "show file extensions" option turned on in the File Explorer in order to see the .lua extension. But it'll be the only .lua file under \SavedGames\DCS\ so just go ahead and copy it to some other folder for backup purposes and then delete it from SavedGames\DCS\ b) make sure the autoexec.cfg file with the below config line exists in %:\Users\yourname\Saved Games\DCS\Config\ folder. If it doesn't exist, just create one with notepad app and copy/paste the following line into it: force_cross_eye_recovery_tool = true ***************************************************************************** 8 ) Since with OpenXR the SteamVR app is no longer launched/used the render resolution is controlled by Varjo Base (the ppd numbers) and it doesn't offer any option for custom resolutions, i.e. it's either at 35ppd or 37ppd, etc. So, in order to set the custom resolution you must use the OpenXR Toolkit developed by a @mbucchia. The toolkit can be downloaded here: https://mbucchia.github.io/OpenXR-Toolkit/ Please read through the manual in the above link, it explains how to launch it and all the settings in the tool-kit. In the tool-kit you have 2 options for resolution control: System tab / Override resolution: Enable overriding the overall OpenXR target resolution. You can just set whichever vertical/horizontal numbers you need to achieve the desired result. Performance tab / Upscaling: OFF (default), NIS, FSR allows you to reduce the 'size' of the screen, i.e. lower the resolution (you'll see ver/horizontal numbers there) then when either NIS or FSR selected, the selected algorithm will upscale the picture to 100% resolution (either the one set in VB, i.e. ppd, or in System/override resolution tab of the toolkit) it also allows you to modify the sharpness. I.e, even if you don't reduce the 'size' you can still add sharpness anyway (you must select either NIS or FSR for the sharpness setting to become available) Color Saturation/Sharpening: 1) use OpenXR toolkit from above, there are multiple options available (read the manual) 2) Reshade 5 doesn't work with OpenXR.

@nikoel and others here: do you happen to know how to adjust the World Scale in this OpenCompositeACC mod? Looking at their release information for version v0.3.1 it says "Support for setting IPD offset (World Scale)" yet there are no instructions on how to achieve it...

nope. I had to buy an htc controller just so I could launch the stupid dashboard in VR. It's an atrocity, however there aren't any workarounds for it.

your top screen shows an incomplete folder name "\DCS Open Beta\" <-- top screen "\DCS World OpenBeta\" <--- bottom, which I assume is where your game is installed. make sure the top screen properties reflect the correct path to DCS.exe on your PC (i.e. "D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR )

go to %:\users\yourusername\savedgames\dcs\ (or \dcs.openbeta, in my case it's just \dcs\) there's going to be a file with .lua extension (if you have extensions enabled), it'll be the only file with .lua. See bignewy's screenshot below, pay attention to the file below (although he doesn't have extensions enabled), the "DELL VISOR VR118.LUA" is the vr config file for his headset. Since you have G2 your file will have a different name, but it'll still be there, just enable extensions in file explorer to see which one it is. 1) Delete it. 2) configure autoexec.cfg per the tool's instructions

man, such a disappointment for no fuzing in the latest update "Fuze parameters are now set up to use real-life values" <-- what does this mean? Instead of 0.08s delay we get 0.079s (sarcasm)? sigh.. ************ WWII Weapons. Reworked fuze modelling of WWII bombs and containers. Fuze parameters are now set up to use real-life values. The GUI to adjust various fuze settings is in the works. ************ They could've at least released it for WWII. The Mosquito fans plus all other wwii ground pounders (myself included) would've been super happy.

This past weekend I saw a bunch of folks on Normandy Wolfpack server(s), around 30-40 folks at night (Eastern time). During the week it's pretty much 4-8 players on whichever server happens to attract the most attention.

reading your commentary is exciting. but all I'm waiting on for now is the delayed fusing so I can do some proper low level bombing runs in my favorite wwII bird without blowing off its wings.. If ED doesn't include delayed fusing in tomorrows update I'll do something drastic. Like not play DCS for couple of days. Sigh.

can you possibly point me to the "forked foveated vrperfkit" ? I found the regular one on github, but where can I find the forked one?

ED acknowledged it in this thread:

there's another thread on this issue where bignewy finally acknowledged this bug.

finding the proper abbreviation in the context of the text is the challenge, not the lack of effort. The centralized location of all related abbreviations is a wise approach.

I know this isn't a fix per se but I use it in P47. I mapped a button for 'move pilot down' or something like that in the bindings, so when VR view is too high it's very easy to adjust it by pressing the button.

I gave up on using it 6 months ago..

wow.. this is cool.. i've never seen it reach such high temps! .. So those louvers (sic?) can actually be used for their purpose to cool off the motor. But the engine won't die, that's for sure. I once ran it with 0 oil pressure for 25 minutes flying back from Dover to Dunkirk ...

in the Russian forum I read that ED introduced a new engine cooling couple of updates ago, however I haven't seen anything in the release notes... not sure if this guy is making stuff up, however he's very active in WWII modules.. translated: Somehow "quietly" the process of adding a new cooling model for piston engines went through, IMHO the question is actually very interesting and important. I would like to ask Dmitry Yo-Yo (if there is time and desire) to describe (as was done as usual for engines and systems related to them) what is the meaning, differences and basic principles of the new cooling model