sar_cam_control 0 doesn't give back normal camera if you loaded a save/map with TAS
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 122
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
To reproduce:
Go into sar_cam_control 1
Play a TAS file that either loads a save or a map
When the TAS finished playing (or you stopped it manually with a bind) go into sar_cam_control 0
You'll be unable to move or look around now, until you type in_forceuser 0 in console.
If you do sar_cam_control 0 while the TAS is still playing this issue won't occur.
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 the sequence using sar_cam_control 1, a TAS that loads a save or map, and sar_cam_control 0; compare it with stopping camera control while the TAS is still running. Trace the camera-control and TAS cleanup entry points, including the in_forceuser state, and verify that normal movement and view control return without requiring in_forceuser 0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100