Raycaster, laser-controls, raycaster-intersected event in Rift: intersection point values
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
The plane is listening for raycaster-intersected events and I get the intersection point and can set the indication circle position.
If I move the plane in the code AFTER the laser-controls entity, just before the scene closes, the raycaster-intersected events are still triggered, BUT the intersection point is just returning the position of the plane, and not the position of the intersection.
- A-Frame Version: 0.7.1
- Platform / Device: Rift
- Reproducible Code Snippet or URL: https://codepen.io/anon/pen/wyJqBN
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CodePen reproduction and trace the laser-controls raycaster-intersected event, focusing on how the intersection point is calculated after the plane moves. Done means the event reports the actual ray-plane intersection rather than the plane's position, while preserving the existing event behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100