Possible Bug Fixes for Developers
Posted by DayZ_SP on Jan 23, 2013; 4:29am
URL: http://kodabar-dayz-daizy-single-player-forum.163.s1.nabble.com/Possible-Bug-Fixes-for-Developers-tp2585.html
I apologize if this is the wrong forum, but the Releases forum is the most active and has the most viewers. If the mods want to move this that's cool with me.
With that said...
I've been reading up on bugs on all the forums and there are some common ones that AboveDayZ and Fedus_87 should be able to easily fix in future releases depending on how much (or not) Rocket alters the core code as the Mod progresses.
The number one bug is Zombies and Loot don't spawn after the player spawns.
This is due to a number of factors:
A) The spawn radius for the random coastal player spawns is 500 meters. Reducing this should place the player closer to where they should actually be... On the beach... As well keeping them outside the loot and Zombie spawn radius around most buildings.
NOTE: If you adjust the player spawn radius, make sure to MOVE the spawn markers in-land toward the coast because a lot of them are set over the water and with the lower the spawn radius, the greater chance players will spawn IN the water.
B) Players often spawn too close to buildings that generate Zombies and loot.
The smallest building that can generate Zombies & loot is a dog house, and all buildings have a spawn radius of 120 meters for loot and Zombies to spawn. The minimum spawn radius is 30 meters to prevent players form just camping outside buildings waiting for loot. So, anywhere between 120 and 30 is the "sweet spot" for loot and Zombies to spawn. These radiui can be adjusted in one of the zombie scripts in the "dayz_code" (I can't remember which one).
C) The overall spawn radius is set to 1000 meters and a limit of 40 zombies per client.
I advise developers to increase the spawn radius to anything above 1000 e.g. 1500, and anything above 40 Zombies per client see if this improves the stability of Zombies appearing in the game. It shouldn't effect performance unless players are running anciet hardware, but that is why this needs experimentation and has no definitive number.
D) Since this is a Client Side mod, there is no tick rate in Single Player that determines how fast the code is processed. It is processed as fast as your hardware can compute it since it doesn't have to verify things with the server like it does in MP.
So, one big reason things don't spawn is you may be running the game at 60 FPS (Frames Per Second), which is TOO fast for the game to function, ironically, and why some functions don't work, or take a while to work such as Zombies and loot spawning.
The only solution for adjusting tick rate is to trick the game into thinking it is running at 30 FPS which is standard for MP games.
You can do this with third-party GPU programs like MSI-Afterburner and others where you can manually set your framerate to whatever your monitor can handle in relation to its refresh rate. This might not seem like an optimal solution since 30 FPS appears "jerky" if you are used to 60, 100 and 200 FPS on most games, but once you get used to it, it actually becomes the preferred frame/tick rate because then the game play experience is butter smooth -- remember it is not the maxium frames you can render, but the LOW END number that determines smoothness -- And a side benefit is 30 FPS doesn't tax modern video cards at all. Remember, 23.97 and 29.97 are standard frame rates for full motion video (movies and games) on TV, so running at 30 FPS should feel no different.
I'll add more to this thread if the developers are interested, but for right now this is probably enough considering the amount of info. presented
URL: http://kodabar-dayz-daizy-single-player-forum.163.s1.nabble.com/Possible-Bug-Fixes-for-Developers-tp2585.html
I apologize if this is the wrong forum, but the Releases forum is the most active and has the most viewers. If the mods want to move this that's cool with me.
With that said...
I've been reading up on bugs on all the forums and there are some common ones that AboveDayZ and Fedus_87 should be able to easily fix in future releases depending on how much (or not) Rocket alters the core code as the Mod progresses.
The number one bug is Zombies and Loot don't spawn after the player spawns.
This is due to a number of factors:
A) The spawn radius for the random coastal player spawns is 500 meters. Reducing this should place the player closer to where they should actually be... On the beach... As well keeping them outside the loot and Zombie spawn radius around most buildings.
NOTE: If you adjust the player spawn radius, make sure to MOVE the spawn markers in-land toward the coast because a lot of them are set over the water and with the lower the spawn radius, the greater chance players will spawn IN the water.
B) Players often spawn too close to buildings that generate Zombies and loot.
The smallest building that can generate Zombies & loot is a dog house, and all buildings have a spawn radius of 120 meters for loot and Zombies to spawn. The minimum spawn radius is 30 meters to prevent players form just camping outside buildings waiting for loot. So, anywhere between 120 and 30 is the "sweet spot" for loot and Zombies to spawn. These radiui can be adjusted in one of the zombie scripts in the "dayz_code" (I can't remember which one).
C) The overall spawn radius is set to 1000 meters and a limit of 40 zombies per client.
I advise developers to increase the spawn radius to anything above 1000 e.g. 1500, and anything above 40 Zombies per client see if this improves the stability of Zombies appearing in the game. It shouldn't effect performance unless players are running anciet hardware, but that is why this needs experimentation and has no definitive number.
D) Since this is a Client Side mod, there is no tick rate in Single Player that determines how fast the code is processed. It is processed as fast as your hardware can compute it since it doesn't have to verify things with the server like it does in MP.
So, one big reason things don't spawn is you may be running the game at 60 FPS (Frames Per Second), which is TOO fast for the game to function, ironically, and why some functions don't work, or take a while to work such as Zombies and loot spawning.
The only solution for adjusting tick rate is to trick the game into thinking it is running at 30 FPS which is standard for MP games.
You can do this with third-party GPU programs like MSI-Afterburner and others where you can manually set your framerate to whatever your monitor can handle in relation to its refresh rate. This might not seem like an optimal solution since 30 FPS appears "jerky" if you are used to 60, 100 and 200 FPS on most games, but once you get used to it, it actually becomes the preferred frame/tick rate because then the game play experience is butter smooth -- remember it is not the maxium frames you can render, but the LOW END number that determines smoothness -- And a side benefit is 30 FPS doesn't tax modern video cards at all. Remember, 23.97 and 29.97 are standard frame rates for full motion video (movies and games) on TV, so running at 30 FPS should feel no different.
I'll add more to this thread if the developers are interested, but for right now this is probably enough considering the amount of info. presented
| Free forum by Nabble | Edit this page |