Search Issue Tracker
Active
Votes
1
Found in [Package]
1.17.17
Issue ID
1324512
Regression
No
Using different Play Mode Script options makes Animation Rigging behave differently when loading an Addressable Prefab
How to reproduce:
1. Open the user's attached "AddressablesAnimationRiggingBug.zip" project
2. Open the SampleScene Scene
3. Open the Addressables Groups window (Window -> Asset Management -> Addressables -> Groups)
4. Set the "Play Mode Script" to use "Asset Database (fastest)"
5. Enter the Play Mode and observe the Game view
6. Set the "Play Mode Script" to use "Use Existing Build..."
7. Build the Assets (Addressables Groups window -> Build -> New Build -> Default Build Script)
8. Enter the Play Mode
9. Observe the Game view
Expected results: Both Play Mode Scripts options have the same behavior
Actual results: Both Play Mode Scripts have different behavior
Reproducible with: 10.10.0, 1.17.17 (2020.3.4f1, 2021.1.5f1, 2021.2.0a14)
Could not test with: 10.10.0, 1.17.17 (2019.4.23f1, 2018.4.33f1) (Cannot downgrade the project and Animation Rigging package)
Note:
-Using the "Play Mode Script" option "Simulate groups" gives another different behavior (cubes move but are out of sync)
-Building the project gives the same behavior as using "Use Existing Build"
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