User-created experiences · Updated 2026-08-09

Roblox input lab

A platform-aware Roblox input hub that avoids pretending every experience shares one sensitivity or control model.

ExperienceRecord exact titleControls and supported devices can differ between Roblox experiences.
PlatformRecord device + OSA PC browser result cannot prove console or mobile behavior.
ReproductionTwo experiencesCompare a second experience to separate platform input from experience scripting.

Do not diagnose the whole platform from one experience

Roblox is a platform for separately developed experiences. An input that fails in one place but works in another points toward experience-specific controls or scripting; a signal absent across experiences deserves platform and hardware checks.

Record the exact experience, device, connection and account state. That note is more useful than a generic claim that “Roblox controller does not work.”

Repeatable checklist

  • Test the device in Keymap
  • Compare a second Roblox experience
  • Record exact experience and platform

Choose the correct test for mobile

Touch layouts can place controls near browser or operating-system gesture areas. The touch lab maps where the page actually receives contacts and how many concurrent contacts survive.

Motion sensors require permission and are not exposed in every browser. A missing API should be recorded as unavailable, not reported as a broken phone sensor.

Repeatable checklist

  • Run multi-touch with normal grip
  • Inspect missed edge zones
  • Request motion permission only when needed
Game-specific boundary: Experience creators control many mappings. Keymap can test the input path but cannot promise that an individual experience implements a device.
Do not lose the baseline

One change. Same test. Clearer answer.

Keep the device, connection, platform, game build and previous setting beside every result.