Hey, I’m trying to set up ROS2 actions and use them with Isaac Sim. I’m running into a weird issue where Isaac Sim fails during its bootup. I’m 90% sure that since I need to source some ROS2 actions package (sourcing the package with .action file) in the same terminal as the one that’s initiating the Isaac Sim, that’s causing some issues.
I just want to know if is there a workaround for this.
Just wanted to see if the developers have any updates on this.
Hi @karthik.ganesan1 - You can find about this more here in the attached doc link.
https://docs.omniverse.nvidia.com/app_isaacsim/app_isaacsim/install_ros.html
Hey, sure. So, the main reason I want to source the ros script in the same terminal as the Isaac sim, is I need some specific ROS action message type, which means I’d need to source those ROS actions package to make sure the Isaac sim code that uses those message type can be used correctly.
But I’m unable to do that, coz sourcing ROS in the same terminal as isaac-sim causes errors. This is fine for the most part of using ROS, but with ROS actions, if I’m creating my own custom message action, that needs to be sourced to be accessible, hence making this as a blocker.
