Ahmed Posted April 25, 2022 Posted April 25, 2022 Hi, While ED staff are probably not aware, A LOT of the DCS online virtual squadrons don't use the AI CATCC. This may be due to immersion reasons preferring SRS to AI comms, having a human controller, or not liking some of the inconsistencies. However, ED seem to have implemented this as only working with following the whole script of AI comms. Can you at least consider making the lock-on work after only making the initial AI marshal check-in, so that the online virtual squadron community can also use ACLS? Ideally it would work even without that, but at least gives us the option to use it after only entering the F10 menu once. 6
ED Team BIGNEWY Posted April 25, 2022 ED Team Posted April 25, 2022 Hi Ahmed I will pass on your comments to the team, but can make no promises. thank you 1 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
Ahmed Posted May 27, 2022 Author Posted May 27, 2022 @BIGNEWY thanks. Now that a logic was added to the non-SC carriers, would it be possible to pass the team the idea of having the same logic to be used in the SC so that ACLS lock-on is simulated from 5.5nm/1200ft/5º when only calling Inbound on the SC without following the rest of the CATCC script? This would allow the same logic of the Stennis to work too in the SC for the many online squadrons that want to use ACLS but don't want to use the CATCC F10 commands and want the simple Stennis logic to work on the SC. 3
Swift. Posted May 28, 2022 Posted May 28, 2022 (edited) +1 super critical feature request IMO. You've spent so much energy creating the ACLS system, only for it to not be used by online groups because it's tied to a single player comm system! Super simple fix, super important impact Edited May 28, 2022 by Swift. 3 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2
JackCooper Posted May 29, 2022 Posted May 29, 2022 +1 contacting AI durig case 3 in big groups only makes trouble 1
CaliJoshua Posted Monday at 11:02 PM Posted Monday at 11:02 PM On 4/25/2022 at 12:38 AM, BIGNEWY said: Hi Ahmed I will pass on your comments to the team, but can make no promises. thank you It has been a few years and we are doing more CASE III with human CATCC. Any chance this is being worked on?
Coyle Posted Tuesday at 12:21 AM Posted Tuesday at 12:21 AM (edited) 1 hour ago, CaliJoshua said: It has been a few years and we are doing more CASE III with human CATCC. Any chance this is being worked on? I remember the day the ACLS video dropped. I was so excited to finally hook up to it and properly call in needles... And yet before I even pressed play on the video, I knew it would be tied into the blasted AI comms. Of course, to the surprise of no one it was, and I sought out a solution to bypass it. I remember later after it released that not even twenty minutes of messing around with it, I could bypass it via Viacom and the command "Platform", only needing to be within the conditions to do so at the back of the carrier where one would call for it and it worked. No obnoxiously tedious AI call ins for our large multiplayer squadron necessary once I spread the word. I even went so far as to ask for direct support from the Viacom devs to help streamline this method a bit but since they didn't seem to understand the issue, it went nowhere. Still, I would wind up using this little trick for a time. It had been so frustrating seeing my and many others request to get this sorted for the multiplayer crowd ignored, with our lovely community managers demanding an essay on why they should take the time to support such a change. Things never change here at ED I suppose. Edited Tuesday at 12:24 AM by Coyle
Recommended Posts