Sile

Thank you. @slughead @diamond26I didn't ask about OpenVR. That's not supported in MT, i think. But there is or was also the Oculus API which i thought might (still) work. See the picture I copied over from fred emmotts homepage (fredemmott.com). Marked the two paths in yellow.

Do you guys run the QPro with openXR and DCS Multithreading Client? Or asked the other way around: Is it still possible to use Oculus API in DCS-MT? Or is DCS-MT exclusively supporting OpenXR? I lost track somehow.

@Shug Ninx

You are right. After reading again, i see he answered specific to the Aero Quad View DFR. But the core statement isn't completely wrong if i add "quad view" and even without it i think it was still "helpful": "That's not a problem. quad view DFR plays it strength on high res headsets. Think it's not needed for the relatively low res QPro So now i have to find out, why i don't see DFR option in OpenXR Toolkit in DCS. Dev mode is on. I guess it works for you all like @Shug Ninx states? Does it work for you @Shug Ninx?

Why not simply change the OpenXR Toolkit Bindings? Edit: Picture copied over from openxr toolkit quickstart guide.

Wow.

hm. "Adaptive GPU Performance Scale" doesn't stay off.

And what about this? Or is this not related? (Link below Post) The guys there write, that it might be possible by enbling beta mode (developer account???) and switching on: "Developer Runtime Features" and "Passthrough over Oculus Link" But maybe i misunderstand something.

What does that mean, can you explain, please? Do you mean "hand tracking support?"

thank you! @slughead

Headset and cable are on their way. What software is needed? - I see screenshots of that dark mode software with res slider. Seems mandatory. - Then there is ODT? „… Dev Tool“. And OTT? „… Tray Tool“?! Both needed? - And do i need to have a developer account for the ODT? And is there a way to start DCS from the 2D desktop or do i have to it from within the headset? Can this be done without ever touching the controllers like in the G2?

hey @nikoel, thanks for your reports. I find them very informative and interesting since i'm also on the fence for a QPro. To better classify your result: May I ask what system you are using? CPU / GPU / (RAM)? Battery going down to ~80% seems to be normal behaviour for running and charging the QPro with link cable. I read it should hold that charging state forever with a proper cable and capable port...?! Are you using the 129 $ link cable from Meta?

last post (toykilla) was from september 2020. why not let it R.I.P.

That's not a problem. DFR plays it strength on high res headsets. Think it's not needed for the relatively low res QPro. Citing the @mbucchia here:

No DFR for Quest Pro in DCS.

thanks!

how comfortable is the quest pro for you? People complain about getting discomfort / headache due to the halo head mount design pressing quite hard on their foreheads. So i'm not sure... possibly something i can only test after purchase and return otherwise...

Maybe a important find vor VR Users (G2) who want to try the mod. I did some more testing in VR because a friend reported not seeing ridiculously big dots that i do in VR with the G2 despite using nearly identical settings (100%, PD 1.0) except 2D Resolution. The dot size in VR seems to depend on the setting "Resolution" for the 2D Resolution and the state of the VR Mirror Window. 1) System Options - Resolution. Set to e.g. 1280x1024. Maybe smaller than 1920 x 1080 works. AND 2) VR - VR Mirror Options - USE DCS System Resolution set to ON 3) Restart DCS - Mirror should start in a bordered Window on the Desktop With 3440x1440 i get big dots. With 1280x800 i get smaller dots in VR. And mod is usable. Maybe the 2D Resolution - of the VR Mirror? - is relevant here. Couldn't test more, but for me it only works when DCS starts in a small bordered window after setting 2) which is why i recommend the manual restart of DCS. Only after manual restart DCS started reliably in a window on my system. Maybe because i still had set "Fullscreen" in System Options...

Just tried the modded dots.fx in in VR with my G2 (OpenXR) at 100% und 1.0 PD. It's like you describe. I find the dots way to big. Big pixelated squares that show at about 20nm with high transparency, get darker when approaching and hide the aircraft till they suddenly vanish at 1.5 nm. Before they vanish they are nearly completely black, hiding the aircraft. Is this intended? Unfortunately on screenshots the effect and size isn't visible. So i see the improvement for 2D but not for VR in my case. But maybe someting is wrong on my end?

Please move it out of the input device section, at least. Maybe one level higher - same level as Input Devices?!

Yes, i saw that post, too. And it confused me. On the other hand, there are posts in the realsimulator forum, asking for that functionality to be expanded for game feedback, so i think it is not giving that feedback currently. I wish realsimulator was less vague on that feature.

Only for limit indication. This is very useful in VR for me. No game feedback for me, maybe i'm missing something? But to my knowledge it's only for travel limit indication. Edit: See screenshot from the manual for reference.

I'm quite sure the OP is waiting for the F18CGRH (which is still out of stock) and not the F16SGRH v2.

Do you mean this sentence on their website: "Haptic vibration actuator (available only in Right Hand v2 versions and functional only with FSSB-R3 Lighting)." I think it simply wasn't updated after the Ultra Release. Happily using a V2 Grip with Ultra base and a working haptical vibration feedback here.

Can't check the file and values myself currently. So has this been fixed like stated in changelog from 13.4.2023 (DCS 2.8.4.38947 Open Beta)? I mean the values are clearly reversed. Or does the changelog line refer to a different issue? "Fixed: Tuned rudder authority limiters. One effect is greater rudder authority at higher angle of attack."