Proton: enable LAA by default

[soredake]

Feature Request

I confirm:

• [X] that I haven't found another request for this feature.
• [X] that I have checked whether there are updates for my system available that
  contain this feature already.

Description

Enable LAA by default and disable for problem ones.

Justification [optional]

Many games will benefit from this.

Risks [optional]

Some games might crash https://github.com/Tk-Glitch/PKGBUILDS/issues/401, but we can disable laa for them.

References [optional]

TKG did this
https://github.com/Tk-Glitch/PKGBUILDS/commit/b0fe54e1e3b939b3faf97d78340626cac25fb411
https://github.com/Tk-Glitch/PKGBUILDS/commit/5a694743b95586857b034129725b7ce353769ed3

[mirh]

I don't know, this seems more like a hack to workaround the bigger problem of mysteriously higher memory usage (#177 https://github.com/doitsujin/dxvk/issues/1318) than anything

[Tk-Glitch]

It most definitely is. But can this actually be fully fixed? I would assume DXVK's memory overhead reduction has its limits.

[mirh]

I mean, just this month nvidia finally fixed a big bug with that. So.. we are progressing?
It doesn't help that the number of users actually reasoning with the memory map numbers under the eyes is pretty low.

[CSahajdacny]

Well.. Borderlands: The Pre-sequel running via forced Proton still crash complaining about memory allocation error if UHD textures pack is installed, with D9VK/DXVK enabled.... With PROTON_USE_WINED3D enabled it doesn't crash, but the performance sucks!

[vinifmor]

@CSahajdacny, if you are running over a Nvidia GPU, try to disable the game vsync. It's not a rule, but one of my games was raising DxvkMemoryAllocationError because of its own vsync implementation. The sync is still done even when the setting is turned off. It makes me believe somehow for this specific game the vsync was done twice and the memory crashed.

[CSahajdacny]

@CSahajdacny, if you are running over a Nvidia GPU, try to disable the game vsync. It's not a rule, but one of my games was raising DxvkMemoryAllocationError because of its own vsync implementation. The sync is still done even when the setting is turned off. It makes me believe somehow for this specific game the vsync was done twice and the memory crashed.

Thanks for the tip. I'm gonna try and report the result.

[soredake]

[aeikum]

As you noted, the Large Address Aware flag is enabled by default beginning with Proton 5.0-4. If you find this causing issues with certain games, please let us know in the game's issue page.

You can disable forcing the LAA flag by setting PROTON_FORCE_LARGE_ADDRESS_AWARE=0.

[shoober420]

Awesome!