Sounds like VRAM exhaustion if anything.

it is, vram usage a is little bit above total vram, changing resolution or screen mode forces VKD3D) to "reload" and that seems to clamp vram usage, that usually causes AMDVLK to crash, doesn't crash RADV...

however i just tried it on windows (without VKD3D) and although it still exceeds 4GB VRAM (using roughly 4.1) it barely stutters if ever, running around ~85 fps... not sure on how going about profiling this one...

Edit: let me try VKD3D on windows... VKD3D freezes on windows...

Windows always does significantly better when vram is almost, or has just run out. Linux amdgpu is just bad at handling this. I wondoer if radv perf changes if you revert https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6833

6 Feb 2023, 16:44 by @.***:

Sounds like VRAM exhaustion if anything.

it is, vram usage a little bit above total vram, changing resolution or screen mode forces vkd3d to "reload" and that seems to clamp vram usage, that usually causes AMDVLK to crash, doesn't crash RADV...

however i just tried it on windows and although it still exceeds 4GB VRAM (using roughly 4.1) it barely stutters if ever, running around ~85 fps... not sure on how going about profiling this one...

—
Reply to this email directly, > view it on GitHub https://github.com/HansKristian-Work/vkd3d-proton/issues/1416#issuecomment-1419294953> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A3G6J6I6YQXU7BUZCJN3RHDWWEL4PANCNFSM6AAAAAAUSG3NRQ> .
You are receiving this because you are subscribed to this thread.> Message ID: > <HansKristian-Work/vkd3d-proton/issues/1416/1419294953> @> github> .> com>

I wondoer if radv perf changes if you revert https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6833

~~interesting, i'll try that later on, too bad that it isn't switchable with RADV_PERFTEST or RADV_DEBUG, that was barely tested and left as it is... probably because most AMD GPUs have 8GB VRAM or more, similar issue submitted here:https://gitlab.freedesktop.org/mesa/mesa/-/issues/8107~~

EDIT: helps a little bit but it doesn't come close to fixing it, going to 90% works ok but just that single 10% uptick completely destroys performance.

So seems like its definitely RADV, AMDVLK is unstable so i'm going to report that on their issue tracker also.

To be noted, Alan Wake Remastered uses Double Buffered Vsync, and performance tanks hard and easily if max refresh rate isn't achieved at all times.

Try running the game with all forms of Vsync disabled.

I'm pretty sure double buffered vsync doesn't work on radv in the first place and it is always triple buffered.

Windows always does significantly better when vram is almost, or has just run out. Linux amdgpu is just bad at handling this. I wondoer if radv perf changes if you revert https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6833 6 Feb 2023, 16:44 by @.***:
…

Sounds like VRAM exhaustion if anything. > > it is, vram usage a little bit above total vram, changing resolution or screen mode forces vkd3d to "reload" and that seems to clamp vram usage, that usually causes AMDVLK to crash, doesn't crash RADV... however i just tried it on windows and although it still exceeds 4GB VRAM (using roughly 4.1) it barely stutters if ever, running around ~85 fps... not sure on how going about profiling this one... — Reply to this email directly, > view it on GitHub <[#1416 (comment)](https://github.com/HansKristian-Work/vkd3d-proton/issues/1416#issuecomment-1419294953)>> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A3G6J6I6YQXU7BUZCJN3RHDWWEL4PANCNFSM6AAAAAAUSG3NRQ> . You are receiving this because you are subscribed to this thread.> Message ID: > <HansKristian-Work/vkd3d-proton/issues/1416/1419294953> @> github> .> com>

Sorry forgot to add that you were right, reverting that commit does fixes performance issues when vram limited (on many games actually) back then i think i was building mesa incorrectly,

No reason to keep this open, for future reference, issue on mesa