TomCatMucDe Posted April 9, 2016 Posted April 9, 2016 Hi guys, I have observed that after unlocking a target the radar elevation will go decrease and the radar will point down , at 20 miles it will scan between negative altitudes. Anyone has seen the same issue? Regards
jojo Posted April 9, 2016 Posted April 9, 2016 Where was your forget when you unlocked ? Mirage fanatic ! I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2. Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi
nomdeplume Posted April 10, 2016 Posted April 10, 2016 (edited) I just encountered something that might be related. Head-on contact (B-52) at about 45 nm. My altitude ~18,500, theirs ~15,600. Was able to tag it for PID mode, but after a few seconds the contact was dropped. Altitude readout at the radar cursors says 0 - (-33). When I reset the antenna elevation the contact re-appears. Attached screenshots might show it clearer than I'm describing. First: before tagging contact for PID/TWS. Second: contact is tagged. Third: right after losing contact. (Elevation is 6 to (-27) - did not take screenshots first time it happened.) Edit: some more playing with it, and it looks like it's related to the player's pitch axis. Pointing the nose down results in the altitude cursor showing higher numbers, pulling the nose up causes lower numbers. With pitch at -11 degrees (as shown in the statusbar in F2 view) the cursors are showing 49 - 33 for the altitude. This does not occur without a contact tagged. It looks to me like the antenna elevation just remains where it was when the target is lost, which I think is the expected behaviour. The strange occurences with PID/TWS mode might be unrelated. The min/max altitude readout does change with a target locked in PIC/STT, but only as expected. Edited April 10, 2016 by nomdeplume
Recommended Posts