RogueRunner

nullWasn't fixed in the last patch yes

Confirm this behaviour

Also Sperenberg RSBN (ch 28 per F10) for me (mig21) did not work at all.

Some invasive plantlife there

Quest 2 via Virtual Desktop RX7900XT GPU

The Jester wheel in the F4 is only partially visible in VR (quest 2). Heatblur is indicating that this is an issue on the DCS side and that a fix ED implemented already was only partially successful, as is the case with me, I still need to do the workaround everytime I want to fly the F4. Is this still being looked at and when can we expect a resolution?

lemme go poke them in the VR forum

That does work but kinda a PITA to change everytime I want to fly the F4. Did ED indicate that there is a solution in the near future?

What is the procedure to launch them in HOJ if I may ask? i cannot find information regarding that

it's in a big hole N35.20.354 E036.04.902

How do you clear the cautions when you jump in on a hotstart?

Very frustrating. Also using AMD 5700X3D and have that exact problem. Will go look at ST tonight

13 modules of mine was affected

See Noticed this first on the F16, same is happening with my Mirage F1, the F18 works.

Not just the F16 it seems, same with the Mirage F1 also.

As per the topic. Simply cannot map any axis to thrust.

For me none of the solutions worked. My pixel density in the settings VR tab was set to more than 1. When I set this to 1 the solutions provided here worked for the Jester wheel. I have not tried the other popups yet though.

not just TMS AFT, tried CZ on the radar and on the TGP MFD. Is the masked issue a bug?

I understand that if you designate something with the TGP in PRE mode an offset is created. My problem is I cannot marry up the steerpoint and the TGP again afterwards in PRE mode however many times I press CZ. Something else I need to do? Pressing CZ ini NAV mode will reset the steerpoint to the correct place but the TGP never points to the steerpoint again unless I change delivery modes. This means essentially I can drop things in PRE mode once, since I can never get the TGP to look at a steerpoint or HMCS designation again it's almost impossible to deliver something in PRE again. I'm sure this is just operator error but I canoot figure it out.

Still happening, changing the spawns to 'start from ground' is a workaround.

I get that sometimes binding will just stop working. Had it on the F16 and now it happens quite regurly for me on the M2000. In the 2000 today my PTT buttons stop working, trying to bind anything to these buttons does not work again. If I jump into a Hornet which uses the same buttons on my warthog for PTT it works. Only way to make it work is to delete the throttle config and rebind everything again. Happend twice today on the 2000, like I said, happened previsouly on the Viper but never again after I deleted the config file.

what exactly did this entry in the patch notes fix? Before the patch I had to press CZ OSB on the ground radar to reset the nav waypoints after creating a SPI. The HOTAS CZ function did not do this. I could never figure out from the posts if this was intentional and working as is or a bug. The above entry I thought was to address this but it still is not working.

Track file Notice how the time to impact reaches zero and then it still takes about 5 - 10 secs before the bomb arrive. Sorry about the views, was not using headtracking for this one. gbu24.trk

I looked but could not find a way to move one radio to receive on the left ear for example and the other radio in the right ear. Is this possible?