Closed utk-hua closed 4 months ago
@utk-hua I believe you need to enable PhysX 5 for the Robotic Workflow using ROS2 to work correctly for manipulation. That can be done at the CMake configure step by setting the CMake cache variable of AZ_USE_PHYSX5.
The workaround is only needed temporarily as the Phys Gem is being split into both a PhysX 4 and PhysX 5 version as of this PR by @spham-amzn
@lumberyard-employee-dm thanks for your reply! forgot to mention that I have built the engine with physx5 enabled. I have updated it in the description.
I did a fresh build using o3de/o3de-extras 2310.2 (same commits as yours) and the template worked correctly for me. Maybe your problem is caused by #668?
Hello @utk-hua did you managed to run articulated robot with guidance from Jan? Please give us feedback to have this issue concluded.
I will close the issue due to no response. Please reopen if you still have any problems.
Describe the bug While using Physx debug tools in Game mode of the robotic manipulation template, enabling visualizations, collisions, contact etc. The joints, articulation, mesh collider components of the robot are not visualized.
Assets required O3DE Robotic Manipulation Template
Steps to reproduce Steps to reproduce the behavior:
Expected behavior Joints, Colliders of the robot prefab to be visualized
Actual behavior Physics components of other entities in the environment are visualized, but there are no visualizations for the robot prefab.
Screenshots/Video
Found in Branch point-release/23102
Commit ID from o3de/o3de and o3de/o3de-extras repositories
o3de : e22213ea946932dc2f94d9f1392e98b4bf2b2c3f o3de-extras : e2426a4242e9fd11c7b902f6aff3379af06d3556
Desktop/Device (please complete the following information):