Manage physics objects in unloaded areas #1
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Some large physics objects may span multiple chunks, therefore it is entirely possible that part or all of an object is in an unloaded chunk. The default behavior when a chunk is unloaded is to remove that chunk's object from the physics space, but this presents an issue where any objects that may have been supported by that mesh are no longer supported and fall through the world in the physics space. Even if the chunk meshes were never unloaded, there is still the chance that a sufficiently large object may extend into unloaded chunks where no mesh exists. A solution needs to be found which is a compromise between limited memory/processing power and logical physics while also making sure it cannot be abused for unintended side effects.