=4c=Nikola Posted May 30, 2018 Posted May 30, 2018 (edited) OT Edited August 22, 2018 by =4c=Nikola Do not expect fairness. The times of chivalry and fair competition are long gone.
Auditor Posted May 31, 2018 Posted May 31, 2018 Azimuth scan for me was always whole numbers. I have a small bug report on the radar as well: PRF doesn't appear to function despite functioning in the review videos, which leads me to believe that it's a new bug. Steps: Enter radar Press MFD button for PRF, default is high/med. Notice no change.
Solid84 Posted May 31, 2018 Posted May 31, 2018 1.Does anyone experience azimuth scan crazy numbers. It should be 20, 40, 60, 80, and 140 degrees, but it changes to 8, 28, 38, 48... Is that correct behavior? i've experienced the same thing I5-7600K@4,8Ghz - G Skill TridentZ 16Gb 3200 CL14 - Aorus GTX 1080TI - Samsung 950 PRO 512GB NVMe M.2 PCIe 3.0 x4 - Lenovo 24'' 1440p - Hotas Warthog - TrackIR 5 DCS 2.5 OB - M2000C - Mig21Bis - A10C - FC3 - AJS37 Viggen - F5E - AV8B N/A - F/A18 C - L 39 Albatros - Bf109 - Spitfire - P51D - Black Shark 2 - Nevada - Persian Gulf - Normandy
Andrei Posted May 31, 2018 Posted May 31, 2018 1.Does anyone experience azimuth scan crazy numbers. It should be 20, 40, 60, 80, and 140 degrees, but it changes to 8, 28, 38, 48... 2.Sensor Control Switch Right in ACM doesn't work. It should be "Exit ACM mode to Return To Search (RTS) " Is that correct behavior? I've had same issues as you did, both 1 and 2. But I could not yet figure if it was a bug or user error. I think it all started when I entered AACQ - when you press sensor select RIGHT when the radar is already selected. After that I started to get that strange azimuth scan angles and could get to the normal RWS anymore. It was either ACM modes, or this AACQ. AMD R7 5800X3D | Aorus B550 Pro | 32GB DDR4-3600 | RTX 4080 | VKB MGC Pro Gunfighter Mk III + STECS + VKB T-Rudder Mk4 | Pimax Crystal FC3 | A-10C II | Ка-50 | P-51 | UH-1 | Ми-8 | F-86F | МиГ-21 | FW-190 | МиГ-15 | Л-39 | Bf 109 | M-2000C | F-5 | Spitfire | AJS-37 | AV-8B | F/A-18C | Як-52 | F-14 | F-16 | Ми-24 | AH-64 | F-15E | F-4 | CH-47 NTTR | Normandy | Gulf | Syria | Supercarrier | Afghanistan | Kola
bwRavencl Posted May 31, 2018 Posted May 31, 2018 I've had same issues as you did, both 1 and 2. But I could not yet figure if it was a bug or user error. I think it all started when I entered AACQ - when you press sensor select RIGHT when the radar is already selected. After that I started to get that strange azimuth scan angles and could get to the normal RWS anymore. It was either ACM modes, or this AACQ. Yes I am heaving the same issues. 1. Sensor Select Right does not exit ACM mode 2. When in AACQ mode and hitting Sensor Select Down, then Undesignate, the radar stays in an 8 degree scan mode. Now if you increase the scan zone by clicking the corresponding button on the MFCD, you can choose invalid scan zones, such as 252° (screenshot). After switching through the scan zone sizes multiple times by clicking the MFCD button it will return to the allowed values eventually and remain within the allowed set, unless you provoke it again. ControllerBuddy - A highly advanced game controller mapping software (for flight simulators)
112th_Rossi Posted May 31, 2018 Posted May 31, 2018 Same here. Can lock up initially, but can't unlock and return the radar to RWS. The issue seems to be after I have shot down a plane with AIM7. I think, the radar is still trying to track even if the target is dead.
LazyBoot Posted May 31, 2018 Posted May 31, 2018 Yes I am heaving the same issues. 1. Sensor Select Right does not exit ACM mode 2. When in AACQ mode and hitting Sensor Select Down, then Undesignate, the radar stays in an 8 degree scan mode. Now if you increase the scan zone by clicking the corresponding button on the MFCD, you can choose invalid scan zones, such as 252° (screenshot). After switching through the scan zone sizes multiple times by clicking the MFCD button it will return to the allowed values eventually and remain within the allowed set, unless you provoke it again. I noticed the same, at some point I could also select weird amounts of scan bars.
Deadpoetic6 Posted May 31, 2018 Posted May 31, 2018 omg I though I was crazy! I have the same problem! Crazy scan range number, and unable to lose lock sometimes. Even turning the radar off and back on to operate would still lock on the target, even if it was behind me!
112th_Rossi Posted May 31, 2018 Posted May 31, 2018 I've unbound sensor right for now. I'm using the regular ACM modes
bradleyjs Posted June 3, 2018 Posted June 3, 2018 So, has there been any resolution to these issues??? Alienware Area 51 R5 - Intel i9 7980XE (4.7 GHz), 32GB Dual Channel HyperX DDR4 XMP, Dual NVIDIA GeForce GTX 1080 Ti Graphics 11GB GDDR5X SLI, 4.5 TB combo of SSDs/HDDs, Alienware 1500 Watt Multi-GPU Power Supply, Alienware 25” 240Hz Gaming Monitor, Alienware Pro Gaming Keyboard, TM HOTAS, TM Cougar F-16C MFDs, Saitek Pro Flight Rudder Pedals, TrackIR5, Win10 Pro x64
bradleyjs Posted June 3, 2018 Posted June 3, 2018 Ok thanks - i will give it a try. Alienware Area 51 R5 - Intel i9 7980XE (4.7 GHz), 32GB Dual Channel HyperX DDR4 XMP, Dual NVIDIA GeForce GTX 1080 Ti Graphics 11GB GDDR5X SLI, 4.5 TB combo of SSDs/HDDs, Alienware 1500 Watt Multi-GPU Power Supply, Alienware 25” 240Hz Gaming Monitor, Alienware Pro Gaming Keyboard, TM HOTAS, TM Cougar F-16C MFDs, Saitek Pro Flight Rudder Pedals, TrackIR5, Win10 Pro x64
Jerec Posted March 2, 2019 Posted March 2, 2019 The SA-6 Kub LN 2P25 dosn´t appear on the RWR. A bug? This SA-6 Kub unit also doesn´t attack me.
Opalias Posted March 2, 2019 Posted March 2, 2019 The SA-6 Launcher has no radar of its own, you need to add the matching tracking radar (tr) to the group. That will fix both problems.
Recommended Posts