Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.1.5f1
6000.2.0b3
6000.4.0a1
Issue ID
UUM-107757
Regression
Yes
“OnGUIDepth changed: was 0 is 1. Event type was 0” error is thrown when opening newly created VFX Graph
Steps to reproduce:
1. Create a project and install the “Visual Effects Graph” package
2. Create > Visual Effects > Visual Effect Graph
3. Without pressing anywhere else double-click to open newly created VFX Asset
4. Observe the Console
Actual results: “OnGUIDepth changed: was 0 is 1. Event type was 0” error is thrown
Expected results: No errors or warnings are thrown
Reproducible with versions: 6000.1.0b14, 6000.1.5f1, 6000.2.0b3
Not reproducible with versions: 2021.3.52f1, 2022.3.62f1, 6000.0.50f1, 6000.1.0b13
Tested on (OS): macOS Sequoia 15.5 (Intel)
Not reproduced on: Windows 11, macOS Sequoia 15.4 (M4)
Notes:
- Issue is only reproducible on macOS Intel
- Issue is only reproducible for the first time in a project, new project is needed to reproduce it again
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
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.