Releases: lukrop/GCICAP
Releases · lukrop/GCICAP
1.0.0-rc.5
- GCICAP doesn't use any event handler for despawning and removing logic anymore. A garbage collector is running various checks at a fixed interval and removes/despawns accordingly. This eliminates problems with stuck AI.
- CAPs have a (configurable) VUL time. This is the time they will be orbiting on-station. This can distribute traffic a bit better, lowering the possibility for AI flights to get stuck or the ATC to freak out.
- CAP flights now use the orbit task at a random point in their assigned zone. By default, for now, the 'Circle' orbit pattern is used because the race-track pattern often makes the flights move far outside their zones, potentially entering enemy airspace. If you still want to try it out set the gcicap.cap.race_track_orbit option to true. I'm already working on a technique to have realistically oriented race-tracks.
- Callsigns are now correctly assigned. Blue flights will use Colt and their flight number. Red flights will start at 601 and count up.
- The script should be less prone to spamming GCI flights. Before a GCI flight is spawned it checks if there are any free CAP or GCI flights closer to the new intruder than an airbase. It also tasks flights which are RTB.
- Initial spawning of groups can be delayed between each group.
- If using start
gcicap.red.start_airborne = true
orgcicap.blue.start_airborne = true
then the initial CAP flights will start mid-air already in their assigned CAP zones.
1.0.0-rc.4
created showcase mission for NTTR
Avoid roller caster on CAP routes.
Should fix #14 for real now.
Added check for trigger zones existance.