ROS3D.Viewer not appearing

158 views
Skip to first unread message

Isaac Isao Saito

unread,
Sep 23, 2014, 2:58:05 PM9/23/14
to robot-w...@googlegroups.com
# I knew I get more responses on emails so allow me to cross-post from http://answers.ros.org/question/193334/ros3dviewer-not-appearing/

With our custom package, I used to be able to show ROS3D.Viewer object on Chrome last year but now I can't. So what can cause ROS3D.Viewer to not appear in general? Sorry for sounding elementary but I can't even provide more info without advice from experts.

Live demos on http://robotwebtools.org/demos.html seem to be working for me.

Environment:

  • Ubuntu 12.04. FF32.0, Chromium 37.0.2062.94
  • OSX 10.9.5 37.0.2062.122
# If someone wants to run, there's a readme but the package is still under development and the way it installs is hacky for now.

Thanks for your advice,

Isaac

Moritz Tenorth

unread,
Sep 23, 2014, 3:18:26 PM9/23/14
to robot-w...@googlegroups.com
Hi,

some issues I had with our 3D visualizations:

- WebGL not working in my new laptop -- test at get.webgl.org (though this should not be the issue since the other demos work for you)

- Does the web console show any errors? It should show something like "THREE.WebGLRenderer 61 "

- Does it work in Firefox or another browser?

cheers
Moritz
--
You received this message because you are subscribed to the Google Groups "Robot Web Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robot-web-too...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Isaac Isao Saito

unread,
Sep 23, 2014, 3:19:42 PM9/23/14
to robot-w...@googlegroups.com
As a proof, I posted a picture how it used to look: http://answers.ros.org/question/193334/ros3dviewer-not-appearing/

--Isaac

Isaac Isao Saito

unread,
Sep 23, 2014, 3:58:37 PM9/23/14
to robot-w...@googlegroups.com
Thanks Moritz,

I'm posting logs from web console on FF and Chrome.

On FF,

    The connection to ws://192.168.8.110:9090/ was interrupted while the page was loading. roslib.js:427
    Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead jquery-1.9.1.min.js:1
    mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create roslib.js:121
    "THREE.WebGLRenderer" "56" three.js:17888
    Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead jquery-1.9.1.min.js:7
    Empty string passed to getElementById(). jquery-1.9.1.min.js line 3 > eval:6
    Use of getPreventDefault() is deprecated.  Use defaultPrevented instead.

On Chrome,

    Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: only screen and (-webkit-min-device-pixel-ratio: 1.3), not all, only screen and (min-resolution: 200dpi)
    THREE.WebGLRenderer 56 three.js:17888
    GET http://code.jquery.com/jquery.min.map 404 (Not Found) code.jquery.com/jquery.min.map:1
    GET http://192.168.8.110:8000/rwt_moveit/jquery.mobile-1.3.2.min.map 404 (Not Found) :8000/rwt_moveit/jquery.mobile-1.3.2.min.map:1

Sourcemap problem was easily removed by deleting this line[1], but View object hasn't become visible yet:

    //@ sourceMappingURL=jquery.mobile-1.3.2.min.map


[1] https://github.com/tork-a/visualization_rwt/blob/bdd862e27a14672f0da07914a4e54a497a96eda1/rwt_moveit/www/js/jquery-mobile/jquery.mobile-1.3.2.min.js#L8

Moritz Tenorth

unread,
Sep 24, 2014, 2:46:07 AM9/24/14
to robot-w...@googlegroups.com
Hmm,

weird that Chrome sends a 404 error that it cannot find the jquery.min.map but Firefox does not. However, it does not seem to be mandatory [1].

I'm sorry, I'm somewhat out of ideas. I'd recommend to try a minimal example from the tutorials that works for you, host that on the same server with the same imported JS files that you are using, and to see where things start to break down.

cheers
Moritz

[1] http://stackoverflow.com/questions/18365315/jquerys-jquery-1-10-2-min-map-is-triggering-a-404-not-found

Isaac Isao Saito

unread,
Sep 26, 2014, 11:51:05 AM9/26/14
to robot-w...@googlegroups.com
Ok, my collaborator got it working by simply specifying the size of ROSViewer object by parenthesis[1].

Still, I'm not yet sure how it used to work and now doesn't, wondering if this issue[2] I just opened is related or not.

[1] https://github.com/tork-a/visualization_rwt/commit/1bc5421fc7edbefc23ad15d0788f14a03b1b25a2
[2] https://github.com/RobotWebTools/roslibjs/issues/108

Thanks for the help.

--Isaac
Reply all
Reply to author
Forward
0 new messages