TGP cursor drifts away when trying to lock on moving ground target
-
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.
-
@E69_Manta said in TGP cursor drifts away when trying to lock on moving ground target:
@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.
I have also a TWCS. Without deadzone I had a lot of issues with the cursor. With large deadzone I have no issues, everything works fine!
-
@hiuuz What program did you use to set the dead zone?
-
@E69_Manta I set mine in the launcher for my X56
-
I put medium and large in dead zone in bms launcher but it didn’t work. I have disabled the y axis and the x axis. I have used the up, down, left and right radar cursor keys. I have them on an 8 position hat switch but up-left, up-right, down-right, down-left are not set as they don’t work well. My tgp doesn’t go far when I release the block so i am happy. For air to air radar the movement is very slow but it stays completely stopped and works very well. In the long run I’ll buy another throttle with a easy replaceable minijoy (slew). I know with warthog is easy i dont know about winwing.
The twcs (T16000 throttle) slides badly so if i want to fix it i would have to buy a mod for about 60-80 euros, also to fix the problem of the slew, open it and try to fix it with this mod https://www.reddit.com/r/HotasDIY/comments/it8eub/thrustmaster_twcs_microstick_analog_stick/
If it was not enough, i would have to buy another slew blindly and i think it would have to be desoldered of the plate. In the end, it’s not worth it. For 215 euros I have the warthog, the only thing I lose is the zoom wheel but I gain a replaceable slew which is more important. For now i’ll survive with twcs i think i just have to get used to using the hat switch for radar.
-
@E69_Manta
Hmm. If you mind, you can check in TM TARGET software the raw readings of your mini stick. I set my deadzone ingame or in the Launcher and worked. But if you have a faulty mini stick maybe your offset is greater than even the large deadzone. -
@hiuuz Thanks for the suggestion. I don’t like target and I don’t know how to use it. I used joystick gremlin. I had to put 25% on each axis. The result is very good in air-to-air radar and very bad in tgp. In other words, for small corrections it is better to put keys or in my case a hat switch. For air to air radar the keys are slow and one axis is better even if it has a large dead zone. I prefer control over tgp since I’m good at air-to-air contact detection but bad at air-to-ground hahaha.
I’ll try the radar hat for a week. If I don’t get used to it I’ll try to do the zip tie mod. If it doesn’t work I’ll make a decision: warthog throttle or winwing.
In any case, even if I had a solution, the throttle gets stuck, it doesn’t slide well, which is bad for small corrections, for example, maintaining formation or in air refueling. As I already said it can also be fixed but it is expensive. Better to have something that slides well and with easily replaceable slew. I have seen that the winwing F-15 has screws in the slew. It seduces me but I have read problems in quality control. So I’ll have to wait for more information.
EDIT: twcs disassembly