Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network opportunistic physics #603

Open
mwfarb opened this issue Dec 4, 2023 · 0 comments
Open

Network opportunistic physics #603

mwfarb opened this issue Dec 4, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@mwfarb
Copy link
Contributor

mwfarb commented Dec 4, 2023

Capturing discussion between @johnchoi313 @mwfarb @hi-liang.

Goal: create consistent remote physics operations publishing pose.

Plan: create a remotePhysics scene-option parameter Boolean when false, by default, local physics in use by web and unity. When true, disable all local physics on all platforms and let any remote python or unity client publish pose updates from physics. Use schema established from aframe physics cannon.js to communicate physics properties of all objects on the wire.

Affects: properties of impulse, dynamic-body, static-body, scene-options

Needs:

  • web-core: add remotePhysics handler. Disable pose updates for local physics when using build3d.
  • python: centrally add physics like pybullet to library. Implement remotePhysics true for above Affects properties of objects and publish physics pose updates.
  • unity: use unity's native phyx physics library. Implement remotePhysics true for above Affects properties of objects and publish physics pose updates. Do not publish pose updates when local physics in use, but rendering is ok.
@mwfarb mwfarb added the enhancement New feature or request label Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant