Ian Chen

I think there may need to be a physical object for the mouse click (ray cast) to register a correct point otherwise it returns incorrect result as described.

possibly related Qt issues: * https://bugreports.qt.io/browse/QTBUG-103592 * https://bugreports.qt.io/browse/QTBUG-95638 - mentions bug is fixed in 5.15.11

You could try other map plugins that are listed in this page: https://doc.qt.io/qt-5/qtlocation-index.html#plugin-references-and-parameters I don't know how well they work though.

the `mapboxgl` plugin works for me. I created a PR: https://github.com/gazebosim/gz-gui/pull/520 Update: closed PR as it's not clear if we can use the `mapboxgl` plugin and it still freezes. Gazebo...

> So I think part of the solution is to ensure that Ogre is initialised on the main thread in Scene3D (in the RenderThread object) before it is moved to...

> params["useCurrentGLContext"] = "1"; > is treated differently on Linux (and is effectively ignored on macOS and windows). ah! that param is important as we are sharing GL context and...

hmm the output does not show the compilation error. Someone suggested this fix for focal: https://github.com/osrf/gzweb/issues/184#issuecomment-704398535. It's partially applied in the 1.4.1 branch. You can try also the `sed` cmd...

the changes in `fix_build_gz11` branch have been merged in to `gzweb_1.4` branch. https://github.com/osrf/gzweb/pull/194 You can try the `gzweb_1.4` branch instead.

can you try with node v12?

I think the gazebo bottle is fixed but it could still be affecting downstream libraries that depend on gazebo. Possible workaround: https://github.com/PX4/PX4-Autopilot/issues/17644#issuecomment-847638715