AWACS menu greyed out

[Zaltys]

Posted this question on ITO but got no answer there, probaly here will get more luck:

I’ve created TE in ITO and menu of AWACS is greyed out. All are on the same side/team, even tried same package, distance from package is short, AWACS is on station and providing general picture calls.

Any thoughts?

[DBond]

What is the role for the AWACS at the station steerpoints? Usually, when you frag an AWACS they default to ‘training’. It should be set to ELINT. If it is, I am already out of ideas.

Edit: Actually, maybe it doesn’t ‘default’ to training, but I have seen this happen.

[Zaltys]

Yeah, checked that and it has ELINT. Also, tried to change E-3A to E-2C with no results.

[white_fang]

If …. I’ve seen similar behavior in Balkans , when 2 AWACS swap shifts. … one is close to going home , the other, new one, is still not in the “loop” , so the commands were greyed-out , but the calls were working from the old one which was on RTB.

I flew campaign mission without support , the calls ceased totally after mission time +0.30 ~ 1hr , the old AWACS went silent, but the new one didn’t “fire up”.

The next mission was OK, the new AWACS was working Ok.

Are the calls, that are working, coming from old AWACS or yours new AWACS ?

You can try saving campaign, skip that mission and try flying next one , 30mins ~ 1hr later in campaign, then check if the new awacs is working ok, … if not, then I don’t know… something is NOT OK

I’ve never seen (in Balkans) that default mission for AWACS is training??? It should be ELINT 99%,… what are mission profiles in DB for E-2c/E-3 ? …
It should be ELINT 90% and Training 10% , but Training should never fire up because of ATC mission profiles, check units in DB editor.

Also check the saved mission with Mission Commander (for your team) under tab TEAMS > Bonus/Priority > Mission … then see entry “Training” should be 0(%).

Cheers

[Zaltys]

It’s a TE and there is only one AWACS, which is on station 30 minutes prior of package T/O. And yes, priority of training in MC is set for 0 percent.

Thing is that I really have seen working AWACS in ITO TEs, but can’t find where problem is in this TE.

[white_fang]

Can you post that TE , if not a problem , I have ITO installed here so I can check real-time , … is it “Add-On Israel” or “Add-On Carrier Ops ITO” ?

It is really hard to say what is fubar just like that out of description … many things involved. From unit itself , then mission profile, then even team setup, but somehow I think is nothing that I’ve said here.

But, still I’ll gladly check for ya.

Cheers

[Gancio]

Any news about that awacs probs? Balkans TE, same conditions and properties and same grayed menu.
As usual, place first squadron then create a flight.

[Zaltys]

I haven’t fixed it.

White fangs, if you are still interested, I will send it to you. Sorry, missed your post previously.

[white_fang]

… 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

[Mower]

I’ve seen this myself over the years when creating TEs and never figured it out. …I think it’s a bug.

[Axe]

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.

[Axe]

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.

[Zaltys]

@white_fang:

… 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.

[white_fang]

@Mower:

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

[Axe]

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.

[Axe]

Crap, what are we doing wrong? I ain’t putting it past me to have something screwed up,

[Axe]

@Zaltys:

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…

[Gancio]

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