Administrator
Last active 9 years ago
Ok thanks for the report, we will look into it!
multispawn does not work in single player, you would need to run on a local MP or local dedicated server.
as for the second issue, thanks for reporting that, I'll get it fixed for the next release.
You can change the versioning settings in the require alive module to warn. As ToeJam says this warning is a leftover from the alpha and beta periods when frequent map updates forced us to release new ALiVE versions for every release.
Yeah not forgotten the wall of text :) I'll spend some time over the weekend going through it and answering those ones.
Yeah we can't carry over any init code currently, BIS removed setVehicleInit scripting command for security reasons, so like I say ALiVE is best used with mix of traditional editing methodology for achieving complex and custom set pieces and ALiVE modules for the dynamic and upredictablity aspects.
Yeah triggers have no effect on profiled units because they aren't there to trigger anything if despawned.
If they are spawned and you are using a name on the unit this also won't work because the profiling removes the names you give units in the editor.
I wouldn't worry too much about a couple of groups or whatever that are not profiled, shouldn't have much effect on FPS at all.
The moral of the story: If you want to achieve the fine grain control of triggers and complicated waypoint types or scripting, do not profile the units. Leave ALiVE to providing background ambience and dynamic chaos :)
Yeah, no worries, good that you are testing it thoroughly. Also different maps will have a big difference on init times also. A large scale mission on Altis with all the bells and whistles can take 2-3 minutes to init depending on the hardware.
Yeah that looks pretty standard to me. Init time will differ greatly, but resupply probably isnt the main culprit. Placement modules, CQB and OPCOM generally have the longest startup times.
Yeah checked with our release manager, we always use the same key since 2013, and no one else has reported issues, so I would assume something else is at play there.
WOW, that is a lot to cover, glad you are getting into it :) I'll try to get through all this over the weekend, thanks for the feedback!