Jump to content

AI CAS will engage when testing, but refuses when client is present; help


Recommended Posts

Posted (edited)

I'm working on a sandbox mission with a whole litany of random triggers, and one task in particular is driving me nuts. It should be rather straightforward:

1. F10 menu rolls random: pickup at LZ marked on F10 map.
2. Part of group from client CH-47s at Bastion enters 2nm trigger zone, blue infantry, red infantry+fire at point, and green smoke are spawned.
3. 10 seconds later, A-10 CAS support spawns and takes out the red infantry.

A-10 is set to CAS, search and engage group "red infantry" with guns, if flag is true+"red infantry" dead, AI push task to switch waypoint for RTB.

Here's where it gets weird. If I skip the F10 menu and do a timer-based trigger, with an AI CH-47F entering the trigger zone, everything works as it should. If I fly it as programmed above, with the F10 menu selection and a client CH-47F, the A-10 ignores the CAS tasking, the search and engage group tasking, and doesn't honor the group dead=switch waypoint programming either. It flies off without firing a shot.

The only two differences between it working and not working are:

A. Client CH-47F group instead of AI CH-47F group
B. Task triggered by F10 menu random flag instead of time more than x-seconds

Can someone take a look at this replay track showing the erroneous behavior and see what's going on, because I'm lost at this point. I set up a failsafe that explodes the offending infantry if they're still alive after some minutes, but ideally I'd like the A-10 to do it's job. 

The mission is a mess of triggers, but this one in particular is the set of 8 triggers labeled "Bastion-CH47-2" under the pink marked Bastion-CH47 F10/random flag headers.

Big track file (AI voicelines): https://we.tl/t-Fg5scD2Z1J

Edited by Nealius
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...