-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Add a max FPS limit control to the options menu #43626
Copy link
Copy link
Open
Labels
A: AccessibilityArea: Accessibility settings and features.Area: Accessibility settings and features.A: PreferencesArea: Player preferences and options.Area: Player preferences and options.D3: LowDifficulty: Some codebase knowledge required.Difficulty: Some codebase knowledge required.P3: StandardPriority: Default priority for repository items.Priority: Default priority for repository items.T: UI / UX ImprovementType: UI and player facing interactive graphical interfacesType: UI and player facing interactive graphical interfaces
Metadata
Metadata
Assignees
Labels
A: AccessibilityArea: Accessibility settings and features.Area: Accessibility settings and features.A: PreferencesArea: Player preferences and options.Area: Player preferences and options.D3: LowDifficulty: Some codebase knowledge required.Difficulty: Some codebase knowledge required.P3: StandardPriority: Default priority for repository items.Priority: Default priority for repository items.T: UI / UX ImprovementType: UI and player facing interactive graphical interfacesType: UI and player facing interactive graphical interfaces
What version did the issue occur in?
wizards/b9a97b9
Description
Apparently some GPUs don't understand the concept of moderation without the game you're playing telling them there's a frame-per-second limit. Mine are apparently in this category.
With Vsync turned off and in full-screen mode my GPUs push themselves into their non-overclocked limit and in doing so spiking their energy draw, heat to about 70 Celsius, and make a massive amount of hellish noise.
I strongly request the addition of an alternative frame limit should Vsync be disabled as this can and will go so far as to physically damage the computers of the unaware and unprepared.
(Some people play on toasters and they shouldn't suffer this for doing so)
Reproduction
Additional Context
I only realized this was a universal thing to all servers recently when I turned Vsync off and went to test if it was just the one.
On the plus side; my computer took it like a champ apparently. It seems like there's no damage aside from possibly my hearing.
Apparently there was a post on Discord about this exact issue back in 2024 that just never made its way to Git.
There may have been similar reports of this. If there are then I couldn't find them; I am not very familiar with Github in general.
Either way, since then everyone that has the issue has collectively decided to just use Vsync.