SimTMSUp not designating target, not sure if U3 related
-
As the title implies, I’m finding that randomly during a mission in Campaign mode…I do something that causes TMS Up to stop working. I’m not sure if there’s a bug where Ive messed up the MFDs and misconfigured the DTC, or if this is intended functionality and I’m doing something wrong.
- I have had this happen to me a few times in the past 24 hours…usually when in AG mode and switching between GM and GMT, and then switching back and forth from AA mode.
- all other TMS buttons work (IFF, TMS Down, TMS Right, etc), but no matter what I do (press cursor enable, cursor zero, turn off FCR) it does not seem to fix it…I have to restart.
- This is not a hardware issue, the keyboard shortcut for SimTMSUp does not work during this either
Has anyone run into this problem?
-
Will you post an image of your SOI when this is happening.
-
@fish44 said in SimTMSUp not designating target, not sure if U3 related:
Will you post an image of your SOI when this is happening.
I just reproduced it again, but do not have screenshot.
At the time of the FCR issue, my SOI is the FCR.
This issue also affects the TGP and WPN sensors (such as mavericks)
This time I was doing a SCAR sortie on Balkans, with LANTIRN and AGM65B’s. I switch to AG and, somewhere while switching Mav modes and FCR to GMT, I lose the ability to designate on FCR.
When I lose ability to designate on FCR that also means that any other sensor does not lock, this includes all AG and AA FCR modes, TGP, and Mav.
Changing SOI to any of the MFDs does not make a difference, if that is what you are troubleshooting.
I lose the ability designate/lock targets, period.
-
Yes we have experienced this problem with U2 if it can help the Dev Team in their research. We experienced this problem within our squadron on a tactical mission (not in a campaign).
This problem already existed on certain occasions in
Air-to-Ground mission with U2.
We will attempt to reproduce this intermittent problem and provide more info as soon as possible.Three of our virtual pilots have experienced this kind of problem with the TMS Up becoming inoperative, but on very rare occasions.
I thought it was a ghost keyboard command issue or our HOTAS setup that was causing this problem but it seems to be related to other things.
-
@101-spyder said in SimTMSUp not designating target, not sure if U3 related:
Yes we have experienced this problem with U2 if it can help the Dev Team in their research. We experienced this problem within our squadron on a tactical mission (not in a campaign).
This problem already existed on certain occasions in
Air-to-Ground mission with U2.
We will attempt to reproduce this intermittent problem and provide more info as soon as possible.Three of our virtual pilots have experienced this kind of problem with the TMS Up becoming inoperative, but on very rare occasions.
I thought it was a ghost keyboard command issue or our HOTAS setup that was causing this problem but it seems to be related to other things.
Ok great thank you @101-Spyder. I will try to document my steps when I am able to recreate this again.
My inkling is that it has to do with the f16 getting “stuck” in the HUD-based maverick modes (VIS, BORE, etc), but not 100% sure yet. Thanks again…hopefully will report back.
-
I have experienced this when dogfighting. I don’t change modes as I am just dogfighting in dogfight mode with guns only and the enemy re-spon and I will randomly not be able to lock on using TMS up. It is seemingly random.
-
When it happens, check if TMS up long works on FCR (spotlight).
-
And, if you try to change the callback associated to TMS-Up (ShF-Home) with a different keystroke ? Maybe the problem origin from a conflict between the syntax and “who knows” windows process. Just an idea to help…
-
I believe I experienced this as well. I just got used to change mode and back again. If you have a clear repro case, let us know, worth fixing.
-
@lorikeolmin said:
When it happens, check if TMS up long works on FCR (spotlight).
Will do, good idea.
And, if you try to change the callback associated to TMS-Up (ShF-Home) with a different keystroke ? Maybe the problem origin from a conflict between the syntax and “who knows” windows process. Just an idea to help…
Already tried this but didn’t say it explicitly. It’s why I titled this “SimTMSUp not designating”, because I also tried non-HOTAS input. Thanks though!
-