The short version is that the Lofte has two main algorithms, one to track the target (keeps the crosshairs on the target as the plane moves) when automation is engaged, and one to calculate the bomb release point for that target point. The problem is that the user's inputs are treated as different units (imperial vs metric, this is what happened before the beta) by each algorithm, or they use the IAS/TAS conversion tables that correspond to the other set of units (so if you are flying at 300km/h and 3000m, you look at the imperial chart in the manual and get your TAS for 300mph and 3000ft).
However, it seems this only happens for the bomb release algorithm.
That means you can either track correctly and release at the wrong time by using metric, or you can release correctly for the aim point by using the imperial data, but the aim point doesn't stay on the target because the tracking algorithm seemed to work in metric. And i say seemed, because with the beta patches that has also changed, now it won't stay in place.
What it should do is that once you calibrate for speed and altitude over target, it should require almost no correction at all.
There's also a video on the atag forums by Aus3620 that shows the current workaround for scoring hits, but we have a couple of things regarding altitude conversions that we need to test before deciding on the final way to do it.
In order not to derail this thread, here's the link to all bombers issues i have managed to collect with the help of other users:
http://forum.1cpublishing.eu/showthr...hlight=bombers
That thread needs a bit of updating because the pre-beta workaround doesn't work now (they changed something in the Lofte but it's still not working according to specification), but you can get an idea of what is left to debug. Cheers
