-
Notifications
You must be signed in to change notification settings - Fork 49
Gazebo does not start #368
Comments
This can be worked around by setting the follow environment variables: |
Attempting to start Gazebo 10.2.0 from other drives that C:/ causes it to freeze at spashscreen. After setting up the env variables:
The following errors appear after launching Gazebo via its [Err] [C:\a\1\s\ws\src\gazebo\gazebo10\gazebo\gui\GuiIface.cc:526] Unable to save INI file["\Users\Admin\.gazebo\gui.ini"]
After a little investigation, it seems that for Windows systems Gazebo 10 tries to retrieve the location of the settings from Thus next attempt was to change [Err] [C:\a\1\s\ws\src\gazebo\gazebo10\gazebo\Server.cc:388] Unable to initialize sdf
The root cause of the problem is probably in the Gazebo itself: #386, #363, however, maybe someone knows a solution (besides creating an alias with the first command ROS2 Foxy installed according to https://ms-iot.github.io/ROSOnWindows/GettingStarted/SetupRos2.html |
Describe the bug
With a default foxy chocolatey install, gazebo does not start from the command line using gzserver/gzclient.
Cause
During the build, gazebo sources try to capture the install location during a cmake pass. This install location is set in a variable which is injected directly into a source file. However, it is not escaped. Windows uses backslashes for path separation, which the C++ interpreter will try to escape. you end up with
c:ptrosfoxy...
AB#509368
The text was updated successfully, but these errors were encountered: