Search Issue Tracker
Fixed in 2017.4.0
Fixed in 2017.4, 2018.3, 2019.1
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
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
- [VCS] Improve UI/UX of connection params (history of previous params, auto-find p4config, etc.)
- [VCS] After working offline in Perforce, show UI for "p4 reconcile" or some other way of getting in sync
- [VCS] UI lacks a File History window (note: needs plugin changes, UI work)
- [VCS] Version Control window context menu: add "Open in P4V" and tweak wording
- [VCS] Perforce/etc. settings could really use a separate entry in Project Settings sidebar
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.