Haleks wrote
Mmm I'm not sure why you say that the mission files are messy (remember how they were on older releases?), but anyway I don't think the script-lag experienced by some players is related to the mission itself : it is always the same scenario, zeds & loot stop spawning (handled by the dayz_code) while everything else is still working - scripts inside the mission file don't seem to be affected.
What we really need is some heavy work on the dayz_code to remove everything that ain't used/needed in SP (humanity function, all those login/server/hive checks in player_monitor etc).
About the zed spawn issue : I've noticed that both the player_spawncheck (handling zed & loot spawns) and the stream_locationCheck (handling wrecks, deerstands & junk spawns) files are called in the same loop - but using different methods. Wich gives me pause, because, while the spawncheck seems to fail now and then, it's never been the case with locationcheck (AFAIK).
What the dayz_code does is this : it spawns the spawncheck script, wait for it to be finished, then calls the locationcheck script, pauses for 2 secs (sleep 2) and do it all over again.
Now from what I understand with sqf scripting, spawning a script is usefull if, let's say, you wanna launch the same script on several objects (one thread by target); but if you need to execute a script often without overloading, you definitely want to call it (and it's less heavy on the CPU).
Sooo... I'm not sure why they spawn the player_spawncheck : it's not like there's multiple threads each one checking a single building (can't be, since the code waits the end of the script to proceed); it is one single script checking several buildings - so why spawn it rather than calling it? (Not super sure I'm clear here)
Anyway, I'm trying a playthrough with a small modification (spawncheck & locationcheck are both called) to see what happens. I do think the game is a bit less laggy, but I'll keep testing and see if anything goes wrong with this set up.
About the AI, I'd love to see what you came up with! (Eventhough I wonder what you mean about bandits shooting each others - is this not already the case? - except for squads, obviously)
There are a lot of different folders in weird places, such as a !scripts folder alongside the scripts folder, dayz_code, Dayz_factions etc.
It'd look a lot more appealing to all be merged into the scripts folder. Of course, this is just an aesthetics
thing.
Zombies not spawning also occurs in normal DayZ origins, and has been reported a lot on their forums. It may not be the script breaking, per say, but the amount of local nearby zombies on the client still existing. The dayz_maxLocalZombies and dayz_maxNearByZombies set the limits before zombies are not spawning.
dayz_CurrentNearByZombies would be the amount of zombies around. One of two things could be happening.
Either zombies getting killed are not lowering this value, or zombies are simply not despawned.
Of course, I will try your suggestion. It would, at the least, reduce some of the script lag.
Onto the AI, they always seemed to be friendly to each other for me. Occasionally, they do shoot eachother, but I often saw bandits just run by eachother.
An easier method is to make REDFOR hostile to itself. Zombies are on REDFOR, but they can't attack eachother anyway.
AI also will hunt you down once they spot you, you shoot your gun etc.
Which can lead to some really insane gunfights. When every bandit in a city, hostile to eachother, come to one position to get you, it'll be a huge free-for-all.
AI using your health system is pretty neat too. Makes gunfights last longer, and makes them more dangerous.
DaiZy Single-player Developer (AI Units)
Locked
