Important note for users of MOOSE and the SPAWN class

[Pikey]

Due to a change in the way Eagle Dynamics handle addGroup https://wiki.hoggitworld.com/view/DCS_func_addGroup (spawning) at Airbases, late activated templates will have their parking spot honoured, regardless of whether there is another plane in that spot. This affects Spawn(), Respawn(), SpawnScheduled(). It affects the AI_Balancer module and may affect user missions and other modules (extent to be determined).

 

The previous behaviour was that addGroup would determine an available free parking spot at an airbase inherently.

 

The current behaviour, I'm not sure I completely understand, but it appears there is now no check on the airbase parking spot when the group is activated. I have not determined affects on carriers or farps/rigs. This is occuring for approximately 4 weeks.

 

Test case:

Code: SPAWN:New('spawnme'):SpawnScheduled(1,1)

Old behaviour: The template would spawn a new plane and take the next available free parking spot. After the number of seconds equal to the number of parking spots, planes will have occupied every available parking spot at the airbase.

New behaviour: The template takes the same spot, despite others being available. If the previous plane has not vacated there will be a collision.

 

 

Mitigation:

SpawnAtAirbase() https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Spawn.html##(SPAWN).SpawnAtAirbase is a method that will do the check on the availability of the parking spot for you and find an available one, by default, unless parking is specified.

 

We await to discover if this change is by accident and a defect, or by design and permanent. In either case, we would strongly advise checking your missions, avoiding indiscriminate spawning using Respawn or scheduled Spawns, in particular.