Crptalk

From the discussion in this thread. Stick hat trim is currently around 4 times more sensitive than it should be according to F16FLCS-SME. He states pitch trim should be 20 seconds side to side and roll 45 seconds side to side. Currently the DCS F-16 pitch is around 5.5 seconds side to side and roll 11 seconds side to side.

Hopefully ED will adjust it then.

Using the trim hat? Because that's about 4 times slower than it is right now in the DCS F-16. I'm getting 5.5 seconds from side to side for pitch and 11 seconds for roll.

Simultaneous tracks work fine for me in VIS without a targeting pod. However missile stepping resets the target designator back to boresight. Correct me if I'm wrong but missile stepping should not reset your target designation. BORE doesn't work at all for me and PRE doesn't work because the missile seems to get stuck to the current steerpoint/SPI.

I've been able to boresight just fine against buildings, cars, streetlights, cranes, etc while bore sighting on the ground. As long as the maverick can get a good contrast lock it works.

Track from todays open beta hot patch tgpfpsloss3.trk

VIS should allow you to refine your aiming point/SPI with the TGP just like in DTOS. In fact VIS is described as one of the two modes used to boresight the TGP and Mav.

TGP to A/A in Nav mode (on the ground) causes significant performance loss when switching from Nav master mode to another master mode and then back to nav mode at Al Dhafra on Persian Gulf. 50-90% fps loss in single player, complete game freeze in MP. Setting the TGP to Standby OR A/G in Nav mode immediately fixes the issue. Right HDPT switch to off also fixes it. TGP to A/G in Nav mode does not cause this issue to happen. In the second track I discovered that commanding a point track immediately fixes the issue as well. It seems when switching back to nav from a-a/a-g/dogfight/msl/jett the TGP is no longer boresighted but pointed in a random direction. This was most noticeable at Al Dhafra and that's where the tracks are located. tgpfpsloss1.trk tgpfpsloss2POINTTRACK.trk

All you have to do is put a hq7 down in mission editor and check yourself

The -34 makes it sound like in reality as long as the maverick and tgp boresights are close enough to compare video, the missile boresight correlator will still be able to correlate the tgp and maverick video and achieve a lock. Bore sighting makes the process faster.

And the F-18's simplified harms.

R7 would fit the timeline of the DCS F-16.

AFAIK because of misalignment when mounting the Mavericks, every plane that carries them and wants them to be aligned with their TGP will need to boresight them. This included the A-10 and F/A-18. As for why the A-10 and F/A-18 don't need to boresight at the moment as well.... who knows. Maybe it's coming later for them.

Have you not done A2G with a tpod the past few months? It is a bug with partially implemented SPI that likes to get stuck to the steerpoint.

fixed

DTOS is basically boresight and additionally can be cued with your hmcs.