fixed internally STT Undesignate makes TMS unresponsive in TWS

[LastRifleRound]

Track attached.

 

What happens:

1. Initiate TWS

2. TMS right to make system tracks (bug makes this invisible)

3. TMS right again to bug priority target

4. Repeated presses of TMS cycle targets

5. Move cursor to bugged target, TMS up to enter STT

6. TMS down to undesignate and return to TWS

7. FCR format will no longer respond to TMS right or TMS up. It is not possible to cycle bugged targets, manually bug new ones, or enter STT using the cursor.

 

Expected behavior:

After #6 above, TMS right and TMS up should function as they did before.

 

EDIT: Bug appears to sometimes appear without STT. From Instant action "Fighter Intercept" in the Caucuses. TMS right and TMS up will not do anything in TWS here. Can't upload this mission as base file size is 5MB

 

 

F16FCR_unresponsive.trk

Edited September 13, 2021 by LastRifleRound

[BIGNEWY]

Hi 

 

good news is I am unable to reproduce this on our internal build, 

please wait for the next patch and retry, I think it is resolved.

 

thank you

[LastRifleRound]

This is still an issue in this latest patch. Open instant action caucuses, select fighter intercept. AWACS will call out the targets, seems like they come from 115 or around 85 degrees at 60. When they get on the screen, you'll find the contacts completely unmanageable in TWS. TMS Right does nothing, TMS Up does nothing.

[Frederf]

I would describe this simplest as:

If there is a TWS bug then it is impossible to elevate any contacts/tracks. TMS up seems to be entirely reserved for designating the bugged target as STT. It is not possible to select another TWS bug from system track, elevate a tank to a system, or elevate a contact to a tank track with TMS up in this condition.

 

However if I remove TWS bug then normal behavior resumes. It doesn't seem right that once TWS bug exists that a lot of TWS functions become impossible. You should be able to switch TWS bug for example by TMS up on a non-bug system track under cursor.

 

Indirectly related I see after TWS transition to STT, then reject back to TWS: Previous system track(s) (the one that didn't go STT) are not retained despite a short time spent in STT. Tracks should be extrapolated for several seconds (13?) when transitioning TWS/STT and should resume at their old status if returned to TWS before they time out. STT doesn't erase old track files from the system (despite being not visible). It just stops updating them and they will persist and resume if returned to quickly.

 

 

F16 TWS with bug TMS up.trk

Edited September 18, 2021 by Frederf