Lisovsky Posted June 2, 2024 Posted June 2, 2024 (edited) I encountered a strange problem. In almost all horizontal bombing modes, the bombs fall short by about 1.5 miles. Even with perfect compliance with the specified parameters. The “cure” was moving the aiming point to these 1.5 miles. That is, now the bombs are falling not at her, but at the IP. Perhaps it's worth clarifying. What is important is that the bombs hit the IP. Which can be located at any distance. It is enough just to move the aiming point to the same distance. In any mode, the undershoots are simply monstrous. As a rule, about 1-1.5 miles, even with the most accurate speed and altitude control. I fully believe in an error of a couple of hundred meters due to errors, but not that much. Jester says "next point IN" too soon. Accordingly, the release button is pressed too early and the bombs fall short. You can easily check this yourself by setting a point above some clearly visible building. And I also noticed that Jester often doesn't enter any data into the computer at all... Edited June 2, 2024 by Lisovsky
Grundar Posted June 2, 2024 Posted June 2, 2024 That does seem strange, the bombing computer https://f4.manuals.heatblur.se/dcs/bombing_computer.html should allow you to calculate it quite effectively and allow you to feed that info to Jester. Maybe a value is off by mistake and is throwing that off?
Lisovsky Posted June 2, 2024 Author Posted June 2, 2024 I checked literally dozens of times. Accurate bombing based on Jester's commands became impossible for me. With the exception of the DTOSS mode, of course, and “laser” bombardment.
Zabuzard Posted June 2, 2024 Posted June 2, 2024 Could you share a track or video?Jester calls out switching turnpoints within 1nm, as that's the usual distance used to initiate a turn. You should definitely not use that to start your bombing run. A VIP has to be visually identifiable, clicking bomb button the moment you are visually over it. If you really want to use the Nav system for this, make your IP a holding point, not turn point and look at the distance on the HSI and wait until it reaches zero. Or put the target as your waypoint and wait until the distance reaches the desired release range, for example 2nm.Note that when you fly your pattern, the airspeed you set is TAS, not IAS. So you need to fly the numbers shown on your TAS gauge - sth I see people often do incorrect.Hope that helps, cheers :) 1
Recommended Posts