raelias Posted September 8, 2018 Posted September 8, 2018 Hello, I found a buggy behaviour today on the radar Scenario is as follows: target is roughly 50nm away both aircraft at angels 19, radar is set at 40nm BUT i lock him up anyways using AAQC. The HUD shows his correct range, but im getting a flashing RNE cue (obviously spurious) A good lead to the root of the bug is that when the aircraft brakes the 40nm range (to which the radar is set on the right DDI) the cue corrects itself instanly I belive the shoot cue is somehow considering his simbology at a 80nm range radar as if it was at 40nm range or something like that, because when it shows on the top of the radar at 40nm it gets corrected Good luck! :pilotfly: Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf
raelias Posted September 8, 2018 Author Posted September 8, 2018 One more track now getting a RNE shoot cue from over 60nm awayShoot cue bug 2.trk Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf
raelias Posted September 13, 2018 Author Posted September 13, 2018 So... reported? Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf
Recommended Posts