Phantom711

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?

Hi...I have a Hornet Radar question: I set the RDR for the specific weapons as given by some standards of my virtual squadron (i.e.: 80NM for the AMRAAM etc...) via the SET button. Reason I mention this is mainly to illustrate the problem and also because it kind off negates one possible way of "canceling" my following problem. Let´s say I use RWS and lock a target (STT) at 20NM. If i then decide to undesignate via the NWS button, the rdr goes back to RWS as expected and remains in a range scope where the former target is somewhat centered and there is aslo still the AMRAAM WEZ displayed. No problem so far, BUT no matter how often I press the WSS right for the AMRAAM again (or an other weapon, the associated 80NM scope will not come up. The track has to fade out completely for the weapon specific scopes to be available again. One could press the RESET button on the right, but that defeats the purpose, because it sets the weapon specific radar scope back to default (40NM for the AMRAAM). I mean WTF...I UNDESIGNATED the target...I want to have control over my radar back!!!! I can post a track if required. No, I don´t have evidence, that this is wrong. But it does not seem very plausible.

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?