Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
5.6.3f1
Issue ID
947990
Regression
No
Animator culling mode 'Cull Completely' does not update after enabling an object with Time.timeScale equal to 0
Reproduction steps:
1. Open the attached project "Mechanim Bug.zip";
2. Open the scene 'Test Scene' and hit play. There are 3 cubes, each of them has a different animator culling mode;
3. Click the on the button "Disable Objects" to make each cube inactive in the scene;
4. Select "Pause Time" to set the timescale to zero;
5. Click the button "Enable Objects" to have the cubes set to active again (while the timescale is zero);
6. Click on the "Start Time" button to set the timescale back to 1.
Expected results: After enabling Time again, all three cubes should be animated again.
Actual results: The red cube (set to culling mode 'CullCompletely') is not animated.
Reproduced on: 5.6.0f1, 5.6.3p2, 2017.1.1f1, 2017.2.010, 2017.3.0a7.
Note: Not able to reproduce the issue on lower than mentioned versions as some of the used methods including "fixedUnscaledTime", "inFixedTimeStep" and others, were introduced only on 5.6.0f1.
Comments (3)
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
ProgrammerSi
Apr 26, 2019 12:47
We are also experiencing this in 2017.4.23f1
Greng
Apr 30, 2018 19:45
This is also being seen again in 2017.3.1p1
jjejj87
Apr 05, 2018 05:40
This issue is back on the 2017.4f1 LTS. Please fix it ASAP!