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
5.0.0b16
Issue ID
653604
Regression
No
Transition destination context menu is inconsistent
Transition destination context menu is inconsistent
Repro:
See the attached video.
Depending on the structure of the destination state machine the context menu will look different.
a. State are always displayed in the hierarchy of menus, while State Machines are sometimes in the root menu other times in the State Machine menu
b. It is impossible to have a good overview of which State (or State Machine) is in which State Machine due to lack of clear hierarchy
Suggestion: use the same structure as in the Optimize Game Object transform selection. (Model Importer - Rig)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment