I was wondering if anyone could offer some insights.
Bit the bullet and purchased Alan Wake 2 on the Epic Game Store. With the DLC on the way I just can't wait any longer and maybe this one will never come to Steam? (With Epic as publishers, who knows)
I've installed Heroic Game Launcher, downloaded the latest Wine-GE and Proton-GE, downloaded the game and managed to get it running. Tried it with both Wine-GE and Proton-GE. No noticeable difference.
My specs:
- Intel Core i7 10700K
- 48Gb RAM
- Radeon RX 7800 XT 16Gb
- Manjaro Linux, kernel 6.9
- Mesa 24.1.1 (using the mesa-nonfree repo)
- Game is installed on my 1TB NVME drive
I'm running things on Medium/High, with FSR2 on Balanced, in 2560x1440
No raytracing enabled anywhere.
Honestly, it doesn't matter what resolution I choose. Even when running is 720p on Low, the framerate is the same.
I get around 27 fps with regular dips into the lower 15-20 when I spin the camera around quickly.
I've finished the first chapter (just in the morgue) and the framerate got choppier and choppier. I get Bright Falls has a lot more going on than the intro woodsy bit. But at this rate, I'm just not sure what to do.
When I look at other people on YouTube, their framerates are much higher. Even on Linux. And with less powerful hardware. Other games run MUCH faster. I get AW2 is demanding, but I can play CP2077: Phantom Liberty at 140+ fps in Dog Town on High in 1440p with FSR2 enabled, so I don't feel that AW2 should tank my PC that hard.
Is there something I'm overlooking here? I've tried the CyberFSR as well, made no noticeable difference.
Mangohud shows my CPU is consistently around 50% and my GPU is around 40% so there's definitely room to push things more, I feel. So why isn't AW2 using these resources?
Any help would be greatly appreciated. I love this game and want to play it, but the framerate is stopping me from really enjoying it.
Ah my mistake. I wasn't sure if it was a subtitle like Alan Awake 2: An American Nightmare.
You may want to try searching around GitHub. There's a few posts regarding vkd3d.
https://github.com/HansKristian-Work/vkd3d-proton/issues/1754
If you scrolls down to the bottom there are a few potential fixes mentioned in the form of launch commands.
There was this comment on Reddit as well
Still mostly spitballing but maybe it will get you going in the right direction or someone else can elaborate.
These all sounds like good ideas to play with, thanks! I'll have a go later tonight and will update here. It would be bonkers if the mesh shaders were at fault, since I got my 7800XT specifically for that feature...
If it works mind following up in an edit or comment so anyone who stumbles across this post knows?
I'd done that a few days ago, but you're right, not specifically to these suggestions. I tried the export VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader VKD3D_FEATURE_LEVEL=12_0 VKD3D_SHADER_MODEL=6_5 %command% and variations of it. It reduced performance significantly, so would not suggest people on more recent Mesa versions try this anymore. When I looked into it, it seemed to mainly be in place for Mesa 22.x which was still lacking mesh shader support.