Member
Last active 5 years ago
Yepp, seen that before. Think it has to do with the setFog
command and different decay and base values. Shows up in vanilla too, so pretty sure its unrelated to ALiVE.
Try executing 0 setFog 0
on the server and see if it goes away ....
The AI distributer affects only server owned AI, and distributes them across all detected HC's in a circular fashion. If you spawn AI on a HC, they will stay there, as there is no loadbalancing between the HC's.
Check your server logs for ALiVE SYS DATA PNS - Local machine is not the server or local save not available! Exiting...
If that message appears, you don't have your Data module set up correctly (make sure you have PNS set as datasource).
Otherwise there should be an on-screen save message every 900 seconds, and log lines from each module that have persistance enabled.
Check these sections for reference:
https://github.com/ALiVEOS/ALiVE.OS/blob/master/addons/sys_data_pns/fnc_autosave.sqf#L31
https://github.com/ALiVEOS/ALiVE.OS/blob/master/addons/sys_data_pns/fnc_autosave.sqf#L43-L49
https://github.com/ALiVEOS/ALiVE.OS/blob/master/addons/sys_data_pns/fnc_autosave.sqf#L88-L146
https://github.com/ALiVEOS/ALiVE.OS/blob/master/addons/sys_data_pns/fnc_autosave.sqf#L150-L153
Could you get a server rpt up on pastebin or something, or just check the logs for ALIVE AI Distributor switching group '<group_name>' to HC '<hc_name>'.
.
Make sure your CS assets group(s) isn't being listed as transferred.
I have a hard time believing this is caused by ALiVE_sys_acemenu
, since its not even loading.
The ALiVE_sys_acemenu: ACE interact_menu not active or no interface found, exiting
message is expected in the server logs, since it doesn't have an interface. And loading continues normally after that.
All CS units have the exclusion variable set so they get skipped in the ALiVE HC script. If you're using any other HC script, CS may break.
If you're doing it at init it might be a problem with module init, i.e the module hasn't completely started when you run the pause.
Try doing it manually from the debug console (Exec Server
) after the server logged ALiVE Global INIT COMPLETE
.
All CS assets are already exempted from switching locality, so everything should work just fine as long as you're using the ALiVE AI distrubutor. If you're running Werthles's HC scripts it will break.
If you get a server log up on pastebin and link it here, we could have a quick glance if anything looks out of order ....
What was the log message it froze on ?
Unfortunately its hardcoded, so cant be controlled through static data mapping.
https://github.com/ALiVEOS/ALiVE.OS/blob/master/addons/mil_opcom/fnc_INS_helpers.sqf#L666