Try running Woodlands cinematic flythrough on both 5.5.2 and 5.6.1 on highspec, then record lowest fps and highest fps, then calculate the average fps on both, like a proper benchmark should. Also take notice on actual MS per frame on both.
Thank you for the updateUnfortunately we cannot reproduce this issue consistently enough for verification.
Please make sure to provide exact Hardware, Driver versions for hardware and Windows build/updates. (A DXDiag will suffice).
If you have already done so, it is not necessary to provide again.
We will continue to monitor and investigate this issue.
Update on this, i'm getting a lot of CPU hitching in the new Noir Neon Demo, a lot of stutter5.5 Woodland Time Demo:
Average FPS: 82.74
Max FPS: 187.62
Min FPS: 24.06
TimeDemo Play Started ,Level=woodland (Total Frames: 14903, Recorded Time: 252.97s)
Play Time: 180.11s, Average FPS: 82.74
Min FPS: 24.06 at frame 4138, Max FPS: 187.62 at frame 1
Average Tri/Sec: -9899000, Tri/Frame: -119634
Recorded/Played Tris ratio: 1.11
Memory Usage: WorkingSet=1306Mb, PageFile=3307Mb, PageFaults=906102
AutoTest Play Ended, (1 Runs Performed)
5.6 Woodland Time Demo:
This one looks different. i'll put it in a .zip because its huge... it has a lot of this
-Peak at Frame 1, 154.30ms : Wait - Physics Update (count: 1)
-Peak at Frame 1, 143.00ms : CSystem::DoFrame (count: 1)
-Peak at Frame 31, 332.77ms : Wait - StreamIO New Request (count: 1)
-Peak at Frame 50, 131.61ms : Wait - Network Wakeup (count: 1)
in it, one for each frame, 14900 of them.
Average FPS: 10.03
Max FPS: 16.77
Min FPS: 5.21
Edit: 154ms and 143ms is a long wait for whatever its waiting for, no wonder the FPS are so low, 150ms is equal to about 7 FPS. might that explain what's wrong here?
Users browsing this forum: No registered users and 6 guests