reported DES TOS calculations not functioning properly.

[WHOGX5]

In our block and tape of F-16C, if your current steerpoint doesn't have a set DES TOS but a future one does, any CRUS TOS speed indications will reference the next available TOS even if it's set for another steerpoint. As an example, lets say you've entered a DES TOS timing for STPT 4, your currently active steerpoint is STPT 2 and neither STPT 2 nor STPT 3 has a DES TOS timing. In that case, if you activate CRUS TOS mode your required speed will be given based on you flying to STPT 4 via STPT 2 and 3. At the moment, the absence of a DES TOS timing will show you what speed you need to maintain to reach STPT 2 at 00:00:00 which is incorrect behaviour.

B_TOS_Show_Next_Steerpoint_Timing.trk

[Lord Vader]

Hello @WHOGX5

There's definitely something going on here. We've marked this for internal analysis.

thanks. 

[Lord Vader]

@WHOGX5

We've analysed this and concluded it's working as intended. The TOS speed will always calculate to whatever time is input, even 00:00:00. If the aircraft is way too early or way too soon, the groundspeed required will be unrealistic. For your track, it's calculating 70kts (incorrect minimum value, see below), because that's the minimum calculated GS, not a realistic calculation. It's just saying that it can't go lower to reach an impossible zero time on steerpoint. The maximum value, btw is 1700kts. 

The only bug we did found is that according to documentation, the range should be 80 to 1700kts and that will be corrected in a future update. 

Thanks for bringing this up. 

[Lord Vader]

Hi again

Just to correct my previous statement, the limited speeds to 70kts and 1700kts as we have in DCS are correct to the model aircraft we have simulated. No further change is required. 

[WHOGX5]

2 hours ago, Lord Vader said:

Hi again

Just to correct my previous statement, the limited speeds to 70kts and 1700kts as we have in DCS are correct to the model aircraft we have simulated. No further change is required. 

Just to clarify, the issue is that the DES TOS is 00:00:00. By default, DES TOS should be invalid if it doesn't have a set time, rather than 00:00:00, meaning that both the DES TOS and REQ G/S fields should be blank. If a time is already set for a steerpoint, entering 0 into the DES TOS window should blank it. If the DES TOS for a steerpoint is invalid, it will calculate speed based on the next steerpoint with a valid DES TOS.