pointers on how to network planck about planck.js HOT 8 CLOSED

Oops! I completely misinterpreted what was going on in src/serializer.ts. Thanks again, this is super helpful!

from planck.js.

Current serializer is optimized for saving/loading a world in a readable format, and is not optimized for fast and efficient networking.

For networking I recommend directly iterating over all objects and fields and write to and read from an efficient stream.

from planck.js.

Here's a list of things so far that seem like might be sufficient to sync a physics object's state:

• object id (does planck.js generate one for all objects/fixtures/etc. ?)
• angle
• angularVelocity
• position (vec)
• linear velocity (vec)

Are there any other things that might need to be sync'd? I'm not sure how I'd go about syncing a joint constraint for example

from planck.js.

Hey! There is a serializer in src/serializer already. It isn't optimized for file size, but you can probably follow it for your implementation

from planck.js.

Ah, thanks for the pointer! So it seems this serializer is just enumerating all the object/array props, rather than a hardcoded list.

from planck.js.

I don't think it just enumerates all props, see for example _serialize in Body.ts. Every class defines what properties are relevant this way (so it is hardcoded per class)

from planck.js.

For networking I recommend directly iterating over all objects and fields and write to and read from an efficient stream.

That's the plan, I just didn't have any list of the "important" fields that one might need to sync for different primitives (fixtures, joints, etc.)

from planck.js.

Hmm, I'm not quite sure, but happy to help with implementation.

We probably need to implement an interface like current serialize but write to a streaming interface (instead of json).

We also need to find out the answer to your question, probably we can see how this is implemented in C++ for Box2D.

from planck.js.