Keep camera in primary scene
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 797
- Forks
- 98
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
I suggest having a way to keep the camera in the primary scene. As discussed here: https://discord.com/channels/740090768164651008/1162488856088690879/1239947711696863316
There is a issue where Ecctrl takes out the camera, therefore we cannot use const { camera } = useThree(); camera.position and trust the position is the same as it's moving with Ecctrl.
This also breaks the whole workflow on pmndrs/uikit as it depends on using the camera in the scene.
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 by tracing how Ecctrl handles the camera and how useThree() accesses it in the primary scene; the issue names no files or tests. Check the interaction with pmndrs/uikit, and consider the work complete when the camera remains in the primary scene and its position stays reliable while Ecctrl moves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, three.js, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100