wmd7 loses track - potential issue?

[witness_me]

If i stabilize onto something (area or point track) and then perform a tight flat turn there's a chance the tgp will lose track/start tracking some other area, many times miles away, from the point i was originally tracking

 

it's as if the tgp is only using image stabilization and not ins etc? I'm not saying it should track perfectly but since i'm within laze range the tgp should be able to use the calculated coordinates/lock on to the approximate area instead of jumping to another spot miles away?

 

it's not happening if i'm banking smoothly (even if the target is masked for a while), almost as if it's some sort of "gimbal lock" like-effect when i bank aggresively at almost 90 degrees etc (you're using quaternions right? :P)

 

i'm not sure if this is intended or not / couldn't find anything in the forums, hope i'm not creating a duplicate or this is some user error ?

 

I can work around this using mark points and briefly slave the tgp to the markpoint/then when i'm done maneuvering start searching near the markpoint for moving targets etc, if i know beforehand that i'll be banking aggresively, so not a big issue

[witness_me]

 

 

in this screenshot you can see that the tgp is pointed at some area in the ground, however masked is flashing and it lost track

 

 

hope this helps

Edited December 27, 2019 by witness_me

[AeriaGloria]

I think some of the masking is WIP, looks like it’s pointed almost as far left as it can go

[L0op8ack]

maybe the LOS to the tracked point exceeds max gimbal az/el limits

[witness_me]

Hi L0op8ack - thanks for the response

 

The "problem" i'm seeing is that in some occasions the tgp will either start tracking another area than the one i was originally pointing at, or lose track altogether and start drifting

 

The location where a user has slewed the tgp is normally held in memory and the tgp will try to point it's camera towards it once it's back within normal az/el limits, in our case it seems the tgp will either jump to some other location (sometimes tens of miles away) or lose stabilization altogether and start drifting

 

an easy way to reproduce this i guess would be to target an area and once you're on top of it do a roll

 

then on the next pass, track an area, turn it into a markpoint, slave the tgp and then do the roll

 

after the first roll the tgp should lose track altogether and either start tracking some other random area on the ground or lose stabilization/start drifting etc

 

after the 2nd roll, once the tgp is within az/el limits, the camera will revert to tracking the markpoint

 

if you do the roll test with a litening, the tgp will always be looking at the original area once it's back in acceptable az/el limits (the litening works a bit too well in the sim i think in this case, as there'll always be some level of drift and kalman filters will eventually drift etc)

 

if you're saying this is normal then it's all good by me - i'm just wondering if it's intended behaviour or a bug

[L0op8ack]

and another reason, you roll too fast, exceed the WMD7 gimbal moving speed(~30 degrees/second).

but is this case, WMD7 will try to track the last known point when the plane is steady.

It should not point to somewhere within the gimbal az/el limits.

Edited December 27, 2019 by L0op8ack

[witness_me]

hi, just wanted to say i don't experience this anymore since the last patch, when i egress at high G or when i do a roll & dive etc

thanks so much for fixing! feel free to delete the post for clean-up purposes etc