Phantom711

Well…even though we (NATO countries) are all „friends“ and such…there is still competition amongst companies and one can not simply steal a „cool idea“ from another companies HUD layout. Or they might not even have had access to the particular HUD features of Dassault jets.

As far as I know, you can also transfer your steam version to standalone.

In any case, since the comms menu is not F/A-18 specific, you need to look under the „General“ or „UI“ tab (don‘t know which one exactly right now).

Not related to your original problem, but I have the same specs and I can only recommend using 72Hz. You will be able to hit the native refresh FPS most of the time and revert to ASW for the rest (or accept some stutter). Maintaining 90 FPS is simply hard, even with the 4090.

I thought, that was actually the same developer like the Reality Mixer. But I could be wrong though. But steamVR can be selected as an OpenXR runtime. That‘s why I also had the thought, that it could be combined with DCS (in OpenXR). So I thought I would simply use VD, start up SteamVR with the respective tab in VD and have SteamVR selected as the OpenXR runtime. But even just getting into the main menu of DCS was in the single digit FPS. So I didn‘t try any further.

So can you kind of talk us through the process? how do you set up VD? Do you tell it to execute SteamVR? Why does it have to be OpenVR? That also limits you to the ST version of DCS…

But as far as I know, you need Virtual Desktop additionally to make it work. I could not get both (VD and steamVR) to work with DCS. I had brought up that matter a few weeks ago already. If you get it to work, let us know.

@Granny

Which „menu“ are you talking about specifically?

I doubt it. Also there are probably very few headsets at the consumer market level, that could actually make use of it. Only the Quest3 comes into mind…so ideally Meta would include this into their PCVR software. I made that suggestion in their forum…but well…

Was mir noch einfällt, da ich darüber zu Anfang selbst gestolpert bin: In VR kann man das DTC UI nicht anzeigen lassen. Man kann es aber vor DCS starten und die gewünschte Datei schonmal aufrufen und auf die Upload Seite gehen. Den Upload kann man dann in DCS trotzdem, wie in der Readme beschrieben, starten.

It doesn`t work just like that via Oculus/Meta. You need this: GitHub - fredemmott/HTCC: Hand tracking for flight simulator cockpit clicking I tried it. It work, but not at the same level as the oculus hand tracking in the oculus VR UI.

You mean on the actual leg/knee of the virtual pilot model? It`s awork in progress. Wrong subforum though.

ED arbeitet zwar bereits an einer Data Cartridge, aber bis dahin ist diese tool sehr hilfreich und eine gute Übergangslösung. Wobei ED an diesen Funktionsumfang überhaupt erst einmal herankommen muss! Zur Zeit unterstützt das Tool F-16, F/A-18 und F-15. GitHub - the-paid-actor/dcs-dtc

Hmm...well...yeah...and that simply is a shortcut to the dcs_updater.exe... I don`t know where that comes from when I explicitly said, that you don`t have to run seperate shortcuts a few posts above.

Try using DLAA instead of MSAA! I have a different system and a Quest Pro not the Quest 3, but my approach is to achieve the 72 FPS most of the time and have ASW on „auto“ for those cases where I can‘t achieve that. Also note, that the term „ASW 45“ is misleading and derives from a 90Hz baseline. So it effectively means „half rate ASW“. So you will see 36 FPS when ASW kicks in (if you use the 72Hz mode).

Oh…if you switch between VD and Oculus Link, you must recheck in the Oculus software under options again, that it is set as your „OpenXR runtime“. You need to re-do this everytime after you used VD and intend to use Oculus Link instead (with an OXR application).

Because you go through the folder path everytime to get to the respective dcs.exe instead of having a shortcut on the desktop?

@bflo Yes, but only to set it up initially. I never needed it again ever since. But yeah…Meta wants your data…

Do you have the OpenXR Toolkit Companion installed? If not, then that menu won‘t show up. If you are using the dcs.exe from the bin-mt folder, it can not run by anything else but openXR. And please forget most of that video that you posted…!

@Brun The problem is not so much the larger pin holding together the throttles but the tiny one that is missing and might be dangling around in the base. I would not want something metal rolling around uncontrolled on a PCB.

@edmuss Thanks…those kind of the numbers I was looking for. What turns me off from the Varjo is the fact, that they don‘t offer refresh rates lower than 90Hz.

@Tomcat388th for the umpteenth time now…YOU DON‘T NEED THAT!!! You are not using Windows Mixed Reality. It has zero effect. It might confuse others.

I think the little pin is screwed in the larger pin (or in your case „was“). I actually removed both completely. Real aircraft don‘t have them stuck together either. EDIT: If the little pin fell into the base, I‘d be a bit worried, that it could cause a short.