Search Issue Tracker
Third Party Issue
Votes
3
Found in
1.18.0
Issue ID
UUM-134030
Regression
Yes
Mouse input is not blocked when Steam Overlay is open
How to reproduce:
1. Open the attached project "IN-133408"
2. Build the project
3. Add the build to Steam as a Non-Steam game by selecting "Games > Add a Non-Steam Game to My Library..." in the Steam menu bar
4. Open the game using Steam
5. In the game, press 'Shift' + 'Tab' to open the Steam Overlay
6. Observe the in-game buttons while left-clicking on them with the Overlay open
Actual result: The buttons are able to be pressed down while the Steam Overlay is open
Expected result: The buttons cannot be pressed down while the Steam Overlay is open
Reproducible with: 1.10.0 (6000.0.57f1), 1.18.0 (6000.0.57f1, 6000.0.67f1, 6000.3.8f1, 6000.4.0b8, 6000.5.0a6)
Not reproducible with: 1.10.0 (6000.0.56f1), 1.18.0 (6000.0.56f1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Keyboard input is blocked
- Also tested with Discord Overlay where the issue did not reproduce
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated this issue and confirmed that the difference is behaviour changed with fixing the following bug: https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-134030, which was back ported into Unity 6000.0.57f1 which explains why the behaviour is different between 6000.0.56f and newer versions. Since Steam hooks into input to integrate with the platform (especially on Windows) and doesn't rely on best practices laid out by Microsoft doing so, this results inevitably in this kind of issues.
We will close this case as a third-party issue. We recommend contacting Valve or maintainer for support. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation.
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated this issue and confirmed that the difference is behaviour changed with fixing the following bug: https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-134030, which was back ported into Unity 6000.0.57f1 which explains why the behaviour is different between 6000.0.56f and newer versions. Since Steam hooks into input to integrate with the platform (especially on Windows) and doesn't rely on best practices laid out by Microsoft doing so, this results inevitably in this kind of issues.
We will close this case as a third-party issue. We recommend contacting Valve or maintainer for support. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation.