You signed in with another tab or window. Reload to refresh your session.You signe
8000
d 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
{{ message }}
Repository navigation
Feature request: MetalFX Native AA / TAA at native ultrawide resolutions (reflections shimmer at 21:9) #89
Feature request: temporal anti-aliasing (MetalFX Native AA / TAA) at native ultrawide resolutions
Problem. With Ultrawide or 16:10 on, the launcher and the GPU library switch upscaling off ("Ultrawide runs at the selected native resolution, with upscaling off"). That leaves only the game's own post-process AA, so reflective surfaces (wet stone, metal, glass) shimmer and crawl whenever the camera moves. At 16:9, MetalFX Native AA cleans this up; at 21:9 there's no way to get it.
My setup: Apple M3 Max (30-core GPU, 36 GB), external 2560×1080 @ 144 Hz (set to 120 Hz), 0.5.8, native 2560×1080 · 21:9, full screen, game AA on, texture compression on. The benchmark (#88) has the GPU at 13.5 ms a frame at 1080p native, so a native-size AA pass at 2560×1080 has room in the 16.7 ms budget.
Where it's switched off (current master):
gpu/shim/bbport_settings.cppLoad(): when BB_ULTRAWIDE_RES is one of the native wide sizes, it sets upscaler = UpscalerOff, preset = NativeAA, live_resolution = 0 ("Native wide patches own scene/UI dimensions. Disable generic host resizing.").
scripts/launch_settings.shbb_native_ultrawide: exports BB_UPSCALER=none ("The complete game patch owns scene/UI sizes. Do not resize/composite it again.").
launcher/Model/GameSettings.swift: writes upscaler=off when ultrawide is on; LauncherView disables the picker.
Why it isn't a one-line change:TemporalUpscaler (vk_temporal_upscaler.cpp) takes its target size from the 16:9 output list (OutputWidths/OutputHeights, output_res) and composites the UI separately. With the wide patch, the game already draws scene and HUD at the wide size, so a straight enable would size targets wrong and/or composite the HUD twice. The rasterizer already observes the real scene depth size in ultrawide sessions (vk_rasterizer.cpp, "Native ultrawide: observed scene depth …"), which could provide the target size.
Proposal: a native-size, AA-only mode for ultrawide sessions:
allow MetalFX (and TAA) with preset Native AA only (render = output = the wide size, no rescaling);
size the upscaler's targets from the ultrawide size (BbSettings::OutputSize() already returns it) instead of the 16:9 list;
keep the game-drawn HUD as is (no second UI composite), the same way the wide session works today;
check that subpixel jitter and the camera/object motion vectors are right with Kyo's wider projection (jitter in pixels of the wide target);
launcher: in ultrawide mode, offer Off / MetalFX Native AA / TAA (no scaling presets).
I'm happy to test any build on this 2560×1080 display, and to work on a PR for it once I have the full build environment set up.
A related finding from #115: above 1920×1080 the game's own anti-aliasing doesn't reach the picture at all, because the game's buffers stay at 1080p there. At native ultrawide sizes that's true too, which is likely part of the shimmer you see. Anti-aliasing at native size for both cases is in the backlog and planned after the 0.6 frame-generation release. Keeping this open.
Activity
Wooloomooloo2 commentedon Oct 31, 2026
A related finding from #115: above 1920×1080 the game's own anti-aliasing doesn't reach the picture at all, because the game's buffers stay at 1080p there. At native ultrawide sizes that's true too, which is likely part of the shimmer you see. Anti-aliasing at native size for both cases is in the backlog and planned after the 0.6 frame-generation release. Keeping this open.