Phantom711

Uhmm…yeah, but this is not a native refresh rate of the Q3, so it will be a stuttery experience.

The numbers are for the year. (I believe the year it will graduate or fiscal year it takes place). The B in the middle is for B-Course and the other letters have something to do with when in the fiscal year it started or ended and also a reference whether it was like the 1st, 2nd or 3rd course within the year. Sorry, still a very rough explanation, but you catch the drift. Maybe it helps to deduct more info if you have access to some B-Course data.

@lazduc Hey…just wanted to say, that I find it pretty cool, that someone at your age ist still interested in flighsims and now even steps into something as fancy as VR. I hope you still have many happy years ahead of you with this hobby and whatever else amuses you.

Ich habe mir so viele Funktionen wie möglich auf Stick, Throttle und Throttlebase gelegt. Zugegeben, ich habe auch noch weitere Eingabegeräte, wodurch das ganze dann irgendwann recht einfach ist. Den Rest kann man ja meist per Maus im Cockpit klicken. Man muss sich also gut überlegen, welche Funktion man eher schnell griffbereit haben will. Aber klar, oft findet man einen Button ggf trotzdem nicht so einfach. Wie ich bereits vor 1-2 Tagen in einem anderen Thread geschrieben hatte, habe ich eine Quest Pro, welche unten ein stück weit offen ist, so dass man da recht bequem durchschauen kann. Womöglich gibt es auch für andere Headsets solche Facemasks. Anders als man vllt denken könnte, reisst es mich nicht aus der VR Immersion.

Ok...die Einstellung müsstest du mir bitte auch mal zeigen. Bei mir ist es auch so etwa wie Landei beschreibt: Klar kann ich den Cursor bewegen, aber die kleinste Kopfbewegung versetzt den Cursor um eben diese entsprechende Distanz. Ich kann den Cursor dann auch wieder weiter mit der Maus bewegen, aber es ist eben die ganze Zeit, als ob 2 Geräte (Maus und Headset) dem Cursor Input geben. Ja, der Cursor verschwindet auch höflich, wenn er nicht genutzt wird.

@BuzzU No…the WW F-16 throttle never had that „issue“.

I just tested my connection with the official Oculus Link cable…I got 2.7GBps…just for your reference.

Have you checked, if this is really your fastest USB-Port? Oh and even though not directly related to your problem…definitely try the 72Hz mode. You are more likely to match 72 FPS than 90. So there is also lesser cases where it drops into ASW. This is also why you get 45 FPS in MP. Your PC simply can‘t achieve 90 FPS so it drops to half rate ASW. Now this could still be the case even with 72Hz, but not as often.

@Yurgon Dass etwas ernsthaftere Sim-Fliegerei so keinen Spaß macht, kann ich schon verstehen. Aber klar, da muss sich jeder unter VR halt schon Gedanken machen, wie er das vernünftig löst. Kein normaler Mensch kann sich einen ganzen 9-liner + Remarks/Restrictions merken oder die Koordinate direkt in Echtzeit eingeben. Es gibt dazu wohl 2 Lösungen, die mir einfallen: 1. Mit OpenKneeboard und einem entsprechenden Tablet (zum Zeichnen), kann man wohl direkt Notizen aufschreiben und in VR sehen. Hab ich aber noch nie probiert. 2. Ich selbst nutze eine Quest Pro. Die ist unten offen. Ein Feature, von dem ich erst dachte, dass es mich womöglich stören würde, aber inzwischen möchte ich es nicht mehr missen. Man kann darunter recht bequem durchschauen und mit Zettel/Stift arbeiten.

@SharpeXB Well, as far as I can tell, Virtual Desktop has its own Motion Reprojection. I think it‘s not as good as ASW, but it‘s there. You can also run Quad Views with VD, so apparently Meta allows the VD app to grab the eye tracking information from a Quest Pro. The DFR is then done in VD, right? Quest Pro and Quest 3 don‘t have a video cable either. So basically what I am saying is, VD or something like it for the Apple Vision Pro it is not completely unthinkable.

Yes. https://www.pinterest.at/pin/735846026589065621/

@venec Would be great, if you could share the files. This pretty much exactly mimics the Winwing MIP…. Passthrough in the Quest Pro isn‘t all that great, but I would like to try if/how it works in principle.

@silverdevil Thanks for looking into it anyways…

dcs05Feb.logdebrief05Feb.log It happend again this session. MP first and then SP...don`t know if they are both in the respective logs, but I think so. Please if someone could check my logs again...right before the end...that`s where I had massive freezes and I start to believe, it has to do with the Supercarrier Module. What would be the procedure to uninstall and reinstall the SC again? If I click the trashcan in the modules section, would it then reappear as available DLC...I mean...I guess so... EDIT: Uninstalled/Reinstalled SC. Next flight was without problems. But we‘ll see…

If you fancy a force sensing stick, then „Realsimulator“ might be for you. Other than that, I also use WW for the throttle, rudder, PTO and MIP.

Ok. Did another testflight. This time single player. Supercarrier Launch mission with the F/A-18. first time was a huge freeze-fest.dcs_freezes.logdebrief_freezes.log Then after restarting DCS twice and also reinitiating Oculus link...flawless....at least the few minutes that I did. But I did pretty much the same as the first time.dcs_no problem.logdebrief_no problem.log So what is the difference between the first and second attempt?

Why don‘t you just invert the axis under the „Axis tune“ tab in the DCS controls settings. Done.

dcs.20240204-164849.crashdcs.20240204-164849.dmp Unzipped

dcs.log-20240204-164849.zip Ok. This is the only one from today. Just checked. file extensions are turned on.

Hello... I experience game crashes very freequently and especially (but not necessarily only) during MP missions when others do not encounter any server issues or anything. For me the game basically freezes. Sometimes it recovers from this after a few seconds (30s maybe) sometimes not and sometimes I am dead by then. I thought the problem was gone since I did a DCS repair and also chose not to use Oculus Tray Tool anymore, but today it appeared again. dcs.log.oldCarrier_Practice_2.3.3_day-20240204-175148.trk Don`t know if the trackfile repliceates that as well. My specs: 13700K/4090/64GB RAM DDR5 Quest Pro via cabled link Thanks for your help

RDR_Weapon_Set.trk @Tholozor So here is a track I just made to illustrate the matter. I simply took the MAriannas Free Flight instant action. At the beginning I select the AMRAAM and manipilate the radar settings (80Nm, 80AZ, 4Bar). I turn north and lock one of the Strike Eagles inbound to Andersen. Scope autoranges down to 40NM scope. I undesignate. Now neither selecting AIM7 nor AIM120 via WSS selects the respective radar setting I had set previously. Pressing RSET sets it back to how it was before I changed it to my liking (so the DCS default). As I said previously...I am not saying it is wrong...just asking if this is desired behaviour after undesignating. Let me state that I explicitly thank you for looking into this. EDIT: So I see 3 possibilities here: 1. This is "correct as is" according to public available knowledge. 2. This is not correct and after undesignating a weapon selection via WSS should directly invoke the desired radar setting. 2. Or this is not correct and after undesignating and WSS would still not invoke the desired radar setting BUT maybe the RSET button is not modelled correctly and should not revert the settings to the DCS default but the previously SET radar parameters.

Moin, meine Dienstag direkt bestellten Winwing Ruderpedale (ohne Dämpfer) sind heute angekommen. Machen so weit einen soliden Eindruck...alles aus Metall. Nun hatte ich bisher die günstigen TFRP T.Flight rudder pedal von TM...es war also nicht schwierig, sich zu verbessern. Da ih bisher keine Hubschrauber fliege, habe ich kein sonderlich emotionales Verhältnis zu rudder pedals, ich wollte nur etwas, das etwas sensibler reagiert und man somit auch verlässlich formation take-offs machen kann. Ein erster Rolltest und take-off stimmen mich dahingehend auch optimistisch. Wenn Ihr sonst etwas wissen möchtet...go ahead. Ich kann sie nur eben nicht selbst mit Virpils oder MFG vergleichen.

Das lese ich etwas anders. Eher so, dass sie diese Woche noch an diversen Dingen arbeiten….

Hmm…not sure if you understood my problem here really. As long as there is still some „residue“ of a track file, I can not invoke any weapon specific radar scope. If I undesignated a target…and let‘s say at that time the radar was in the 10NM scope, then pressing the WSS forward (AIM7) or right (AIM120) does not invoke a change to the associated radar scope. And this is not just about range, but also bars, azimuth scan and PRF selection. Yes one can manually change it again…but ffs this is a single seat jet…I don‘t have time to press buttons on a DDI while flying formation and checking the SA page shortly prior a re-attack. Anyways…in my virtual squadron the more experienced guys have a solution: go BST briefly, then GACQ (WSS aft) and then WSS right or forward to your liking and the respective AIM7 or AIM120 radar scope is being selected. So I am not saying it is wrong as it is. Since there is a workaround to achieve my desired effect, I still consider that as „case closed“.

@Condor060 I am absolutely not familiar with Varjo, but since you seem to launch via SteamVR.... Do you have SteamVR set as your OpenXR runtime?