some1

It's an issue since day 1. Razbam when creating the payloads did not realise there are 2 different generations of unguided rockets in DCS (FFAR and M151) and randomly mixed both of them. Of course if was reported several times over the years.

The gunsight, compass and some other gauges suffer from excessive reflections since the lighting update in DCS:

That's a different problem with FLIR image in all DCS aircraft, since a year or so. ED can't reproduce, therefore problem is unsolvable.

TGP image in F-16 is much worse than in other aircraft. It has low dynamic range (whites are gray, not white) and the contrast adjustment does not really adjust contrast. Same mission, same distance, same targeting pod in the Hog, Hornet and Viper. In the Viper even the target cross and north arrow are dark gray while they are white in the other aircraft. You can try to manually play with gain control, but it will only make parts of the image even darker. Though it will help somewhat with making the tanks stand out against the background. Another possible issue is that the contrast rocker (bottom right) does not adjust contrast, but something else. Instead of making "brights brighter and blacks blacker" evenly across the range, the contrast increase makes everything black except the whitest spots, which now become white. And the opposite when clicking the other way. While changing contrast on a grayscale image should work like this (if it is really a contrast adjustment):

After the changes to DCS cockpit lighting few months ago, Spitfire cockpit looks particularly bad. Those baked reflections on glass and gauges are very distracting.

Yeah, TGP contrast is the worst of all Lighting equipped aircraft, since the previous beta everything is grayish gray.

Locking distance is not the subject of this report. The problem is Mav can't follow a moving target once locked, because it's constantly forced to look at the point designated by TGP. No matter if it locked at 5 or 10 nm. This creates the "jittery" lock effect. Same happens when the target is not moving, but the TGP designation is not right on top of the target.

The wording in TACMAN (and Razbam's quick guide) is pretty clear. "if no EHSD is displayed headsdown, initial actuation selects the EHSD on the left MPCD. Subsequent actuations toggle between modes"

MAV is constantly slewed to the initial position desginated by TGP, even if uncaged. There's no handoff. If it happens to lock the target and the target moves, it will fight for a while, switching between ground designation and target tracking several times per second, and eventually it will loose the target. The only way to stop this is to undesignate and loose TPOD track. In the attached track you will see that after locking the first vehicle in the convoy, MAV will constantly jitter and switch targets, until the whole convoy passes through the initial designation point. MAVPTRK.trk

1. Select Waypoint, press DESG on EHSD, the TPOD will slew to the target waypoint 2. Press HOTAS Undesignate - now you need to press DESG TWICE (?) to slew it again to the target waypoint. But it works, eventually. 3. Move TGP cursor in TDC 4. Undesignate again Now the TPOD won't slew any more to the designated waypoint, no matter how many times you press DESG. Neither in TDC nor TDC DESG.trk

If EHSD is already on the right screen and you cycle EHSD using Sensor Select Left HOTAS button, then: First click will change EHSD on the right screen it to Decenter View - OK Second click will change the right screen it to EW page - OK Third click will open another EHSD on the left screen - WTF? And all subsequent clicks will cycle EHSD Center/Decenter/EW pages on the left screen. If EHSD is already on the right screen, then cycling it should keep it on the right screen. EHSD.trk

So if it is not a bug, how do we attack a moving target now?

Yeah, the Mav in the Hornet does not follow TGP any more. It will slew only to the initial position once uncaged. Probably Viper changes broke it. Or yet another WIP feature.

Guess where the bombs will fall.... Same problem with Mav indicator on HUD in Vis/Bore mode. BTW why TPOD cross/gate and north symbol are gray instead of white like the rest of the symbols? They are completely invisible against some backgrounds. tpod.trk

I don't think you can. In this mode TGP is slaved to Mav, not the other way round. So make MAV a SOI and slew it directly.

Unlike every other airframe in DCS, Mavericks are not powered if mission begins in the air. You still have to wait 3 min to use them.

You can't ground stabilize if the target is too far away. But thanks for the tip, I'll play with those special settings, haven't noticed them before :)

No, as I said it's a normal convention in Windows. Towards the user is +, away from the user is -. That's how the throttle looks in Windows with all axes full forward:

Each aircraft has separate assignments and also there are different settings often for game and sim mode. Are you sure you're assigning them in correct place?

The axis control for TV/IR missiles needs to be faster at max deflection, especially when zoomed in. Right now it is not possible to track a ground target just a few degrees below horizon, like on a screenshot below. The ground moves faster, than you can slew the seeker.

It's normal, just a convention used in Windows. If it's reversed in game, click the invert checkbox, that's what it's for.

Not rotate. Move sideways. Or when you look at something that moves sideways, like the terrain. Smoothing head rotation is handled by lower-level smoothing algorithm that is always enabled, something Oculus calls Asynchronous Time Warp (ATW) but other companies use something similar. On the other hand, reprojection (or ASW) smooths also translational movement. That's why reprojection on/off look basically the same if you just sit in the cockpit and pan your head around. But if you start moving the head sideways, without reprojection the instruments will blur.

I fell sorry for Baltic Dragon as his works are always exceptional and now he is also dragged into this affair. But that's the point. Why call something complete, when it clearly is not. The manual is just one among many things that need attention.

Is that a bug?