What is ROS as a measure of distance on the HSI, what did I miss?

[AvgWhiteGuy]

I was flying a mission and noticed my distance being displayed as 8344.37 'ROS'. This was on the HSI as distance to Carrier TACAN and HUD. Never seen that before, and what's worse is that it didn't change thru the flight until I turned off TACAN and turned it back on. After 'resetting' TACAN it still read ROS but the distance was correct in nautical miles.

I have also noticed earlier this week that the TACAN distance was not changing on other F/A-18 flights but was corrected by resetting TACAN.

Couldn't find this reference anywhere, I should have taken screen shot or save track.

Anyone else notice this?

 

 

Edited July 25, 2021 by AvgWhiteGuy
clarity

[Swift.]

ROS will be the TACAN identifier set by the mission creator, most like Roosevelt here.

 

The strange large number is probably because of the TACAN bug where it turns off if the mission has been running too long.

[AvgWhiteGuy]

Hmmmmmmmm, interesting,,,never seen that before. Regarding the large number-TACAN bug-running too long, I set the TACAN when I left the Roosevelt and turned it off almost immediately. Turned it back on after the strike and,  having cleared the strike area by 10+ miles on my way home. HSI & HUD displayed the proper nautical miles initially and it was after another 30-40 miles I noticed the ROS and huge number. After some quick mental calc I assumed a ROS was some strange new measurement (55ROS =1 NM). But it didn't change until I reset TACAN.

So it sounds like the TACAN bug of not updating is separate from the ROS issue?

 

In any case would this be a designer flaw, bug, and is it something I can fix in the mission (Operation_Deep_Strike)?

 

 

Thanks for the quick reply....

[Swift.]

ROS isnt an issue, its the tacan identifier. Thats expected. 

 

The TACAN turning off after a few hours of use is a long running DCS bug. You've correctly found the workaround already.