Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.22f1
2022.2.13f1
2023.1.0b10
2023.2.0a8
2023.3.0a1
6000.0.0b11
6000.1.0a7
Issue ID
UUM-32488
Regression
No
Errors are thrown when attribute with source location is connected to SpawnEvent block in Spawn System
How to reproduce:
- Import the attached package
Actual result: Errors are thrown to the console
Invalid operation type: 544
UnityEngine.StackTraceUtility:ExtractStackTrace ()
VisualEffectAssetEditor:OnEnable () (at Library/PackageCache/com.unity.visualeffectgraph@12.1.9/Editor/Inspector/VFXAssetEditor.cs:221)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
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. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
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.
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. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
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.