Phantom711

@FatCap Yes. OpenXR is the default for DCS VR. BUt OpenXR and OpenXR toolkit are not one and the same. You do not need OpenXR toolkit to run DCS in VR.

Wenn es in XPlane funktioniert und in DCS nicht, liegt das Problem sehr sehr wahrscheiblich bei DCS. Da Du ja alles neu installiert hast, hat DCS vllt auch noch anderen USB devices die fraglichen Axen zugewiesen und diese „stören“ sich jetzt gegenseitig. Schau also einfach mal im controls menu, ob Pitch und Roll noch durch ein anderes Gerät belegt sind.

Yes...I never said anything else. So with the OpenXR toolkit disabled now, does it work any better now?

EDIT 2: I did dig a little further and in fact Varjo Foveated is explicitly incompatible with OpenXR toolkit. So by ticking the QuadViews box you have probably for the first time really experienced Varjo Foveated, the extremely low FPS probably being a side effect of the incompatibility.

@Semaphore Apparently your API layer manager states, that OpenXR toolkit is incompatible with Varjo Foveated. So you could try disabling the OpenXR toolkit. There is a tickmark option for that if you open it in Windows. I‘m not familiar with the Varjo ecosystem, but since you are not using QuadViews really, but Varjo Foveated, which is also recommended that way by mbucchia as far as I know, I also don‘t know how the QuadViews button in DCS interacts with that in the first place… EDIT: Wait…do you use the Foveated setting in the OpenXR toolkit? I believe you can definitely not use them in conjunction with QuadViews and probably also not with Varjo Foveated (I guess).

Haven‘t watched your tracks, but the most likely error would be, that you enter the coordinates in the wrong format. Lat/Long coordinates can be degrees minutes seconds or degrees minutes decimal minutes. And then there are even more precise versions of both formats with decimal seconds or more digits of the decimal minutes respectively. Recheck if you are using the correct format. The Hornet can handle all of these formats if you select them accordingly. Another error might be that you forgot to also enter the elevation of the desired target.

Isn‘t it nice, when solutions are so easy….

Dude…“VR recenter“! It‘s a keybind in DCS under the controls options. You can also bind it to a joystick button…

Simply shut down SteamVR or don‘t launch it in the first place. (It probably launches automatically, right?). just have WMR running and then launch DCS (with VR selected next to the Launch button as described above).

There is no ST version anymore. It was abandoned a couple of weeks ago. Both DCS.exe in the bin as well as the bin-mt folder currently do the same thing as far as I know. From my experience ASW is noticably superior to SSW with regards to image quality. But YMMV… I believe you could use OpenXR toolkit to reduce the displayed FOV. Before advised that OXR toolkit might introduce it‘s own problems since it is no longer supported (it might just as well work absolutely flawlessly also).

Before OpenXR became a thing, WMR with SteamVR was the only way to run DCS with the G2. Then there came OpenComposite first and now for quite a while we have native OpenXR support. Many would probably agree that SteamVR is an additional bottleneck. But to run with only WMR you need…uhmmm…have I mentioned „OpenXR tools for WMR“ yet…?!

I don‘t think they are a thing on the Hornet. Can‘t recall ever seeing a picture of a Hornet with tripple Maverick racks…

Maybe you have some window popping up there on your monitor that interferes with your mousepointer. I think I‘ve had this with Antivirus pop-up messages. Not with a Q3 though…

Das könnte Dich ggf interessieren. @schmiefel

@RotoDan As I said, I don´t ask you to be under VR while taking screenshots. Nor do I want screenshots from within DCS (for now). At no point up to now did you really acknoledge, that you have set WMR as your OpenXR runtime in the "OpenXR tools for Windows Mixed Reality" from the Microsoft store (for free). This program is not to be confused with the "OpenXR toolkit" that you can get from github.

@MAXsenna I agree with Tankom…this is a great tip! Thanks!

@RotoDan What do you mean? you don‘t need to be in VR in order to take screenshots of the OpenXR tools for WMR.

Remember that DCS has it´s own IPD setting under the vR options tab. Maybe recheck that one. Try turning it off or set your individual IPD. Still wouldn´t explain why it acts differently between Quest and VD, but who knows, maybe it interacts differently with each of them. VR mysteries.

I didn´t mean screenshots from DCS. I rather meant from "OpenXR tools for windows" or your SteamVr settings. Windows has a Snipping tool that is very handy. Just search for it in the Windows search bar at the bottom left.

Ja, aber wenn Du den Regler auf 40FPS setzt, kommst Du ja nie über die native Refresh rate und ASW müsste dann auch im Automode auf 36FPS begrenzen. Alternativ könntest Du die FPS auch im NVidia Control Panel auf das FPS genau begrenzen. Unabhängig davon sollte auch die Einstellung „45Hz forced“ im OTT den gleichen Effect haben, nämlich immer auf halber FPS rate ASW zu laufen. Aber ich glaube diese Einstellungen funktionieren zum Teil irgendwie nicht so zuverlässig. Es gibt im OTT noch die Möglichkeit Hotkeys zu belegen, um in der laufenden Session die verschiedenen ASW modes durchzuschalten. Das funktioniert wohl bei manchen dann etwas besser.

But then again, let‘s also stress, that lights, especially the strobe light, should be visible at a much longer distance. We did a night mission last thursday and lights only became visible within a nautical mile…and that was with NVGs even…

Can you make screenshots of your settings in either SteamVR or the OpenXR tools for WMR pls!

Ich glaub unter dem "General" Tab.

Hast Du auch mal drüber nachgedacht DCS von Steam abzukoppeln? Ich weiss nicht genau, inwiefern Steam nicht trotzdem nochmal ein zusätzliches Nadelöhr ist, auch wenn Du kein SteamVR nutzt. Und QuestLink ist in Deinen Settings auch als OpenXR runtime ausgewählt?

„Kein support mehr“ heisst de fact wohl nur, dass es nicht mehr gepflegt/geupdated wird. Man kann es immer noch nutzen. Einige haben inzwischen berichtet, dass es bei ihnen zu Problemen führt. Netterweise kann man aber das Toolkit auch per Tickmark zeiteeise deaktivieren und/oder auf Default Werte zurücksetzen, wenn man testen möchte.