unknown Posted June 19, 2016 Posted June 19, 2016 I had an unexpected behaviour of the radar azimuth scan zone. I did some testing and found the following behaviour in DCS 1.5.3 open beta. If i select the radar azimuth of 30° or 15° and have my TDC/scan zone direct in front of my aircraft and press the "Target CANCEL LOCK" button assigned to one of my warthog stick coolie hat everything works like expected, no target there and pressing the button results in nothing, so far so good. If i now move my TDC/scan zone a little to the left or to the right and press the "Target CANCEL LOCK" button my scan zone jumps to the left or right side of the HDD dependent on which side of my "aircraft ahead line" my TDC was. Have a look at the pictures below, pic1 shows the behaviour with the TDC centred before and after pressing the "Target CANCEL LOCK" button. pic 2 and 3 showing the strange behaviour with the TDC to the left and pic 4 and 5 shoing the same with the TDC to the right. I hope you can understand what i mean. I did a search in the Mirage Forum but couldn't find anything related. Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings
PiedDroit Posted June 19, 2016 Posted June 19, 2016 (edited) Yeah I reported that one a long time ago: While sweep is 30 or 15 degrees, pressing special mode deselect makes radar sweep go to all the way to the right or to the left (even if not previously in any special mode). Moving the TDC a little will put the radar scanned zone back to where it should be (i.e. linked to TDC). (1.5.3.51417.46) Bug Reports » Radar special mode deselect make sweep go full left or right Edited June 19, 2016 by PiedDroit
unknown Posted June 19, 2016 Author Posted June 19, 2016 Yeah I reported that one a long time ago: That is interesting, i only searched for the "Target CANCEL LOCK" button/function. I tried the "Special Modes DESELCT" button/function as you mentioned and i get a different behaviour than i described above or you described in your post. For this test i placed the Mirage in DCS 1.5.3 open beta in the air and switched the radar on, changed the radar azimuth to 15°(30° same behaviour) and panned the TDC to the left pic1, then i pressed "Special Modes DESELECT" and the TDC jumped back in the "ahead" position and the little dash was also scanning the "ahead zone" but the "zone marking" stayed in the previous position, see pic2. Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings
PiedDroit Posted June 19, 2016 Posted June 19, 2016 That is interesting, i only searched for the "Target CANCEL LOCK" button/function. I tried the "Special Modes DESELCT" button/function as you mentioned and i get a different behaviour than i described above or you described in your post. For this test i placed the Mirage in DCS 1.5.3 open beta in the air and switched the radar on, changed the radar azimuth to 15°(30° same behaviour) and panned the TDC to the left pic1, then i pressed "Special Modes DESELECT" and the TDC jumped back in the "ahead" position and the little dash was also scanning the "ahead zone" but the "zone marking" stayed in the previous position, see pic2. Indeed it looks like the same kind of bug but with different action. The one I posted is quite old, maybe the behaviour has evolved a bit since. I hope this will get some attention :thumbup:
Recommended Posts