You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Best guess at the reason: the ultrawide code was carried over from “TOTK”. The 16:9 value it patches is probably not the one Ocarina of Time’s camera actually reads. The readme claims “the 3D keeps its shape”, but it doesn’t.
Follow-up with log evidence (5120x1440 monitor, ultrawide=1, in a 32:9 window):
[hos host] boot: aspect ratio 3.5556 in place of 1.7778
[hos host] vk: swapchain 2560x720
So the patch in host/hos_main.c is applied, but the camera doesn't use the patched value. Round objects (the moon in Kokiri Forest at night) come out about twice as wide as tall: the 16:9 picture is just stretched.
Note that PR #205 keeps stretching when Ultrawide is on, on purpose. Until the camera actually reads the new aspect, Ultrawide will still look stretched even after that PR is merged.
Thanks for the report! This is the same problem as #297, so I'm folding it into that issue to keep everything in one place. Please follow #297 (and add your log there if it shows something new).
Activity
turpcorp commentedon Nov 7, 2026
Exact same result on 32:9.
Best guess at the reason: the ultrawide code was carried over from “TOTK”. The 16:9 value it patches is probably not the one Ocarina of Time’s camera actually reads. The readme claims “the 3D keeps its shape”, but it doesn’t.
turpcorp commentedon Nov 7, 2026
Follow-up with log evidence (5120x1440 monitor,
ultrawide=1, in a 32:9 window):So the patch in
host/hos_main.cis applied, but the camera doesn't use the patched value. Round objects (the moon in Kokiri Forest at night) come out about twice as wide as tall: the 16:9 picture is just stretched.Note that PR #205 keeps stretching when Ultrawide is on, on purpose. Until the camera actually reads the new aspect, Ultrawide will still look stretched even after that PR is merged.
NotRexed commentedon Nov 7, 2026
Thanks for the report! This is the same problem as #297, so I'm folding it into that issue to keep everything in one place. Please follow #297 (and add your log there if it shows something new).