Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
2019.2.0b10
2020.1.0b11
2020.2
Issue ID
1254395
Regression
Yes
[MacOS] Performance regression when dragging nodes in ShaderGraph window on heavy GPU load/integrated GPUs
How to reproduce:
1. Open attached project "shadergraph_bug.zip"
2. In the Project window, go to Assets and double-click "graph"
3. Undock the ShaderGraph window and maximize it
4. Try dragging the "graph" or any other node
Expected result: there is no dragging delay
Actual result: there is dragging delay
Reproducible with: 6.9.0, 9.0.0-preivew.14 (2019.2.0b9, 2019.4.2f1, 2020.1.0b14, 2020.2.0a17)
Not reproducible with: 1.1.1-preview, 6.7.1 (2018.4.24f1, 2019.2.0b9)
Notes:
Reproduced on macOS Catalina 10.15.5 Intel Iris Pro 1536 MB with Metal and OpenGLCore APIs, reproduces with all ShaderGraph graphs
Didn't reproduce on a Windows 10 with Intel(R) UHD Graphics 630, tested with Direct3D11, Direct3D12, Vulkan, OpenGLCore, OpenGLES2
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This behavior is unfortunately very difficult to mitigate in our current graph UI framework. We are working to replace that framework and ensuring the performance of the new framework does not have this issue.