Render resolution setting in the Insert menu (1x / 2x / 3x scale) #777

Closed

opened 2026-11-08 20:56:44 +00:00 by EjianYT · 2 comments

EjianYT commented

2026-11-08 20:56:44 +00:00

(Migrated from github.com)

The idea

Add a "Render resolution" option to the Insert menu so players can raise the game's internal resolution as a
scale (1x = the console's native resolution, then 1.5x, 2x, 3x... up to 4K).

Right now the game always renders its scene at 1920x1080 and upscales it to a 2560x1440 picture, whatever the
monitor (as documented in nx2/oot_wide.py). On a 4K screen it never goes past that, so it looks soft. The existing
"Resolution" option only goes down (100%, 75%, 67%, 50%) within that 1080p scene.

The infrastructure seems to be there already: oot_wide.py patches the two size sites (picture {2560,1440} and
scene {1920,1080}) through hos_wide_out / hos_wide_scene, but only when the screen is wider than 16:9. Letting those
sizes grow at 16:9 too would give higher resolutions without new patches in the game's code.

Suggested choices (picture / scene, at 16:9):

Native: 2560x1440 / 1920x1080 (as today)
1440p scene: 2560x1440 / 2560x1440
4K: 3840x2160 / 2880x1620
4K native: 3840x2160 / 3840x2160

The option would set heights only; widths follow the picture's shape, so it works the same with Ultrawide on.
On a 3440x1440 monitor today the scene is 2576x1080 stretched to 3440x1440; a "1440p scene" choice would render
it natively at 3440x1440. A "Match monitor" choice (the picture's height = the screen's) would pick the right
size for any 16:9 or ultrawide display. Note that ultrawide multiplies the cost: 4K native at 21:9 is 5120x2160
(11 MP) versus 3840x2160 (8.3 MP) at 16:9.

Since the sizes are set at boot, it would need a restart, like Handheld profile.

(Generated with CLaude Code)

Anything else

No response

### The idea Add a "Render resolution" option to the Insert menu so players can raise the game's internal resolution as a scale (1x = the console's native resolution, then 1.5x, 2x, 3x... up to 4K). Right now the game always renders its scene at 1920x1080 and upscales it to a 2560x1440 picture, whatever the monitor (as documented in nx2/oot_wide.py). On a 4K screen it never goes past that, so it looks soft. The existing "Resolution" option only goes down (100%, 75%, 67%, 50%) within that 1080p scene. The infrastructure seems to be there already: oot_wide.py patches the two size sites (picture {2560,1440} and scene {1920,1080}) through hos_wide_out / hos_wide_scene, but only when the screen is wider than 16:9. Letting those sizes grow at 16:9 too would give higher resolutions without new patches in the game's code. Suggested choices (picture / scene, at 16:9): - Native: 2560x1440 / 1920x1080 (as today) - 1440p scene: 2560x1440 / 2560x1440 - 4K: 3840x2160 / 2880x1620 - 4K native: 3840x2160 / 3840x2160 The option would set heights only; widths follow the picture's shape, so it works the same with Ultrawide on. On a 3440x1440 monitor today the scene is 2576x1080 stretched to 3440x1440; a "1440p scene" choice would render it natively at 3440x1440. A "Match monitor" choice (the picture's height = the screen's) would pick the right size for any 16:9 or ultrawide display. Note that ultrawide multiplies the cost: 4K native at 21:9 is 5120x2160 (11 MP) versus 3840x2160 (8.3 MP) at 16:9. Since the sizes are set at boot, it would need a restart, like Handheld profile. (Generated with CLaude Code) ### Anything else _No response_

JulesThePooh commented

2026-11-08 22:16:01 +00:00

(Migrated from github.com)

This would be the best, waiting for something like this to really start the game !

NotRexed commented

2026-11-09 05:56:46 +00:00

(Migrated from github.com)

Thanks for the idea. Feature requests are now collected in #1007, which lists this one with a link back here, so closing it in favour of that list (this is not a decision against the idea). v2.0.6 adds an Output resolution option (2048x1152, 2560x1440, 3840x2160; PR #849), which covers part of this.