Is there a way to copy a space safely?

[fanhe]

As title, I have not found such api. Is there a plan to add a similar api?
Thanks.

[slembcke]

Currently no. That's actually a lot more difficult than it sounds.

Adding serialization is one of my higher priority features to add in the future and that would allow for copying. Not sure when it will be done though.

[fanhe]

Thanks for reply.
I will try other methods.

[ShiftZ]

[slembcke]

Yeah, I know. It will be a pain, but I think it will open up a lot of opportunities. I'll probably develop the serialization stuff in a separate branch so that any other Chipmunk changes don't have to be developed in lockstep.

[nikki]

Actually, because of the nice property listings in cpShape.h and cpBody.h, this isn't too bad. I support save/load in my game engine and the save/load of chipmunk bodies and shapes works out nicely. The code is .

What is the other data that should be save/load'd? I'm guessing 'global properties' such as iterations or gravity, and this would all be in cpSpace.

[slembcke]

Saving out a list of the bodies/shapes/constraints gets you most of the way there in practice, and that's pretty easy with the exception of supporting *all* of the constraint types. The problem is that it doesn't store the persistent contact information, or the internal state of the collision detection structures. This is necessary for collision events (begin, separate, etc) to span across serialization calls correctly and for the collision detection to be deterministic. Ideally if you save a simulation and play it back again it shouldn't give you a different result. For that to work, it really has to recreate all of the data structures verbatim, and that's where it gets hard.

[log_2]