View Issue Details

IDProjectCategoryView StatusLast Update
0000098Falcon BMS Known BugsAvionicspublic2021-02-19 23:06
ReporterSixpack Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformPCOSWindowsOS VersionWindows 10
Product VersionBMS 4.35 
Summary0000098: During Maverick boresight, TGP jumps off target when point track is commanded and then drifts away from target
DescriptionAlways observed during Mav bore sight procedure. It looks like this:

https://drive.google.com/file/d/1MkAKPOMr6rkdJ65-gg7P3Tg4qTYuwnYD/view?usp=sharing

Possibly related to cursor movement during TMS-UP and/or noisy cursor pots.

Applying large dead zones to the cursor XY axes reportedly helps in some cases

Useful workaround is to avoid Maverick load outs on human controlled lead aircraft and instead use TGP to ground stabilize on a target and command AI wingman/element to “attack my target.”
Steps To ReproduceAttempt Maverick boresight and move cursor slightly while commanding point track.
Additional Information4.34 and 4.35, possibly other versions.
TagsNo tags attached.
Theatre of OperationsKTO

Activities

Blu3wolf

Blu3wolf

2021-02-14 22:38

manager   ~0000260

If you are moving the cursor while commanding point track, isnt this expected behavior?
Sixpack

Sixpack

2021-02-19 22:54

reporter   ~0000270

Yes, possibly. I don’t have any real world experience with a jet like this so I can’t judge how realistic this behavior is.

On my rig, I do not need to move the cursor while commanding point track. For me, just commanding point track will cause this behavior unless I have a configured a dead zone on my cursor x and y axes.

The dead zone has good effect, so this problem is trivial for me now. If it’s a bug it’s very low impact with the workaround.

If this is designed behavior then maybe adding some language to the training manual might help.

For example, “Some pilots have persistant trouble using the TGP and commanding point track makes the TGP viewfinder lose ground stabilization and drift randomly. Adding a dead zone to the cursor x and y axes usually solves this problem.”

Thanks very much for looking into this!
Blu3wolf

Blu3wolf

2021-02-19 23:06

manager   ~0000271

My take: If its solved by changing hardware settings to add a deadzone, its an issue with the hardware, not with the sim.

That having been said... there are some features already in the sim designed to help workaround common hardware limitations - for example, the self-cancelling override modes.

Is there any software component? If its solely due to the hardware, perhaps this would be better off being rewritten as a feature request instead of a bug report?

Issue History

Date Modified Username Field Change
2021-02-14 22:06 Sixpack New Issue
2021-02-14 22:38 Blu3wolf Note Added: 0000260
2021-02-19 22:54 Sixpack Note Added: 0000270
2021-02-19 23:06 Blu3wolf Note Added: 0000271