-
Notifications
You must be signed in to change notification settings - Fork 52
Debugging Client Performance
WebGL runs on a wide variety of systems, but because of this wide support, it's common to encounter devices that exhibit poor behavior out of the box. Often there are simple fixes to many performance problems that only need to be done once, to allow the browser to get the best performance out of the underlying hardware.
If you're experiencing consistent black screens or poor performance even in simple worlds, the first thing to check is WebGL Report. This will tell you the capabilities of your system as seen by the browser, and give you some hints about what might be wrong. Check to see if the "Unmasked Renderer" lists your GPU - if you've got a gaming desktop or a high-end laptop with an NVIDIA or AMD Radeon GPU, it should be listed here.
If WebGL Report reports that WebGL isn't supported, or if your GPU isn't showing up in the report, a driver update can often be the key to fixing the issue. Even if the GPU is detected, keeping your drivers up to date is generally recommended for best performance and compatibility, and updating drivers can often solve a lot of problems.
Sometimes, if you're using a system which hasn't really been used for gaming before, there are other driver updates you can install which can help improve overall system performance. If you know which motherboard your system has, check with the manufacturer's website to get the latest chipset and audio drivers.
If you're on a system with an integrated GPU in addition to a high-powered discrete GPU (often found in high-end laptops), the browser has the option of using either the low-power or the high-performance GPU. We make efforts to instruct the browser that we prefer the high-performance GPU to run our experiences, but sometimes it's necessary to make changes to the underlying system settings. On NVIDIA GPUs, the NVIDIA Control Panel software allows you to set the preferred power profile for different apps.
On some systems, your browser might decide that it doesn't like your GPU, and it blacklists it from using hardware acceleration. You can check to see if this is happening on your system and override it using the instructions here https://www.lifewire.com/hardware-acceleration-in-chrome-4125122