Robot model randomly appears in gzweb

[osrf-migration]

Original report (archived issue) by Alexander Wentz (Bitbucket: aleWe89).

---

Hi guys,

i described the problem here more detailed.

So basically my simulated robot sometimes appears in the gzweb-gui and sometimes not. On my local machine i can make it appear by move it around in translate mode in the gazebo gui. There was a case when i restarted gzweb and the robot wasn't there anymore.

This bug happens more often when i'm running the simulation and gzweb in a docker container.

PS: This is my first issue report in bitbucket, sorry if the description isn't that good.

[osrf-migration]

Original comment by Alexander Wentz (Bitbucket: aleWe89).

---

• Edited issue description

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

Which gzweb version / branch are you using?

When the model doesn't appear in the gzweb GUI, do you see the sim time / real time being updated or do they stay at 0:00:00?

It'll also be useful to check in the browser's developer console to see if there are any suspicious error messages.

[osrf-migration]

Original comment by Alexander Wentz (Bitbucket: aleWe89).

---

So on my local machine i used the branch 2.0.0, but in docker i left the branch in default (basically the installation is like in the docker files of osrf).

The simulation time is updated correctly. I can pause/unpause the simulation via rosservice, gazebo-gui or gzweb-gui and see the expected effects. Also the ground plane is always listed in the model tree.

When i start gzweb from docker the developer console show some warnings about a shader:

#!javascript
THREE.WebGLShader: gl.getShaderInfoLog() fragment 0:2(12): warning: extension `GL_ARB_gpu_shader5' unsupported in fragment shader / unsupported in vertex shader    (three.js:16998)

There are also some errors which doesn't look so suspicious to me:

and

Edit:
I checked console output when starting gzweb on my local machine (above are from starting in docker). The model was displayed correctly and the "big" difference was that there wasn't any warnings about the extension `GL_ARB_gpu_shader5'.

[osrf-migration]

Original comment by Mohamd Ayman (Bitbucket: Mohamd Ayman).

---

@aleWe89 The branch gzweb_2.0.0 still has some problems, You can try the default branch, the default branch now support recent nodejs versions just like gzweb_2.0.0 .

And you can tell us if the same issue appeared again with you :)

[osrf-migration]

Original comment by Alexander Wentz (Bitbucket: aleWe89).

---

Well, the problems are with the default branch which i use in my docker container. On my computer i use 2.0.0 and the most times the robot model is shown correctly in the gzweb-gui.

PS: Only installed gzweb on my computer to test it and i am more interested in using it in docker. On my computer it works fine in 9 of 10 cases, in docker it works probably in 1 of 10 cases.

[osrf-migration]

Original comment by Mohamd Ayman (Bitbucket: Mohamd Ayman).

---

Ah I see.

Did you try running gzweb_2.0.0 in docker?

Also if you tried running gzserver like gzserver --verbose do you see any errors or warnings in the terminal?

Thanks.

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

found this issue related to the GL_ARB_gpu_shader5 warning. Were you using the same browser to access gzweb in the docker container and your local machine? Also note if the browser is launched from within the container, make sure the container has gpu access.