Difference between revisions of "Useful Chrome Flags"
From Verge3D Wiki
Jump to navigationJump to search| Line 13: | Line 13: | ||
Specify this flag to simulate running your app on older devices with missing WebGL 2.0 support. | Specify this flag to simulate running your app on older devices with missing WebGL 2.0 support. | ||
== Disable 60 FPS limit == | |||
By default, web browsers limit rendering framerate for WebGL apps. Specify the following flags to disable this limit: | |||
<code>google-chrome --disable-gpu-vsync --disable-frame-rate-limit</code> | |||
== Disable GPU hacks == | == Disable GPU hacks == | ||
<code>google-chrome --disable-gpu-driver-bug-workarounds</code> | <code>google-chrome --disable-gpu-driver-bug-workarounds</code> | ||
Revision as of 12:59, 2 August 2021
See this page to find out how to specify these flags.
Disable WebGL (both WebGL 1.0 and WebGL 2.0)
google-chrome --disable-webgl
Run Chrome with this flag to test that your app response properly to missing WebGL capabilities on the user device.
Disable WebGL 2.0
google-chrome --disable-webgl2
Specify this flag to simulate running your app on older devices with missing WebGL 2.0 support.
Disable 60 FPS limit
By default, web browsers limit rendering framerate for WebGL apps. Specify the following flags to disable this limit:
google-chrome --disable-gpu-vsync --disable-frame-rate-limit
Disable GPU hacks
google-chrome --disable-gpu-driver-bug-workarounds
