Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.3.5f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-133609
Regression
No
Mouse input extends beyond playable area when playing on a Web build
How to reproduce:
1. Open the attached project "IN-123904"
2. Build and run the project for Web
3. In the game, navigate to the location shown in the reproduction video by moving the mouse cursor and using left mouse click to break the rock blocking the entrance to the location
4. Attempt to move left while maintaining the cursor in the playable area
5. Attempt to move left while positioning the cursor outside of the playable area
6. Observe the results of steps 4 and 5
Actual result: The character does not move left with the cursor within the playable area
Expected result: The character is able to move left without moving the cursor outside of the playable area
Reproducible with: 6000.2.0a1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Could not test with: 6000.0.66f1 (URP errors relating to shaders)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Browsers that the issue was tested on: Edge, Firefox
- Issue does not reproduce in the Editor
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We have found a potential fix on the project side which is to rename FixedUpdate to LateUpdate (https://docs.unity3d.com/6000.5/Documentation/ScriptReference/MonoBehaviour.LateUpdate.html) in InputController.cs, since the value for camZ (which is used in calculating movement for the fish) differs between Update and FixedUpdate when running the project on MacEditor and Web. This difference in camZ value does not occur with using LateUpdate.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements. If you would like to reopen the case, please provide a minimal repro of the specific issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We have found a potential fix on the project side which is to rename FixedUpdate to LateUpdate (https://docs.unity3d.com/6000.5/Documentation/ScriptReference/MonoBehaviour.LateUpdate.html) in InputController.cs, since the value for camZ (which is used in calculating movement for the fish) differs between Update and FixedUpdate when running the project on MacEditor and Web. This difference in camZ value does not occur with using LateUpdate.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements. If you would like to reopen the case, please provide a minimal repro of the specific issue.