Search the Community

Hi everyone, Contrary to this thread being marked as fixed and locked, there are still problems with the cursor in the F-16. I'll copy and paste what I had written there as all of it still applies: Certain pages in the F-16 have the cursor move at inconsistent speed when changing direction, leading to it appearing to jump. It's most commonly seen when going left/right and then adding some up/down. As far as I can tell the following are affected: The HUD (for instance, CCRP, DTOS, Maverick VIS etc). The HAD page (though the cursor does move more smoothly - as if its position is updated at a higher rate compared to every other page. Unsure what the rate should be). The WPN page for HARM. Everything else appears to work as it should and motion is predictable (though the rate at which the position is updated seems to be lower than the HAD page). No other module appears to suffer from the same bug (the A-10C for instance is very smooth and very consistent, with the exact same control on my stick bound), there are also no conflicts in the control set up. The track I originally posted can be found in the previous thread, as can my control profiles for both the A-10C (which shows no issues) and the F-16CM. Here's a video to show what I am seeing (this is after a recent calibration), this video is before recent updates but still depicts exactly what I am seeing with the most recent update at time of writing (2.9.20.15010). Note the following: The FCR and HSD pages don't show this issue - the cursor behaves entirely predictably and there are no sudden rapid accelerations - all good. However, the HAD, HARM WPN page and the HUD (here shown in DTOS, but the same applies to say, Maverick in VIS mode or any other mode using the HUD's cursor), show sudden, rapid accelerations when the switch is moved in a circular fashion. When I make just max X or just max Y inputs, the cursor generally moves more slowly and sudden, rapid accelerations are less frequent (though not entirely 0, you can sometimes still see the cursor suddenly start moving very quickly). The bug appears to affect the Y-axis more than it does X. The sudden, rapid acceleration of the cursor occurs when changing direction. Towards the end of the video I show my control bindings, you can see that my control moves as smoothly as I can make it. It properly re-centres to 0 and I can move it to the extremes of either end without any observable jitter. Here's a video showing what happens when I try another module, here I try the A-10s TAD cursor and the HUD cursor - note how there is no sudden rapid accelerations and the cursor behaves completely predictably and is generally very smooth. I also again show my control bindings and test, you can see that the exact same control is bound and (aside from not being inverted) the same exact settings are used: Every other module I've tested (A-10C II, AV-8B, F-4E, F-14A/B, F-15C, F/A-18C, Ka-50, Mirage 2000C, Su-25, -25T, -27S, -33) work as they do as seen in the A-10C video - smooth, predictable motions, with no sudden rapid movement - if I move the control to its extremes the speed of the cursor stays clamped. It is only the F-16CM and only for the HUD, HAD page and HARM WPN page that exhibit this issue, other pages (such as the FCR, the HSD, the Maverick WPN page, the TGP page etc) show no issues.

Maybe I am doing something wrong, but I cannot get the threat rings to show up on the Harm Attack Display as they should. If needed I can provide evidence that they should.

I am not sure if this is a bug or intended as is but sometimes, when I track a site in the HAD, and then switch to the TGP, the TGP is just moving and doesn't lock the target in space. Look at the track files I have. I lock the SA-5 in the HAD just to get the general direction, then search with the TGP but in both Point mode and Inertial reference mode, the picture keeps moving. I have not figured out the reason why it only is sometimes, but it is happening in the attached track files. I would exepect the TGP to be stabilized once I take it over with the SOI or especially when I move the TGP via the throttle joystick. I have no clue on how to reduce the time it takes to the action in the track files, but skip to : 08:03:00 for file 1 08:01:50 for file 2 (Ignore the bad flying) My guess is that this happens when the waypoint is far away from the SAM site, but I have not confirmed it. Point track not working on TGP2.trkPoint track not working on TGP.trk