... PROTON_FORCE_LARGE_ADDRESS_AWARE=1 not help
WINE_LARGE_ADDRESS_AWARE=1 + PROTON_FORCE_LARGE_ADDRESS_AWARE=1 not help (small test)
WINE_LARGE_ADDRESS_AWARE=1 + PROTON_FORCE_LARGE_ADDRESS_AWARE=1+ d3d9.evictManagedOnUnlock ...
set
`PROTON_FORCE_LARGE_ADDRESS_AWARE=1`
`WINE_LARGE_ADDRESS_AWARE=1`
fixed only
`mmap() failed: Невозможно выделить память`
problem still exists
`err: DxvkMemoryAllocator: Mapping ...
... Kron4ek/Wine-Builds) and setting PROTON_FORCE_LARGE_ADDRESS_AWARE=1 or WINE_LARGE_ADDRESS_AWARE=1 will fix it. The LARGE_ADDRESS_AWARE patch is not ...
... DXVK_ASYNC=1 PROTON_ENABLE_NVAPI=1 PROTON_USE_WINED3D=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 WINE_LARGE_ADDRESS_AWARE=1``
I'm running on Arch Linux with an ...
comment by ElmerFuddDK · 2023-09-11 · view · github
... export VK_ICD_FILENAMES=
export PROTON_FORCE_LARGE_ADDRESS_AWARE=1
export PROTON_LARGE_ADDRESS_AWARE=1
export WINE_LARGE_ADDRESS_AWARE=1
Each time the prefix creation process hang ...