Lange_666

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"

I have never had it fail in the middle of a game. But... Previous PC + my 1ste Rift-S: USB connection problems after almost each startup. Solution, unplug-re-plug USB and connection OK. Went through the entire USB solution mic/mac, power management, powered USB hub, 2 separate PCI USB cards. The last one solved the problem for like 80%. For the other 20% the headset came with a USB connection problem i found that cycling the Oculus service on/off (through OTT for example) would let it re-connect without unplugging the USB. Simple solution. New PC + 1ste Rift-S: No USB connection problem at all!! Worked flawlessly on each boot. But the Guardian would sometimes have to be redone after a startup, at a given point even after each reboot/startup and then that problem stopped again without any software updated. While that was happening i checked the camera lenses, these where not dirty of had fingerprints on them. Then early april my 1ste Rift-S suddenly wouldn't pass the sensor check anymore. Most of the time this came together with a USB connection error message, unplugging / re-plugging fixed that connection error but it still it didn't pass the sensor check. Tried everything i found, no joy. Everything pointed to the cable. Device manager needs to see 2 Rift-S devices under USB or it doesn't work, always had only one. Went for a Pico 4 after a month of getting the Rift-S back to work without any succes. Returned the Pico 4 after 29 days, not good enough. It only gives good quality when the FPS matches the native refresh freq. New PC + 2de hand Rift-S (bought one in mint condition): Works fine but... unlike my first Rift-S almost each time i reboot, come out of sleep or boot from a cold start i now have to unplug / re-plug the USB cable with this headset. Just once unplug / re-plug and then it's OK. If i don't, only one Rift-S entry in device manager is visible, unplugging / re-plugging creates the second one and then all is fine. So there's definatly a difference between these 2 Rift-S headsets when it comes down to USB connections. However, cycling the Oculus service like i did with my old PC and 1ste Rift-S doesn't always work with this PC/headset. Sometimes unplugging re-plugging is the only option to get the Rift-S going again. But just as the my first Rift-S, it never disconnects while running a game. Powered Hub gives the same problem. Power cycling the hub is not enough, the USB has to be unpugged / re-plugged before it works? Then went for a powered PCI USB card for a little PCIE slot. No joy there either. Same problem. Then replaced that one with one that goes into a large PCIE slot. This worked, Rift-S doesn't loose connection anymore, USB doesn't need to be unplugged / re-plugged anymore... but with the USB plugged into this card, game play isn't smooth. The headset seems to have tracking issues, the image shifts or hangs briefly (also in other games or in the Dash), sometimes the controllers end up on an entire different place as there location....etc so i removed that USB-PCI card again.

I have never seen motion blur give any extra sense of speed.

What if you use VR Headset as preset instead of VR (on the main page)? Must say that the presets setting in this 2.0 version are still messy compared to the previous version. I can't get them to work as it did with the old version neither.

Not everybody has or can afford a top machine dude.

And depends on the expectations. There's quite some difference if you expect (accept) to run at 40, 60, 90 or 120 FPS.

If you go for a pre-build, it comes installed with Windows and should work out of the box, no need to tweak anything for starters. If needed, this can be done later. Just hook up your flightgear, install DCS and off you go. One thing i would recommend is not go max on the DCS settings the first time you run it. Start with lower settings and then move up.

When running the Oculus Api, there is no openxrtk. Also not when running DCS MT.

Check the next thing: You should have 2 DCS folders in your Saved Games folder (c:users/your name/saved games), the stable one and the open beta one. Check the scripts folder in the open beta one, you should have TacviewGameExport.lua there and in the Hooks folder you should have TacviewGamesGUI.lua If these are not there, you can copy those over from the stable DCS script folder.

The question then remains, why 2 different outcomes from 2 different launch methodes when both (should) have the same arguments in the command line.

That's what i did and what i do all the time. I did believe that MT was OpenXR exclusively which doesn't seem to be the case then. However: - Selecting Oculus API in the app, setting MT ON in the app, selecting VR headset as preset and then hit the button Launch VR ON launches DCS MT in Oculus mode: no OpenXR toolkit proves that. - Launching DCS MT from the desktop icon with --force_enable_VR --force_oculus_VR added ("E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_Oculus_VR) launches in OpenXR because now the toolkit works. That's where my confusion comes from.

Whatever i add as VR argument onto the MT DCS.exe (example: "E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_oculus_VR ) it always starts in OpenXR (proof is that OpenXR toolkit works). I can not start the DCS.exe from the bin-MT with Oculus as API. It's always OpenXR. When i use the ST version, it works conform the argument that is used, either Oculus or OpenXR. Not so from within the updater: MT set to ON (so it should launch DCS from the bin-MT if i understand it correctly), Oculus VR API selected, no OpenXR (toolkit doesn't work). Does the updater really starts the DCS.exe from the bin-MT when MT is set to ON?

"Maybe" found a bug (previous and latest just published version). MT in VR is OpenXR only if i'm correct. If i launch DCS in MT mode directly from the icon instead of through the updater with --force enable VR --force_Oculus added, it will always run OpenXR disregarding the " --force_Oculus" and i'm able to access the OpenXR toolkit. It doesn't when i run in ST. However, If i chose Oculus as VR API in the updater app and if i select to launch in VR "with" Multi-Threading set to ON, i can't access OpenXR Toolkit which i guess means DCS is started in ST instead.

About the presets: Is it possible to write a quick step by step on how to set them? I've done what i have done in the old updater, go in DCS, set the settings i want for a certain preset, save to a custom preset, exit DCS, create a preset name in the updater app and then hit apply. This doesn't seem to work anymore in the new version. My presets are all mixed up now. Also, select a preset, change the settings in the updater instead of in DCS and then save doesn't save any of the changes i made to that preset. I guess to problem sits on my end but i don't see the tree through the forest...

Multi-Threading: ON/OFF button always reverts to ON when DCS is exited when set to OFF prior to loading.

Oculus Tray Tool: You don't need it since it's ment for Oculus/Meta headsets. I would not wait to start and enjoy VR. Just start with everything at low settings and then work your way up to see what you can maintain with your current system to get a smooth experience, not the other way around.