Flycontrols gets stuck on yaw/pitch with mousedown.
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 858
- Forks
- 144
- PR merge metrics
- No merged PRs in 30d
Description
threeversion: 0.173.0@types/threeversion: 0.163.0three-stdlibversion: 2.35.6
Problem description:
When using Flycontrols and specifically using mousedown for yaw and pitch, the mouse can get "stuck" so that when released, mouse movement still cuases yaw and pitch. Its then impossible to get out of this mode.
Relevant code:
Suggested solution:
It seems the fix is straightforward here. See:
https://github.com/pmndrs/three-stdlib/pull/406
Contributor guide
No contributing guide indexed for this repository
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 FlyControls implementation and review the suggested solution in pull request #406. Reproduce the mousedown yaw/pitch behavior described in the issue, then verify that releasing the mouse stops further yaw and pitch movement and that the control can be exited normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100