gazebosim / gazebosim/gz-rendering
Optix: Support mouse picking
- Dominant language
- C++
- Stars
- 81
- Forks
- 90
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 10
Description
**Original report ([archived issue](https://osrf-migration.github.io/ignition-gh-pages/#!/ignitionrobotics/ign-rendering/issues/19)) by Ian Chen (Bitbucket: [Ian Chen](https://bitbucket.org/%7Beaa6fca5-6deb-43f6-907f-971c144735dd%7D/), GitHub: [iche033](https://github.com/iche033)).**
----------------------------------------
Add a function that lets user pass in x, y coordinates in screen and returns the name / ID of selected entity in the scene
Ogre implementation:
- port gazebo's [selection buffer](https://bitbucket.org/osrf/gazebo/src/eddba39b82cd7a8d9d2e3cff7c6a43174bdd972b/gazebo/rendering/selection_buffer/?at=default) and offer a function similar to gazebo's [Scene::VisualAt](https://bitbucket.org/osrf/gazebo/src/eddba39b82cd7a8d9d2e3cff7c6a43174bdd972b/gazebo/rendering/Scene.cc?at=default&fileviewer=file-view-default#Scene.cc-988)
Optix:
- TBD
Contributor guide
Research direction
Start by reading Gazebo's referenced rendering/selection_buffer implementation and Scene::VisualAt API, then compare how this rendering library exposes engine-independent scene operations. Done means users can pass screen x and y coordinates and receive the selected entity's name or ID, with the Optix behavior clarified and covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100