search

Sporif / dxvk-async

746 stars 37 forks source link

GTA 4 flickering dots using DXVK 1.9 on AMD RDNA2 #19

Closed Fezzy976 closed 3 years ago

Fezzy976 commented 3 years ago

Issues using latest DXVK 1.9 with AMD 6800XT and GTA 4. Producing flickering coloured crosshairs on screen when smoke or bloom effects are used/switched. Flicker happens for a split second so capturing this was tricky.

Drivers used are 20.6.1, 20.6.2, 20.7.1, and UWP drivers. All exhibit the same issue, the issue is not present when using DX. GPU is not overclocked either and no overheating has been monitored. No other game tested or played with either DXVK or standard .API's displays this issue.

Posting this in hopes it can be fixed, as I doubt AMD will provide fixes for a DXVK issue.

Screenshots of issue. GTA 1 GTA 2

Sporif commented 3 years ago

Did you test with both stock dxvk and dxvk-async? Because if it's a general issue with dxvk this isn't the right repo.

Fezzy976 commented 3 years ago

Did you test with both stock dxvk and dxvk-async? Because if it's a general issue with dxvk this isn't the right repo.

yes tested with both dxvk and dxvk async

Sporif commented 3 years ago

And the issue occurred only with dxvk-async?

Fezzy976 commented 3 years ago

No it occurs with both.

It seems to be more apparent the higher the resolution. It happens mainly around light or smoke sources when turning the camera.

Like I said DirectX is not effected but obviously performance is awful.

I have found a sweet spot. 2560x1440 144Hz no FPS cap and the issue whilst still there it barely appears or is noticeable. If I cap the FPS to 60fps with RTSS it becomes more apparent.

I tested out 5k144Hz using AMDs VSR and its a mess with flickering everywhere.

No other games I've played are effected.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Sporif @.> Sent: Friday, July 23, 2021 3:46:47 PM To: Sporif/dxvk-async @.> Cc: Fezzy976 @.>; Author @.> Subject: Re: [Sporif/dxvk-async] GTA 4 flickering dots using DXVK 1.9 on AMD RDNA2 (#19)

And the issue occurred only with dxvk-async?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Sporif/dxvk-async/issues/19#issuecomment-885691233, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU6K2Q5SXWA4K3S5KDBMGBDTZF6FNANCNFSM5A364LAA.

Sporif commented 3 years ago

No it occurs with both.

Then since this not dxvk-async specific, please open an issue in the main dxvk repo (or search for a similar one there):

https://github.com/doitsujin/dxvk