Destiny 2 exhibits rainbow flickering.

dxvkclosed d3d11

doitsujin/dxvk#5914 · opened 2026-09-18 by ziobroaatwit · updated 2026-09-21 · 6 comments · github

Zziobroaatwit 2026-09-18 github

Please describe your issue as accurately as possible. Include screenshots or videos when relevant.

When running Destiny 2, there is a persistent rainbow flickering on various surfaces that almost looks like GPU failure artifacts, but when checking with other 7900XTX users this week on various distros, the flickering is the same. The game was previously never playable through normal means due to the anti-cheat being in the way, so it's unlikely anyone has investigated rendering quirks with this title until now.

Software information

Name of the game, settings used etc. Include any mods or add-ons if applicable.
Game: Destiny 2
Mods: Sunrise (or it's fork, Dawn) Client (In order to launch the game on Linux)
Settings: Maximum Settings (3DAO, SMAA enabled), 3840x2160 Resolution.

Video example 1, note green flash on left then blue flash on right. Issue is more extreme in other areas of the game:

https://github.com/user-attachments/assets/e46174bc-9278-47cc-9c7e-45f0168e5bea

Video example 2:

https://github.com/user-attachments/assets/809dd313-bafd-4624-9086-3f88394e515e

System information

GPU: AMD Radeon RX 7900 XTX (RADV NAVI31)
Driver: radv 26.2.2 (as reported in log) - Mesa 26.2.0-devel (git-035ae2f854) (As reported on vulkaninfo --summary)
Kernel: 7.2.4-valve1-1-neptune-72-g5ab4af5e2eb9 (64-bit)
Wine version: wine-staging 11.0 - GE-Proton11-6
DXVK version: 3.10

Apitrace file(s)

I tried according to the instructions below including pasting the files next to the EXE and including WINEDLLOVERRIDES="d3d8,d3d9,d3d11,dxgi=n,b" as you will see in the steam log, but got no resulting file. Please advise so I can attach this to help :)

For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

Log files

Please attach Proton or Wine logs as a text file:
Proton Log ~50MB so attached via Google Drive

Ddoitsujin maintainer 2026-09-19 github

One of these days we'll actually get bug reports about games that are actually possible to run on Linux again, I swear to god.

Honestly even if there's a DXVK bug here (this does look like compiler memes of sorts), there's just no useful way for us to look into it. I'm not going to violate Bungie's TOS over this and I frankly don't care about games from a company that is so extremely hostile to the platform as a whole. Literally impossible to do anything about this if you can't get apitrace to work.

Zziobroaatwit 2026-09-19 github

Totally understandable (Sorry to be buggin ya with something this...odd!), I'll give apitrace another whack this weekend and see if I can get it to spit anything out so you don't have to.

Zziobroaatwit 2026-09-19 github

Still spinning gears over here trying to get a .trace to appear on my machine, for now, attaching a new proton log which has different output from using: PROTON_USE_WINED3D=1 WINEDLLOVERRIDES="d3d8,d3d9,d3d11,dxgi=n,b" %command%

new log

Of note: Despite the fact that with WINED3D the rendering is hard to look at, the flickering still occurs there. It's arguably easier to see against the otherwise solid colored geometry.

Mmbriar 2026-09-19 github

Have you tried to record the apitrace without using wined3d? So with all d3d dlls set to =n?

Zziobroaatwit 2026-09-19 github

@mbriar Good point. I will try it tomorrow morning. Thus far I've just been getting no output at all, maybe that will do the trick.

Zziobroaatwit 2026-09-21 github

I'll actually be closing this issue as Bungie announced a completely empty promise and both community clients decided to effectively close down operations immediately in response to the news, making playing this on Linux useless again. If Bungie announces actual Linux support one day we can revisit this. I too will not be wasting cycles chasing a dead-end.