Search results

Did you check if your non-despawning AI is related to this entry in the 2.1.0.1 changelog? To check if AI are properly despawning, you should rely on the debug output by the DZAI Monitor instead of the debug markers.

Thanks for reporting this issue. Vehicle AI patrols are something both new to DZAI and to myself, so it will take long while until they're working flawlessly. At the moment I can't even say for certain whether I'll be able to fix this in the near future, but I will be on the lookout for solutions.

@Megaz : You probably hit the limit for the number of vehicles set in DZAI_heliList and DZAI_vehList. For example, if you set DZAI_maxHeliPatrols to 100 but set DZAI_heliList = [["UH1H_DZ",2]], you can only have 2 UH1H_DZ active at one time.

That's great news. Hopefully all issues are sorted now, if not, then it's back to work.

The current version at this time is 2.1.0.1d, if you have a previous version, make sure you update. This is the last edit of 2.1.0.1, hopefully.

@Cikez :I haven't had the chance to test with DayZ 1.8.0.3 but the only thing that might possibly break is the dynamic weapon list. DZAI is able to use backup weapon tables in case this happens so it's not a critical problem. Other than that, I have no reason to believe that there is any...

DZAI 2.1.0.1d released to fix a number of non-critical undefined variable errors.

Updated to 2.1.0.1d. There's now a short time window of 30 seconds before groups are deleted if loot needs to be added, should prevent some of the undefined variable errors. The group_manager.sqf errors shouldn't show up anymore since the DZAI group-deleting function terminates the script before...

I've narrowed down the cause to cases where AI groups are deleted immediately after all units are killed. I'm working on another update to let DZAI wait a while for all after-death scripts to finish executing before finally deleting the group. This should solve all the error messages. There...

I made many new updates during the past few days, make sure you're running the very newest one ( 2.1.0.1c Release Build 7212014).

This update is a small collection of fixes and improvements. [CHANGED] Improved the way DZAI prevents empty AI groups from being deleted by DayZ's cleanup script. Several DZAI scripts require the empty group to continue existing for a short time in order to function properly. [CHANGED]...

DZAI 2.1.0.1 incremental update now available to improve group management and cleanup.

If you want to use Epoch 1.0.4.2 then your options are to either grab the buildWeaponArrays.sqf from DZAI 2.0.0 through the Releases page on Github or disable the dynamic weapon list. Just so you know it is my unspoken/understood rule that DZAI will only support the most recent version of any...

Just about anything is possible with scripting (within reason), though you'd have to consider the annoyance factor for players who would be bombarded with radio messages every 10 seconds every time they're within 1000m of a foot or vehicle patrol (which would be all the time). All of this would...

DZAI 2.1.0.1 incremental patch incoming to improve AI group mangement.

The dynamic weapon list was updated for compatibility with the most recent Epoch version (1.0.5.1). The only other DayZ version tested was Overwatch 0.2.5 due to time constraints.

Thanks for the log sample. Can I please bother you again for another log sample with debug level 2 enabled, showing everything from DZAI starting up to a few lines after the first appearance of the error? Thank you. It seems this problem will need very detailed debug output to help getting...

Can you provide a larger log sample, with a few blocks of lines before and after the error message? It would help me figure out what's happening before and after the error and possibly show the cause of the error. I haven't seen this error once anywhere in my logs within 25000 lines so there...

The error is because the dynamic AI player-hunting isn't able to properly handle cases where the AI group has been completely killed. To suppress these errors, set DZAI_huntingChance = 0 in your dzai_config.sqf to turn off player-hunting. A fix should be out tomorrow sometime. Also, closing...

Can you provide your config file and a sample of your RPT during startup with debug mode 2? I don't know what could be the problem right now but will check when I can.