Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.2.0b3
Issue ID
1037678
Regression
No
Non-Legacy animations cannot be sampled outside the Editor without an Animator error pops up when Animator is added
How to reproduce:
1. Open attached Unity project "BugReports"
2. Build on a Standalone
Expected result: Background color is changing because Lighting is animated.
Actual result: Background color is not changing and "Non-Legacy animations cannot be sampled outside the Editor without an Animator. If you want to sample this clip outside the Editor, add an Animator Component to this GameObject" errors appear in an output_log.txt file.
Reproduced with: 2018.3.0a2, 2018.2.0b9, 2018.2.0a6.
Note: Can not check on 2017.1.0a1 - 2018.2.0a5 version because of errors.
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 2019.1):
Calling AnimationClip.SampleAnimation required a valid AnimatorController attached to the game object's Animator component. This should not have been necessary and changes were made in order to allow Animator to sample an animation clip without an AnimatorController.