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
in the videos embedded in the docs, I have seen that an app DebugView is used to integrate with the PhysX engine and to present the results. Is the source of this app available? I am interested in the PhysX integration, because so far I was getting poor results (simple cube was falling through with one vertex and generating nonsense impulses with its edges) when supplying 3-vertex polygons (triangles in other words) into the PxConvexMeshDesc. I was using the indices and vertices from VHACD. I believe I had the plane equation set up correctly in the polygon part of the PxConvexMeshDesc structure. Another problem was that on some meshes VHACD produces vertices which are not used by any triangles and PhysX also can not digest that. So this makes me interested in the DebugView app. So far I have worked around that by only supplying the vertices from VHACD and adding the PxConvexFlag::Enum::eCOMPUTE_CONVEX. But that is suboptimal and generates work which could be avoided.
The text was updated successfully, but these errors were encountered:
Yes, using the eCOMPUTE_CONVEX flag is probably the best way to integrate this into the PhysX SDK.
With the version4 release I was trying to simplify this package as much as possible so I completely removed all of the debug view stuff as it was extremely large.
That said, perhaps if anyone finds it useful, what I might do is create a new separate GitHub repot with just the DebugView app revised to work with version4. It would probably only take me about a day to do this.
I will let you know if and when I get around to doing that.
Hi,
in the videos embedded in the docs, I have seen that an app DebugView is used to integrate with the PhysX engine and to present the results. Is the source of this app available? I am interested in the PhysX integration, because so far I was getting poor results (simple cube was falling through with one vertex and generating nonsense impulses with its edges) when supplying 3-vertex polygons (triangles in other words) into the PxConvexMeshDesc. I was using the indices and vertices from VHACD. I believe I had the plane equation set up correctly in the polygon part of the PxConvexMeshDesc structure. Another problem was that on some meshes VHACD produces vertices which are not used by any triangles and PhysX also can not digest that. So this makes me interested in the DebugView app. So far I have worked around that by only supplying the vertices from VHACD and adding the PxConvexFlag::Enum::eCOMPUTE_CONVEX. But that is suboptimal and generates work which could be avoided.
The text was updated successfully, but these errors were encountered: