Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b7
Issue ID
1004542
Regression
Yes
[Unity 2018.] DynamicBoneThreaded.Update() in a specific project takes more time than in earlier versions
To reproduce:
1. Open project(link in edit)
2. Open 'FontXR_Calibrator' scene
3. Open profiler, enable deep profile
4. Play scene
Expected: DynamicBoneThreaded.Update() should take the same amount of time in 2018.1.0b5-2018.1.0b8
Actual: DynamicBoneThreaded.Update() in 2018.1.0b7 and b8 takes more time than in 2018.1.0b5-b6
Reproduced: 2018.1.0b7, 2018.1.0b8, 2018.2.0a1
Not reproducible 2018.1.0b5, 2018.1.0b6
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