Last active 9 hours ago
IIRC this is usually caused by the unit not following BIS config standards (insert joke here) for artillery units.
Try manually adding them to CS:
If that doesn't work then test with vanilla units - if they work OK then it's something with the M109
Nothing officially supported... you would need to add an event handler to watch for those events and run some code. I don't see anything on the wiki that would help you unfortunately.
I think by "alive insurgent" he means the one that is not dead :)
If you test the map again and find it's consistently buggy (spawning at 0,0) please post back here and I will update the wiki
More info on the dots and numbers in debug:
That's what we're trying to figure out... this has been reported before and yes it seems to work on hosted MP but not dedicated. The problem is no one has been able to reproduce the issue with just @ALiVE and @CBA_A3 which makes it difficult to pin down. The choppers issue I believe was fixed a while back (it was happening with any type of chopper) however it only seems to happen now with RHS assets.
One of the other testers suggested this.. might be worth a try:
"I’ve had mixed success using the CS modules in combination with manually placing the manned choppers and syncing them to the CS module (and putting the type and callsign code into the chopper init), but the success is mixed"
OK so apparently the chopper issue has been reported before - it only happens with RHS and 5 seems to be the max number of choppers. You can test this by using all vanilla assets for the choppers and report back.
If you can try disabling the HC and see if the AI units stop moving again. What you are reporting (AI standing around) has been reported before when using an HC.
For the objectives...yes in the placement module(s) there is a drop down to filter objectives.... set it to filter out small objectives on each module
And FYI.... as much as we love RHS it does seem to cause strange issues with ALiVE...