TRAUMA LAB WEB EDITIONTrauma Lab v1.20: mobile controls, cleanup limits and camera checks
Tested build: free v1.20. These notes describe this independent browser host. The creator’s simulation and storage keys are unchanged. Touch simulation is not physical iPhone or Android certification.
Three community questions led us back into the player: what cleanup actually removes, how melee controls work on a touchscreen, and what a camera check can prove. This is a dated test record; use the control guide for the current step-by-step instructions.
Clean all does not mean every object disappears
In our first check, a bat created through the ordinary Weapons menu remained after both Lab → Clean floor and Clean all. That observation is narrower than saying cleanup never works: different objects belong to different game systems.
The expanded checks below use menu and canvas input. We read the resulting object counts to confirm what remained, without calling simulation functions or changing game state through a debug hook.
| Test object | Lab → Clean floor | Lab → Clean all | Hand → Remove |
|---|---|---|---|
| Loose Side-view bat, knife or axe | Remained | Remained | Remained |
| Loose bowling ball | Removed | Removed | Removed |
| Table prop | Remained | Remained | Removed |
Try the appropriate individual removal tool for the object you selected. Do not reset the subject just to tidy the room unless you intend to end that experiment. We have not added a new cleanup button or changed the original physics.
Touch melee needs its own explanation
The desktop A/D instruction is only one branch of the controls. In Side view, touch users get ⟲ and ⟳ buttons while a melee tool is selected. Spawning an item, picking it up, holding it and releasing it are distinct actions. See the mobile melee steps and tested limits.
Camera tests have limits
The player already supports fullscreen and view switching. Those checks do not establish that every sequence of panning, zooming and rotation is reliable on physical Apple devices. Our additional checks compare Side, Front and Back, then restore framing with Fit. Desktop Chromium uses middle-drag and wheel input; Chromium touch emulation uses repeated pan/pinch sequences. WebKit uses synthetic pointer events. No lockup or invalid camera state was found in these sequences; this does not exclude transient flicker on a physical device. Read the exact camera test scope and recovery steps.
Fit adjusts the camera. Reset replaces the subject. Reload ends the running session. Keeping those actions separate makes both troubleshooting and feedback more useful.
Sources and method
- Creator’s official game page and the author-approved free v1.20 package.
- Player’s cleanup and view feedback and the creator’s response.
- Melee interaction feedback and Apple / Side-view feedback. These individual reports do not establish a universal bug or identify every device and version involved.
- Our 27 October 2026 checks use isolated Chromium and WebKit sessions. Test files and observations are retained by the web host. No player account or existing save was used.
These are fictional game controls, not medical instructions. We publish new notes when there is a source-backed update or a useful test result, rather than repeating the same advice every day.