1. Delivery Profile

Switch the whole page between a ChronoDivide-like input path and the higher-frequency lab path before touching the lower-level controls.

2. Mode

Pick the input path you want to compare, then click Arm selected mode or click the stage itself.

3. Processing

These knobs are applied in this page only. They help separate OS-level pointer behavior from custom game-side processing like smoothing or acceleration curves.

4. Platform And Delivery

Compare fullscreen modes and browser event paths directly. This lets you test whether latency changes come from lock mode itself, the fullscreen target, or how the browser delivers move events.

5. Visual And Telemetry

These controls let you strip the page down or bring diagnostics back in. If the page itself is adding delay, you should see the feel change as you turn pieces off.

6. Stress

Add deliberate bottlenecks to see how pointer feel changes under lower frame rate, main-thread stalls, or extra DOM work.

7. Suggested checks

• Compare Regular, Adjusted lock, and Raw lock in the same browser and the same fullscreen state.
• Run the same test in stage fullscreen and page fullscreen; some browsers treat them differently.
• Switch Auto, pointerrawupdate, pointermove, and mousemove to see whether delay is in delivery or rendering.
• If adjusted lock feels slower, disable Windows Enhance pointer precision and retry.
• If raw lock fails, inspect the event log for pointerlockerror and fallback behavior.
• Use Minimal telemetry mode plus hidden grid/trail to see whether the page itself is the bottleneck.
• Use Smoothing amount as a reference for what true software-added lag feels like.
• Use the stress controls to see whether “slow pointer” is actually low render FPS or jank.