DLSS: fullbright/emissive textures blur at distance (missing upscaler mip bias?) #1386

Open
opened 2026-11-02 18:15:41 +00:00 by sky_line · 0 comments
Owner

Problem

With DLSS on, some textures blur smoothly as the camera moves away and only look sharp up close. Other textures at the same distance stay sharp. It shows on fullbright and emissive surfaces, and was seen on an alpha-masked texture in Baltimare. The change is continuous with distance, not stepwise, so this is mip level selection while drawing, not texture loading. It's most visible at low render scales (seen with DLSS Ultra Performance + Ray Reconstruction, 1/3 render scale). This is likely part of the "textures stay low-res" reports (see #1314).

Likely cause (unverified)

While the upscaler is jittering, material sampling gets a mip bias of RenderVKTAAMipBias + log2(render height / display height). At 1/3 scale that's about -1.6, which keeps textures at display-resolution detail. taaLodBias() in indra/vkclean/shaders/clean_frame_info.glsl returns 0 when the instance has flag bit 8u set, or when noTemporalFace() is true. In clean_rt_surface.glsl, material flag 8u gates the emissive texture. If fullbright/emissive faces carry that bit, or are drawn on a no-temporal path, they get no upscaler mip bias and sample mips about 1.6 levels coarser than everything else at 1/3 scale.

To check

  • What instance flag 8u means, and whether fullbright/emissive (and masked) faces set it.
  • Every path that writes base or emissive colour (prepass mask, lit, blend, RT surface, shadow) applies the same bias.
  • If those faces deliberately skip temporal accumulation, they still need the render-scale part of the bias (log2 of the render/display ratio), even if they skip the TAA sharpening part.
  • Residency keeps the biased mips for these faces (73a7649957 covers DLSS demand for normal materials).

Done when

At DLSS Ultra Performance, a fullbright/emissive texture and an ordinary texture at the same distance are equally sharp, and both match native resolution.

## Problem With DLSS on, some textures blur smoothly as the camera moves away and only look sharp up close. Other textures at the same distance stay sharp. It shows on fullbright and emissive surfaces, and was seen on an alpha-masked texture in Baltimare. The change is continuous with distance, not stepwise, so this is mip level selection while drawing, not texture loading. It's most visible at low render scales (seen with DLSS Ultra Performance + Ray Reconstruction, 1/3 render scale). This is likely part of the "textures stay low-res" reports (see #1314). ## Likely cause (unverified) While the upscaler is jittering, material sampling gets a mip bias of `RenderVKTAAMipBias` + log2(render height / display height). At 1/3 scale that's about -1.6, which keeps textures at display-resolution detail. `taaLodBias()` in `indra/vkclean/shaders/clean_frame_info.glsl` returns 0 when the instance has flag bit `8u` set, or when `noTemporalFace()` is true. In `clean_rt_surface.glsl`, material flag `8u` gates the emissive texture. If fullbright/emissive faces carry that bit, or are drawn on a no-temporal path, they get **no** upscaler mip bias and sample mips about 1.6 levels coarser than everything else at 1/3 scale. ## To check - What instance flag `8u` means, and whether fullbright/emissive (and masked) faces set it. - Every path that writes base or emissive colour (prepass mask, lit, blend, RT surface, shadow) applies the same bias. - If those faces deliberately skip temporal accumulation, they still need the render-scale part of the bias (log2 of the render/display ratio), even if they skip the TAA sharpening part. - Residency keeps the biased mips for these faces (73a7649957 covers DLSS demand for normal materials). ## Done when At DLSS Ultra Performance, a fullbright/emissive texture and an ordinary texture at the same distance are equally sharp, and both match native resolution.
sky_line added this to the Slipstream project 2026-11-02 18:15:41 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sky_line/Slipstream#1386
No description provided.