Mustang25

I'm having an issue where one of my devices, a VPForce Rhino, doesn't show up in DCS while in VR mode (using a Varjo Aero). All my other devices register in the controls section and when I switch back to 2D DCS the Rhino shows up again. I've tried replugging and rescanning devices while DCS is running without success. Also even when DCS isn't detecting the device, the VPForce configurator software can still see it and registers the inputs so it seems like it's a DCS-specific issue. Does anybody have any suggestions for what could be wrong/how to fix it? UPDATE: Problem seems to be solved for the moment! Not sure if it was restarting my entire system or swapping between SteamVR and VarjoXR that fixed it but it is resolved for now.

Back in the ground crew comms menu is the option to hide the interface once you're done.

That’s what IFF and NCTR are for. The absence of datalink doesn’t make you ineffective.

@NineLine Can we get any update on this issue please? Our current options are to either have an unusable UI or an unusable Petrovich and that's not really conducive to having a good time.

I totally support this. Can't tell you how much time this mod has already saved me, adding this would make it even better!

You can change the Burst Altitude (BA) in the CTRL page. I've found it needs to be set to at least 1000ft to be effective, I usually have it at 1500ft which is the default at least for the 105s.

It actually was posted in the Viper forum then moved over here I guess by one of the mods. No idea why it got moved here though.

Just wanted to wish my beautiful bug report a happy birthday. @NineLine or @BIGNEWY can we get a birthday cake to celebrate one fantastic year of hearing nothing from Ugra?

I believe that only the impact azimuth setting is functional and impact angle has never worked.

I noticed this yesterday as well (unfortunately no track). Had a bunch show up immediately as PGM1 even though the ellipsoid was still really large and it never got smaller. They also never seem to time out and go green either.

For the HAD, class 4 contains all the EWRs if you want to filter them out.

@BIGNEWY I just tested this on the latest OB and it is still a problem.

It is fixed internally, we’re still waiting on the next OB for the fix to get pushed out to us.

Hey @BIGNEWY, do you know if there was any update on this? It's been going on more than 7 months now for what seems like such a simple fix.

What are you talking about? It took Deka literally less than a week from the bug being reported to them fixing it, not to mention that they are also celebrating Chinese New Year during this time. Besides, you were looking at the stable branch patch update today not OB.

It should be noted that IRL and presumably when we get DTC that those points on the HSD are really just steerpoints. So the accuracy of those threats will come down to the accuracy of where those steerpoints are placed, we're just lucky now that they are all autogenerated from the unit locations in the ME.

You guys are surviving aircraft damage? Lol. I don't remember the last time I was hit in the Viper where my pilot wasn't instantly killed.

Correct, it’ll be the -229 and APG-70.

Already reported

Not necessarily, it just means that you’re picking up their radar emissions. Think of it like seeing someone’s flashlight from a mile away. You can see the light but it’s not strong enough to actually illuminate you. Also sidelobes are a thing but I don't know enough about radar to explain it nor do I know if DCS simulates it.

Those sound really good!

Ah, that's interesting, good to know! And yeah, I guess we got a bit off track. My initial question was about the seeker search area but then we drifted to the maneuver footprint in following posts.

Wait if they're not POS shots then why does switching between POS modes in Wags' video change the HARM footprint displayed in the HAD (and also the POS mode is displayed in the bottom right corner of the HAD page)?

Does anyone know the emitter search footprint for each of the POS modes? It would be helpful to have that kind of info for figuring out launch parameters with HTS I think.