Lange_666

Did you set your trimhat control directly in DCS? If yes, it will depend on the duration of the press how much trim you apply. I use a Warthog HOTAS but depending on the aircraft, i use trim in pulse mode (through the TARGET programming software) which means as long as the press on the hat switch is not released, it does just one single short keypress. That way trim is a lot more precise but for more/less trim i need to press the trimhat multiple times now. As said, i use it either by pulse of constant as per aircraft. Also, if your speed changes, you mostly will need to trim again, same of you go flying higher or lower.

I'm running a Rift-S so not much choice in refreshrate (80Hz). Currently i'm always running ASW default mode 45Hz through the OTT which turns it down to 40Hz in my case. I don't use ODT. Nothing special in nVidia because it has no effect in VR. Don't set your settings to high, i'm running high to medium for 2D offline, medium for 2D online and medium to low for VR. Set everything so that you can keep your FPS in VR above 36 and then set default ASW mode in OTT to 45 (will settle to 36 if you run the Q2 on 72Hz) . Don't use adaptive mode because it will switch to 72FPS when it can reach that high and back to 36 when it can not. This causes stutter. Tip: don't use both OTT and ODT at the same time, use one or the other.

I guess it's because terrain textures are re-loaded each time you return from the F-10 map, at least on the PG map, Caucasus doesn't has that problem.

I would not reinstall DCS entirely just to get OpenTrack working. I don't use it so i'm not of any help but i would re-ask the question in the input/output section of the forum: https://forums.eagle.ru/forum/70-input-and-output/

@Dr Zaius: Just out of curiosity... When are you in FullScreen, when the screen has blinked or when the screen didn't blink when pressing Alt-Enter?

Nice find, however after testing this sadly it doesn't work for me. I don't have a scrollwheel for the volume but 2 extra keys. My osd volume overlay shows up all the time...

If it's running butter smooth with SteamVR and not with the Oculus API, something is off.

Not quite, i still have around 2-4% performance loss compared to 2.7.6 (which i still have installed so i can compare directly).

Do yourself a favor and get this utility.

There is none, the repair goes through the updater.exe

As Eaglewings points out, you can use a user file with the same setup as you but you'll find that in the end you'll always set up things differently afterwarts and you have to learn/memorize those controls to. They often come with a keyboard.diff.lua file (if bindings were added/changed compared to the original setup) but if you use a different keyboard layout then the author, things already can get messy from the start and more frustrating. I have a Warthog (with a Virpil stick base for better gimabls) so it's not comparable to your but... I would start with a basic setup (trim, landing gear, flaps, airbrakes, wheelbrakes, weapons), jut put them where you think they are right for you. If it turns out that some of them are not correctly placed to your liking, you can always change later. Then adding other controls to your HOTAS combo as you progress through the tutorials. You can press ECS, go into controls and change directly and then resume). You don't need everything at first run and you don't need everything in the end either. You'll probably move and change a few of them throughout your progress. Go step by step...

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?