Was this issue fixed more recently? Because this was not the way dynamic simulation worked on client side (see example Ticket T150211 which i reported some time ago) and i haven't seen anything in the changelogs that would indicate that there was something changed intentionally.Īlso, if that is the intended behaviour now, should simulationEnabled state on client side only change if dynamic simulation is also enabled on client side? I'm not sure but it seems that, to enable this behaviour, you don't need to flag the same voice in the unit attributes that enables the dynamic simulation.Īm I correct? I've also noticed peculiar interaction between those two features: if Dynamic simulation threshold is smaller than the Simulation manager module, it seems that - since units should spawn when simulation is stopped, they cannot spawn anymore in the opposite situation, simulation starts even if they are not spawned and, when this happens, they have already moved (similarly to ALive VI system) but (although I'm not sure) without interacting with other units, spawned or not.If that is the intended behaviour then there is a different bug, which is that it does not always work and i will try to create a simple test case to reproduce it. The Simulation management module doesn't only stops simulation, but it seems to despawn units until the player reduces the distance to the given threshold when this happens units respawn exactly where they was, in the same position, and the simulation restarts normally. Dynamic simulation stops the simulation of units at a given distance from the player without despawning them, leaving them "freezed" until the distance with the player doesn't fall under the give threshold As from topic, I was thinking that they are almost the same but, after a little bit of testing, it seems they work in pretty different ways:
0 kommentar(er)
