Add persistent force-control toggle to F1 debug menu
This commit is contained in:
1 parent
3078b8afd0
commit
20aa1bc2b9
13 files changed
+96
-12
No files matched your search
@@ -6,6 +6,17 @@ jet pack tutorial flow. This is not a verified faithful complete scene or releas
|
||||
|
||||
## User-requested F1 debug menu
|
||||
|
||||
Follow-up: Force Control is now a persistent TRUE/FALSE menu toggle. It overrides
|
||||
effective ownership while preserving authored control state; switching it off
|
||||
restores that state. Reset/new scene clears it. Cutscene execution continues and
|
||||
DEFAULT music restoration uses authored ownership, avoiding a debug-induced silent
|
||||
return. Menu/director/interaction checks pass; the extended16-frame Linux SDL
|
||||
test records actual forced movement during active neutron1a,14.00 total travel,
|
||||
all menu checks true and zero Vulkan validation errors
|
||||
(artifacts/force-control-window.log).539 original hashes remain unchanged.
|
||||
Both executables are republished for this follow-up; no Windows runtime
|
||||
check is claimed. The full-suite evidence below is from the preceding menu build.
|
||||
|
||||
F1 opens a modern debug overlay with live player/scene/task diagnostics. Keyboard
|
||||
actions cover camera, cutscene skip, energy refill, jet-pack grant, staged SCENE
|
||||
editing,33 prepared levels/original starts, reset and resume. Gameplay, cutscene
|
||||
|
||||
Reference in new issue
Block a user