Lange_666

Which config folder did you check? Default keyboard files are in Your Drive:\Eagle Dynamics\DCS World\Mods\aircraft\Aircraft-Type\Input\keyboard But this is the original file. You should check C://Users/Your Name/Saved Games/DCS/Config/Input/Aircraft-Type/keyboard/ In there you should have a Keyboard.lua file (and a Keyboard.diff.lua if you changed something). If for each aircraft the keyboard folder is empty, you could rename your DCS saved games folder (don't delete it) and let DCS create a new one. That should fix things. Then copy the new keyboard folders over to the backup and rename it again to it's original state.

Did you check the dedicated VR section? https://forums.eagle.ru/forum/302-virtual-reality/

@mtpiperpilot: Tip:

This is no doubt the best way. Only one icon on your desktop for everything, various presets directly set without the need for a restart of the game, side loads other stuff when needed etc... just top notch !!

Oculus updates are mandatory and if they break something, you need to wait until it gets solved because there is no rollback to a previous version. However, you can block the update: https://forums.oculusvr.com/t5/General/Please-Stop-Forced-Updates/td-p/619257/page/2 (it's halfway through the second page, post by "parsecn". After doing this, when Oculus comes with an update, you'll get a notification that an update started downloading but it will never get passed that. This gives you time to go through the (messy) forums and see if they are big or common problems. If so, you can block the update until it gets fixed. To unblock the updates, reverse the above process.

- Where do you see (or don't in this case) that "green flag" for DCS? - What happens if you turn off Variable Refresh Rate? - DCS Full Screen mode changed with the introduction of 2.7 and it went to Windows Borderless Mode instead. I would suggest trying GSync for both windowed and full screen mode and see if that makes a difference.

That's 120Hz alright. My old old monitor showed 59,9 instead of 60Hz. 120Hz is just a rounded value. Set your DCS graphics settings so that your FPS stays above 60 "all the time". You will still see stutter when it dips below. You need to have a bit of overhead all the time for the cap to work. Also, imho, VSync should be turned on if you say that GSync doesn't work.

The refreshrate of the monitor only matters with VSync ON because then when the GPU is not able to maintain the capped FPS, it will adapt to the next lower value. With 120Hz these values are 120/60/30/15 and these are in sync with TrackIR. On these values TrackIR is the smoothtest. With 144Hz the values are 144/72/36/18. As long as you cap your frames to 60 "and then stay there" there is no problem. It will only give a TrackIR induced stutterproblem when it dives under the 60 meaning adaptive VSync will settle in on 36 which is not in sync with TrackIR.

When you run 144 Hz refresh, there is a mismatch between the monitors refresh rate and TrackIR pull rate. When VSync comes into play ( and i run VSync because it still gives me the smoothest movement i can get) you have 144Hz native, 72 and 36 adaptive. TrackIR will pull at smooth at 120, 60 or 30 (30 being already to low for fast moving games/terrain). Setting your monitor at 120Hz refresh matches TrackIR when the FPS is also capped to one of those numbers. The stutter is almost unnoticable when looking forward in the direction of the movement but when looking sideways, and certainly when things move fast, if the FPS doesn't match the TrackIR pull rate you have stutter. If you pause TrackIR, the stutter is gone, if you unpause it's there again. But some people don't notice this at all, some see i directly.

Option: https://smoothtrack.app/ Works with AR capable cell phones.

GSync (or other monitors) works fine with TrackIR as long as you set your monitors refreshrate to the pulling rate of TrackIR and cap the FPS to one of these values. Pull rate of TrackIR is 120Hz (full devisions of this value work too, like 60 or 30 but then 30 is to low for fast movers like in DCS). The moment your DCS FPS will move away from the TrackIR pull rate (either higher or lower), you'll notice a slight stutter, especially when looking sideways when the terrain moves very quickly. The more your FPS drifts from that magic value, the more stutter you'll see. To get around TrackIR stuttering i set my 144Hz capable monitor to 120Hz and then cap the FPS to 60 (because i can't maintain 120 FPS across the entire range). I tried various settings to make TrackIR experience as smooth as possible but the above is the only one that really works, for me at least.

As long as it is a slider... Now i don't fly the F-14 because of the shake...it's utterly disturbing to "see" everything shake but not feeling it.

I hope you did the right thing. Although you're eyes are almost in contact with the headset lenses, you need lenses to see sharp in the distance, not close up (always mess up the meaning of far or near sighted so i don't use that).

What problems do you have?

I'm using a set of VR Optician lenses, good quality, comes in a nice box, each lens comes in it's own little bag. No regrets.

It should have the option, i still have the Make HTML in both stable and latest OB:

I'm in the same boat system wise. I use 3 settings, high for offline 2D play (trial and test runs, learning stuff), a below high setting for online 2D play (but on some servers this setting is to high, even when i'm alone on it as a single player) and a medium to low setting for everything VR. It's just the steps back i need to take to get a smooth (as possible) experience. Expect also a lot more shimmering, certainly around clouds. But... even on this lower setting and the extra shimmer, VR is just amazing. Just don't set your expectations to high and you're in for a threat.

The Mongoost T50 is made for mounted setups (with extensions). It comes without baseplate.

Yes

If you have the budget, 32MB is not a waste, depending on your resolution and settings, DCS uses easily more then 16GB. GPU is OK, comparable to my 1080ti, looking the hardware reviews, sometimes (depending on the game) it performs a bit better or a bit worse then my 1080ti. If you can run a Quest 2 decently will be up to your expectations, my VR settings are quite a bit lower then my 2D settings to make it run smooth and then that's always at half de refreshrate (40Hz for the Rift-S), full refresh (80Hz) i can not maintain, not even with all low settings. But locked at 40Hz (unlocked is way to stuttery), lower settings even multi-player is quite good. But then your expectations may vary.

That setting should not cause cross-eye problems since it changes world scale (or cockpit scale) and has nothing to do with real IPD as spead-of-heat mentioned already above.

You can also buy through the e-shop on the website. After purchase the bought modules will show up in the module manager for download. Tip: If you think of buying FC3, there is no need to re-buy the individual aircraft individually (A-10A, Mig-29A etc....) For your purchases to show up, DCS needs to be connected to the internet "and" autorised, so you need to be logged in!!

Because SteamVR thinks it's needed for everything VR wise which it is not. Never found a solution to block SteamVR from poppin' up. I was so annoyed by it that i uninstalled Steam totally. I didn't had any Steam provided game anyway but installed it because Steam has almost the monopoly on race games (besides Assetto Corsa which is a subscribtion payed game and Live For Speed) and i wanted to try some VR racing. I ended up with Live For Speed.

There is for quite some people (if not all) a significant performance loss when going from 2.7.6 to anything above. You can always revert back to an older version. You can do through a command line or... One of the neatest tools out there to do this is Skatezilla's Update Utility. It lets you upgrade, downgrade (under Adv Updater Options Tab), create a copy, make an open beta out of a stable version and vice versa and lots of other stuff.

My experience: If FPS isn't exactly on the TrackIR (and with Track IR i mean the Natural Point stuff, not some 3th party DIY stuff that's also sometimes called TrackIR) pull rate of 120Hz or a division of it (60Hz) i "always" experience stutter on fast moving terrain. Over the years i used my TrackIR on various GPU/monitor combinations and the result is "always" the same, stutter when FPS and TrackIR pull rate don't match. The closer the FPS comes to the TrackIR pull rate the less noticable it is, the further it drifts away, the bigger the stutter gets. It's OK and almost not noticable with terrain movement looking straight ahais but when looking sideways it's always there. G-Sync is not a solution to this type of stutter. For the moment i'm running a 144Hz monitor but i set it to 120Hz and then use VSync + FPS cap at 60 (i can't maintain 120 FPS with my setup) to make TrackIR real smooth. It's the "only" solution i found so far that works all the time to prevent TrackIR stuttering.