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
Support multiple physics engines #59
Labels
enhancement
New feature or request
physics
Related to the physics engine
unity
Concerns the Unity project
Comments
freezy
added
enhancement
New feature or request
unity
Concerns the Unity project
physics
Related to the physics engine
labels
May 30, 2020
PRs concerning this:
|
Closed by #66. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
physics
Related to the physics engine
unity
Concerns the Unity project
While this repository ships with VPX physics, we would like to have a way of replacing the physics engine at runtime. The main idea that we can a) easily test new engines without having to branch the code all the time and b) finally even deliver multiple engines for the table authors to choose from.
@ravarcade already started on a Bullet Physics implementation, so this has become somewhat relevant now.
Other physics engines aren't necessarily part of the same repo, but can be added as a Unity package and will be discovered by VPE when installed. Ideally, this would work like that:
Architecture will follow.See ravarcade#3.
The text was updated successfully, but these errors were encountered: