AWACS menu greyed out
-
I haven’t fixed it.
White fangs, if you are still interested, I will send it to you. Sorry, missed your post previously.
-
… you necro . I thought you’ve repaired it already by now.
Kinda busy atm, will probably late , but send it I will take a look when able. (and make a note for which theater is it)
Cheers
-
I’ve seen this myself over the years when creating TEs and never figured it out. …I think it’s a bug.
-
Could be a bug, I agree, but if not…
Zaltys and Gancio,
What is the distance from the Awacs on station flight path and you when you have this occur?
Zaltys you mentioned he is close, but I’m asking in miles.
-
Could be on my end, but I fragged a few TE Awacs flights, and it generated a flight plan that was eat up with red errors, when looking through it steerpoint by steerpoint.
If yours looks like mine just did, I can see how it wouldn’t respond. Easy enough to check his flight plan for red errors. Also you can even click in to his seat but don’t commit, then run the clock and
you may see some funny business by watching what he does on the map. -
… you necro . I thought you’ve repaired it already by now.
Kinda busy atm, will probably late , but send it I will take a look when able. (and make a note for which theater is it)
Cheers
Not me, it’s Gancio. Will try what Axe suggested.
-
I’ve seen this myself over the years when creating TEs and never figured it out. …I think it’s a bug.
Yeah, probably… but with what ?.. ‘Awacs’ itself , mission planner … or something else.
Eg. Here’s one tricky situation ,… when you’re on AG support with FAC mission , your Awacs is NOT the Awacs plane itself , then rather the FAC plane … so if (s)he gets shot down Awacs control doesn’t return to the real Awacs plane, … you loose your ‘mission Awacs’ (fac plane) for that mission.
Then you don’t have Awacs support anymore even the real Awacs , or two , is/are alive and available.
You may hear real Awacs on guard or team channel but you don’t have control… picture etc.What @Axe suggested isn’t far from the truth/ … Mission planner , not quite often, but here and then , ****s up flight profile waypoints… speed and time and length of the route , … maybe fuel calculations?..
So , maybe it just BUG’s out trying to abort false mission or even tries to fly it in proper profile which is erroneous.
AI is very confronted by the waypoint timing and always tries to do stuff ‘by the book’… but which was bugged by the mission planner itself at first.So, that’s why you can see sometimes, planes without packages or other-way around , packages without flight(s) , or other discrepancies … flight routes exceeding time / fuel… etc, not much left to say:)
BUT(big butt), most of the time it plays OK , so what’s really causing it … tough to pinpoint . … engine, vehicle/unit db , planner… campaign AI… that can even guess someone with access to the debug , but you can watch and at least capture (save) the moment and then we can do some ‘sniffing’ 'bout it. … Like this, it is pure guesswork I’m afraid , kinda zero chance of detail analysis., moreover finding the truth.
Cheers
-
What I tested and the results:
Made a TE with me flying out of Mandumi, and AWACS out of Fukuoka
Mandumi is a little over 300 miles away
Configuration is set for ‘Awacs Reguired’
All Awacs are airborne an hour prior to my take off time.With E-2C Hawkeye and me on runway, the Awacs Menu is alive but I receive no response. When I’m at 300 miles or closer I get responses.
With E-3A Sentry and me on runway, the Awacs Menu is alive but I receive no response. When I’m at 300 miles or closer I get responses. -
Crap, what are we doing wrong? I ain’t putting it past me to have something screwed up,
-
Yeah, checked that and it has ELINT. Also, tried to change E-3A to E-2C with no results.
E-3A and E-2C working for me. No dead menu, I get responses if within 300 miles.
weird…
-
Tried to build a brand new one and awacs works well. In the TE in question where having grayed menu, Tried to erased awacs flight, saved, close, reopen, add new awcs flight don’t make anything, still grayed menu. Something it’s still somewhere that caused this behavior