Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.8f1
2023.1.11f1
2023.2.0b7
2023.3.0a3
Issue ID
UUM-47316
Regression
No
Blackboard in the Shader Graph does not scroll horizontally when the "Shift" button is held and the mouse wheel or touchpad is scrolled vertically
Reproduction steps:
1. Open the attached "repro_IN-52095.zip" project
2. Open the "Bacteria.shadersubgraph" Shader Graph ("Assets > Samples > Shader Graph > 14.0.8 > Procedural Patterns")
3. Turn on the Blackboard by pressing the "Blackboard" button in the window Overlay
4. Press somewhere on the Blackboard (so you're focusing it) and, while holding the "Shift" button, scroll down vertically with your mouse wheel or with your touchpad
Expected result: The Blackboard view scrolls horizontally
Actual result: The Blackboard does not scroll horizontally
Reproduced with: 2021.3.30f1, 2022.3.8f1, 2023.1.11f1, 2023.2.0b7, 2023.3.0a3
Reproduced on: Windows 11 (10.0.22621) (user's), Windows 10 (22H2)
Not reproduced on: No other environments tested
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note:
While this is a little uncomfortable, we don't feel it represents a critical risk to users at the time. We are currently in the process of reworking some of our UI/UX and expect this will be addressed as a consequence of that. We won't address this as an isolated issue in the current version.
Resolution Note (2023.3.X):
While this is a little uncomfortable, we don't feel it represents a critical risk to users at the time. We are currently in the process of reworking some of our UI/UX and expect this will be addressed as a consequence of that. We won't address this as an isolated issue in the current version.