GAI and Intercept do not work

[Dusty Rhodes]

For GAI, I set up a MIG-29 on GAI with a loadout and a 25K Targetting Zone with "Planes" checked to attack. I didn't put anything else on the map except the MIG 29. I set it up first to take off from Runway. After 40 seconds it took off from the runway for no reason, entered the landing pattern and landed. Nothing else on the map and it did this. Then I set it to Take off from Parking or whatever it is called. After 40 seconds it started taxiing to the runway, took off, immediately entered the landing pattern and landed. Then I put an A10 in the mission flying from one end of the MIG 29's targetting zone, to the other end. The MIG 29 did the same thing, took off, entered the landing pattern and landed. GAI is broken.

 

I then tried the same thing with Intercept to see if I could get it to work. The MIG 29 did the same exact thing with the A10 on the map and without the A10 on the map. I think Intercept is broken also, though I am not sure what the difference between the two are, I am sure it isn't to just take off and immediately land when there is a target in your targetting zone.

 

May have already been reported, but if not, here it is. If it has been reported, sorry for the wasted post.

[Dusty Rhodes]

Pilot rating was set to Excellent, BTW.

[Dusty Rhodes]

OK, further testing met some positive and negative results. I put up an AWACS for the MIG 29 and put nothing else on the map. Wham, 40 seconds went past, the MIG took off, entered the landing pattern and landed. That needs to be fixed. It shouldn't be taking off if nothing is in the targetting zone. This happens when set to take off from runway or take off from parking area (Which was inside a hardened bunker hanger)

 

However I then put an A10 in the targetting zone doing CAP loops and 40 seconds went by, the MIG took off and then the MIG intercepted the Hog successfully. Kewl, that worked like it should. I then had the HOG fly from outside the targetting zone and into the targetting zone, 40 second went by, the MIG took off and successfully intercepted the HOG. Kewl, that worked great. I then had the HOG flying CAP loops about 15K outside the targetting zone and 40 seconds went by, the MIG took off and successfully intercepted the HOG when it should have never taken off at all because nothing was in it's targetting zone. That needs to be fixed. The targetting zone was set at 25000 meters and the zone started about 10KM away from the airbase.

 

I then tried Intercept from both runway takeoff and parking area take off. With the AWACS up and an A-10 doing CAP loops in the targetting zone, successful intercept. Successful intercept when the A-10 flew in the targetting zone from outside the targetting zone. But then I put the A-10 flying CAP loops outside the targetting zone and the MIG took off, entered the pattern and landed when it never should have took off. I then took the A10 off the map and it did the same thing, took off, entered the landing pattern and landed.

 

So GAI and Intercept work partially but there is work to be done to keep the MIG from taking off when it shouldn't.

[GGTharos]

If you attach your missions we can take a better look into it.

 

Here is an example GAI mission.

GAI-A10 Test.miz

[slug88]

Are you setting any waypoints for the MiG-29, besides the takeoff point?

[Dusty Rhodes]

No Waypoints, just set to GAI/Intercept in mission type.

 

GG, I did not save the missions but as you can tell they are easy to duplicate. One Mig 29, One A50, and one A-10 is all you need. I will have a look at your mission and see if I was doing anything different and see how yours goes.

[GGTharos]

You need to use GCI radars, not AWACS.

Set target zone area and target type (Plane).

[Dusty Rhodes]

I set the target zone area as I said in the report posts and and I set the target type to plane. I did use AWACS instead of GCI and it worked fine. The problem is their taking off when nothing is in the target zone. That should not happen. They take off after 40 seconds and immediately enter the landing pattern and land, taking themselves out of combat effectiveness. Now if something enters their zone, they will not respond. I will, however, run these tests again with GCI radars instead of AWACS and we'll see what happens.

[EvilBivol-1]

GAI flight should not be taking off when no targets are detected in the area. This is probably a bug. You can go around this bug by setting a delayed activation trigger to only activate the GAI flight when enemy aircraft enter your trigger zone.

 

However, Dusty, you should not assign a targeting point to the take-off point. Add at least one more turning point after take-off and make that your targeting point. Also add a post-targeting turning point. You generally never want to 'attach' a targeting point to either take-off or landing points.

[Dusty Rhodes]

GG I ran your mission and as I stated in my above report, it works fine intercepting, even when I used an AWACS instead of a GCI radar. The problem is that 40 seconds after the start of the mission, if there is nothing in their targeting zone, they take off anyways, immediately enter a landing pattern and land. That is the bug I am talking about. Just take your mission and get rid of everything but the GAI flight and the radar and run the mission and see what happens.

[Dusty Rhodes]

GAI flight should not be taking off when no targets are detected in the area. This is probably a bug. You can go around this bug by setting a delayed activation trigger to only activate the GAI flight when enemy aircraft enter your trigger zone.

 

However, Dusty, you should not assign a targeting point to the take-off point. Add at least one more turning point after take-off and make that your targeting point. Also add a post-targeting turning point. You generally never want to 'attach' a targeting point to either take-off or landing points.

 

Copy that on the targeting point not attached to take off or land. I will remember that when building missions.

 

The bug is that they are taking off and immediately landing even though there is nothing in their targeting zone. That is a good work around. I never thunk of that. But again, this is a bug and we shouldn't have to work around it, though it is nice to have a work around whilst we wait to see if ED addresses the bug.

[Duke49th]

Is the bug fixed with 1.01 ?

 

Thanks.

[goldfinger35]

I have tested it; bug is still here.

We have to use workaround with triggers.

[Duke49th]

I have tested it; bug is still here.

We have to use workaround with triggers.

 

Thanks for info.;)

 

Daaammmm...:mad:

 

Please, ED, don't forget to fix this bug in the next patch/module!

[Gunhawk]

Thanks for info.;)

 

Daaammmm...:mad:

 

 

Please, ED, don't forget to fix this bug in the next patch/module!

 

Has this been ever fixed? I thinks it is even in FC and beyond.

 

Gunhawk

[Anastasiuss]

any changes in 1.0.2? Does GAI function now like in the manual described?

 

GAI (Ground Alert Intercept). When taking part in a GAI mission, an aircraft is

on alert duty on the runway with warmed-up engines. On receiving AWACS or

other targeting data of in-bound enemy aircraft, the aircraft takes off and

attempts an intercept. Multiple GAI aircraft will take-off one after another to

intercept enemy aircraft. When planning this type of mission you don‟t need to

create waypoints. All you have to do is set the takeoff point at an airfield and

declare it as a GAI Task. Note that when planning a GAI mission, the aircraft on

alert don‟t appear on the runway until the target data becomes available. For

best results, place early warning radars such as the 1L13 and 55G6 at the

airbase.

 

Does somebody have a examplemission?

[Anastasiuss]

I have created a GAI Test Mission.

#1 1 red Mig 29 Agressor WP straight ahead to the AWACS

#2 1 blue F-15 task: GAI, no WP, no holding time

#3 1 blue F-15 task: GAI, one WP, no holding time

#4 1 blue E-3 AWACS

 

#3 starts before the MIG in reach of the AWACS radar (~230-245 km) is.

#2 starts never

Any ideas? Is the radar reach of the AWACS right?

GAI-TEST.miz

[Gunhawk]

I have created a GAI Test Mission.

#1 1 red Mig 29 Agressor WP straight ahead to the AWACS

#2 1 blue F-15 task: GAI, no WP, no holding time

#3 1 blue F-15 task: GAI, one WP, no holding time

#4 1 blue E-3 AWACS

 

#3 starts before the MIG in reach of the AWACS radar (~230-245 km) is.

#2 starts never

Any ideas? Is the radar reach of the AWACS right?

 

I am afraid that this has never been fixed remembering this from even the Flaming Cliffs V1 or even from Lock-on series. Aparently there is no terrain masking as i.e. AWACs can detect you while sitting on runways at ranges it would when flying at 20.000

 

regards Gunhawk

[Anastasiuss]

AWACS has a radar with unlimited reach and penetration? Can I read up the reach in a LUA-file?