Game: the pedestal platform's rim is in the picture on one frame in three in the scene after pulling the Master Sword (map SageRoom, 60 fps, DLSS): a 20 Hz flicker #1942

Open
opened 2026-11-21 00:23:47 +00:00 by magicbeanenjoyerguyperson · 2 comments

Longshot version

v3.0.0-own (source 192e6b3a): my own build of the v3.0.0 tag with a few changes of my own

Channel

Built from source

What kind of problem

Graphics (missing, black or wrong-coloured things, lighting, flicker)

What happened

What I saw. In the scene after child Link pulls the Master Sword (the blue room with the pedestal's platform, then Ganondorf), a part of the picture flickers fast. Going through my recording frame by frame: the dark rim around the pedestal's platform is in the picture on one frame in three and missing on the two frames between. The scene runs at 60 fps, so the rim comes back 20 times a second. It goes on for as long as the platform is in view, which is the first 13 seconds of cutscene_1_flicker.mp4: first as a dark band at the bottom left behind Link's shield, then around the whole platform in the shots with Ganondorf. cutscene-flicker-three-frames.jpg shows three frames in a row at two moments of the clip.

Measured on the clip, in an area of 120 by 120 pixels at the bottom left from 1.0 to 5.5 s: 71 of the 270 frames are the darker kind (a mean brightness of about 61 against 106). Of the 70 gaps between them, 60 are 3 frames and 10 are 6 frames.

I can't tell which of the two pictures is the right one, the platform with its rim or without.

In the next scene in the same map (adult Link and Rauru, cutscene_2_flicker.mp4) nothing changes on that beat, also where the platform is seen from above. There, small dark specks blink on Rauru's collar and sleeve, without a fixed beat. That may be a different thing. I mention it because it is the same map.

What I expected. A steady picture.

Steps. As child Link with the three Spiritual Stones and the Ocarina of Time, open the Door of Time and pull the Master Sword. Watch the edge of the platform in the scene that follows. The scene with Rauru comes right after it.

What my log of that run says (cutscene-flicker-important-lines.txt has the lines, each with its line number):

  • The game's name for the map is SageRoom: map: SageRoom (child), later map: SageRoom (adult).
  • A steady 60 fps through both scenes: 59.9 to 60.1 fps in every count after the first of each scene, about 97% of the presents 15.5 to 17.8 ms after the one before, vi: real-time step on: ratio 1.002, game's frame rate 60.
  • DLSS drew every frame: NVIDIA DLSS: 600 frames drawn (or more) in every status line of both scenes. Frame generation is off.
  • No draw was skipped: (0 skipped) in every count. Draws left out because a shader or pipeline was not ready: 2.0 a frame in the first count after the map came in (three quick pipeline (no optimizer) lines and one pipeline from the caches for a draw ahead of its build stand right there), then 0.0 draws left out (not ready) in every count of that scene. In the scene with Rauru: 0.2 to 0.4 a frame in three counts near its end, 0.0 in the others.
  • The hidden-mesh rule left nothing out in these scenes: it writes an upscaler: faded: frames ... line for every stretch in which it does, and there is none between the sword and the Market.
  • The game's barrier counts a frame stay level through the scene (0x11: 41.0; 0x12: 68.5; ...), so I see no pass that comes only every third frame.

So the log names no cause. It only says what it is not.

What I have not tested.

  • I have seen it once. Both scenes play once in a save, and I have no save from before them, so I can't run it again with RX_VK_FLASH=1 or with other settings.
  • Not tried: another upscaler or none, DLAA, another frame rate, frame generation.
  • This is my own build of the v3.0.0 tag. My changes are listed below. One of them holds the cap at 60 while the game plays a scene of its own (my cap is 240 otherwise), so the scene ran at 60 as it does with the default cap, but it got there by my change. I have not run the project's release build or a nightly.

Related. I found no report of this. #1760 is a flicker in another cutscene (pale grass for about a second, Steam Deck) and #601 is the sun's shadows on Link at the Temple of Time's entrance. Going by their descriptions both are something else.

Found with an AI assistant (Claude), which went through my clips frame by frame and read my log. I played and recorded everything myself, on one PC.

Where in the game

The scene after child Link pulls the Master Sword (the game's map SageRoom), and the scene with Rauru right after it

How often

Once so far

Graphics card and driver version

RTX 5090, NVIDIA 621.24

CPU, RAM and operating system

Ryzen 9 9950X3D, 64 GB, Windows 11

Changes from the defaults

  • Graphics: Output resolution 3840x2160, Fullscreen on. Upscaler NVIDIA DLSS, DLSS model Transformer 2 (M), Render resolution Quality (2560x1440), Sharpness 80, DLAA before the bloom on. Frame generation off. Game frame rate cap 240, NVIDIA Reflex On + Boost, V-Sync off. HDR Expanded, paper white 280 nits. Shadow resolution Highest. Debug tab: Sampler cache on. FPS counter on.
  • Gameplay: Field of view 120.
  • This is my own build from source (the v3.0.0 tag) with a few changes of my own: button mapping and prompt options, hold to quit, a hold at 60 fps for the game's scenes (on during both scenes, by the log: vi: hold 60: on, the cap of 240 set aside), one more case of the hidden-mesh rule (#1529), and #1814 ahead of the release that has it.
  • longshot_env.txt: HOS_DISCORD=0 and HOS_CRASH_WATCH=0.
  • No ReShade, shader-cache tool or injector. Xbox Game Bar enabled. The clips were recorded with OBS.

longshot_log.txt

Neither file names my Windows account.

  • cutscene-flicker-important-lines.txt: start here. The lines that matter, with a short note on each group, and the numbers measured on the clip.
  • longshot_log-cutscene-part.txt: the log of that run, cut down to its start (lines 1 to 320 and 2940 to 2995) and every line from the sword to the Market (lines 214990 to 225070). The lines are as the game wrote them; the three lines in square brackets that say where lines are left out are mine. The whole log is 45 MB (a long play); I can attach it if it helps.

Screenshots or video

Recorded at 3840x2160 and 60 frames a second, the FPS counter top right.

  • cutscene-flicker-three-frames.jpg: three frames in a row from the first clip, at 3.0 s and at 10.0 s. The middle frame of each row has the rim, the frames before and after it do not.
  • cutscene_1_flicker.mp4 (20.6 s): the scene after the sword is pulled. The flicker is there from the start to about 13 s. Step through it frame by frame to see the beat.
  • cutscene_2_flicker.mp4 (8.2 s): the scene with Rauru. The specks are on his collar, left of the medallion, and on his sleeve.

Before you send it

  • The problem is still there on the newest release or nightly.
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### Longshot version v3.0.0-own (source 192e6b3a): my own build of the v3.0.0 tag with a few changes of my own ### Channel Built from source ### What kind of problem Graphics (missing, black or wrong-coloured things, lighting, flicker) ### What happened **What I saw.** In the scene after child Link pulls the Master Sword (the blue room with the pedestal's platform, then Ganondorf), a part of the picture flickers fast. Going through my recording frame by frame: the dark rim around the pedestal's platform is in the picture on one frame in three and missing on the two frames between. The scene runs at 60 fps, so the rim comes back 20 times a second. It goes on for as long as the platform is in view, which is the first 13 seconds of `cutscene_1_flicker.mp4`: first as a dark band at the bottom left behind Link's shield, then around the whole platform in the shots with Ganondorf. `cutscene-flicker-three-frames.jpg` shows three frames in a row at two moments of the clip. Measured on the clip, in an area of 120 by 120 pixels at the bottom left from 1.0 to 5.5 s: 71 of the 270 frames are the darker kind (a mean brightness of about 61 against 106). Of the 70 gaps between them, 60 are 3 frames and 10 are 6 frames. I can't tell which of the two pictures is the right one, the platform with its rim or without. In the next scene in the same map (adult Link and Rauru, `cutscene_2_flicker.mp4`) nothing changes on that beat, also where the platform is seen from above. There, small dark specks blink on Rauru's collar and sleeve, without a fixed beat. That may be a different thing. I mention it because it is the same map. **What I expected.** A steady picture. **Steps.** As child Link with the three Spiritual Stones and the Ocarina of Time, open the Door of Time and pull the Master Sword. Watch the edge of the platform in the scene that follows. The scene with Rauru comes right after it. **What my log of that run says** (`cutscene-flicker-important-lines.txt` has the lines, each with its line number): - The game's name for the map is `SageRoom`: `map: SageRoom (child)`, later `map: SageRoom (adult)`. - A steady 60 fps through both scenes: 59.9 to 60.1 fps in every count after the first of each scene, about 97% of the presents 15.5 to 17.8 ms after the one before, `vi: real-time step on: ratio 1.002, game's frame rate 60`. - DLSS drew every frame: `NVIDIA DLSS: 600 frames drawn` (or more) in every status line of both scenes. Frame generation is off. - No draw was skipped: `(0 skipped)` in every count. Draws left out because a shader or pipeline was not ready: 2.0 a frame in the first count after the map came in (three `quick pipeline (no optimizer)` lines and one `pipeline from the caches for a draw ahead of its build` stand right there), then `0.0 draws left out (not ready)` in every count of that scene. In the scene with Rauru: 0.2 to 0.4 a frame in three counts near its end, 0.0 in the others. - The hidden-mesh rule left nothing out in these scenes: it writes an `upscaler: faded: frames ...` line for every stretch in which it does, and there is none between the sword and the Market. - The game's barrier counts a frame stay level through the scene (`0x11: 41.0; 0x12: 68.5; ...`), so I see no pass that comes only every third frame. So the log names no cause. It only says what it is not. **What I have not tested.** - I have seen it once. Both scenes play once in a save, and I have no save from before them, so I can't run it again with `RX_VK_FLASH=1` or with other settings. - Not tried: another upscaler or none, DLAA, another frame rate, frame generation. - This is my own build of the v3.0.0 tag. My changes are listed below. One of them holds the cap at 60 while the game plays a scene of its own (my cap is 240 otherwise), so the scene ran at 60 as it does with the default cap, but it got there by my change. I have not run the project's release build or a nightly. **Related.** I found no report of this. #1760 is a flicker in another cutscene (pale grass for about a second, Steam Deck) and #601 is the sun's shadows on Link at the Temple of Time's entrance. Going by their descriptions both are something else. Found with an AI assistant (Claude), which went through my clips frame by frame and read my log. I played and recorded everything myself, on one PC. ### Where in the game The scene after child Link pulls the Master Sword (the game's map SageRoom), and the scene with Rauru right after it ### How often Once so far ### Graphics card and driver version RTX 5090, NVIDIA 621.24 ### CPU, RAM and operating system Ryzen 9 9950X3D, 64 GB, Windows 11 ### Changes from the defaults - Graphics: Output resolution 3840x2160, Fullscreen on. Upscaler NVIDIA DLSS, DLSS model Transformer 2 (M), Render resolution Quality (2560x1440), Sharpness 80, DLAA before the bloom on. Frame generation off. Game frame rate cap 240, NVIDIA Reflex On + Boost, V-Sync off. HDR Expanded, paper white 280 nits. Shadow resolution Highest. Debug tab: Sampler cache on. FPS counter on. - Gameplay: Field of view 120. - This is my own build from source (the v3.0.0 tag) with a few changes of my own: button mapping and prompt options, hold to quit, a hold at 60 fps for the game's scenes (on during both scenes, by the log: `vi: hold 60: on, the cap of 240 set aside`), one more case of the hidden-mesh rule (#1529), and #1814 ahead of the release that has it. - `longshot_env.txt`: `HOS_DISCORD=0` and `HOS_CRASH_WATCH=0`. - No ReShade, shader-cache tool or injector. Xbox Game Bar enabled. The clips were recorded with OBS. ### longshot_log.txt Neither file names my Windows account. - `cutscene-flicker-important-lines.txt`: start here. The lines that matter, with a short note on each group, and the numbers measured on the clip. - `longshot_log-cutscene-part.txt`: the log of that run, cut down to its start (lines 1 to 320 and 2940 to 2995) and every line from the sword to the Market (lines 214990 to 225070). The lines are as the game wrote them; the three lines in square brackets that say where lines are left out are mine. The whole log is 45 MB (a long play); I can attach it if it helps. ### Screenshots or video Recorded at 3840x2160 and 60 frames a second, the FPS counter top right. - `cutscene-flicker-three-frames.jpg`: three frames in a row from the first clip, at 3.0 s and at 10.0 s. The middle frame of each row has the rim, the frames before and after it do not. - `cutscene_1_flicker.mp4` (20.6 s): the scene after the sword is pulled. The flicker is there from the start to about 13 s. Step through it frame by frame to see the beat. - `cutscene_2_flicker.mp4` (8.2 s): the scene with Rauru. The specks are on his collar, left of the medallion, and on his sleeve. ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Member

Possibly related, for context:

  • issue #1045 Game: Ground textures flicker while moving in Zora’s Domain — Same Master Sword cutscene area with reported ground/corner flicker; similar visual symptom, but current issue isolates periodic pedestal rim flashing and provides a different GPU/build.
  • issue #1336 Game: Outer edges of the Temple of Time platform flash during young Link cutscene — Same young-Link Temple of Time cutscene and platform edges flashing; upscaler involvement noted there, though exact platform/beat differs.
Possibly related, for context: - issue #1045 Game: Ground textures flicker while moving in Zora’s Domain — Same Master Sword cutscene area with reported ground/corner flicker; similar visual symptom, but current issue isolates periodic pedestal rim flashing and provides a different GPU/build. - issue #1336 Game: Outer edges of the Temple of Time platform flash during young Link cutscene — Same young-Link Temple of Time cutscene and platform edges flashing; upscaler involvement noted there, though exact platform/beat differs.
Author

Thanks. Both look like the same scene to me.

#1336: the platform’s outer edges flashing in the young Link cutscene is what my clip shows. That report is on v3.0.0-rc.3 with an RTX 4080 SUPER and the same driver (621.24), so it is not something my own build’s changes brought in. Its reporter says it goes away with the upscaler off; mine was DLSS Quality at 3840x2160.
#1045: the two Master Sword reports in it sound like it too (ground and corners flickering in the first Master Sword cutscene with Ganondorf, one of them with DLSS Balanced and frame generation 3x). The Zora’s Domain part I can’t speak to.

What this report adds: the beat (the rim is there on one frame in three at 60 fps), a clip to step through, and the log lines of the scene. Fine by me if it is merged into #1336.

Thanks. Both look like the same scene to me. #1336: the platform’s outer edges flashing in the young Link cutscene is what my clip shows. That report is on v3.0.0-rc.3 with an RTX 4080 SUPER and the same driver (621.24), so it is not something my own build’s changes brought in. Its reporter says it goes away with the upscaler off; mine was DLSS Quality at 3840x2160. #1045: the two Master Sword reports in it sound like it too (ground and corners flickering in the first Master Sword cutscene with Ganondorf, one of them with DLSS Balanced and frame generation 3x). The Zora’s Domain part I can’t speak to. What this report adds: the beat (the rim is there on one frame in three at 60 fps), a clip to step through, and the log lines of the scene. Fine by me if it is merged into #1336.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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
MagicBeanDev/Longshot#1942
No description provided.