Skip to content

Sarek9-18 Released
Compare
Choose a tag to compare
@pythonlover02 pythonlover02 released this 03 Nov 22:20
· 8 commits to main since this release
Sarek9-18
ef73b49
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Hotfix:

This release is nearly identical to 9-17, but includes a crucial hotfix to resolve an issue with prefix creation by adding the missing Python uuid import in the Proton script. For more details on this release, see the 9-17 release notes below, as they apply here as well

Sarek9-17:

Stable Build:

Changed the base of the Build to GE-Proton9-17 instead of GE-Proton9-16, all previous patches applied to Sarek9-16 are now working on Sarek9-17, including the ones for WineD3D, the Global Proton Prefix, and the Custom Parameters. The release as usual comes with DXVK 1.10.3 and VKD3D 2.6.

The only things added to this release are 2 new parameters, those being:

  • PROTON_VK_SOFTWARE: Uses Lavapipe to enable CPU-based rendering for Vulkan, supporting API version 1.3.
  • PROTON_OGL_SOFTWARE: Uses LLVMpipe to enable CPU-based rendering for OpenGL, supporting API version 4.6.

The software rendering options are more of a fallback, designed for cases when your GPU drivers are broken, really underperforming in OpenGL/Vulkan games, or lack support for specific APIs used by games or translation layers. While performance is predictably slow since the CPU handles rendering instead of the GPU these options can make some simple 3D or 2D games playable. For the best experience, try using the lowest resolution possible, as it helps a loot.

For example, I was able to run the Windows version of Terraria at 15-30 FPS on 800x600 window mode using the following parameters: PROTON_USE_WINED3D=1 PROTON_OGL_SOFTWARE=1 %command%. While the game didn’t launch with DXVK+Lavapipe, it worked with these settings. (I know there's a Linux version, but this was a test.) This was all on an old office PC with an i5-2400 CPU, 4GB of RAM, and a very outdated NVIDIA GPU.

Based on testing, WineD3D with LLVMpipe seems to work with all games that are already compatible with WineD3D on a GPU. In contrast, DXVK with Lavapipe encounters issues, with some games failing to launch, likely due to Lavapipe incomplete support for certain Vulkan extensions. Additionally, the PROTON_TWEAKS parameter is enabled by default to optimize performance as much as possible. Ideally, you won’t have to depend on software rendering, but if you do, I hope this setup will at least make some games playable.

Requirements for Using Lavapipe (Vulkan Software Rendering)

  • Mesa Version: 20.3 or newer
  • CPU: Multi-core recommended for better performance

Requirements for Using LLVMpipe (OpenGL Software Rendering)

  • Mesa Version: Any recent version (LLVMpipe is well-supported in current Mesa releases)
  • CPU: Multi-core recommended for better performance

Stable Async Build:

This build is similar to the stable version but uses DXVK 1.10.3 Async instead of the regular one.

Release:

Assets 4
Loading