Cannot add models to Gazebo world on macOS with Intel chip #323
Comments
|
Same problem here with macOS Monterey 12.6.2. Ros Noetic, Gazebo 11.10 via Robostack |
|
It also crashes when trying to pause de sim? @troiwill |
|
Well. First update. downgrading the python version to 3.7, there's no problem installing gazebo 11.12.0. However, still the same crashing behaviour. |
|
How are you adding models to the world, via the Gazebo gui? In that case, it may be useful to check if this happens also on an environment with just gazebo, i.e. : Thanks! |
@mora200217: Yes. Furthermore, the (real and simulated) times, FPS, and so on at the bottom of the gazebo window do not work at all (even if I do a simple |
@traversaro: I tried to add models via I also tried what you suggested: ( |
|
@troiwill Update: I've created a conda env with python=3.7 and install gazebo 11.5. It works. |
|
Sorry for taking long to look at this. This is unfortunatly a known issue with I guess that on macOS arm you do not have |
@mora200217, thanks for the suggestion. But I get errors when I try to install |
What kind of errors? @troiwill |
|
Please try again with the robostack-staging channel. |
I am not able to run |
|
Have you tried the robostack-staging channel? |
|
Isn't that the default channel used during setup? Here are my channels currently in use. (ros_noetic_env) user ~ % conda config --show channels
channels:
- conda-forge
- robostack-staging
- defaults |
|
Yes - what happens if you create a new env with ros-noetic-desktop and gazebo? That should work. ps: I would recommend disabling the defaults channel |
|
Made a new clean conda environment with ros-noetic-desktop and gazebo. I still can't install that specific version of qt, it is not available. |
|
Hello @simonbogh, probably I was not clear in my post. The |
|
That's what I tried first, just installing gazebo and ROS, and gazebo still behaves the same way. |
|
Interesting, so you can't add any model? Is this happening also if you just install gazebo on its own, i.e. |
|
Correct, no models can be added. The simulation is not running as seen in the screenshot below (RTF, SIM TIME etc. is not shown at the bottom). The GUI is not frozen, so maybe it is gzserver hanging. The same goes for 11.11 and 11.10.
|
|
The problem seems to be similar to conda-forge/gazebo-feedstock#148, that in theory has been fixed with conda-forge/gazebo-feedstock#152, i.e. since |
|
Thanks for fixing this @traversaro! A new build should be available in the next few hours - could you please try again then @simonbogh? |
|
Great, thanks! Gazebo 11.12 |
|
Indeed, that is what I was afraid of and the reason I am trying to mark those as broken in conda-forge/admin-requests#677 . In the meanwhile can you try to install a build without the problem, i.e. : ? |
|
Ah, do you know what pin is causing the issue @traversaro? I could rebuild the parts of noetic if needed with whatever package has been updated and causes incompatibilities |
Looking at the merged PRs in gazebo-feedstock, I would guess ffmpeg=5 (ros-noetic is on 4.4) and libgdal 3.6 (ros is on 3.5), but I would guess the ffmpeg one as it is far more used (see https://index.ros.org/d/ffmpeg/ and https://index.ros.org/d/libgdal-dev/). However, ffmpeg removed several APIs, so it is possible that the migration is not effortless. |
|
Maybe this is relevant. When trying to install |
|
Hello @simonbogh, were you able to check if |
|
Yes, and Gazebo runs now, but models can still not be spawned. Gazebo works with that build, but if I run a standard Here are the immediate errors I found in the terminal: In the end, rviz loads with the model, but no models are ever spawned in Gazebo. MoveIt |
|
Ok, but the basic models that do not use ROS are working, right? I think the cause behind this new errors are different, can you please open a new issue in this repo with all the details (i.e. |
|
Yes, indeed they do. I will do some more testing and open a new issue if necessary. Thanks a lot!
|
|
Great, thanks! |
|
Just a quick follow-up. Tried the same code (Franka, moveit) on a computer running Ubuntu 22.04, conda/mamba, robostack, noetic, same package versions, same python version. On the Ubuntu computer it works, on my mac gazebo still pauses, and if unpaused the spawn service fails and no models are added in gazebo. Minimal example, the model is not spawned. Maybe some incompatibility between gazebo and ros-noetic-gazebo-ros. rosrun gazebo_ros gazebo
rosrun gazebo_ros spawn_model -file my_model.urdf -urdf -z 0 -model my_object |
|
Perfect! Can you open a new issue at https://github.com/RoboStack/ros-noetic/issues/new/choose . Closed issue are a bit difficult to manage in the longer term. |
|
FYI - not being able to install ros-noetic-desktop and the most recent gazebo comes down to needing conda-forge/qt-webengine-feedstock#24 (ros-noetic-desktop needs qt-webengine needs qt-main 5.15.6 which does not have the most recent migrations ..) |
Ok! Apparently we can't mark the broken builds as broken (see conda-forge/admin-requests#677). It is sufficient to merge conda-forge/admin-requests#677 to avoid that gazebo _3/_4/_5 builds are installed? |
Issue:
Hi, this issue is a follow up from another issue (#279); this post provides more detail than what I mentioned at the end of #279 (see thread start here). Basically, I cannot add any model (including the stock cube and spheres) to a Gazebo world on macOS; I experienced the same issue as the other user. However, I can confirm that this issue only happens on an Intel-based Mac. I do not have this issue on an M1 Mac.
Fixes Tried:
I tried to update gazebo from
11.10.2 -> 11.12.0(as mention at this link). However, I get the following error when I try to update gazebobecause
ros-noetic-rvizrequires the currently installed version ofassimp.I also installed
gazebo 11.12.0locally on my machine (viahomebrew). Then I changed the gazebo softlinks in thecondaenvironment to point to the locally installed gazebo. However, this attempt did not work.System Specs + Environment Setup:
Here is the specs for the Intel-based Mac.
Here is the list of conda packages.
The text was updated successfully, but these errors were encountered: