Difference between revisions of "Useful Chrome Flags"
From Verge3D Wiki
Jump to navigationJump to search (test) |
m |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Browsers]] | |||
See [https://www.chromium.org/developers/how-tos/run-chromium-with-flags this page] to find out how to specify these flags. | |||
== Disable WebGL (both WebGL 1.0 and WebGL 2.0) == | |||
Run Chrome with this flag to test that your app response properly to missing WebGL capabilities on the user device. | |||
<code>google-chrome --disable-webgl</code> | |||
== Disable WebGL 2.0 == | |||
Specify this flag to simulate running your app on older devices with missing WebGL 2.0 support. | |||
<code>google-chrome --disable-webgl2</code> | |||
== Disable 60 FPS limit == | |||
By default, web browsers limit rendering framerate for WebGL apps. Specify the following flags to disable such limit: | |||
<code>google-chrome --disable-gpu-vsync --disable-frame-rate-limit</code> | |||
== Disable GPU hacks == | |||
<code>google-chrome --disable-gpu-driver-bug-workarounds</code> | |||
== Enable WebGPU on Linux == | |||
<code>google-chrome --enable-unsafe-webgpu --enable-features=Vulkan</code> | |||
Latest revision as of 13:51, 8 February 2023
See this page to find out how to specify these flags.
Disable WebGL (both WebGL 1.0 and WebGL 2.0)
Run Chrome with this flag to test that your app response properly to missing WebGL capabilities on the user device.
google-chrome --disable-webgl
Disable WebGL 2.0
Specify this flag to simulate running your app on older devices with missing WebGL 2.0 support.
google-chrome --disable-webgl2
Disable 60 FPS limit
By default, web browsers limit rendering framerate for WebGL apps. Specify the following flags to disable such limit:
google-chrome --disable-gpu-vsync --disable-frame-rate-limit
Disable GPU hacks
google-chrome --disable-gpu-driver-bug-workarounds
Enable WebGPU on Linux
google-chrome --enable-unsafe-webgpu --enable-features=Vulkan
