-
Notifications
You must be signed in to change notification settings - Fork 20
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
PhysX SDK 4.0 support? #4
Comments
Replacing DLLs is not enough, no. |
Here's something meanwhile: https://www.youtube.com/watch?v=6dATi4-wb3o&fbclid=IwAR1u9a7xMArK7fpv7yxWa91D1lIPTjyhCGJYB_ZEKJMi98K_BsfiQTnUSJs |
thanks for the video link.. |
with PhysX 4.1 released.. with next PEEL release we can expect it will be supported also, right? |
PhysX 4.1 and next Peel release coming up ? |
Sorry guys I had no time to take care of PEEL last year. I might try to go back to it this year but no promises. |
thanks for update.. IMHO maybe you can skip 4.0 support.. as seems Physx 5.0 is coming soon.. |
Adding PhysX 4 to the current repository is relatively simple. It's the update to PEEL 2.0 (the framework itself) which is time consuming. The PINT interfaces have changed quite a bit and it's a huge amount of work to update all the plugins and make them all work again (I have about 50 plugins/engines to go through these days). Additionally some engines like Havok only work with VS2008/2010 (they stopped releasing free libs for newer VS versions once they got acquired by Microsoft), but some engines only work with more recent VS versions and don't support VS2008/2010 anymore. It makes everything more tedious than it should be. The way forward might be to do a PhysX-only release next time, because I don't have time to support everything anymore. But then again a PhysX-only release defeats the purpose of PEEL a little bit :) |
This is available now: https://github.com/Pierre-Terdiman/PEEL_PhysX_Edition |
Just asking.. or replacing DLLs is enough?
The text was updated successfully, but these errors were encountered: