| magenta, brown or stale textures; caves or sky wrong |
the CPU filled the texture and the GPU never got the upload (no flush on the console) |
frame dump: the texture's upload count and mirror state in passes.txt |
| rain shows only its splashes on the ground, no falling drops; waterfall splashes and mist blink |
a GPU write-back copies a whole range over particle records the CPU spawned in it (vk_memory.c: the write-back merge, and with shadow = 1 the shadow's pending ranges) |
a run with TOTK_WB_MERGE=0 or TOTK_SHADOW=0 against one without |
| effects that never happen: cut grass stays up, fire does not spread |
the CPU reads a GPU-rendered texture that was never written back |
which texture the game reads after its fence; write-back of that target |
| black scene, black dialog background or loading map |
deferred binds read at record time; a 3D target rejected; a texture compare ignoring the channel mapping |
frame dump: the first pass whose target goes black |
| lime silhouettes, rectangles in the sky |
a target outside the shader's output map overwritten instead of kept |
dump: the target's previous contents versus after the pass |
| dark or magenta 16x16 blocks, missing characters |
a pass samples its own render targets (G-buffer feedback) |
feedback-loop layout and barriers on that pass |
| tile rectangles, wrong data in tiles |
storage buffers bound in the wrong slot order |
passes.txt: storage buffers with their c0 slots |
| streaks on cliffs, characters stretched into streaks |
primitive restart ignored; integer vertex inputs against a float format |
validation run; the draw's topology and vertex formats in the dump |
huge stretched slabs over the ground, a ceiling over Link, the ground up to his chest, from the load on for the whole session (the Depths); some runs only, most at a high frame rate; with sync_ahead, replay_workers and a discrete GPU |
a VRAM mirror copied from the shadow before the CPU's write reached it, and kept the old vertices while marked synced (fixed: vk_memory.c vk_mem_mirror_seal) |
TOTK_MEMORY=verify mismatch lines; memory = import or replay_workers = 0 makes it go; fps_limit = 144 shows it in most runs |
| garbage geometry on title or load screens |
8-bit indices widened on the CPU before a copy in the same submission wrote them |
whether a copy to the index buffer precedes the draw in one submission |
| black tiles, masks not cleared |
clears with a partial channel or stencil mask skipped or done in full |
passes.txt clears and their masks |
| garbage in feedback effects at first use |
new GPU-only images start undefined; the console starts them at zero |
clear on creation and compare |
| empty clouds or fog for the whole session |
a one-shot draw skipped while its pipeline built, never drawn again |
perf: slow frame lines naming pipeline waits; the draw's first frame |
| fog that never parts, flicker in tile rows |
driver constants (c0: dispatch size, point size, base instance) not filled |
the c0 contents the translator expects for that stage |
| no sun shadows, wrong lighting |
unwritten vertex outputs read as zero instead of (0,0,0,1) |
the shader's output map |
| one flat ambient colour |
a 1-layer 2D array sampled as 2D |
the view type the shader expects |
| upside-down text |
lower-left window origin |
origin mode in the log |
| puddles and still water flicker: the reflection turns on and off in patches from frame to frame while the camera stands still, more with DLAA |
the game's water volume mask: a volume's top face lies on the water surface and is tested LEQUAL against a depth rebuilt at quarter size, so rounding and the camera's sub-millimetre motion decide it (fixed: vk_pipeline.c vk_pipeline_volume_bias gives such draws a depth bias toward the viewer) |
a --capture run: the puddle's brightness swing (capture.py frames, a region's mean) with TOTK_VOLUME_MASK_BIAS=0 and without; in a frame dump, the quarter-size mask after the volume draw changes from frame to frame |
| with DLAA on, water seen at a low angle (ponds, streams) flickers in large patches with a period of about three frames, between the reflection of the trees and that of the sky; without DLAA it is still |
the jitter moved the viewport of the scene's draws but not the game's camera, so its full-screen passes rebuilt positions half a pixel off the surface and its screen-space reflections flipped between hit and miss with the jitter's phase (fixed on 1.4.3: vk_dlaa.c puts the jitter into the camera blocks where the game copies its matrices, vk_dlaa_camera_copied) |
TOTK_DLAA_CAM_JITTER=0 brings the viewport jitter back; a --capture run: the region's brightness swing with DLAA, against TOTK_DLAA_JITTER=0 |
| with DLAA on, the world behind the inventory smears into horizontal streaks on the right half, from the second time the inventory is opened (when Link's model is drawn there) |
the camera jitter's read-back took the inventory camera's own off-centre projection (P[0][2] about -0.6) for a jitter and gave DLSS an offset of about 1152 pixels (fixed: vk_dlaa.c cam_offset takes only an offset it gave that block) |
TOTK_DLAA_CAM_JITTER=0 makes it go; a --capture run over the opened inventory: the background's horizontal gradient against its vertical one |
| with DLAA/DLSS on, large distant blocks behind the fog (the Depths) turn darker or lighter for a frame while the camera moves |
DLSS created with AutoExposure estimated the exposure of the dark scene itself, and the estimate moved from frame to frame (fixed with dlss_fixed_exposure = 1: vk_dlaa.c evaluate creates the feature without it) |
a flat fogged patch in capture.py frames: one value without DLAA, jumps with it |
| flicker or a texture swapped with a similar one |
the newest texture picked at shared storage instead of the one with the matching view |
texture lookup by id in the dump |
| with DLAA on, dust and small particles in fog (shrines) vanish, smear or behave oddly; the fog looks processed |
DLSS ran at the bloom, after the fog and the particles, which have no motion vectors or jitter of their own (fixed: vk_dlaa.c effects_point runs DLSS at the first pass into the light target after the lighting, and the effects go over its picture) |
dlaa_effects_after = 0 (Screen tab) brings the old point back; the count "before the effects" in the dlaa: log line against the frames anti-aliased |
| with DLAA on, the picture flickers from frame to frame: a little outdoors; the whole scene in a fogged shrine with an ability's targeting view (Ultrahand) open, where the fog also goes back under DLSS |
DLSS ran before some effects in one frame and after them in the next: their order changes from frame to frame (the yard's half-size effects pass is in some frames only; the ability highlight, drawn into the light target with a D16 depth of its own, comes before or after the fog layer), and a rule that waited for one of them or took any D16 pass for the lighting followed it (fixed: vk_dlaa.c effects_point knows the lighting by its depth and runs DLSS right after it) |
the dlaa: log line: "before the effects" must equal the frames anti-aliased in the world; a log of the passes into the light target per frame |