Hextopia

I think the community as a whole just assumes it's intended behavior, since the AWG-9 has so many limitations that are accurately modeled, and many RIOs don't have an extremely detailed understanding of how it all operates under the hood to begin with.

This is something I routinely see myself in multiplayer, and I (and many other RIOs I fly with) assumed it was just the actual AWG-9 modelling. After looking through all the documentation I can find and testing in singleplayer, I can't get the repeated ghost contacts problem to show up when looking for it. If it's caused by INS drift, it's an EXTREMELY aggressive drift to make the contact drift 10s or 100s of NMs between radar hits while the own A/C INS solution is only drifting maybe 1-2NMs. It shouldn't be related to datalink either, as the contacts that are duplicating are radar contacts, not datalink contacts.

I'd like to suggest adding in DDD range +/- keybinds for the RIO, since having to bind every individual range button is a pain in the ass. And before someone says "but those don't exist in the real plane", in the real plane I'd just rest my hand on the panel and push the buttons. I need some abstraction to make flying in VR without a full sim pit a little easier.

If a RIO jumps into a tomcat with engines already running and has their pilot binding for engine cutoff pressed it will desync the engines and turn them off, causing power loss for the RIO and the appearance of no engines running in external views.

SA-11 CC's and Launchers will sometimes not move after firing. They refuse to retract their antennas and move again, and it's not clear why this happens. See track for examples. SA-11 Not moving.trk