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/<version>/romfs-patches, the folder the game loads at 16:9; the default is
now romfs-patches[-<prompts>]-<w>x<h>[-hud<a>x<b>], 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 <noreply@anthropic.com>
This commit is contained in:
ProSepandClaude Opus 5.5 authored and Marjaperse committed 2026-11-17 03:29:07 +02:00
1 parent 757ee0b2bf
commit bf6ebeafa5
1 file changed
+2 -2
+2 -2
View File
@@ -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-<w>x<h>-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-<w>x<h>-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