Ops.CSAR was throwing the following errors constantly when a player would leave the CSAR helo:
GROUP05000.GetDCSObject((ERROR: Could not get DCS group object of group Archer-1 because DCS object could not be found!))
This was because the SET_GROUP FilterStart on allheligroupset was not handling the scenario when a player left w/o a death.
Co-authored-by: Mike Young <117502908+DarthZyll@users.noreply.github.com>
Ops.CSAR was throwing the following errors constantly when a player would leave the CSAR helo:
GROUP05000.GetDCSObject((ERROR: Could not get DCS group object of group Archer-1 because DCS object could not be found!))
This was because the SET_GROUP FilterStart on allheligroupset was not handling the scenario when a player left w/o a death.
the Label and port were not being pulled from MSRS Config, causing them to default to "MESSAGE" and 5002 when calling the MESSAGE.SetMSRS() function with no params
Co-authored-by: Mike Young <117502908+DarthZyll@users.noreply.github.com>
the Label and port were not being pulled from MSRS Config, causing them to default to "MESSAGE" and 5002 when calling the MESSAGE.SetMSRS() function with no params
* Adding a new TerminalType (100)that seems to be introduced in the update that brought Muwaffaq Salti. The base has a couple of spots (like 04, 05, 06) that can only accommodate smaller type fixed wing aircraft, like the F-16, but not bigger types like the Warthog of the Strike Eagle.
Because we weren't checking for this new type, spawning in these particular spots always resulted in an airstart, because `_CheckTerminalType` would always return `false`
* Adding Shapes over from old MOOSE branch
* cleanup
* adding HEXtoRGBA
* removing Arrow.lua, it's part of Polygon.lua
* Fix when DCS adds duplicate points to the `points` table of a drawing, resulting in wrong triangulation
Applevangelist