You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server needs physics for movement and collision, of course.
Client needs the same physics to interpolate the world state between server heartbeats.
Server is in erlang, client is in C# :S Three options:
Mash box3d into allonet, and put it in the shared C layer. Add an API to take the existing allonet/state.h structures, simulate physics on them for x ms, and return a new set of simulated structures. Use this method in both client and server.
Use another physics library that has nicer APIs, especially up to C#. Use the same library from both client and server.
Just use different libraries client and server side, or even own implementations.
I'm leaning towards 1.
The text was updated successfully, but these errors were encountered:
Server needs physics for movement and collision, of course.
Client needs the same physics to interpolate the world state between server heartbeats.
Server is in erlang, client is in C# :S Three options:
I'm leaning towards 1.
The text was updated successfully, but these errors were encountered: