I don’t know, but I think most of the performance drop is due to pathfinding for visitors rather than rendering them…. Since pathfindibg seems to be the basis for how each guest ‘acts’ (money spent, where, when, etc) I don’t think making guests invisible would affect performance all that much. Why not just reduce the number of guests (as you can already do).Have the possibility in the settings to hide all visitors or a percentage of them in order to limit performance losses when our zoo becomes very popular.
I tried to reduce (to the minimum) but didn't see a difference. Should we wait until people have finished visiting the zoo? If I reduce the number of people, I will inevitably sell less tickets and it will become complicated to make money right?I don’t know, but I think most of the performance drop is due to pathfinding for visitors rather than rendering them…. Since pathfindibg seems to be the basis for how each guest ‘acts’ (money spent, where, when, etc) I don’t think making guests invisible would affect performance all that much. Why not just reduce the number of guests (as you can already do).
We’ll yes, but $ isn’t really an issue after the first couple of habitats are in anyway…. In my experience guests only really affect performance if paths are too congested: try widening paths, making more optional routes, spreading out amenities and exhibits.I tried to reduce (to the minimum) but didn't see a difference. Should we wait until people have finished visiting the zoo? If I reduce the number of people, I will inevitably sell less tickets and it will become complicated to make money right?