[RESOLVED] TOT bug

[Bog9y]

Hi Razbam bug team,

 

I have been having this issue with TOT ever since I started with the Harrier and as far as I can tell it is not functioning as it should. 

 

Please find attached 2 track files of the same mission setup. No mods installed, 1 waypoint about 17 miles away straight ahead. 

 

When we start the 1st trackfile you can see that I press TMR, select TOT, enter a sensible TOT which is achievable (something like 070240) and press ENT. Then I press CS/T to get the command speed caret and luber line. 

 

What you see then is a command speed of 220 kts. This doesn't make sense but for demonstration purposes I slowed down to the command speed and very quickly the command speed starts to creep up to a crazy high number which is not achievable. 

 

2nd Trackfile: same scenario. Waypoint 17 miles away, speed is around mach 0.7 . I do the same again, enter a TOT , press ENT and CS/T ODU.  This time I maintain my speed because I know that it should bring me over waypoint 1 at around 07:02:40.  The command speed initially is slow (238 kts), then at 2.5 nm before waypoint 1 it start to go up and up.  

 

The CS/T function should not work like that. It should give me a stead speed to maintain, in this case around 420-ish knots would have made more sense. 

 

I tried this test again with using REAL time instead of UTC and the results were the same. I also did it by pressing DESG on the EHSD for waypoint 1 but again, the results were the same. 

 

In addition, the CS/T and TOT should reset when you overfly the waypoint and/or if you press RSET on the ODU.  This should also remove the caret and luber line on the HUD but it doesn't. The caret and luber line remain for the rest of the flight. This is incorrect. 

 

Is the TOT function meant to be accomplished in a different method than the published one in the NATOPS TAC-000 manual? 

av8b- TOT BUG1.trk av8b- TOT BUG2.trk2

[Aernov]

I've also reported it earlier, and, as requested, added two tracks. Maybe those will be useful.

[Wisky]

i have tried this and can confirm that something seems to be wrong with how the system calculates the TOO time.

 

As if it forgets to convert Indicated Air Speed into Ground Speed. Starting with a very low speed/number that is going to increase exponentially as you get closer to the TOT

Edited May 24, 2021 by Wisky

[Bog9y]

I had another play with it and as suggested to me by some smart guy I tried using TOT whilst in A/G mode. I confirm that the TOT function works in A/G mode and gives a sensible command speed in TAS. The timer on the UFC scratchpad should count down but it doesn't , it's stuck at the time to go to the TOT when it was entered.  So using A/G is a work around at the moment but the TOT function should be fixed and work in NAV mode too. Perhaps the issue is the conversion from TAS to IAS? 

[myHelljumper]

The issue is fixed and should be available next update.

[Bog9y]

2 hours ago, myHelljumper said:

The issue is fixed and should be available next update.

AWESOME!  Thank you! 

[myHelljumper]

Hey guys, is this still an issue ?

[Shiroka]

18 hours ago, myHelljumper said:

Hey guys, is this still an issue ?

Yes - more details in this thread:

 

 

 

[myHelljumper]

Hi,

 

I'll take a look at this thread, moving this one to resolved.