Search Issue Tracker
Fixed
Fixed in 2021.3.40f1, 2022.3.33f1
Votes
6
Found in
2021.3.37f1
2022.3.26f1
Issue ID
UUM-72121
Regression
No
Crash on Animator_CUSTOM_SetFloatString when a Float parameter for an Animator is set in Play Mode after changing the RuntimeAnimatorController
How to reproduce:
1. Open the “PlayableGraphCrash.zip“ project
2. Open the “SampleScene“
3. Enter the Play Mode
4. Observe the Crash
Reproducible in: 2021.3.37f1, 2022.3.26f1, 2023.2.0a8
Not reproducible in: 2023.2.19f1, 6000.0.0b16
Fixed in: 2023.2.0a9
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- This might in part be caused by PlayableGraph or/and AnimationMixerPlayable objects, since they are essential for the reproduction
- If the “Animator.SetFloat("CrashTrigger", 1)“ method in “CrashLaunch.cs“ Script is commented out, the issue will not reproduce
First 5 lines of the stacktrace:
0x00007ff67c174a15 (Unity) Animator_CUSTOM_SetFloatString
0x00000296120852d9 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Animator:SetFloatString (UnityEngine.Animator,string,single)
0x00000296120851db (Mono JIT Code) UnityEngine.Animator:SetFloat (string,single)
0x000002961207f473 (Mono JIT Code) CrashLaunch:DoCrash () (at C:/Users/[username]/Downloads/IN-73803_PlayableGraphCrash/Assets/CrashLaunch.cs:57)
0x000002961207f0bb (Mono JIT Code) CrashLaunch:Awake () (at C:/Users/[username]/Downloads/IN-73803_PlayableGraphCrash/Assets/CrashLaunch.cs:17)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
Add comment