Phantom711

Well…I clicked on the „Beta Channel“ for the HMD app and then simply forgot about it. But I guess that is the kind of snarky comment that I get, if I openly admit my own mistake, right? And also what does the one have to do with the other? Do I not deserve SSW Auto to work properly because of it?

I think what might confuse people about the CAGE/Boresight mode is, that they know the terminology from other Jets like the F-16 or F/A-18 and expect it to work the same way. It confused me initially at least. I guess in the Phantom, that mode is not a mode designed primarily for dogfighting, but rather against unsuspecting or less maneuverable targets (i.e. bombers) since the pilot needs to stabalize the pipper on the target quite well in order to have the WSO achieve a lock. Might be worth mentioning that aspect in the manual.

My quick tests showed, that it works nicely with the WiFi 6 extender. As I said, my gripe with SSW is mainly, that it doesn´t seem to kick in properly when dropping below refresh rate.

What you are showing is just the OpenXR Toolkit Companion....that should have absolutely nothing to do with your problem. I don´t have a Pimax, but my guess would be, that you don´t have your Pimax software set to be the OpenXR runtime. Check for that in the options somewhere. EDIT: Apparently you also need "Pimax XR". Another software to run DCS(or other titles) in OpenXR without SteamVR. That´s what my interent search came up with.

I wanted to give VD another try, so I bought a better Wi-Fi extender today (one that supports WiFi 6 instead of just WiFi 5). My first tests definitely came out better than with the previous WiFi extender. This was about 2 hours ago. Now I wanted to try out some more but all of a sudden it won´t connect to my PC. It says, or rather "claims" that the streamer is using an older version and I need to update it. So I used the "Check for updates" button on the Streamer App and it says that there are no updates. I even deleted and reinstalled a freshly downloaded version without any change. Version of the streamer is 1.30.5. EDIT: my bad. Had the HMD App on beta and streamer still on release version. One other thing: Is the automatic option of the motion reprojection (SSW) really such garbage? On my tests at least it normally failed to kick in appropriatley. With ASW from Oculus you hardly even realise it, when it kicks in.

Not sure, but I believe it is for Airlink only...but I´ve never heard anyone mention it as a cool feature or something. I think this would dynamically adjust the resolution. I don´t know if this works at all though. And I doubt that it would look nice.

Nö. Quest Pro hat auch kein Auto IPD und eyetacking/QVFR funktioniert bei mir ohne Probleme.

They all do the same thing, but will get multiplied with one another. So for a start it might help to leave all at 1.0 and only manipulate one of them. It does no harm to change them, as long as you know, what you are doing. (Not sure actually, if the OTT/ODT settings just override the Meta App settings or also multiply, which I would guess) I would avoid contradictory settings though…like 0.8 in the Meta App and then PD 1.2 in DCS. Again, it shouldn‘t do any harm…it‘s just pointless… I have the Meta App set to 1.3 (max), but since I want more, I have the PD in DCS set to another 1.3 or so (That‘s with a 4090 though and DFR on the QPro).

And maybe don‘t even fiddle around with ODT or OTT yet, until you have solved your stability issue in the first place. If you used OpenXR Toolkit Companion, you might want to temporarily disable that as well.

When you click on „Quest Link“ and then the little window opens up, where it still says something like „Rift S“ and there is the blue „Launch“ button at the bottom…on the top of that window you can/have to cycle between cabled link and Airlink. For the FOV…don‘t forget to press the SAVE button to the right of it before launching the Meta PC App/starting Quest Link. For some of the functions, OTT possibly needs to remain running in the background.

Still using Oculus Tray Tool, but Ivam also still on Win10. Here are my settings: Please note, that I have a Quest Pro, but it should be the same for the most part. Except for Encode Resolution…but opinions on that vary widely. I‘ve never had a problem with cabled link. Two questions though: 1. Are you using the official cable or an aftermarket one? Did it pass the speedtest alright? 2. Just in case you ever experimented with the Meta Airlink at some point…make sure in the Oculus Link Launch window, you have „cabled link“ selected.

So what you are saying is, that the throttles between pilot and WSO are not synchronized and they don‘t move in the backseat, even though the pilot is moving them?

@Qcumber I am not saying it is a stupid idea, I am just saying it is quite an undertaking. So basically you would want to start a thread, which you (or whoever has the authority) would update on it´s first page frequently...like it was done with the OpenComposite thread back then? Kind of? It would still be open for discussion etc... And instead of saying what to turn on or off, one would rather explain, what it actually does and which positive or negative impact it has (benefit vs. cost). As a baseline one should probably start with the erespective software, that conncts the HMD with the PC (i.e. WMR, Meta PC App, SteamVR) and the DCS settings. Then one could look at the optional stuff, like OXR Toolkit Companion.. possibly QVFR... One should probably limit the scope of the thread to currently available HMDs (as new) and which are also reasonably common. And it should also not be a detailed guide on setting up your HMD.

The WW Orion throttle has underlying buttons on the throttle axis, that you can assign to the respective postions (IDLE detent off/on). Check my picture for reference.

Wenn ich das richtig verstehe, kann man in den Special Options der F-4E doch auch die Simulationsrate etwas herabsenken.

@Qcumber What you would want do do, would be quite an endeavor. Think of all the different HMD types, their respective optional add-on software which then meet all the different users with all their different hardware and personal preferences. And in that regard, who decides, what is good or bad advice? Doing this for one family of HMDs alone (i.e. Quest) is quite a task already. And such threads with lots of discussions already exist... @WipeUout Yeah....I was gonna say the same...I had some questionmarks regarding Glide´s philosophy there as well. Besides that: Now I don´t have a Pimax, but a Quest Pro at the moment and I have a question regarding the "lock to half frame rate" feature of Pimax, that you mention. Does this provide a visually appealing image? Reason I am asking is, if I do this with my QP via Oculus Tray Tool or manually, objects that pass by my 3-9 line, are getting blurry. To clarify: this is with half frame rate FPS (locked) and ASW (Motion Reprojection) OFF. I am thinking, all the HMD has to do, is to show every frame twice....don´t know why it´s getting so blurry. Is this not the case with Pimax? If so, it might make a Crystal Light more interesting...even without the DFR (which I really enjoy in my QP). Thanks in advance.

Well…because it would require measuring equipment in the external tanks and the respective wiring to report it to said gauge in the cockpit.

-Bumpedeebump-

But by slewing it and thereby changing the offset and it´s coordinates one can nicely determine the distance to friendlies as a FAC(A). So in fact I like that aspect of it, but I don´t know if this is rather a bug or a feature.

Just found an error with O/S waypoints. In the track I have waypoint 1 set at Tonopah. I set my elevation to "feet" on the UFC. I create an O/S waypoint just 10m south of wypt1 at the same elevation. I select my ATFLIR. I select wypt 1 and then O/S as TGT designate. I switch from the HSI to the Data page. Both Data page and pod show the correct elevation for the O/S waypoint. But as soon as I start to manipulate the O/S waypoint with the pod, the elevation value for the O/S waypoint on the data page shows a completely different value which in fact equals the correct value in meters, even though it still says "FT". The value shown in the pod is still correctly showing feet. O-S wypt elev error.trk

@kraze Nevada map: Constant Peg III also worked for me. I only get contact on the Flogger though.

What is your expectation of pointing the reticle at the target? What do you think this would do? The Jester Context button only works as you have contacts on the scope. Short press cycles through the contacts. Long press locks the respective contact. Double press goes back to search. Try the Instant Action mission on the Mariannas: Putting the fish to bed. Works as advertised for me.

1. Die in diesem Thread hier erwähnte Pimax Crystal LIGHT hat kein Eyetracking und somit auch kein Dynamic Foveated Rendering (das Du hier meinst). 2. „weniger Leistung“: weniger als was? Weniger als ALLE anderen VR Brillen? Ist doch unrealistisch. Sie braucht halt weniger Leistung als wenn man sie ohne DFR betreibt. Ggf auch weniger als andere Brillen ohne DFR trotz geringerer Auflösung.

So richtig helfen kann ich Dir nicht, aber ich kann mir kaum vorstellen, dass man da etwas „unwiderruflich“ überschreiben kann. Erstmal würde ich nochmal versuchen die Prozedur wirklich penibelst und langsam noch einmal durchzuführen. Da Du ja offensichtlich der englischen Sprache mächtig bist, kannst Du auch einfach in dem von Dir verlinkten thread fragen. Ansonsten…gibt es vllt so etwas wie einen Firmware reset, oder so?

@Rufuz64 The way it is now, is realistic. I guess the fact, that the Stores Page still has the option to change the codes, is just the remainder of how it was until last patch and is itself actually a bug now.