reported DTOS mode Issues with TMS Up

[Renko]

If you enter DTOS mode, the logic is that TMS Up is to ground stabilise. That works.
BUT if while i'm ground stabilised i press again TMS Up it seems that it updates the position, and the TD Box moves position. I think that should not happen.

In the track i added first i use the HMCS, and each time you see the TD Box jump is when i press TMS Up. It seems to follow the Aiming Cross.
I dont think that should happen because the TD Box should not move, just update the coordinates. 
For example to create a MARK point TMS up is to update the coordinates. If i ground stabilise and move away the Helmet Aiming Cross and press TMS Up, the TD Box will not move to the new Aiming Position.
Wouldn't it make sense for the logic to be the same for both situations? Not 100% sure on this one.

But then in the track when i use DTOS with the HUD. After ground stabilised the TD Box, you will see the box jump and jump each time i press TMS Up.
I dont think each time i press TMS Up it should jump, and this time there is no aim cross. Just the HUD.

Best regards!

DTOS_TMS_up_Issue.trk

Edited November 14 by Renko

[BIGNEWY]

Hi, 

I don't think there is any bug here, as far as I am aware TMS up is supposed to command to update position. If you have any evidence it should be different please feel free to DM me. 

 

[Renko]

7 hours ago, BIGNEWY said:

Hi, 

I don't think there is any bug here, as far as I am aware TMS up is supposed to command to update position. If you have any evidence it should be different please feel free to DM me. 

 

 

Sorry, let me rephrase that because I don't think I explained myself very well.

I reported 2 things regarding DTOS.
- 1) Is the discrepancy of behaviour when you use TMS button. You would expect same TMS Up behaviour when you use the HMCS to do a MarkPoint, and when you use it to designate for DTOS.
Not 100% sure as i said, i bet your SMEs could tell you.
Its just a minor thing i noticed while testing the other one, you can disregard this discrepancy if you want.

- 2) The erratic behaviour when using DTOS mode on the HUD, and use TMS.
This one is the one that bring my attention and i wanted to point out before.

I made a new track with only this to be more clear on the issue. Sorry i know its hard to follow without knowing my inputs of TMS, i wish we had something for the tracks that display that, so please bear with me.

First of all i'm not saying that DTOS logic or TMS is wrong.

For DTOS on the HUD:
- Fly the FPM with the TD Box to the Tgt, or Slew the TD box to the Tgt
- Then TMS Up to ground stabilise

Seems that something wrong is happening in DTOS mode using the TMS Up.
As demostrated in the track, and easy to reproduce do this.
If you go to DTOS HUD >> Slew TD Box (without designate first with the FPM) >> TMS Up  >> then after that each time you press TMS Up it jumps, the FPM wont designate it.

It jumps with some erratic behaviour, because after hitting TMP up it doesnt go to the FPM. That will make sense. But instead it jumps

In this track for clarity:
- First i put in the Active Pause. I designate slewing the TD Box to one point, but if i correct it and press TMS up it goes back to the previous designate. Which is weird.
It should either just stabilise the new point or designate a new point marked by the FPM.
- Then after Active pause is off, you can see the FPM designating the new tgt. Thats perfectly fine, if we asume correct the logic of TMS Up DTOS in the HMCS.
- After i climb to gain some altitude it happens again.  I slew the TD box and then you will se the box jumping around, but the FPM is not designating it. Its seems that something in the low part of the HUD is doing it.

For some reason, I see this tagged as 'Check Procedures'. However, as you can see, I am not challenging the procedure and I did nothing wrong.


Best regards!

DTOS_TMS_up_Issue_HUD.trk

[BIGNEWY]

Thank you for the more detailed description, we have asked the team to take a look and have made a report internally.