-
-
Save brunosimon/c15e7451a802fa8e34c0678620022f7d to your computer and use it in GitHub Desktop.
| # Unix (Terminal) | |
| open -a "Google Chrome" --args --disable-gpu-vsync --disable-frame-rate-limit | |
| # Windows (Command prompt) | |
| start chrome --args --disable-gpu-vsync --disable-frame-rate-limit |
what about chromebook
With --disable-frame-rate-limit WebGL games (like shellshockers) are unusable, and youtube videos play with 2 FPS. Without the switch everything is smooth but locked on 60 FPS.
I daresay the switch no longer does what it did a few month back...
--disable-gpu-vsync --- does nothing --max-gum-fps= --- is no longer heeded
(Tested with Chrome Version 108.0.5343.2 on Linux)
I had the same issue in shell shockers on brave and chrome when trying to disable frame limit. Do you think the same command would help on opera?
i find a intersting result,i input this to terminal,and the
n the FPS still is locked on 60,I feel strange,but when i move the browser to the screen where the terminal is located,it is working😂,then it locked 60FPS when i move the browser to another screen,so fully
(Tested with Chrome Version 121.0.6167.184 on Mac)
17813_1708169989.mp4
I’m on a MacBook (M2) and learned that Chrome must be fully killed before launching it with flags. I was following Lesson 46 from threejs-journey.com, and these are the steps that finally made the FPS counter appear.
Step 1. Made sure to kill all Chrome processes:
killall "Google Chrome" 2>/dev/null
Step 2. Launch Chrome with the correct flags (including the FPS counter):
open -na "Google Chrome" --args \
--disable-gpu-vsync \
--disable-frame-rate-limit \
--show-fps-counter
When I did I it I get only 60FPS why?