-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Sarek #248
Comments
I am going to be off for 2 months in a few days, but I will try my best to add it before I am going. |
If the only thing that will not always be there is the testing releases, I am fine with whatever order you want as long as async and stable always exists and are in the same position. |
oh okey, async - stable - testing it is then. |
Okay, so I've excluded the 9.13 and 9.13-r1 since they weren't respecting that order and I will be creating a PR soon |
Just to make sure we're on the same page and for nothing to break on my end, just make sure you always have async and then stable in the assets in that order. |
Yes i understand, also thanks for adding my build, its such an honor :) |
I made a release with it. |
I forgot to add your runner to the list of runner thats in the description of the application, but I'll make an hotfix tomorrow to fix that before I go. |
No problem, sleep well :) |
Normally, projects only had one asset, so we never had the issue before where we have to find the correct asset in a release. But to make this more robust, we will be switching to regex to find assets instead of relying on the current positions. You can subscribe to #261 to keep track of when that issue is closed. Vysp3r will be gone for over a month and after that, regex will be added after the refactoring #246 is complete, so I estimate around 2 months. Until then, it's important that async is always the first asset and normal is always the second asset, as you confirmed already. :) |
I’ll make sure that async is always the first asset and normal is the second. Also, i will keep an eye on #261 and #246 for updates. Thanks again for the clarity, and good luck with the refactor! :) |
Is your feature request related to a problem? Please describe.
Nop
Describe the solution you'd like
Adding Proton-Sarek or Proton-For-Old-Vulkan Builds: https://github.com/pythonlover02/Proton-Sarek/tree/Stable
Describe alternatives you've considered
Manually downloading the Sarek builds
Additional context
Sarek (Proton-For-Old-Vulkan) is a custom Proton build featuring DXVK 1.10.3 and DXVK 1.10.3 Async, tailored for users with GPUs supporting Vulkan 1.1+ (but not 1.3+) and non-Vulkan setups. It offers patched versions of Proton-GE for improved performance on old hardware, with little enhancements to WineD3D. Originally created for two friends with GT 710 GPUs, the goal is to allow users with older GPUs to run Proton-GE without needing to use older versions.
Im the creator and main maintainer of the repo, i come here because some people would really like those builds to be on ProtonPlus for a more easy access, anything that i need to know, or do i am at the orders. :)
The text was updated successfully, but these errors were encountered: