config: use linear upscaling except on classic guests - #7845
Merged
Conversation
The nearest-neighbour default (ba5f7f7, #3371) was chosen for low-resolution guests, where linear washes out already-chunky text. It is the wrong choice everywhere else: a modern guest rarely upscales by an integer ratio, so nearest duplicates source pixels unevenly and looks blocky rather than sharp -- the complaint behind #6209 and #6572. Default to linear and let the wizard select nearest for the guests the original change was about: Classic Mac OS, Windows 7 and below, and any OS configured for legacy hardware. Legacy hardware is checked on its own rather than folded into the Windows case so that choosing a legacy machine opts in under any OS, and because the summary page can enable it after the Windows page has already latched isWindows10OrHigher. Existing VMs are unaffected: upscalingFilter is a required coding key, so a saved configuration always carries its own value. The UTM 2.x migration path is likewise unchanged, since an absent displayUpscaler already defaulted to linear. Assisted-by: Claude:claude-opus-5
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The nearest-neighbour upscaling default (#3371, ba5f7f7, shipped in v3.0.1) was chosen for low-resolution guests, where linear washes out already-chunky text. It is the wrong choice everywhere else: a modern guest rarely upscales by an integer ratio, so nearest duplicates source pixels unevenly and the result looks blocky rather than sharp.
This defaults
upscalingFilterto linear, and has the VM wizard select nearest for the guests the original change was about: Classic Mac OS, Windows 7 and below, and any OS configured for legacy hardware. Legacy hardware is checked on its own rather than folded into the Windows case so that choosing a legacy machine opts in under any OS, and because the summary page can enable it after the Windows page has already latchedisWindows10OrHigher.Existing VMs are unaffected:
upscalingFilteris a required coding key, so a saved configuration always carries its own value. The UTM 2.x migration path is likewise unchanged, since an absentdisplayUpscaleralready defaulted to linear.Testing: Tested by a human on macOS 15.6 (24G84), Mac16,11 — Apple M4 Pro. The author acknowledges that this change has been tested and/or reviewed by a human in accordance with UTM's AI contribution guidelines.