#Is it safe to enable webgl in chrome drivers

Type chrome://gpu in the address bar and press Enter.

To inspect the status of WebGL for Chrome: In any event, your company policy may control what you can and cannot do and you may need, or be required to seek, assistance from your IT professional. Care should be taken when changing any settings to your browser and only proceed if you are comfortable with making such changes. Consult supporting information for your browser. Be aware that settings and elements therein can change at any time and may be labelled differently than stated here. The following sections provide troubleshooting information with respect to checking WebGL (or WebGL 2.0) and enabling hardware acceleration on some of the popular browsers supported by Altium 365 Web Viewer technology. It is recommended to always have the latest version of a supported browser installed. Supported browsers (and their minimum supported version) are listed below.

#Is it safe to enable webgl in chrome drivers

That the video drivers for your computer are up to date (including drivers for dedicated graphics cards).

If your computer has dual graphics cards - integrated and dedicated - then it is suggested to utilize the dedicated GPU over the integrated GPU.

This will typically result in a far smoother viewing experience, since 3D rendering is performed by the dedicated video card (GPU) where one exists, rather than the CPU of the computer itself.

That the option to use 'Hardware Acceleration' is enabled for your browser where available.

That WebGL (or WebGL 2.0) is enabled for it.

The latest version of a supported Web Browser installed.To ensure a smooth experience with Altium 365 Viewer and the Web Viewer interface within the Altium 365 platform itself, ensure you have: Enabling Hardware Acceleration for Opera.Enabling Hardware Acceleration for Edge.Enabling Hardware Acceleration for FireFox.Enabling Hardware Acceleration for Chrome.

Checking that WebGL & Hardware Acceleration is Enabled for Your Browser.Note: You might see the WebGL is not supported message in some cases or it might display the “ WebGL Hit a Snag” error after enabling it on Chrome.

When Google Chrome starts up, WebGL will be enabled and web applications will be able to successfully access the WebGL API.

Once done, click on Relaunch Now to restart Google Chrome so that the changes you have made may be applied.

Note: If the Disable WebGL option is already disabled (you’ll know because there will be an Enable button under the option instead of a Disable button), WebGL is already turned on in your instance. That being the case, if this option is enabled, all you need to do in order to turn WebGL on is to disable this option by clicking on Disable. When this specific option is enabled, it prevents web applications from accessing the WebGL API, whereas web applications have complete and unrestricted access to the WebGL API while this option is disabled.

Scroll down the list of Experiments and locate the Experiment titled Disable WebGL.

Doing so will take you to the Experiments

Type chrome://flags/ into the URL field, and press Enter.