Search the Community

I do expect ED can do way better job on AWACS call and bandit calls, i do expect to get something like https://gitlab.com/overlordbot/srs-bot out of the box, however lets reduce expectation way lower than this at least AWACS should be a little more smart enough to give BRAA to closest bandits and be able to priories the bandits base on Range, closure rate and aspect, When I am going to get merge with hostile in transonic at 10 nmi, maybe I dont expect AWACS ignore that and give me info about enemy AWACS orbiting at angles 30 with distancer of 80nmi !

I have received a few requests for my E-7a AEW&C mod, so here it is. However, as I might release more AEW&C or ISR mods in the future, I am making a single thread to capture all of the "magic collection" This post will be reserved for download links. E-7a DOWNLOAD HERE (v1.1.0317): E-7a Wedgetail (AI only) (digitalcombatsimulator.com) P-8 DOWNLOAD HERE (v1.1.0408 ) P-8 Poseidon (AI only) (digitalcombatsimulator.com)

I've been struggling to get my E-2D's to maintain a decent airspeed so their escorts don't have to hang in the air like kites. Can anyone share some tips for good AWACS/Escort setups for missions?

Hello ED team, I'm a moderator on the Growling Sidewinder server and after getting several bug reports about disappearing datalink contacts, I started my own investigations. I set up a single player mission with a awacs and many bandits around him to see what happens. The results are quite interesting. I first started with my main plane the JF-17 and its seems like the awacs has a blind spot on his 10-11 clock position when orbiting. You can see that the Awacs doesn't fly a perfect orbit and every time it fly straight, all bandits are visible but if the Awacs is orbiting, the bandits on his 10-11 clock position disappears. I repeated the test several times and all awacs have this blind spot. Awacs blindspot.trk The Bug become really interesting when I started to check the issue with different aircraft's. I just changed my aircraft and therefor I should get the same result like in the test before but instead of having just one blind spot, I got TWO now in the Flankers. Repeated the test several times with the same results. This bug is not only awacs, its also plane dependent. Awacs blindspot Flanker.trk I hope you can fix the bug soon. Thank you for your time and effort.

Hello everyone. I hope you are fine. What is the best altitude and speed of AWACS? because I guess it must be ideal. awacs does not work most of the time, it either has to do with mission editor or its altitude and speed.

Getting braa calls every 2 seconds to every bandit in a 50000 nmi radius isn't helping, nor is it realistic. it's just clutter and you will just ignore it instead of constantly listening and trying to determine if it's a threat or no factor. Make it smarter. Here are my proposed changes that can only make things better, even if those changes are not perfect and could still be improved upon. However there is no need to make it perfect right away. Incremental updates can still be applied. Anything (except constant static noise or pop songs on the radio from awacs) is better than now. Even turning it off is better than the nonsense we have now. > 80nmi -> stfu (always) passing 80nmi -> braa call (once, time limit (maybe 60 seconds) to prevent bandits on parallel track to fade in and out of 80nmi generating a million calls) < 80nmi -> pop up call (once) passing 40nmi = braa call (once, limit see above) passing 20nmi = braa call (once, limit see above) contact faded/lost = call it (limit by time to prevent bandits popping in and out behind some mountains to be generating a million calls) this is important so you don't shoot a splashed bandit, potentially hitting a friendly instead contact regained = call it (limit see above) merge = merge call (once) anything else = only when you ask for it generally prevent the awacs from constantly annoying you for no reason. there really is no need to call out that mig29 on the other side of russia add type/print information if available add guessed type information if available (fighter, transport, helicopter by speed/altitude/rcs or monitored taking off an airfield for which intel indicates a specific type of aircraft being stationed there) call furball when asking for bogey dope when bandit mixed call groups and group composition when bandits within 10 nmi from each other new picture call every x minutes (no less than 5 to avoid clutter) or when significant alterations to the picture occured (multiple flights popped up/vanished/departed AO, etc) since awacs will now not be on the radio 99% of the time, you can remove that ugly 'fix' of them only talking to you and you not hearing awacs calls to anyone else. awacs will assign air targets to different flights that have checked in for dca/sweep people calling for help -> awacs orders other flights to change course and attack bandits, advising furball if needed. awacs will keep track of assigned air targets and updates the flight if parameters change (destroyed, furball, no longer a factor, new target, etc) awacs will keep track of ground attack aircraft and will warn them if their ground targets or the route to them have threats and advises fighters to attack to clear the path awacs will keep enemy aircraft away from friendly helicopters by assigning fighters to deal with them awacs will generally be helpful and not spam the radio all day long. when asked for this awacs will provide vectors and frequencies (if applicable) to nearest airfield, nearest threat aircraft (fighter), nearest bandit (any), flight leader, home airfield, carrier fighters can call awacs and tell them can not comply, or accept the task. fighters can check out from awacs and be taken out of the loop. ai will accept tasks if able (weapons, fuel, aircraft faults) ai will check out if unable to be effective

Something I really miss in the Huey is the ability to talk to "jtac" and "ewr/awacs" unit's in the radio menu. For the Hind this feels like a must have sice it's a attack helo and will (from what I understand) get the R60. But I guess the jtac would require a big rework of the core mechanic/communication so maybe something for the future? Just my two cents...

Trying setting up mission Iran F14B and Awacs(s), Jester will NOT show TAC Link when F14 is Iranian and Awacs is Iran/Russian A-50 Testing Joint Combined forces red/blue, still, ONLY USA/USA E3A works ?