witness_me Posted January 2, 2020 Posted January 2, 2020 (edited) if i have one or more aircrafts targeted as HPT/SPT or STT/DTT and manoeuver so that they're located near my radar's horizontal gimbal limits (i.e. crank), the radar elevation sometimes drops below the elevation required to continue tracking these targets, without any input from me, however the track remains stable The problem this causes however, is that if radar lock is lost (e.g. accidentally banking / turning away from the target at a greater angle than the elevation gimbal limit of the radar ~30 degrees during cranking), the elevation when the radar starts scanning again is set to whatever that buggy elevation value was, making re-acquisition of the target problematic (e.g. if the player didn't notice the target's altitude, just before the track was lost etc). The same problem will happen if i want to deselect for example one of the DTT targets, so that i can pick another one - the radar elevation will drop to whatever the buggy value is, so then i have to raise the elevation again / wait to re-acquire tracks etc in the screenshot below you can see that the target is at 20k ft, the radar cursor is showing 15/3 and the radar elevation is -7 degrees, all while i maintain stt on it in this screenshot the target is at 23k ft, the cursor is showing 17/8 and the radar elevation is -6 degrees Edited January 2, 2020 by witness_me
witness_me Posted January 2, 2020 Author Posted January 2, 2020 another one, the target is about 2k ft above me, radar elevation is -13, cursor is showing -29/-46
foxwxl Posted January 3, 2020 Posted January 3, 2020 (edited) Some part of radar elevation stablization calculation is wrong based on airframe at current OB build and thus cause such problem like very large elev angle when U break lock at F-pole or cranking. This has been fixed internally and changed to space stablization. Waiting to be validate once update is available. Edited January 3, 2020 by foxwxl Deka Ironwork Tester Team
witness_me Posted January 3, 2020 Author Posted January 3, 2020 Some part of radar elevation stablization calculation is wrong based on airframe at current OB build and thus cause such problem like very large elev angle when U break lock at F-pole or cranking. This has been fixed internally and changed to space stablization. Waiting to be validate once update is available. thanks for letting us knwo mate
Tiger-II Posted January 4, 2020 Posted January 4, 2020 I see this as well. Good to hear it's hopefully fixed! Motorola 68000 | 1 Mb | Debug port "When performing a forced landing, fly the aircraft as far into the crash as possible." - Bob Hoover. The JF-17 is not better than the F-16; it's different. It's how you fly that counts. "An average aircraft with a skilled pilot, will out-perform the superior aircraft with an average pilot."
Recommended Posts