Last active
December 23, 2025 19:25
-
-
Save brunosimon/c15e7451a802fa8e34c0678620022f7d to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # 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 |
Linux
google-chrome --args --disable-gpu-vsync --disable-frame-rate-limit
https://frameratetest.com/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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/nullStep 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