Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.58f1
6000.0.38f1
6000.1.0b6
6000.2.0a3
6000.3.0a1
6000.4.0a1
Issue ID
UUM-97507
Regression
No
[sw-unity-6-1] Shadergraph panning area size is constant regardless of the size or the zoom level
How to reproduce:
1. Open the "ReportingBugs.zip" project
2. Open the "Repro.shadergraph" Shadergraph in a small docked square window
3. Click, hold and move the "Vertex" Node a tiny bit in the Shadergraph Window
4. Observe the Shadergraph window
Expected result: The Vertex Node does not move or moves slower
Actual result: The Vertex Node starts panning
Reproducible in: 2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a3
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Note: It would be best to scale down the panning areas based on the size of the Shadergraph window or based on the zoom level in the Shadergraph window
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
- Build for iOS with UnityAds fails with linker failures when performing a CocoaPods build
- NavMeshManager.LoadData takes a long time and causes performance spikes when enabling a NavMeshSurface with already instantiated NavMeshLinks
- Shadows created by real-time Spotlights are rendered at a very low resolution on terrain when HDRPAsset Lit Shader Mode is set to Forward or Both
- “STP” in Project window > Advanced Upscalers by Priority menu list is shown as available to add when it is already added to the list
- Rename fails with an error “Canceling DisplayDialog” when renaming a Mipmap Limit Group in Project Settings > Quality after adding a new group
Resolution Note:
There are options in the settings to adjust the panning speed.