Search Issue Tracker
By Design
Votes
0
Found in
2019.1
2019.1.6f1
2019.2
2019.3.0a1
Issue ID
1162409
Regression
No
[TrailRenderer] Boolean properties are not animated when 'Optimize Game Objects' enabled in FBX Model
How to reproduce:
1. Open the attached 'Optimized FBX interfere with Timeline Animation Track.zip' project
2. Play 'SampleScene'
3. Observe both models
Expected result: Both models are animated the same
Actual result: Boolean properties are not animated in optimized FBX model
Reproducible: 2019.1.8f1, 2019.2.0b7, 2019.3.0a7
Can't reproduce:
- 2019.1.0a1, 2019.2.0a1, because of NullReferenceException error and optimized object is not moving
- 2017.4.29f1, 2018.4.3f1, because can't assign Timeline asset to GO Playable Director component
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
- 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
Resolution Note:
The animation paths were incorrect. Looks like they may have changed due to duplicating the objects.
E.G TrailRenderer (1) was now TrailRenderer (2).
The paths must match in order to animate correctly.