Reimplement CPU Affinity #4110
Merged
Reimplement CPU Affinity #4110
Conversation
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
Member
|
The exact implementation in this PR was requested, because to be clear, certain system configurations (thought to be CPU) it gives heavy input lag and general system instability if using CPU affinity 0. An example of this are certain modern AMD Ryzen (Mobile) processors. Thanks! |
Member
|
Fixes: #4119 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Better version of #4096
Resolved #4088
Added information that the setting is experimental when hovering over it
Added a warning when enabling the setting, indicating that it is experimental
The setting is now disabled by default
I moved the checkbox for saving screenshots in userfiles to the multiplayer tab (imo, this is a more appropriate place for this setting than the advanced tab). The advanced tab no longer has space, which caused the informational text at the bottom of the window (the one that appears when hovering over various elements) to be cut off and not visible.