Lange_666

This... And change the value directly with a hugh amount like going from 60 to 6 instead of little tiny steps.

What happens if you (backup first so you can restore, parts of entirely) delete your DCS saved games folder and then let DCS create a new one. Deleting the input folder in there might be enough.

You don't have the option Synchronize Cockpit Controls With HOTAS Controls ticked do you? If so, remove it.

Normally i don't use the default path if i can avoid it. I can only check the startup checks in a week or 2 (on holiday right now).

The icon is presented when the path to TacView (64 bit) is set. However, when the updater/launcher app is closed and reopened, the icon is gone and stays gone but TacView still loads normal when selected through the app. The only option to bring the icon back is to re-select the TacView path. The icon then shows up again until the updater/launcher app is closed. That's all...

^^ This...

I'm having the same. Also, selecting TacView.exe instead of TacView64.exe results in an error each time.

Why not put a link in here or in a signature so people who read your posts can directly "surf" to your Youtube channel instead of going to the Tube manually and then search for your channel. Life can be easy sometimes you know...

Every TrackIR comes with a trackclip (non IR), you could have used that to see rule out the device itself.

This has been an issue since the early days of TrackIR. When the FPS is not in sync with the TrackIR pull rate, slight microstutter is visible when not looking into the direction of motion. When looking straight ahead, i don't notice it, when looking sideways it's noticable, even when the FPS dips or jumps 1 frame below or above the pull rate (or a division of it). It gets worse the more frames it diverts from the optimal value. And it becomes more noticeable the faster the image is moving. That's why i VSync and cap to 60 (120 isn't reachable all the time in every situation) since i run TrackIR. Without TrackIR, fluctuating FPS values are no problem, with TrackIR it's a no go (for me at least, not everybody's perception of stutter is the same). PS: Same goes for VR, fluctuating FPS is never smooth for me.

It doesn't only crash when i take the headset off but also when i wait to put it on. Before the second to last update i started to not put the headset on while DCS was loading because it took an awful lot of time to load (which is corrected an update or 2 ago). When not putting the headset on it gives the same crash result in MT with Turbo set to ON. Just to add to the story...

Mine are lying next to my monitor. I don't use them while flying.

That's what i thought all along but the big red message in the toolkit's menu that it turns off ASW all together makes it a bit confusing.

Now that's one part i don't understand. I use ASW through Oculus Tray Tool which caps the FPS at 40 (80Hz refreshrate for my Rift-S) since i can't keep that 80FPS up all the time and certainly not in more detailed and complex environments. If turning on Turbo disabled ASW the FPS should go up which it doesn't, it just stays locked at 40.

One sec in Google... https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/

I'm having this also. I need Turbo mode set to ON in MT environment to get a smooth ride otherwise there is some stutter. ST runs smooth without it.

I guess it itches...

Standard it should be capped at 180 in the graphics.lua file (DCS install directory Config folder (not in Saved Games)). Check it's not set at 60...

@ admins: can the mark "solution" be removed? Thx

Update: not really solved. Same problem again this morning after starting up PC. OpenXR Toolkit active, DCS MT crash to desktop when i put the headset on. Switched the ST, works fine. Switched back to MT, crash. Disabled toolkit: MT runs fine (with stutter, that's why i need Turbo mode set to on in the toolkit, it removes the stutter). Re-enabled toolkit: MT crashes again. Ran ST mode, turned Turbo Off, ran MT again, runs fine with stutter, turned on Turbo mode, stutter gone, quit. Ran MT again, crash. Ran ST again, loaded default values, Ran MT again, runs but since no Turbo mode, slight stutter again. Set Turbo mode in MT, stutter gone, smooth run. Exit and reloaded, same problem, DCS MT crashes with Turbo mode on when i put the headset back on. Next step, loaded DCS this time with the headset already on my head. DCS MT doesn't crash. Tried the same a few times, seems to work every time.

Update: just had another go at it, MT crashed in VR on first run. Then i disabled OpenXR toolkit and re ran DCS MT in VR without a problem. Enabled OpenXR Toolkit again, no more problem... ... so...?

Since the latest update i'm unable to launch DCS in VR in MT. When launched, it will reside in the taskbar but when i put my headset on, i'm looking at a turning hourglass then a few seconds later, DCS crashes to desktop. Before the update i had the same problem but only at the first run after starting the computer. On the second run after the first one crashed, it all worked just fine. Since the latest update it always crashes. No problems with same version in VR in ST mode, runs just fine. No problems with same version in 2D in both ST and MT, they run just fine. Ran a slow repair, no joy. dcs.log dcs.20230809-093021.crash

Little bug: When the application is send to tray and i right click on it and then select "Restart Application" it closes but never restarts.

I'm having the same problem with MT when OpenXR Turbo isn't set to on. If set to off, micro stutter, if set to on, smooth. (noticed same thing with Rift-S and Pico 4). Setting it to on comes with a drawback of small black flickering bands on left and right side of the view when head is moved quickly. Therefore i prefer ST for VR and only run MT in 2D mode. For me it's an OpenXR problem because when running MT through Oculus api (yup, it's possible) OpenXR toolkit doesn't work and then there is no micro stutter on MT and no black side banding either. It then looks / behaves like ST does.

To be honest, the one thing in this new version i really can't get my head around is the Graphics Preset Editor. I played around with it a bit a first thinking i could set presets with the values/options chosen in the editor. It turned out to be a mess not knowing what setting would actually load when launching DCS. Even more, when i enter the Graphics Preset Editor tab and then leave again the utility always comes with a warning that i need to save the changed values although i didn't even change a single value. Just selecting the tab is enough to come with changed values. Changed values from what setting? Same goes for the radar display in there. I just don't understand why a ED High or SZ Ultra preset with high settings gives a lot smaller radar cone then my own LOW setting where everything is set to minimum.