When hiding the GUI overlay, trying to adjust the camera speed using Right Mouse Button + Scroll or Alt + Scroll does not work when a UI element is positioned between the mouse cursor and the 3D Studio viewport.
Adjusting the camera’s panning speed only works when the ScreenGui instance is disabled.
The issue described, where adjusting camera speed via Right Mouse Button + Scroll or Alt + Scroll fails when a GUI overlay is present, highlights a deeper interaction problem between Roblox Studio’s input handling system and the rendering of ScreenGui instances. In Studio, input events are processed through a layered system: the 3D viewport captures camera controls, while GUI overlays intercept mouse and keyboard events depending on their positioning. When a ScreenGui element is positioned between the cursor and the viewport, it effectively consumes the input, preventing the camera speed adjustment from registering.
This behavior is consistent with how Studio prioritizes UI input, but it introduces unintended friction for developers. The expectation is that camera controls should remain functional regardless of GUI overlays, especially when the overlay is hidden or non‑interactive. The fact that disabling the ScreenGui instance restores functionality confirms that the input pipeline is not correctly distinguishing between interactive and non‑interactive states.
Key points to consider:
Input event prioritization: Studio currently routes scroll and modifier inputs to the topmost UI element under the cursor. This prevents the viewport from receiving the event when a GUI overlay is present.
Hidden vs. disabled states: A hidden GUI (Visible = false) may still intercept input if the instance is active, whereas a disabled ScreenGui correctly releases input back to the viewport. This distinction is critical and explains why the bug occurs.
Developer workflow impact: Camera speed adjustments are essential for efficient navigation in Studio. Losing this functionality when overlays are present slows down iteration and frustrates developers working with complex UI systems.
Consistency expectations: In most professional environments, hidden or non‑interactive overlays do not block input to underlying systems. Aligning Studio with this standard would reduce confusion and improve usability.
Implementation feasibility: The fix would involve adjusting the input pipeline so that hidden or non‑interactive GUI elements do not consume scroll events. This ensures that camera controls remain accessible regardless of overlay state.
Version context: The issue is reported in Roblox Studio Version 0.702.2.7020633, which provides engineers with a clear reference point for reproducing and addressing the bug.
The benefits of resolving this issue are clear:
Improved navigation efficiency: Developers regain reliable control over camera speed, even when working with overlays.
Alignment with industry standards: Professional tools typically prioritize core navigation controls over hidden UI elements. Fixing this bug would bring Studio closer to those standards.
Community trust: Addressing input handling bugs demonstrates Roblox’s commitment to refining Studio usability and supporting developers with reliable tools.
In summary, the inability to adjust camera speed when a GUI overlay is present is caused by input events being consumed by active ScreenGui instances, even when hidden. The solution is to refine the input pipeline so that hidden or non‑interactive overlays do not block viewport controls. This adjustment is technically feasible, highly impactful, and would be welcomed by the community as a meaningful improvement to Studio’s navigation system. By resolving this bug, Roblox would reinforce its commitment to providing developers with a professional, efficient, and frustration‑free environment.