Topper81 Posted May 26, 2021 Posted May 26, 2021 (edited) Steps to reproduce: - Activate boresight mode (SCS FW) - Lock a target - Try to make the ATFLIR SOI (SCS LFT) ==> Will not work; Instead the radar goes into WACO mode; I don't expect this as long as a target is locked because else there is no way to zoom in on the ATFLIR display to identify the target. To activate WACO mode I excpect to have to undesignate the locked target first and then press SCS LFT. (Same behaviour as for AACQ mode) WACO.trk Edited May 26, 2021 by Topper81
Hulkbust44 Posted May 26, 2021 Posted May 26, 2021 Steps to reproduce: - Activate boresight mode (SCS FW) - Lock a target - Try to make the ATFLIR SOI (SCS LFT) ==> Will not work; Instead the radar goes into WACO mode; I don't expect this as long as a target is locked because else there is no way to zoom in on the ATFLIR display to identify the target. To activate WACO mode I excpect to have to undesignate the locked target first and then press SCS LFT. (Same behaviour as for AACQ mode) WACO.trkWell the ACM modes are taking priority here, as they should. Yes, it is annoying. SCS right in ACM doesn't have a function so FLIR to right DDI should work.Mobius708
Topper81 Posted May 26, 2021 Author Posted May 26, 2021 (edited) No that even isn't working. I cannot make ATFLIR SOI even not on the right side. Edited May 26, 2021 by Topper81
VIXEN413 Posted May 26, 2021 Posted May 26, 2021 I saw the same behaviour and it kinda make sense since you are in ACM and the logic of that A/A mode take precedence over DDI sensors of interest. Same if U wanna go AMPCD SOI, you ll just enter VACQ... Thing is, if you are in ACM and lock a target, the Flir on left DDI Will go on him (L&S pointing) but no auto track will be done. the only way to get away from the ACM selection is to undesignate but that will send your pod to Rome unfortunatelly... So use ATFLIR in Radar mode not in ACM modes and U should be good... Rig: MB Gigabite z390UD, CPU Intel I7 8700k, RAM 32G DDR4 3200 Gskill ripjaws, GPU MSI RTX2080SuperOC, HDD Crucial mx500 1tb M2 sata, PSU Corsair 850W, watercooling Corsair h100, Controlers TM f/a 18 stick on Virpil warbrd base, TM cougar f16 stick on cougar base, Cougar F16 throttle on TUSBA, ch pedals, TM cougar MFD 27" monitor with trk IR 5 and HP Reverb HMD. Modules F18, F16, F86, Mig15, FW 190D9, Nellis range map, Aggr campaign, Middle East map
Topper81 Posted May 26, 2021 Author Posted May 26, 2021 26 minutes ago, VIXEN413 said: I saw the same behaviour and it kinda make sense since you are in ACM and the logic of that A/A mode take precedence over DDI sensors of interest. Same if U wanna go AMPCD SOI, you ll just enter VACQ... Thing is, if you are in ACM and lock a target, the Flir on left DDI Will go on him (L&S pointing) but no auto track will be done. the only way to get away from the ACM selection is to undesignate but that will send your pod to Rome unfortunatelly... So use ATFLIR in Radar mode not in ACM modes and U should be good... As I understood, the ATFLIR should track the target opticaly by pressing SCS left twice (Frist time: Make ATFLIR SOI, Second time for locking the target) so there is no reason. So you can undesignate the L&S pointing without loosing the ATFLIR lock by pressing SCS left twice, make radar SOI (pressing SCS right in the standard DDI configuration) and press undesignate. But I'm not sure here but this is what I would expect.
ED Team BIGNEWY Posted May 26, 2021 ED Team Posted May 26, 2021 Hi, if you have evidence it should be any other way please DM me with the information. thank you 1 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Topper81 Posted May 26, 2021 Author Posted May 26, 2021 (edited) Thank you BIGNEWY but from my side I havn't, but if you even don't have an evidence in your sources our best expactation is that we can expect that it should be possible to make the ATFLIR SOI somehow to zoom in the designated target to identify it using HOTAS. And currently I see no way doing that without loosing the lock of the target or releasing the HOTAS. In ACM mode, we can expect the pilot is allready very close to a CAC/dogfight situation and then it seems to be impertinence to me to excpect that the pilot has the time to release the HOTAS and press some push buttons on DDI's to make it possible to identify the target for a shoot / no shoot decision because each second can decide if the pilot will survive or not. Just my 50 Cent... Edited May 26, 2021 by Topper81
Jak525 Posted May 26, 2021 Posted May 26, 2021 (edited) Behavior is correct. The Hornet remains in ACM condition while in STT having entered STT from an ACM mode; hence "ACM" still being boxed. There is no need to assign FLIR TDC priority to make it slave to the L&S I'd note also. That being said the boxed "ACM" button on the Attack format in STT should be able to be pressed to exit the ACM condition but stay in STT. Pressing "ACM" in an acquisition mode like WACQ will exit it entirely, but for STT, it stays in STT while exiting ACM. This is the solution to your issue if you wanted to use the castle switch to assign TDC to the FLIR. The caveat would be that there is no way to do this when the Gun is selected as in that scenario the ACM condition is not exitable. What you describe here is not a bug. However there is a separate bug here if the behavior I mentioned doesn't work. I'd give it a test. Edited May 27, 2021 by Jak525 4
Recommended Posts