Search Issue Tracker
Fixed in 2017.4.0
Fixed in 2017.4.X, 2018.3.X, 2019.1.X
Votes
10
Found in
2017.1.1f1
Issue ID
965251
Regression
Yes
Cluster Rendering performance is slower on newest versions
Steps to reproduce:
1. Download and open the newest attached project (OC link)
2. Build for standalone
3. Run with "StartCluster.bat"
4. Start playing on all instances
Expected result: 60 fps or any other set refresh rate
Actual result: 20-40 fps
Reproduced on 5.6.0a5, 5.6.4p1, 2017.1.2p3, 2017.2.0p2, 2017.3.0b10, 2018.1.0a6
Not reproduced on 5.6.0a3, 5.5.4p4
Regression introduced in 5.6.0a5
Tested on:
i5-6400 2.7 GHz
GTX 750ti
Fixed in 2017.4.24f1, 2018.3.9f1, 2019.1.0b7, 2019.2.0a7
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
pxcoder
Mar 22, 2019 16:57
2017.4.24f1 using diff pc test is not good and fps is 25-45
pxcoder
Mar 22, 2019 07:03
test 2018.3.9f1 is always slower! please check!
LostPanda
Mar 20, 2019 10:07
want to know 2018.3.x is fixed? Only 2019.2?thanks.