DXVK 1.4.3 released helping games with a large number of different shaders

It means that you're running into this problem with the Nvidia driver. No official fix available at this time, although they know what's causing it.

Is from Borderlands The Pre-Secuel via Forced Proton, with high Resolution textures pack installed and D9Vk enabled..
With D9Vk disabled the game doesn't crash, but the performance sucks..

I'm gonna continue in the github you mentioned...

Then nevermind, it just happens because it's a 32-bit game and runs out of address space. Please mention such things in the future.

Try PROTON_FORCE_LARGE_ADDRESS_AWARE=1.


Last edited by YoRHa-2B on 19 Oct 2019 at 6:53 pm UTC

Then nevermind, it just happens because it's a 32-bit game and runs out of address space. Please mention such things in the future.

Try PROTON_FORCE_LARGE_ADDRESS_AWARE=1.

It is enabled.

Then nevermind, it just happens because it's a 32-bit game and runs out of address space. Please mention such things in the future.

Try PROTON_FORCE_LARGE_ADDRESS_AWARE=1.

It is enabled.

You can try to enable the large address aware flag by patching the game's exe directly. Tool here: https://github.com/randomstuff/pe-set-laa

Personally I don't use proton and patching the game's exe helped me with a lot of games.

It is enabled.

Then there's nothing you can do besides maybe trying wined3d. D9VK and DXVK do need more memory, this is a known problem with 32-bit apps.

What are the advantages of DX12 over Vulkan for developers? I can only think of the Xbox support.

Well, for starters, D3D12 works on all Windows 10 systems and has excellent driver support from all vendors.

Windows drivers shipping with Windows Update sometimes don't come with Vulkan support -> games straigt-up don't work. Driver quality is also way worse (AMD is pretty bad, Intel seems to be especially bad, only Nvidia is acceptable these days - and that also was a whole different story ~2 years ago).

On the other hand, for Windows systems that aren't Windows 10, I remember hearing that DX12 wasn't available at all. I believe that still represents quite a few dollars left on the table, although of course it's gradually shifting.

What are the advantages of DX12 over Vulkan for developers? I can only think of the Xbox support.

Well, for starters, D3D12 works on all Windows 10 systems and has excellent driver support from all vendors.

Windows drivers shipping with Windows Update sometimes don't come with Vulkan support -> games straigt-up don't work. Driver quality is also way worse (AMD is pretty bad, Intel seems to be especially bad, only Nvidia is acceptable these days - and that also was a whole different story ~2 years ago).

On the other hand, for Windows systems that aren't Windows 10, I remember hearing that DX12 wasn't available at all. I believe that still represents quite a few dollars left on the table, although of course it's gradually shifting.

I think Xbox is the real driver behind DX12 since as you point out Windows 7 didn't support DX12 until very recently (and only for a selected few titles if I'm not mistaken). That and some devs/publishers are simply entrenched in the DX-camp (I once worked for a CEO that often bragged to potential customers how many Windows servers we had where the implication was that since Microsoft where a successful company then a company that uses their products is also be definition successful...)

It is enabled.

Then there's nothing you can do besides maybe trying wined3d. D9VK and DXVK do need more memory, this is a known problem with 32-bit apps.

Well.. There are things I can do for to play this game:

*To sacrifice graphics quality for to get performance, removing the UHD textures pack and keep using D9VK, waiting for improvements in the memory usage...

*To Sacrifice performance, playing the game with Proton's default OpenGL for DX9 games, like you said.

Spoiler, click me

*Or to play this game with the maximum performance and graphics quality on my other machine with Windows 7, with Physx enabled.

At the end of the day, D9Vk and DXVK are tools in beta stage and I use Steamplay just for the sake of the Linux gaming experiment :)..

Thanks for the input, Philip.

What are the advantages of DX12 over Vulkan for developers? I can only think of the Xbox support.

Well, for starters, D3D12 works on all Windows 10 systems and has excellent driver support from all vendors.

Windows drivers shipping with Windows Update sometimes don't come with Vulkan support -> games straigt-up don't work. Driver quality is also way worse (AMD is pretty bad, Intel seems to be especially bad, only Nvidia is acceptable these days - and that also was a whole different story ~2 years ago).

Would you mind to elaborate a bit about AMD's Vulkan driver state on Windows?
What's so bad about it?

That's really sad to hear as AMD was actually initiating all the low-level API thing with Metal.

Edit: Plus, I thought making a good Vulkan driver is by far *much* easier than a good OpenGL one.


Last edited by sub on 20 Oct 2019 at 9:35 am UTC

Would you mind to elaborate a bit about AMD's Vulkan driver state on Windows?
What's so bad about it?

It's fairly buggy even compared to the open-source AMDVLK driver, which would indicate issues in the proprietary shader compiler.

It wouldn't be so bad if things were at least consistently broken, but they aren't. One driver update might randomly fix an issue, the next update might fix something else but break the very same thing they fixed in the earlier update. It's a rollercoaster, and honestly I just can't be arsed to report bugs against it.

AMD's Windows driver has been a broken mess ever since Navi launched anyway, with D3D9 being completely broken in some cases and other major issues, but that's a different story.


Last edited by YoRHa-2B on 20 Oct 2019 at 11:16 am UTC

Would you mind to elaborate a bit about AMD's Vulkan driver state on Windows?
What's so bad about it?

It's fairly buggy even compared to the open-source AMDVLK driver, which would indicate issues in the proprietary shader compiler.

It wouldn't be so bad if things were at least consistently broken, but they aren't. One driver update might randomly fix an issue, the next update might fix something else but break the very same thing they fixed in the earlier update. It's a rollercoaster, and honestly I just can't be arsed to report bugs against it.

AMD's Windows driver has been a broken mess ever since Navi launched anyway, with D3D9 being completely broken in some cases and other major issues, but that's a different story.

Thanks.

That doesn't sound promising, indeed.
I have a very old card. Radeon HD 7950.
The Windows driver never gave me headaches.
Even when that card was new.

All games I tried with Vulkan run great on that old beast (paired with a Phenom II X4).
DOOM and Wolf 2. FullHD. Perfectly smooth. :)

In the not too far future I will update the full rig.
The idea was to go for Navi judging from my AMD experience so far... Hmmmm.

Specifically for Navi, would you suggest using AMDVLK or RADV?

Specifically for Navi, would you suggest using AMDVLK or RADV?

I don't have any personal experience with Navi, but from what I'm hearing from users, it doesn't seem to be stable at all yet, on any driver; the kernel driver is apparently also causing major headache (read: system hangs and fun stuff like that). I'd give it a few more months.


Last edited by YoRHa-2B on 20 Oct 2019 at 7:10 pm UTC