Search Issue Tracker
Fixed in 5.1.0
Votes
0
Found in
5.1.0b1
Issue ID
688397
Regression
No
New AW messages are inconsistent with current state
New AW messages are inconsistent with current state
1. What happened
The new AW messages are very useful, but presently not always reflecting the current state ( wrong message)
2. How we can reproduce it using the example you attached
repro:
(a) Create an object
note that the message says to create Animator and Clip
Create Animator component using "Add Component" in the Inspector window
note that the message still says the same thing although the Animator component does exist on the selected object (bad).
Clicking the AW canvas/graph area forces the message to update to the correct message... "... create clip"
(b) Click the Create button in AW to create a Clip
(note that the Rec mode is enabled in the AW, but the Editor Play controls are not red, as expected, bad. disable/enable the AW Rec button/mode to put the Editor into the proper state)
Now remove the Animator component from the object in the Inspector
note that the object no longer has an Animator component, but the message only says to create a clip (bad)
Click Play, the Stop in the Editor to force the message to update to the correct message, asking the user to create both the Animator and the Clip.
(c) File>New Scene
note that the AW continues to display any keys that were previously displayed, rather than the expected message.
Create a new object to force a refresh and proper message in the AW.
(d) Create a new object and Animator component
Drag'n'drop a Clip from the Assets folder onto the object in the Scene window
note that the AW did not update to show the animation clip, although the clip is presently applied (bad).
Unselecting, clicking Play or any other action forces the AW to refresh and display the keys.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment