What's the difference between SV [serialized variable] culling in 3.1 and network bind culling?

Okay, so bind culling will be that entities that are far away from you are not present on clients at all. So they won't be taking any memory. They won't be taking any CPU load. Serialized variable culling, on the other hand, is that we just stop sending the network updates for those entities, those entities that are far away, so far away on your client that you can't actually see them. So the entities are still there, they're still present in memory, and they don't require any CPU updates because they're not getting network updates. So the natural state of entities on the client, or most entities on the client, will be if they're not getting any network updates from the server, they'll go to sleep and wait for the next network update and decide what they need to do. So I hope that explains the difference.