Open two-one-five opened 4 years ago
from hifi roadmap:
According to the documentation, our general physics system is already using PyBullet.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Note: The old, pre-C++ implementation of flow in JavaScript reportedly worked well. https://hifi-content.s3.amazonaws.com/jimi/avatar/Niconico/Jene_5/scripts/jene_Flow.js
Hello! Is this still an issue?
Hello! Is this still an issue?
Currently the C++ implementation of flow is buggy. It currently is its own little mini-segment of a physics engine. It should be refined and fixed, but is it easier to try and fix the current implementation? Or, would using Bullet or PhysX be easier, and then that ground work allows for further usage and module creation.
If the path of fixing the current implementation is used, it should be well isolated and the code should not be reused to avoid creating a physics nightmare. We should be trying to use a third party implementation for an engine (e.g. PhysX) that is well featured and tested, made to work with software like this.
So modularizing and improving what we have now or replacing it would be a good place to start.