Search Issue Tracker
Not Reproducible
Votes
3
Found in
5.4.0f3
Issue ID
818706
Regression
Yes
[5.4][Windows] 30% Performance degradation happens when upgrading project to 5.4
How to reproduce:
1. Open the attached project
2. Download FPSDisplay.cs script and place it to Assets folder
3. Open test scene, create emply game object and attach script to it
4. Build and run test scene
5. Test it in windowed mode 1680x1050
6. Notice FPS written in the left top corner
Comparing results in Unity 5.3.6p1 and 5.4.0f3 performance got worse around 20%, in Unity 5.5.0a5 it got worse even 70%
Notes:
- Reproducible only on Windows; not reproducible on OSX;
- Reproducible only on high-end machines with powerful GPU;
- Bug may have significant impact on users in 5.5.
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