My config: Brave 1.77.101 with Chrome 135.0.7049.115, Windows 10 Home x64 22H2
I was reading about a user having frame rate problems when using Brave. The suggestion was to use the --disable-frame-rate-limit command line argument. Wow, what a huge difference in framerate when testing at vsynctester.com. Why isn’t this the default?
I went into brave://flags to change throttle-main-thread-to-60hz, but the default is Disabled which means there is already no 60hz throttle. The --disable-frame-rate-limit command-line argument really needs to be a user configurable setting, or a flag, to remain persistent across all web browser sessions.
Yes, I can edit a shortcut that loads Brave to add the command-line argument, but that is ineffective when clicking on a hyperlink in an e-mail, document, or elsewhere. When Brave is configured as the default web browser, there are many more ways to load it than using a shortcut. Plus, only when using the shortcut will the command argument get used. All other methods of starting Brave will NOT have this setting. This command-line arg really needs to be replaced with a flag or setting that is stored as a preference, and will always be enabled regardless of how Brave got started.
Are there known issues when using --disable-frame-rate-limit?