Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.7.0
Issue ID
ISXB-636
Regression
No
Performed callback is invoked if moving the cursor while the “Completing Domain/Hold on” loading bar is visible when using the New Input System
How to reproduce:
1. Open the user’s attached “NIS.zip” project
2. Enter Play Mode
3. While the “Completing Domain/Hold on” loading bar is visible, move the cursor
4. Observe the Game window
Expected result: Text is “New Text”
Actual result: Text is some value (0.02 or other value)
Reproducible with: 1.6.3 (2021.3.30f1), 1.7.0 (2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a6)
Reproduced on: macOS 13.5.2 (Intel), Windows 10, Windows 11 (user’s info)
Not reproducible on: No other environment tested
Note: the user was able to reproduce this issue just when the Game window is set to “Play Focused” but not with “Play Maximized”, but I can reproduce with both of them and also with “Play Unfocused”
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.