Phantom711

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.

@sniperpr1 Are you using the link cable? You have the oculus software installed on the PC as far as I understand… In the options of the oculus/meta software you must set it as your „openXR runtime“. Don‘t worry mate…it is some setting you are still missing…

Thanks for your answers so far. My question was not about DLSS/DLAA though but about by how much you increase render resolution. As far as I understood, @Nedum you don‘t increase it at all.

Theoretically yes…but I have 4090 and there are still situations where I can not maintain the 72 FPS. I use one shortcut to the updater and one for 2D and one for VR. Both for the MT version. I don‘t see a need for the ST version. Not much of a „hassle“ really. Not sure about the upscaling options… EDIT: You don‘t „need to“ run seperate exes for VR and 2D unless you want to switch between both modes regularily… It is just a matter of convenience.

There are no nuances…. If your FPS are equal to the refresh rate of the headset the movements are smooth. Yes…if you could run the respective game at even higher refresh rate with the matching FPS it would be even smoother. examples: 72 FPS at 72Hz —> smooth 90 FPS at 90Hz —> even smoother 85 FPS at 90Hz —> not smooth For the 120Hz…well I don‘t know. Maybe they lock their FPS to 60 so that every frame is shown twice which would also be smooth. Or they use motion reprojection a whole lot. The Dcs.updater.exe is used to look for updates of the game but yeah…it also starts the game which I find annoying. No idea if it starts the MT or ST version. To be sure use the dcs.exe from the bin-mt folder.

I would always recommend the lowest possible Refresh rate on the headset. It is far easier for your GPU to deliver FPS at native refresh rate and provide a smooth gameplay. I find 72Hz smooth enough. For the occasional drops below I use ASW on auto.

Hi... So I am wondering, how much supersampling do people use with those HMDs? Isn´t it pretty hard for even e 4090 to push all those pixels (even with DFR)? I went for the QPro intentionally because I thought it would be insane to go for such hi res HMD...but then again I also supersample by about x1,7 also which ends up rendering more than 3000x3000 per eye. So my question actually is: Does the need to supersample actually decrease with a higher native resolution so that at the end it doesn´t even impact performance that much? My specs: 13700K/4090

What are you talking about? Why would MT have been „moved to Open Beta“? Moved from where?

I have Quest Pro...so pretty much the same resolution. What you observe is "normal". Here is what you can do though: 1. Increase the supersampling resolution via Oculus Tray Tool, Oculus Debug Tool or simply by increasing PD in the DCS VR options tab. Since your system is not on the strongest side probably not the best solution. 2. In the DCS controls options you can assign a button for "VR zoom". It breaks the immersion a little bit....but still... 3. Also under the VR options in DCS there is the "Force IPD distance". This basically mimics the IPD (distance between eyes) of your virtual(!) pilot. If you set it to your real life IPD, the world in DCS should appear to you at true scale. If you set it to something very small, you will feel like a mouse in a giant cockpit or, if set to something large, like an elephant in a toy plane. Now somewhere in between those extremes might be a sweet spot for you, where things become better readable but it`s not immersion breaking. Normal IPDs for males are from 53-77mm (source:wikipedia).

@jackson @xoxen Ich meine das Problem mit dem HDG/CRS selector wurde auch schon mal im WW subforum besprochen. Soweit ich weiss gibt es dafür keine wirklich zufriedenstellende Lösung. Die Throttle Base ist halt zwar stark Hornet-inspiriert, aber eben nicht 100%ig darauf ausgelegt.

Well…being precise to 100m (MGRS 6 digit) or even 10m (8 digit) should usually be good enough, but as I said, that‘s not the point.

@Rainmaker what kind of HMD are you using? What was your process of starting DCS via virtual desktop and SteamVR?

@Rainmaker Maybe I was not specific enough: I had given VD a try before and it worked reasonably well. But I used VD with its VDXR runtime…so without the additional loop via SteamVR. To my understanding SteamVR is necessary though to get the mentioned apps (either the mixed reality or the hand tracking one) working. So this time I used VD and then started SteamVR and then DCS which ends up completely unusable even just in the main menu. I haven‘t even bothered yet to try the mixed reality app.

Has anybode got this to work with DCS? I strted Virtual Desktop and I set SteamVR as my OpenXR runtime, but when I started DCS, I only got as far as the menu screen and it was already super stuttery. OXRTKC indicates fluctuating FPS usually below 30. fpsVR is also running and shows the CPU to be the problem here. I have Quest Pro and of course, normally use Quest Link Cable with Oculus being the OXR runtime. EDIT: I use DCS standalone.

Generally speaking, in aviation Lat/Long is more commonly used. If you look at aviation charts or approch/departure charts, coordinates are usually Lat/Long. Aviation kind of derives from seafaring, which is one reason. Also Lat/Long is a system, that can be applied in a coherent way over the whole world, whrereas MGRS is clutter of squares if you look at it from further away, which leads to some "weird" effects at some places, where those squares converge.

@slyly666 Erwartungsmanagement...So wichtig!!! Wie bereits von einigen angemerkt wurde, ist es ja immer ein "...and beyond" Video. Heisst, dass die gezeigten Features ggf auch erst später erscheinen..."Versprochen" wurde somit also gar nichts. Davon abgesehen, helfe ich mal Deinem Gedächtnis auf die Sprünge. Hier mal ein paar Dinge aus dem 2023 video, die sehr wohl auch 2023 erschienen sind bzw implementiert wurden. - verbesserte Skins und Modelle diverser AI Flugzeuge (S-3, B-1, B-52...) - F-15E Early Access Modul - Normandie 2.0 -und natürlich so lächerliche "Kleinigkeiten" wie z.B. Multithreading und DLSS. Darüber hinaus sind auch Module erschienen, die im Video gar nicht grossartig aufgetaucht sind, z.B. die Sinai-Map. Oder features wie z.B. das neue F/A-18 Piloten Model, Double-Seat Mirage F-1.... Plus viele weitere Verbesserungen, die diesen Rahmen hier sprengen würden. Ich finde Deinen Kommentar also insgesamt unsachlich und ein Stück weit "undankbar". Für `nen Österreicher meckerst Du besser als ein Deutscher.... Was hattest du denn erhofft/erwartet?

@Qcumber Copy…that makes sense now.

Uhmm…. The whole purpose of ASW is to maintain a smooth experience when FPS drops below refresh rate. Half rate ASW is smooth for me at the price of occasional artefacts/ghosting/wobbling. It should definitely not be stuttery.

It‘s currently work in progress since the new pilot model.