Skip to content

fix(gazebo): resolve mesh URIs and the gz GUI on Windows - #28

Open
Arcod7 wants to merge 3 commits into
feat-pixifrom
aes/fix-windows-gz-args
Open

fix(gazebo): resolve mesh URIs and the gz GUI on Windows#28
Arcod7 wants to merge 3 commits into
feat-pixifrom
aes/fix-windows-gz-args

Conversation

@Arcod7

@Arcod7 Arcod7 commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Mesh URIs and the Gazebo GUI break on Windows.

  • base_path is pasted into file://$(arg base_path)/robot_description/meshes/dae; with backslashes gz cannot resolve it, so the robot renders with no geometry.
  • gz is a .bat on Windows, and ExecuteProcess does not search PATHEXT, so the GUI process was never found — resolve it with shutil.which.
  • World and base paths passed as posix.

Verified locally: the InMoov renders in the Gazebo window on Windows with these applied.

Arcod7 and others added 3 commits September 2, 2026 12:18
Three separate failures, all Windows-only:

The world path went into a PythonExpression string literal, where a Windows
path is read as escapes. It crashed on the drive-relative part, and a folder
whose name starts with n would have silently become a newline. Pass it as a
posix path; Gazebo accepts forward slashes everywhere.

gz sim then refused to run: the server and the Qt GUI cannot share a process on
Windows any more than on macOS (gz-sim#168). Windows now takes the same split
macOS already used, running the server with -s and the GUI separately.

That GUI process could not start either: gz is a .bat on Windows and
ExecuteProcess does not search PATHEXT, so it exited with WinError 2. Resolve
the path before handing it over.
…dows

base_path is pasted straight into a file:// URI in inmoov.urdf.xacro. With
Windows backslashes that produced file://C:\...\description/robot_description/...,
which gz could not resolve, so every visual failed to load and the robot
appeared in the window with no geometry.
@Arcod7
Arcod7 force-pushed the aes/fix-windows-gz-args branch from 3a87899 to 2b00f98 Compare September 3, 2026 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant