From bf6ebeafa599fa861f757b2c63ca0a1a0a66c3e3 Mon Sep 17 00:00:00 2001 From: ProSep <9l0mhe7e@prosep.anonaddy.me> Date: Thu, 5 Nov 2026 23:14:39 +0100 Subject: [PATCH] Name make_romfs_patches.py's default output after the size, so an --aspect run no longer replaces the 16:9 romfs-patches Without --out, --aspect wrote into build//romfs-patches, the folder the game loads at 16:9; the default is now romfs-patches[-]-x[-hudx], the name runtime/romfs.c overlay_init looks for. totk.ini.example says which sizes get the 21:9 HUD layout. Co-Authored-By: Claude Opus 5.5 --- totk.ini.example | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/totk.ini.example b/totk.ini.example index 7c14509d..d182f7da 100644 --- a/totk.ini.example +++ b/totk.ini.example @@ -203,8 +203,8 @@ # HUD width on a game resolution wider than 16:9: full, the default, puts the HUD at the screen's left and right edges; # 21:9 keeps it within the middle 21:9 of the screen and 16:9 within the middle 16:9 (the game's own HUD), so the # corners of a 32:9 screen stay clear. A cap not narrower than the screen is the same as full, and a 16:9 or taller -# screen ignores it. The installer prepares these layouts for the sizes in the list above (romfs-patches-x-hud21x9 -# and -hud16x9); without the folder the HUD stays at the edges. Read at start. +# screen ignores it. The installer prepares 16:9 for every size above wider than 16:9 and 21:9 for the 32:9 ones +# (romfs-patches-x-hud16x9 and -hud21x9); without the folder the HUD stays at the edges. Read at start. # hud_width = full # 3D render scale: the scene's size relative to the game resolution, game (5/6, the game's own 1600x900 at 1080p) or # a percentage (25 to 400); above 100 supersamples the scene (anti-aliasing). The scene stays within 8192 pixels a side