Lange_666

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.

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

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...

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.

Go Control Panel / Devices and Printers / select your X-56 / right click / Game Controller Settings / pick your X-56 out of the list / Properties

I searched and tried all i could find for 30 days in a row, no joy. Only solution was turn everything down so i could keep that 72 FPS steady on my 3080ti. But then visual quality suffered to a point that my Rift-S was simply better (and dealed a lot better with space warp). Moving visual quality up mend dipping below 72 FPS and then stutter came lurking around the corner.

That's the reason why i returned the Pico. Way to many disturbing artifacts with space warp on and with a 3080Ti i needed space warp to get a fixed FPS rate.

As long as the stand alone versions don't offer the same video throughput as headsets with a display port the future headsets will need a display port imho.

Guess that was me. Performance (on Ethernet-USB-C adapter cable to get a full stable stream) is only good when you can achive FPS at native headset refresh (72 or 90Hz so 72 or 90 FPS). But that was only possible with lower settings on less demanding maps and with not much going on. When not FPS would drop below the freshrate resulting in stutter (i still don't understand how people manage to get their headsets working stutterfree with a variable FPS). Forcing ASW removes the stutter but introduced a lot of ghosting on distance objects when looking at it sideways. My Rift-S doesn't have that and Oculus ASW works far better then that of the Pico 4. I tried everything i could find but never found a solution so the Pico went back to the store. + on a lot of tube video's about the Pico 4 they say that it's a good headset "if" you have the system to run it with an FPS at native refresh rate. My 5800X3D + 3080ti couldn't do that in DCS, at least not for the visuals i wanted.

My 4th gen Intel had already HT so yours should do to.

If you're looking for some speed it's not the way to go. As Bitmaster says, the more complex your electrical wiring is, the less performance you get out of it. And in your case, going from downstairs to upstairs probably means you will cross over to another circuit in your fuse box... far from the best option. Form the tests i ran a few years ago, loss could easily go up to 80% of your starting speed. Nothing to get happy about.

DPI settings: 100% Didn't touch anything there Windows wise but i use Verdana as my font in Windows instead of the standard Segou UI (which i find to blurry). To make that work in under Windows 10 i use Winaero Tweaker. Used to use size 8 but changed to 9 due to my eyes getting older and older.... Log file (from the 34 version, i've upgraded to 35) ED Updater Utility v2.old.log

Another confusing message: When entering the Graphics Preset Editor and then selecting another tab "without making any changes on whatever preset", the utility comes up with the next message: None of the above setting have been changed or touched, just entering the tab and selecting another tab gives a warning about unsaved and changed values.

Version 34: Maybe a little bug: Updater Extra Settings: The Launch Sim After Update has a dropdown menu visible which partly covers the Launch Sim After Update text + when moving the mouse over it comes with the text "Set A-10 License"