Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2022.2.3f1
2023.1.0a26
Issue ID
UUM-22233
Regression
No
[VFX Graph] Field transform defined on type UnityEditor.VFX.TTorus is not a field is thrown when editing gizmos in the scene view
- How to reproduce
- Import the attached project
- Open New Scene scene
- Open New VFX
- Select New Arc Torus property
- Select New VFX GO in Hierarchy
- In Visual Effect Panel (Scene View), select New Arc Torus in Gizmos dropdown
- In the Scene View, try dragging scale X gizmos
- Error is throwing to the console: {color:#de350b}ArgumentException: Field transform defined on type UnityEditor.VFX.TTorus is not a field on the target object which is of type UnityEditor.VFX.TArcTorus.{color}
{color:#de350b}Parameter name: obj{color}
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
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- 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”
Resolution Note:
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.1.X):
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.