direct raycaster intersection with text component does not work
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
Need to add a mesh/geometry for it to work. The geometry is created by the three-bmfont-dependency and it looks like the vertex positions of the generated buffer geometry are quite large? Perhaps we cannot fix it, but at least document it as adding an invisible mesh plane is not too bad.
- A-Frame Version:
- Platform / Device:
- Reproducible Code Snippet or URL:
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 by reproducing direct raycaster intersection with an A-Frame text component and inspect the geometry generated by the three-bmfont-dependency, especially its vertex positions. Done means either restoring intersection behavior or documenting the invisible mesh-plane workaround if the generated geometry cannot be fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100