This is the direct line to the team. Hit something broken, confusing, or missing? Tell us here — the more specific (what you did, what happened, what you expected), the faster we can fix it. Feature ideas welcome too.
Having re-created museum_world.sdf (initial state) in the correct location. I start the simulation and the gz viewer without any apparent errors but nothing happens in the simulation window when i click the connect button
Is the gazebo websocket service running? gz-launch websocket.gzlaunch
All running - terminal output below
root@localhost:~# ps aux | grep gz
root 315 26.0 2.2 820836 183368 pts/0 Sl+ 12:01 1:39 gz sim -r -s museum_world.sdf
root 410 2.0 0.3 455568 24960 pts/1 Sl+ 12:01 0:07 gz-launch websocket.gzlaunch
root 1116 0.0 0.0 3956 1920 pts/2 S+ 12:07 0:00 grep gz
Right this is a bug. I just checked, let me get back.
@threent , this is fixed. Can you try again after stopping and starting the workspace
the simulation window starts but shows a blank environment rather than the picture in the text. Do you want me to list my museum_world.sdf?
It takes a while for the museum model to load in the sim, while gazebo is pulling the asset. After the first load it’s cached and subsequent loads will be faster.
Sorry I forgot to change the world in the load command. I now get
root@localhost:~# gz sim -r -s museum_worlrld.sdf
Unable to find or download file
Could you check the filename once? Here you’ve mentioned museum_worlrld.sdf
Sorry - my typo. now loaded. I will continue to add the other elements.
1 Like
I have now started creating the urdf. The box appears so small in the simulation window that I can barely tell what colour it is let alone see the size change. In native Gazebo I could zoom in but I can’t see a way to do this in the simulation window
You can zoom using the scroll wheel in the Gazebo viewer here as well. Try it out and let me know
I have dug out a mouse and attached it to my laptop. I can now expand the picture. As an old hand I used keyboard shortcuts in native Gazebo.
That’s a great suggestion. I’ve added keyboard shortcut controls in our roadmap. Will let you know once its implemented.
I no longer seem to get any free time. I think it is because I have left the browser page open on the section I was reading and that keeps the clock ticking. Is the correct way forward to keep closing the web page when I am not actively using it?
Or I have just spotted I can log out which presumably stops the clock. I will log out for today and hopefully be able to re-start tomorrow afternoon.
I have progressed happily as far as starting Foxglove. I still get the warning
You’re using an unsupported browser. Foxglove Studio currently requires Chrome v76+.
Check out our cross-browser support progress in GitHub discussion #174.
Should I worry about this?
As I am almost out of time for today. I will start again fresh -probably on Friday afternoon
It just occurred to me that as I am running Firefox the Chrome message is definitely irrelevant unless you run it in the background to load Foxglove
Hi @threent, once you close the page, we auto shutdown your workspace after an idle time of 15 mins, but the idle time is not counted towards your usage limit. Another alternative is to just stop the workspace before closing the lesson. That stops it immediately.
Also the free usage limit resets in a dynamic rolling 24 hours window which starts when you first launch the workspace in that window.
Do let me know if you face any discrepancies.
Thanks for pointing this out. Let me check and get back.
I’ve verified our course project running end to end in Firefox, and it runs fine. So you can ignore the compatibility message for now.
Let me know if you come across any issues though.