Home > Video > In-meeting controls > Virtual background or Presentation mode not supported on your device

Virtual background or Presentation mode not supported on your device

Last updated on August 5, 2022

This article explains how to troubleshoot when RingCentral Video Virtual background or Presentation mode isn’t supported on your device.

Issue

When you try to use Virtual background or Presentation mode in the RingCentral app for web, you may see a message that the feature isn’t supported on your device without browser hardware acceleration.

Resolution

Virtual background and Presentation mode require hardware acceleration to be turned on in your browser. If hardware acceleration is already turned on, your display drivers may need to be updated to support WebGL.

Note: RingCentral Video only supports Google Chrome and Microsoft Edge.

Turning on hardware acceleration in Google Chrome

Click the three-dot icon at the top right of your browser window.
Click Settings.

Click System in the left navigation bar.

Make sure Use hardware acceleration when available is turned on. If hardware acceleration is off, click the toggle to turn it on. Click Relaunch for the setting to take effect.

Turning on hardware acceleration in Microsoft Edge

Click the three-dot icon at the top right of your browser window.
Click Settings.

Click System and Performance in the left navigation bar.
Make sure Use hardware acceleration when available is turned on. If hardware acceleration is off, click the toggle to turn it on. Click Restart for the setting to take effect.

Hardware acceleration on, but still not working?

If hardware acceleration is turned on in your browser but you're still seeing the error message when trying to use Virtual background or Presentation mode, your display drivers may need to be updated to support WebGL.

To test if WebGL is supported by your system, visit: https://get.webgl.org/.
- If you see a spinning cube, your display driver supports WebGL.
- If you don’t see a spinning cube, try updating your display driver (refer to the manufacturer’s support site for info), and then retest WebGL.