Bowman-011 Posted December 27, 2021 Posted December 27, 2021 (edited) Observed in OB 2.7.9 in the Syria map "Canyon Run Attack" mission. The mission is to bomb an early warning radar which I do every now and then to check out new DCS versions. This time I observed that my MK-82 Snakeyes always fell long and hit the ground behind the target when using high drag. At first I thought it was just lack of skill but after several repetitions I started to wonder. I noticed that the waypoint was always shown in front of the actual target rather than on top of it. If I drop the bombs with the pipper on the target they always impact way beyond the target. But if I drop using the indicated waypoint I hit right on the mark. Note that the bombs hit not just slightly off target. They hit the ground quite far from the expected impact point. As you can see, the waypoint is placed perfectly on top of the target in the mission editor. Approaching from different directions also moved the waypoint indication to a different side (notice the attack heading in the screenshots) . Using dive bombing CCIP I was always able to hit the target without any issue just by aiming straight on top of it. Is there something wrong with level flight bombing? I'm 100% sure that this was never an issue in previous versions. Am I missing something here? Edited December 27, 2021 by Bowman-011 i7-12700KF - 64GB DDR4@3600MHz - RTX 4090 - HP Reverb G2 - Thrustmaster Warthog HOTAS - Thrustmaster Cougar MFDs - LG Rudder Pedals
Bowman-011 Posted December 27, 2021 Author Posted December 27, 2021 Added two tracks to show the two aiming scenarios. IA-F-16CM-Canyon Run Attack CCIP on steerpoint diamond.trk IA-F-16CM-Canyon Run Attack CCIP on target.trk i7-12700KF - 64GB DDR4@3600MHz - RTX 4090 - HP Reverb G2 - Thrustmaster Warthog HOTAS - Thrustmaster Cougar MFDs - LG Rudder Pedals
Frederf Posted December 27, 2021 Posted December 27, 2021 Looks like an altimetry error. Steer is below possibly. You can tell a vertical error if it looks "in front" from all directions of approach. Was the atmospheric pressure different than standard? With normal CCIP you're using FCR in AGR, TGP with laser, or PR from DTS which makes the steerpoint elevation irrelevant as the system uses other distance information of higher quality. If the steerpoint was supposed to be on the surface that's a concern separate from CCIP. 2
Bowman-011 Posted December 28, 2021 Author Posted December 28, 2021 Seems like it has something to do with the weather effects, indeed. I recreated the mission by myself using default weather. With these settings everything seems normal. The steerpoint and the target are perfectly aligned (see added track file). Browsing through the weather settings I found that the temperature was configured to 0°C in the original mission compared to 20°C in my own replica. After changing this in my mission I could observe the same behavior with the steerpoint being ahead of the target. Is this to be expected? If so, how do I compensate such effects in the jet? If I wouldn't have a steerpoint right on top of the target I wouldn't be able to make the attack at all, because I wouldn't even notice the offset. IA-F-16CM-Canyon Run Attack CCIP own mission.trk i7-12700KF - 64GB DDR4@3600MHz - RTX 4090 - HP Reverb G2 - Thrustmaster Warthog HOTAS - Thrustmaster Cougar MFDs - LG Rudder Pedals
Frederf Posted January 1, 2022 Posted January 1, 2022 Simple barometric altimetry is pressure and temperature-dependent. Pressure-height relationship is "squashed" at colder temperatures and so a QNH-calibrated altimeter will read low relative to true height proportional to displacement from the calibrated level. But the F-16 system altitude is more sophisticated than that plus the AGR should make it moot since it's directly measuring CCIP slant. I have seen this effect though.
Recommended Posts