Spectator mode broken
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Camera entities with spectator="true" applied do not appear to enter spectator mode when the VR headset is in use. The scene either disappears entirely or freezes on the last frame before entering VR (wasd keys are unresponsive and changes made to the scene by the player are not reflected in the monitor view)
- A-Frame Version: 1.2.0 & commit: #bbd27c76
- Platform / Device: Windows 10 / Chrome / SteamVR beta 1.19.7 / First gen HTC Vive
- Reproducible Code Snippet or URL: aframe-issue-4905.glitch.me/
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 reproducible Glitch URL and test the spectator="true" camera while the HTC Vive is in use. Trace the spectator camera behavior from the VR entry point, then verify that the scene remains visible, WASD input works, and monitor changes reflect player edits without freezing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100