Lange_666

You can remove the contents of both the fxo and metashaders2 folders (or delete the folders entirely, they are re-created when you first run DCS after they have been removed). Personally, i have never seen any difference in performance if these where not deleted (i've done both ways). Pagefile setting: fixed space (so not windows managed) and as large as your RAM is. So if you run 32GB RAM, set the page file max and min to 32 GB.

Yes, use the Custom Presets under the App Settings tab. Run the updater, start DCS, set your settings in DCS, quit and set a preset name for it. Repeat for more presets. When done, these are available under Select Preset on the main page of the updater.

I missed that part, just did read over it after reading that i should never use Windows Calibration to calibrate a controller (which i never do). Thx for the heads-up...

I'm using DX buttons for that, that way you don't send a keyboard command (or need to hold one). //Autopilot Select Switch MapKey(&Throttle, APPAT, Autopilot_PITCH_Switch_ALT_HOLD); // DX88 MapKey(&Throttle, APAH, Autopilot_PITCH_Switch_A_P_OFF); // DX86 MapKey(&Throttle, APALT, Autopilot_PITCH_Switch_ATT_HOLD); // DX85 PS: I'm using the 120DX button mod to get more then 32 DX buttons. Gives you plenty of option for not using the keyboard.

After contact with Milan and receiving the steps (same as in the manual) the problem still persisted. Flashing v5.0.9 resulted in full deflection already in the center, resetting the device as advertised did nothing, going back to v5.0.5 always solved the problem. Then Milan gave the tip to reset (set to default) the device in Windows Calibration. This worked. v5.0.9 is up and running.

I didn't calibrate with Windows Calibration, just used it to see the response of the Z-axis to confirm the behavior and what i saw in the controls setup in DCS. Just gave it a second try, followed the instructions step by step, same issue. Went back to firmware v5.0.5 (with the same instructions), all fine again.

Can't make this work on my V2. Flashed the new firmware (v5.0.9) through the MFG Configurator (and Bootloader) and after the flash all is fine in the MFG Configurator, the resolution doubled to 8192, pedals at rest (middle) show 4096, pressing full left gives 0, pressing full right 8192. However, in game or Windows Calibration or DIView it does not work, it shows 0 with full left pedal but gives 8192 at middle position and still 8192 at full right. Manual recalibration halfs the res instead of doubling it, full left is then 1224, middle 2048 and full right around 3072. Going back to auto after that goes back to original problem. Flashed back to v5.0.5 (redusing the resolution back to default) and all is fine again. Also, after the flash to v5.0.9 i'm unable to run the MFG Configurator 2.17. It runs (it shows up in taskmanager) but the program is nowhere to bee seen, not even after a reboot. The only way to run the configurator again was using version 2.15

So my Oculus software settings tells me that it's using OpenXR as runtime. Does it use the OpenXR from within the DCS dir or another one installed somewhere else by Oculus?

I'm having the same issue with my Rift S when running OpenXR but the shift of the whole cockpit is rather small (but enough for me to drop OpenXR). Reset WMR doesn't work for this and my room is well lit.

In DCS, go controls then disable hot plugging

Been there done that, works for a couple of times, then stops.

Been already a problem for years for me. Solution from support is always the same, we see nothing wrong but try a different e-mail adres. Works for while and then same problem roars its ugly head. Another e-mail adres solves the problem again for a few weeks and then all comes to a stop again. I just gave up on the newsletter all together...

Yes Can't answer your other question because i don't have anything Steam related. What i do know is that once you have the standalone version, you can make a copy (like for a second install, being it the stable version or one in which you install mods or try some other stuff) and update that copy to the version you want. And if you want to make your life easy: just use Skatezilla's updater/launcher: Also, everything Steam related is to be found here: https://forum.dcs.world/forum/284-steam-support/

Whatever, D3DCompiler_47.org or something.

Could you please please please link directly to the download file instead of an overview page with lots of directory's and files? If there is one thing that always confuses the hell out of me it's the Gitlab jungle. I never ever know what i need to download...

You will have more chance of getting an answer in the Input/output section of the forum: https://forum.dcs.world/forum/70-input-and-output/

Nope but then i don't have WMR installed, i'm running native Oculus, no need for all that <profanity>.

When in VR, my IHADSS view is slightly tilted to the right when i look straight forward. So the IHADSS horizon line doesn't match with the real horizon. I have to tilt my head a bit left to make then match. I find this annoying. Anybody else have this problem?

Always used that one, still do today.

This is something i don't understand, if there is specific profile, doesn't that get the upperhand over a global one when the exe is run? Also, if VRDirectX is global when applied, what with the specific settings of other global or specific profiles when those are executed? If this is the way it works, why have specific profiles at all?

That's the thing, how does one compare if there is no difference to be seen? I find the 3D effects not bad at all but Don also thought he had very good 3D effects until this trick enhanced his experience. Tried one last thing, DDU'ed the drivers, re-installed the latest from scratch and ran the above test, first without and then with the changes, no joy...

True on not knowing what i'm missing but I suspect the latter is the case, why would i have enhanced 3D effects when most people don't and on an older system? Still wanting to know if people with a Rift-S (running native Oculus) see the effects or not.

Just created it's own profile, didn't do that before because inspector only allows one exe tide to one single profile, not multiple. - So unhooked DCS.exe from it's own profile (the Black Shark one). - Created a new profile with global settings and ran DCS, vanilla so to speak (Persian Gulf coastline/building flight). - "Carefully" changed the 5 settings and tried again, no difference in depth between this and vanilla. - Added dcs.exe to the new profile and ran DCS again, no difference...

This one is also something that bugs me. If you set the five settings and see a difference and then reset them back to the previous setting then the effect should be gone. It just doesn't make sense that it can't be reverted. Again i gave it another shot after reading through the entire topic page by page and taking note of some other stuff that was mention that "could" have an impact (example: VSync unchecked in the VR tab in the DCS settings). None of these things brought the extra 3D depth effect you guys see and what i'm looking for.

Tried again, i really don't see any difference with the settings set or not (directly into the DCS profile). Played around with shadows and stuff (turned those off to keep FPS high enough in multi-player) but that didn't bring anything either. Then tried a Caucasus mountain run, same, no joy. Also updated (not re-installed) to the latest nVidia driver, no joy there either. Still wondering why it works for some and not for others.