Skip to content

[ROS2RobotImporter] Add warning banner for registries and articulations - #1099

Merged
nick-l-o3de merged 1 commit into
o3de:developmentfrom
RobotecAI:jh/importer_notifications
Sep 23, 2026
Merged

nick-l-o3de merged 1 commit into
o3de:developmentfrom
RobotecAI:jh/importer_notifications

Conversation

@jhanca-robotecai

Copy link
Copy Markdown
Collaborator

What does this PR do?

Creating a project from O3DE template results in different registry settings compared to creating a project from robotic O3DE templates. Some assets might be correct or incorrect due to the fixed coordinate system, see o3de/o3de#18686 for details.

I wasted nearly two hours rebuilding assets and different versions of engines to find out why I cannot import the same robot in different project anymore. In this PR I added a warning for robot importer, so it get very easy to spot when working on the project with configuration that might influence .dae and .stl readouts typical for URDF/SDF robots.

Additionally, I adjusted warning about >64 articulations to follow the same style.

Screenshots below:
Screenshot from 2026-09-21 18-10-55
Screenshot from 2026-09-21 18-11-04

How was this PR tested?

Imported robots with and without registry flag.

Signed-off-by: Jan Hanca <jan.hanca@robotec.ai>
@byrcolin byrcolin added the sig/simulation Categorizes an issue or PR as relevant to SIG Simulation label Sep 22, 2026
@nick-l-o3de
nick-l-o3de merged commit 2518837 into o3de:development Sep 23, 2026
3 of 5 checks passed
@jhanca-robotecai
jhanca-robotecai deleted the jh/importer_notifications branch September 24, 2026 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sig/simulation Categorizes an issue or PR as relevant to SIG Simulation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants