TGP cursor drifts away when trying to lock on moving ground target
-
I was closer than 10nm I’d say.
I dunno if I’m using zoom correctly - how is it supposed to be used? I was in some magnification for sure.
Concerning the target, i first locked FCR, then switched to TGP and continued slewing and searching from there i think.
Will try to redo if i have the time. Wasn’t the first time happening so should be able to reproduce soon.I have a MP TGP Training mission that covers exactly those issues if you want to fly it with me; that way I can see what you’re doing wrong and also help you get the most out of the sniper pod for both AA and AG.
Cheers.
-
Hey Stalker, really appreciate your willingness to help, but it’ll probably be difficult to meet up, because i’m on a very limited time budget, only able to fly between 21h-23h CET only some days a week.
Edit: Forget the first video i posted, it might be different issue.
Here’s another video where the issue can be seen. The units aren’t even moving in this one.
Just shows the issue of the TGP cross drifting away fast once point lock (TMS up) is commanded.
Only some rare times it works to get the lock (near beginning and end of video).
Distance is around 7nm here, with TGP narrow FOV.https://drive.google.com/file/d/1MkAKPOMr6rkdJ65-gg7P3Tg4qTYuwnYD/view?usp=sharing
-
Read this in TO BMS1-F16CM-34-1-1, CHANGE 4.34.0, p159:
NOTE: It is important to cease slewing before commanding a POINT track or the cursors will jump off the target as you’re trying to lock up the mover. You can practice this and see exactly what happens. It is also important NOT to
make any slew inputs while in POINT track as it will also make the cursors jump off and away of what you were tracking, unless you are intentionally wanting to break POINT track. The cursors jumping off is a bug. As you can guess, this can make getting a POINT track on a mover a challenge. It is best to lead the mover and let him drive into your cursors and then command POINT track. Also note that you may likely need to be in narrow or expanded FOV to get a POINT track, as the size of the object is important in if the TGP can get a track on it. […]So is this a known issue?? If so, is it being worked on by the Devs or do we just have to live with it?
-
AFAIR if you ground stabilize with TMS right and enter expanded FOV then you are in Area mode and no jumping of cursors will happen. Not sure what happens with moving targets though if they require POINT?
-
AFAIR if you ground stabilize with TMS right and enter expanded FOV then you are in Area mode and no jumping of cursors will happen. Not sure what happens with moving targets though if they require POINT?
TMS right doesn’t do anything in my situation.
But anyway, even if i have an Area track before and then try to Point-designate, it still moves away the same way. -
Does anyone else have another comment about this subject?
I 'd really like to find out if this is a bug or if 'm doing something wrong. -
seems like user error
:noidea:
-
I will try to re-produce in a few hours and will report back good Sir……
-
unable to reproduce…works fine for me and SWWs
-
Thanks a lot for bearing with me!
I think i found the issue: It’s probably linked to my controller setup.
When i mapped the radar/TGP cursor slew back to keyboard, i had no issues.
It’s only when i use the analog ministick on my TM TWCS throttle.
Gave it a bigger dead zone and it’s playable now. I get a good lock in about 3/4 of cases.
It’s still intriguing, as the cursor does NOT move just prior to lock, then starts moving away really fast after TMS up. (As in the video)
Well strange, but found a solution i can live with now. -
Thanks heaps for your last post, Logic!
I was just having the same problem with my TGP, and your solution worked.
My Cursor X axis value had drifted just barely outside of the deadzone I had set for it. I re-set the deadzone, and the drifting-TGP problem went away.
It’s a curious problem, because at first I thought I had a problem with the TMS switch on my Warthog stick, because I wasn’t getting a good IR AREA track from my TGP. And when I tried to command IR POINT tracking from the TGP, it just kind of drifted around. So I wondered if there were problems with my TMS switch, or with the mappings of the TMS actuations.
I double-checked the mappings of my TMS-Up and TMS-Right, and they were correct. I wondered if a recent Windows update had scrambled something. But nope, I just needed to re-do my Cursor X deadzone. Now the TGP works normally. Thanks!
-
That`s right! TWCS mini stick has this problem, just adjust the dead zone, my TWCS also happened, there is no problem with BMS.
-
Yeah, TWCS mini stick is cr*ppy.
I now use a large dead zone but still have the issue fairly frequently.There still is this bug in BMS like written in the docs as i mentioned in post #6 though
https://www.benchmarksims.org/forum/showthread.php?40357-TGP-cursor-drifts-away-when-trying-to-lock-on-moving-ground-target&p=553083&viewfull=1#post553083So it’s a combination of both issues.
-
Hey Stalker, really appreciate your willingness to help, but it’ll probably be difficult to meet up, because i’m on a very limited time budget, only able to fly between 21h-23h CET only some days a week.
Edit: Forget the first video i posted, it might be different issue.
Here’s another video where the issue can be seen. The units aren’t even moving in this one.
Just shows the issue of the TGP cross drifting away fast once point lock (TMS up) is commanded.
Only some rare times it works to get the lock (near beginning and end of video).
Distance is around 7nm here, with TGP narrow FOV.https://drive.google.com/file/d/1MkAKPOMr6rkdJ65-gg7P3Tg4qTYuwnYD/view?usp=sharing
This is exactly the issue I am having now and I’m positive it’s not user error. Last year I must have done the Maverick TE a couple dozen times and I had my boresighting skills honed pretty sharp. Now I cannot get a point track with the TGP, so boresighting is impossible.
My throttle is different and uses a new ministick which is probably half the issue. The bug would be the other half.
I see this behavior both in 4.34 and 4.35. Large deadzone on the ministick had no effect and made my cursor very slow. When I checked the values coming out of my ministick pots, I found they are a little noisy. They aren’t stable at a middle point even when I take my hands off the controls. I’m guessing this means that the tiny fluctuations coming out of the pots are triggering the bug and making the TGP point track jump off the target. I added a filter that seems to have cut this noise way down. I’ll try to boresight again tomorrow and share what I learn.
-
Download the vkb joystick tester. That will tell you how reliable your ministick is. Mine seems pretty good, surprised I had issues pre- deadzone
-
Download the vkb joystick tester. That will tell you how reliable your ministick is. Mine seems pretty good, surprised I had issues pre- deadzone
Yes, I used this and the mmjoy2 configurator to see numerical values. It was noisy without the filter but better now.
-
Yes, I used this and the mmjoy2 configurator to see numerical values. It was noisy without the filter but better now.
How did you add a filter?
-
How did you add a filter?
My throttle uses arduino to communicate between the buttons/pots and the USB interface. The mmjoy software running on the arduino has filter that can be applied to the raw pots values. The values are clean now but it still it didn’t help which surprises me. I guess I don’t understand how BMS works at all.
-
I overcame this problem by adding a medium deadzone to my cursor x and y axes within BMS.
-
@Logic I know it’s an old thread but I must thank you. I also have the twcs throttle and it was freaking me out. I didn’t know what I was doing wrong. I know it’s not me but the mini-joy. I’ll try to put a dead zone and if it doesn’t work I’ll look for a new throttle.