Ranom
1
[SOLVED] - see posts below!
Hi All,
For some reason I’m getting terrible FPS when running my virtually empty scene in Chrome.
I connected the profiler and can see that most the time is spent in WaitForTargetFPS.
On FireFox: approx 13ms → achieving target 60 fps
On Chrome: approx 49ms → achieving <20 fps.
Unity: 2020.2.1f1
Chrome: 87.0.4280.88 (Official Build)(64-bit)
Firefox: 84.0.1 (64-bit)
The scene composes of:
- Main Camera
- Directional Light
- Canvas w. one TMP text field
- Free camera controller script
- Really simple FPS counter script
Any help would be appreciated.
Thanks
Ranom
2
Here’s some snapshots from the profiler…
Ranom
3
I took a look in the chrome profiler but couldn’t really work out much from it.
There’s some big long running task (which I’m guessing is the WaitForTargetFPS)
The GPU seems to be doing something at the bottom too but you can’t drill down in to it.
Ranom
4
Hi All,
I enabled this setting in chrome://flags and now performance is as expected.
I guess chrome was using the wrong renderer for some reason.
You can check by going to chrome://gpu
It’d be nice if it was more obvious that it was GPU time rather than VSYNC in the profiler.
Hope this helps others out.
2 Likes
