Degraded navegation with human RIO

[Tulkas]

We are encountering a recurrent problem when flying with a human RIO. It does not happen always but often, too often.  We fly always from the boat so we have no checked if it also happends from shore.

Right from take off appears that all waypoints have drifted. Ten or more miles. Coordinates are correct for the waypoints and they have correct position regarding each other. Datalink contacs appear on the correct position regarding the Wps, but our plane thinks is somewhere else. An INS fix does not correct it.

It has happened to more than one RIO and so far we have not been able to detect some error on the start up rutine so I wonder if anyone alse has encountered the problem and has a fix for it or maybe knows what are doing wrong.

 

thanks!

[IronMike]

42 minutes ago, Tulkas said:

We are encountering a recurrent problem when flying with a human RIO. It does not happen always but often, too often.  We fly always from the boat so we have no checked if it also happends from shore.

Right from take off appears that all waypoints have drifted. Ten or more miles. Coordinates are correct for the waypoints and they have correct position regarding each other. Datalink contacs appear on the correct position regarding the Wps, but our plane thinks is somewhere else. An INS fix does not correct it.

It has happened to more than one RIO and so far we have not been able to detect some error on the start up rutine so I wonder if anyone alse has encountered the problem and has a fix for it or maybe knows what are doing wrong.

 

thanks!

You are not doing anything wrong. The catapult shot blasted your IMU, which was a thing in real life. It is possible if there is a high latency between pilot and RIO that this effect is more likely to appear though, due to rubber banding or similar, but that is just a wild guess. It should be rather rare to encounter it else.

[Tulkas]

Thanks for the answer. Interesting. We have RIOs much more prone to suffer this problem, almost every mission. Others very seldom have seen it. But if the IMU is damaged, shouldn`t we get advisory lights? We always look at the caution panel but it does not appear to be caution lights associated to this error.

I understand that this IMU fails are not connected to random fails so it is not possible to try to turn off this fail possibility?

 

Edited December 15, 2021 by Tulkas

[IronMike]

1 hour ago, Tulkas said:

Thanks for the answer. Interesting. We have RIOs much more prone to suffer this problem, almost every mission. Others very seldom have seen it. But if the IMU is damaged, shouldn`t we get advisory lights? We always look at the caution panel but it does not appear to be caution lights associated to this error.

I understand that this IMU fails are not connected to random fails so it is not possible to try to turn off this fail possibility?

 

 

If you are not getting a failure, then something else might be happening. It is also unusual for this to happen more than "extremely rarely". We'd need to know more details to investigate this.

[near_blind]

Shots in the dark to eliminate the basic stuff:

Are you inputting ownship position?
Are you doing a stored heading alignment, and if so, what's the boat doing?
Are you messing with NAVGRID?

[Tulkas]

18 minutes ago, near_blind said:

Shots in the dark to eliminate the basic stuff:

Are you inputting ownship position?
Are you doing a stored heading alignment, and if so, what's the boat doing?
Are you messing with NAVGRID?

1.No, we are doing carrier aligment

2.Yes. Sailing through the seas (other Tomcats flying off the same boat have no trouble)

3. Yes we are. We love NAVGRID

[near_blind]

With ASH be careful that the carrier doesn't make any sort of turn in the time between you spawn in and you are connected to SINS and have begun your alignment. 

With NAVGRID, well, it can happen with any coordinate entry but Jester loves doing it while entering NAVGRID, if the CAP isn't set properly and the buffer isn't cleared, it's possible to accidentally set a waypoint position as the ownship position, which will offset the aircraft's perceived location. 

[Tulkas]

Thanks with the inputs.

I will pay attention to the carrier course, but having several F14s aligning and take off at the same time and most of them having no problem I'd discard this.

Jester is not a problem, is with a human RIO.

NAVGRID input error is one of my main suspects. It's easy to mess if you don't notice that you have something hooked and start introducing coordinates. But a NAV FIX should put you back on place and fix the issue and apparently it does not. User error is still my main suspect and where we focus our investigation, the second one would be some kind of pilot-RIO desynchronization over the net.

We don't really have dedicated RIOs per se, we all are mainly pilots, but in order to enjoy this amazing module to its full potential we try that every pilot have basic knowledge on the back seat so we always have a fully crewed Tomcat. And then, you know, if you sit a stick monkey on the back and starts to push buttons anything can happen. Literally. We have a few good stories  on that   I personally don't fly online mission on the F14 if we are not two on the plane. The work HB have made with Jester is brilliant, but nothing compares to the fun and interactivity of having another person on the back. It really has brought a new level to the simulation.

Edited December 16, 2021 by Tulkas

[near_blind]

Indeed! I wasn't trying to imply jester was the issue, just explaining why I suggested input error might be. I hope you're able to narrow it down.

[IronMike]

Given the frequence, given the fact that most are fine, given the fact that NAVGRID is used a lot - I, too, would suggest that it may be input error with Navgrid here. Good thinking @near_blind