Phantom711

@Schmied Was ist denn eine SLB? EDIT: Start-Landebahn? Also liegt der Marker auf dem falschen Flugplatz?

Ferraris exist and yet I don‘t have one. What I‘m trying to say is, that just because something is being offered by the manufacturer, doesn‘t mean it‘s being fielded by the military or at least not for everyone. The picture apparently shows a helicopter pilot. I don‘t know the particular system, but possibly the night vision on that one is being portrayed on that monocle, so a clear visor for night ops makes sense. If the general understanding in the F-16 and F/A-18 is, that JHMCS is only for daylight ops and NVGs for nighttime, then there is no need for a clear JHMCS visor. I might still be wrong though.

No worries. Glad you got it sorted out.

Just to recheck on that: Have you turned on eye-tracking and Quad-Views in the DCS settings also?

That‘s the one I was talking about as well….

Well…not an issue with QVFR really, but until recently it only worked with my Quest Pro when Eye-tracking was actually disabled in the DCS settings. It was counter-intuitive, but that‘s how it worked. Now last week I had to activate that option in order to have eye-tracking and hence QVFR working. Other than that I agree, that your issue might be the order of layers. There is an app called „XR Layer Manager“ or something like that. It will even recognize errors in the layer order by itself and offer a solution.

@C0re Am Ende ist ja entscheidend, dass Du das Final mit dem korrekten AOA fliegst, daher bietet sich an, vor dem 180 im Geradeausflug den Trim nochmal zu überprüfen und ggf. nachzutrimmen. In der Kurve ist die Anzeige dann ja immer etwas off.

If you read carefully, you‘d realize, that I did not deny that there is a problem with how the HMD is displayed in the Q3. The reason I brought up the Quest Pro is because it had been mentioned previously as well (maybe by mistake). Also I was rather pointing out, that fixing it might not be as easy as someone suggested. I‘m not saying it should not get fixed at all.

@bak3dp0t4to I would not interpret too much into it. I would also argue that „just making it adjustable“ is not that easy. You really only want some of the HMD symbology to be adjustable. All the symbols that need to by on top of the outside world objects (i.e. flight members, target designation boxes etc) should remain where they are now. And all of a sudden it‘s not „just“ a matter if sliding all HMD symbology up or down. The problem seems to be very specific to the Quest3 and maybe even among all Q3 users specific to how one wears the Q3. EDIT: BTW I am using a Quest Pro and it has never occurred to me, that the HMD symbology would be too high.

I‘m not an expert regarding base stations, but I recently bought the 1.0 base stations, because I thought I might want to get the BSB2e. Now I think I will just wait for the SLAM version of the Pimax Dream Air SE. Anyways, since I did some reading about setting up the base stations before…isn‘t there something like that they also need to be able to see each other? Sounds like this could be difficult, if you put them at 10 and 2 o‘clock. Maybe that was only for the 1.0 types and not the 2.0… Or you could also run a sync cable between them as far as I recall. But the setup recommendation for the 1.0s was definitely to have them at opposite sides of the room.

Does that function exist in the real jet?

This would be on Metas part to make it happen, not ED. I doubt, that DCS has access to the passthrough feature of Metas headsets. You need to step back and see the big picture here: how many people play in VR? How many of them have a headset that offers at least „good enough“ passthrough quality? How many of those have peripherals that are arranged in an almost replica-cockpit style that would make mixed reality even an option? You can get mixed reality working with virtual desktop and open kneeboard though. And also you can activate/deactivate passthrough by double-tapping on your headset if you just need the passthrough momentarily.

Also what I just tried, if you turn on „Tooltips“ in the game options, it shows you the name of a switch/button etc when you hover your mouse over it in the cockpit. The name seems to correspond to the name in the „controls“ options.

Problem is the naming convention. That‘s the one you are looking for. At least as a button that is…so it works on a rotary. As far as I can see, it does not exist as an axis though.

Sorry, but can‘t resist to follow up on this….and just out if curiosity. Why would this be the case? All Q3 can do passthrough. Or is that some requirement that comes with using Virtual Desktop and Open Kneeboard in order to get a Mixed Reality cockpit.

@QuiGon @VpR81 Dank Euch beiden für die Tipps. Dass ich mich mit meinem ISP in Verbindung setzen müsste, war mir auch schon bewusst. Ich werde das dennoch vorerst nicht weiter verfolgen, da ich es einfach nicht unbedingt brauche. Als Client bei meiner Virtual Squadron fliegen funktioniert auch ohne Probleme. Und ich hab Kabel von Kabel Deutschland/Vodafone…nur so als Info. Mein Post war nur als Anmerkung gedacht, dass es bei MP eventuell doch noch Hürden geben kann.

@Desert Drydock @sleighzy I think the pink outline is simply a side effect of how the whole passthrough works ATM. You are telling virtual desktop, that it should show the passthrough where ever the PCVR stream has a certain color (i.e. pink). So I‘m not sure you can get rid of the pink outline. Another thought I had on this was to „simply“ create an alternative cockpit for the Hornet where you would just make the relevant parts show up in pink (i.e. UFC, DDIs and AMPCD). That would save you the CAD work because those textures are already on the correctly shaped polygones. Just thoughts and very theoretical in nature…the passthrough of my QuestPro is not good enough to jump into that adventure.

I think this is probably the way you want to go:

@Desert Drydock I still think you got caught up between different terms here. Metas own Mixed Reality does not work with PCVR. Doesn‘t matter if you upgrade to Windows 11. I think the way people do get a Mixed Reality cockpit with their Quest3 is to use Virtual Desktop which allows passthrough of certain colors and Open Kneeboard to get that color in the desired shape into DCS. There are videos on youtube about this. but since you want to send the Q3S back anyways, go and get the regular Q3…pancake lenses are so much better. EDIT: Oh and „Windows Mixed Reality“ has absolutely nothing to do with it. I was a program to link certain headsets like the HP Reverb G1 and G2 (and others) to the PC.

Bedenke aber noch, dass die Preise auf der Pimax Seite immer erstmal ohne MWSt. sind! musst also ein bisschen und dann noch ein bisschen oben drauf legen.

Also ich hatte vor etwa einem Jahr mal versucht selbst zu hosten und es hatte nicht geklappt. So bin ich auf die Problematik überhaupt erst gestossen.

Du hast doch bestimmt irgendwelche DCS module? Dann hast Du auch einen Account. Oder fliegst Du nur Su-25 und T-51 auf Caucasus und Mariannas? EDIT: Ach so…das läuft dann über Steam…hmm…

Und da kann eventuell der Hase im Pfeffer liegen. Ich musste bei mir leider feststellen, dass mein Kabel-Router nur eine IPv6 Adresse hat. Vielleicht war ich aber auch einfach zu doof…hab es dann nicht weiter verfolgt, weil meine Virtual Squadron ja einen Training Server hat. Aber Multiplayer öffnet auf jeden Fall nochmal eine ganz neue Tür…

@C0re Gewissermaßen. Die Light hat ja die gleiche Auflösung wie die Crystal OG, aber eben kein Eyetracking. Eyetracking und das damit verbundene Dynamic Foveated Rendering bieten halt ein nicht unerhebliches Plus an Performance bei hoher Auflösung da wo man gerade hinschaut. Q3 und Pico haben von Anfang an eine geringere Auflösung. Die Light hatte ich aber nicht erwähnt, weil sie neu über Deinem Budget liegt. in ein paar Monaten wird von Pimax wohl die DreamAir SE erscheinen, die klingt für mich auch sehr interessant. Als Referenz: Ich hatte mit einer HP Reverb G2 angefangen und bin jetzt seit gut 2 Jahren mit einer Quest Pro unterwegs. Ich hab auch noch eine Pimax Crystal, die ich von jemandem hier im Forum erstanden hatte und die auch sehr gut funktioniert. Insgesamt bevorzuge ich aber tatsächlich die QuestPro, obwohl sie auf dem Papier eigtl die schlechtere VR Brille ist.

@C0re Mit Deiner Hardware bist Du ja gut aufgestellt, da wäre es wirklich schade DCS nicht in VR zu geniessen. In dem von Dir angegebenen Preissegment sehe ich hauptsächlich die Quest3 oder Pico4 als naheliegende Option. Wenn Du keine Scheu vor dem Gebrauchtmarkt hast, gehen in Deinem Preissegment natürlich noch andere Türen auf: die Pimax Crystal OG wäre dann zum Beispiel drin. Bei neuen Headsets würde ich in der Regel davon abraten etwas zu nehmen, dass keine Pancake Linsen hat.