RIO wing sweep bug temporary fix (wings in oversweep by default)

I've been aware of this bug since day 1, but the Supercarrier has made it even more dangerous and annoying. Because any multiplayer client can report a collision to any other client, the RIOs who occupy the slot of an aircraft on the carrier deck cause anything within the wingspan of the F-14 to instantly be hit and destroyed.

Additionally, with the new supercarrier spawns and spawn protection any time a RIO is in a seat the pilot must cycle the wings or he is blocking all of the spawns around him due to the RIO's client reporting the wings out (which I assume is a hitbox related check).

This would all be solved easily if the default wing position the RIO sees is the wings swept fully aft in oversweep upon joining into the cockpit. The sync could occur as normal when the wings move as always, but this isn't as important of a problem in the air because:

1. The wings will almost always move shortly after the RIO is in the seat since wingsweep is constantly changing.

2. The RIO seeing the wings swept temporarily doesn't matter for any practical purpose and would rarely be noticed.

3. The RIO seeing the wings swept is actually less dangerous even in the air during formation flying.

From my experience in MP, most of the time RIOs are going to be joining their pilot on the ground or carrier before a sortie anyway and the wings are in oversweep by default from a cold start or hot parking start. So the RIO would actually see the correct indication in *more* cases than before.

Does this wing cycle have to be done with power on, or can we "cheat" the system by cycling the E-sweep handle before startup?

The wings have to actually move, so you have to have hydraulic and electric power.

On Grouned happens too .

If the Rio Jumps in after a cold Stark you have to cycle the wings to update the wing position status to the RIOS POV.

This is a good idea

+1

Is there any news or response from Heatblur about this?