EVERY CPU gets bottlenecked by this game 'cause of it's limiting engine and poor optimization, sad but true and it also doesn't look like it's gonna change anytime soon >.>
What influences my FPS most?
- Thread starter Noiza
- Start date
EVERY CPU gets bottlenecked by this game 'cause of it's limiting engine and poor optimization, sad but true and it also doesn't look like it's gonna change anytime soon >.>
DirektX 11 doesn't care about your 8 CPU cores. The CPU bottlenecks the GPU without beeing utilized fully by the game. Thats why changing the graphic settings doesn't make a difference. I hope that explanation is dumbed down enough for you
I have a question on this one: FanDan Extra said in one of his videos, that grouping items together has a positive effect on performance. For example grouping a group of foliage together, if it is close n´by. Does anyone know if this is true?
In other, mod-able, games it's a thing to "bake" objects from multiple meshes, but groups in PZ are just groups. Which we use anyway...and with grid-objects you would have to take effort to not build within a group.
Maybe there is a minor side effect in the object organization about relative coordinates within a group vs absolute coordinates, but I'm a bit skeptical.
And while the object count certainly is a part of performance, it's compared to the visitor issue totally negligible
I can clutter the whole park with trees, multiple copies of my large domes with plants (each one around 20K objects) and the frame-rate stays on the frame-cap.
But....the moment I remove the visitor limit and they go above 7K....welcome sub 60th.
I do not notice guess lag until they get over 6k. But I also do not have buildings or habitats with thousands of little pieces or rocks. I think objects cause more lag than guests.
Pretty sure that's not the case, since the CPU has to calculate way more for the guests than it does the building pieces, though to really get an answer to that we'd have to test it. Like take a very detailed park with at least 20 species and around 7-8k guests, see how FPS are and then limit guests numbers to 500 so you can see the difference in FPS. After that let the guests in again and once they're there pause the game delete all the building pieces until only the basics are left, and play again to see what difference it makes...maybe even save after limiting guests/deleting pieces and restart the game, so the game has to reload it in both cases. That way you can find out what really causes the most lag between the two.
Imagine you buy for example NHL game and it starts lagging after the second third and someone says "don't play the whole game then".
We were given some space, we should be able to use it. Where is the problem? It's like with many other games where the RAM usage was limited to, let's say 4 gb? Or is it locked to only use one CPU core?
We were given some space, we should be able to use it. Where is the problem? It's like with many other games where the RAM usage was limited to, let's say 4 gb? Or is it locked to only use one CPU core?
This thousand times. A zoo with 20 species cannot really be my "Zoo of my dreams". I would understand if it would be a PC specs problems. But even on high end PCs it seems to have problems once the zoo is big enough and that continue until it is unplayable. Why even have maps so big if we cannot really use them.
Also terraforming and buildingpieces/foliage affect it alot if you have much of it. I had to give up on my first sandbox zoo because of absolute extreme lagg (even in pause mode). I had about 10-20 animals at the time an 0 guests. But i did have big mountains and other terrain modifications that covered the entire map
I guess different system, suffer from different things....but all have problems with visitors.
In my case PlanetZoo with all the associated threads ( a lot) uses (so far) up to 12 GB of RAM (no talking about GPU-Memory), while the plain exe just uses 3-4 GB.
As I still have enough headroom, this might be the reason I don't have much trouble with the object count...just my guessing.
In my case PlanetZoo with all the associated threads ( a lot) uses (so far) up to 12 GB of RAM (no talking about GPU-Memory), while the plain exe just uses 3-4 GB.
As I still have enough headroom, this might be the reason I don't have much trouble with the object count...just my guessing.