In the current version of Space Game, the application fails to take control of the mouse pointer, preventing players from freely aiming or rotating the camera. In previous versions, pointer capture worked correctly, allowing smooth free-aim camera movement. The issue causes the camera to remain locked, breaking core gameplay functionality.
Issue Description
The game’s camera system is bound to the pointer input for free-aim control. However, the pointer lock event is not triggered when entering gameplay, leaving the camera static. This prevents players from looking around or controlling their ship’s orientation properly. The issue appears to be related to missing or broken pointer lock initialization logic.
Environment
Property
Value
Game
Space Game
Module
Camera / Pointer Control
Environment
Production
Platform
PC
Version
v2026.10.02a
Device
Desktop
Preconditions
Player launches the game and enters flight mode or exploration mode.
Steps to Reproduce
Start Space Game.
Enter a playable zone or flight mode.
Attempt to move the camera using the mouse.
Observe that the pointer remains visible and the camera does not move.
Expected Result
The game should capture the pointer (hide it) and allow free-aim camera control when entering gameplay.
Actual Result
Pointer remains visible and unlocked.
Camera movement is disabled.
Player cannot aim or look around freely.
Evidence
Screenshot shows the in-game interface with static camera and visible pointer.
No pointer lock or camera rotation occurs during gameplay.
Impact
Severely limits gameplay functionality.
Prevents proper navigation and combat control.
Breaks immersion and usability.
Frequency
Always
Reproducibility
100%
Severity
High
Suggested Fix
Re-enable pointer lock logic using requestPointerLock() on game canvas initialization.
Ensure pointer lock is triggered after user interaction (e.g., click or focus event).
Verify that camera binding correctly references pointer movement events (mousemove or equivalent).
Test across browsers and platforms to confirm consistent pointer capture behavior.
## Summary
In the current version of **Space Game**, the application fails to take control of the mouse pointer, preventing players from freely aiming or rotating the camera. In previous versions, pointer capture worked correctly, allowing smooth free-aim camera movement. The issue causes the camera to remain locked, breaking core gameplay functionality.
## Issue Description
The game’s camera system is bound to the pointer input for free-aim control. However, the pointer lock event is not triggered when entering gameplay, leaving the camera static. This prevents players from looking around or controlling their ship’s orientation properly. The issue appears to be related to missing or broken pointer lock initialization logic.
## Environment
| Property | Value |
|-----------|--------|
| Game | Space Game |
| Module | Camera / Pointer Control |
| Environment | Production |
| Platform | PC |
| Version | v2026.10.02a |
| Device | Desktop |
## Preconditions
Player launches the game and enters flight mode or exploration mode.
## Steps to Reproduce
1. Start **Space Game**.
2. Enter a playable zone or flight mode.
3. Attempt to move the camera using the mouse.
4. Observe that the pointer remains visible and the camera does not move.
## Expected Result
The game should capture the pointer (hide it) and allow free-aim camera control when entering gameplay.
## Actual Result
- Pointer remains visible and unlocked.
- Camera movement is disabled.
- Player cannot aim or look around freely.
## Evidence
- Screenshot shows the in-game interface with static camera and visible pointer.
- No pointer lock or camera rotation occurs during gameplay.
## Impact
- Severely limits gameplay functionality.
- Prevents proper navigation and combat control.
- Breaks immersion and usability.
## Frequency
Always
## Reproducibility
100%
## Severity
High
## Suggested Fix
- Re-enable pointer lock logic using `requestPointerLock()` on game canvas initialization.
- Ensure pointer lock is triggered after user interaction (e.g., click or focus event).
- Verify that camera binding correctly references pointer movement events (`mousemove` or equivalent).
- Test across browsers and platforms to confirm consistent pointer capture behavior.
Root cause: the unified Godot client never asked for the pointer. Nothing in it set Input.mouse_mode. The three.js space game locked the pointer on a click and steered with the mouse, and that was never ported. The Godot client's only mouse look (right-drag) was removed on 2026-08-05 when the mobile sticks were added, so on desktop you could only steer with the arrow keys. That is the same in Chrome, Firefox and the desktop build, and why the controls legend lists no mouse look. The iframe was not the problem: it has no sandbox, and pointer lock is allowed there.
Fix: spikerj/spikersoft-games-godot#189 adds mouse aim. Click on empty space, or press Z (rebindable), to capture the pointer. The mouse then turns the ship and the left button fires. Esc gives the cursor back. Opening a panel or the options, or typing in chat, also frees it. Sensitivity and invert are in Options. The touch layout is unchanged.
It reaches players with the next web-client publish and the next desktop release.
Root cause: the unified Godot client never asked for the pointer. Nothing in it set `Input.mouse_mode`. The three.js space game locked the pointer on a click and steered with the mouse, and that was never ported. The Godot client's only mouse look (right-drag) was removed on 2026-08-05 when the mobile sticks were added, so on desktop you could only steer with the arrow keys. That is the same in Chrome, Firefox and the desktop build, and why the controls legend lists no mouse look. The iframe was not the problem: it has no sandbox, and pointer lock is allowed there.
Fix: spikerj/spikersoft-games-godot#189 adds mouse aim. Click on empty space, or press Z (rebindable), to capture the pointer. The mouse then turns the ship and the left button fires. Esc gives the cursor back. Opening a panel or the options, or typing in chat, also frees it. Sensitivity and invert are in Options. The touch layout is unchanged.
It reaches players with the next web-client publish and the next desktop release.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
In the current version of Space Game, the application fails to take control of the mouse pointer, preventing players from freely aiming or rotating the camera. In previous versions, pointer capture worked correctly, allowing smooth free-aim camera movement. The issue causes the camera to remain locked, breaking core gameplay functionality.
Issue Description
The game’s camera system is bound to the pointer input for free-aim control. However, the pointer lock event is not triggered when entering gameplay, leaving the camera static. This prevents players from looking around or controlling their ship’s orientation properly. The issue appears to be related to missing or broken pointer lock initialization logic.
Environment
Preconditions
Player launches the game and enters flight mode or exploration mode.
Steps to Reproduce
Expected Result
The game should capture the pointer (hide it) and allow free-aim camera control when entering gameplay.
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Severity
High
Suggested Fix
requestPointerLock()on game canvas initialization.mousemoveor equivalent).Root cause: the unified Godot client never asked for the pointer. Nothing in it set
Input.mouse_mode. The three.js space game locked the pointer on a click and steered with the mouse, and that was never ported. The Godot client's only mouse look (right-drag) was removed on 2026-08-05 when the mobile sticks were added, so on desktop you could only steer with the arrow keys. That is the same in Chrome, Firefox and the desktop build, and why the controls legend lists no mouse look. The iframe was not the problem: it has no sandbox, and pointer lock is allowed there.Fix: spikerj/spikersoft-games-godot#189 adds mouse aim. Click on empty space, or press Z (rebindable), to capture the pointer. The mouse then turns the ship and the left button fires. Esc gives the cursor back. Opening a panel or the options, or typing in chat, also frees it. Sensitivity and invert are in Options. The touch layout is unchanged.
It reaches players with the next web-client publish and the next desktop release.