MP RIO Crash - No RIO Control After Rejoining

[Whiskey11]

The other night, myself and SK0 were playing around with the LANTIRN pod on the Through the Inferno Persian Gulf Server. I was the RIO. At one point my game crashed (unknown if related to the F-14 or not as my game locked up with the Harrier during the live stream earlier, a few times, as well as since then). After rejoining, I attempted to rejoin the RIO seat and upon rejoin, I was able to get in the RIO seat, but nothing worked. I could not control the LANTIRN pod, nor could I control the TID cursor or anything involving the RIO control stick. None of the pit controls worked either.

 

This was on the Open Beta Server Build. LANTIRN pod was on, and a bomb was enroute to target. I had just latched the target with the laser because SK0 was being lazy and dropped it far enough off line that I had to latch the target immediately to get the bomb to the target. My game crashed at this point. SK0 reported that the laser remained latched, target remained locked, and bomb impacted the target without any problems. Upon returning to the RIO pit, SK0 advised his LANTIRN repeater display showed the LANTIRN pod still locked onto the target with laser active. My screen showed the LANTIRN pod pointing at the ADL straight ahead and I could not control it, nor any other aspect of the RIO pit. Exterior model showed the pod pointing straight ahead for me, and at the target for SK0. SK0 attempted to drop another GBU-12 on target but it did not work even though his screen showed locked and latched (laser active) while mine did not.

 

I also noticed that the RIO pit did not have the same buttons selected as when I crashed. The red lighting was off, the bomb panel had been reset to it's default panel state, and the LANTIRN/TCS selector was switched back to TCS from the LANTIRN pod. SK0, reported his repeater still showed the LANTIRN pod info and not the TCS. SK0 also reported not being able to bring up Jester (this is already reported I think) and Jester never showed up even after I exited again to get in a different aircraft.

 

I'm at work at the moment, I'll try and dig up the respective LOG file of this occurring when I get home.

 

Cheers and thanks for the otherwise epic module! I'm guessing this is a DCS related error (not saving panel states, etc), but figured you guys should know! Thanks again!