Support us on Patreon
PayPalUpdate 17/08/24, 9:00 UTC: Proton Hotfix was updated with the needed fix to get it working. Valve has set this by default for it so you should uncheck any forced compatibility options you have set. Nice to see Valve react so quickly once again.
Original article below:
Hunt: Showdown had a huge update and rebranded to Hunt: Showdown 1896, but the update came with breakage on Linux Desktop and Steam Deck.
Thankfully, Valve have been really quick at times when this sort of thing happens to bigger games. And once again, Valve to the rescue. Use this fix at your own risk though, as it can cause other issues, it will also affect any other games you currently have set to Proton Experimental.
For the fix:
- Open Proton Experimental in your Steam Library.
- Go into Properties -> Betas.
- Select the "bleeding-edge latest and untested dxvk, vkd3d-proton and wine changes; backup your prefixes before using" (not the 8.0 version!).
- Then ensure Proton Experimental has updated.
- After that, find Hunt: Showdown 1896 in your Steam Library.
- Go into Properties -> Compatibility, tick the box and select Proton Experimental.
After that, you'll be good to go. No doubt a fresh normal version of Proton Experimental will come soon so that first part eventually won't be needed.
What's new in the game? Highlights:
- New Map – Mammon's Gulch, a whole new biome set in the Rocky Mountains of Colorado.
- New Wild Target – the Hellborn is Hunt's newest Wild Target who uses an onslaught of fiery attacks. Once downed, the Hellborn will grant a Bounty Token with no Banish time.
- Scorched Earth – a new Live Event giving players brand-new rewards to earn.
- New CRYEINGINE 5.11 integration – ushering in upgraded visuals, audio, performance, and more.
- New UI - overhauled to improve navigation, with plenty more updates to come.
Here's the trailer for the new update:
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Direct Link
Direct Link
It's having a Free Weekend on Steam right now too so you can try before you buy.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
12 comments
hardpenguin Aug 16
Such a pity devs do not take time to test on Steam Deck or Linux with Proton.
1 Likes, Who?
.
That's my preferred Proton version anyways .You're a fan of the don't use this or it might kill you and everyone you know build?
3 Likes, Who?
That's my preferred Proton version anyways .You're a fan of the don't use this or it might kill you and everyone you know build?
Yes, and I never ran into an issue. Besides, it's the only Proton option that made the stupid EA launcher work for the games that require that to play.
1 Likes, Who?
Update 17/08/24, 9:00 UTC: Proton Hotfix was updated with the needed fix to get it working. Valve has set this by default for it so you should uncheck any forced compatibility options you have set. Nice to see Valve react so quickly once again.
2 Likes, Who?
Only use Proton Experimental for the edge cases where something isn't working properly, like this one. There's already a fix and it'll be merged into stock Proton as necessary, making Hotfix version the current proper choice for this specific game at this point in time. Once merged, change back to stock Proton.
Do not use Experimental as default or as a permanent choice. It cannot be overstated or repeated enough times. Come on people.
Do not use Experimental as default or as a permanent choice. It cannot be overstated or repeated enough times. Come on people.
2 Likes, Who?
Do not use Experimental as default or as a permanent choice. It cannot be overstated or repeated enough times. Come on people.
I think you left the part where you explain what's so bad about using the Experimental version as default
.
1 Likes, Who?
Do not use Experimental as default or as a permanent choice. It cannot be overstated or repeated enough times. Come on people.
I think you left the part where you explain what's so bad about using the Experimental version as default
I've one argument that might be compelling to you the rest you don't believe.
It keeps the devs from experimenting.
I know that the wine staging developers refuse to start implementing a certain graphics feature, because "people treat wine staging as yet another wine release".
The problem with this is that it would be a lot of work and thus could span multiple wine releases before it gets finalized and until than users will have to content with crashy apps in staging version.
Edit:
my source
Last edited by LoudTechie on 17 August 2024 at 3:56 pm UTC
2 Likes, Who?
what's so bad about using the Experimental version as default .
that's not how Proton is designed to work. Proton Experimental and Hotfix might have regressions that can break older games. Once you find a version that works, you stick with it. If a game breaks, because of an update (eg. EA App), THEN you try the latest version. If that doesn't work, then you try Experimental or, if available, Hotfix.
Using Experimental on everything is like installing Windows 11 Beta build to fix a problem with a game that's bugged on Windows 10. Sorry for using Windows as a example.
2 Likes, Who?
If a game breaks, because of an update (eg. EA App), THEN you try the latest version. If that doesn't work, then you try Experimental or, if available, Hotfix.
For me, the opposite happens here, EA App doesn't work UNLESS I use Proton Experimental, at least that was the case 2 months ago across several days when I had to reinstall the damn launcher a dozen times before I figured this out, I don't want to "test" if the launcher now works with the regular Proton because I'm really done with troubleshooting that specific issue, it still works under Experimental, I don't care what I "should" and "shouldn't" do here, no offense.
I selected regular Proton as default for Steam now to make you all happy, it's probably no different and all games would work on either version, but for EA games I'm sticking with Experimental.
2 Likes, Who?
Only use Proton Experimental for the edge cases where something isn't working properly, like this one. There's already a fix and it'll be merged into stock Proton as necessary, making Hotfix version the current proper choice for this specific game at this point in time. Once merged, change back to stock Proton.
Do not use Experimental as default or as a permanent choice. It cannot be overstated or repeated enough times. Come on people.
Wait what... I always use experimental and haven't ran into issues. If i would then i would switch to normal proton for said game, but running experimental has been fine and its nice to have latest and greatest improvements....now bleeding edge experimental is entirely different topic ofc.
edit: i mean each their own, but experimental stable channel is just fine.. newer releases usually work the best with it before the fixes get into hotfix or into stable.. in rare cases where regressions happen, its not hard to switch to stable then for that game.
Last edited by Xpander on 17 August 2024 at 5:25 pm UTC
2 Likes, Who?
About the stability issue.
The current design of the wine release program is as such that staging is better for new breakages(new games) and that stable avoids regression(old games).
The problem with "stability" in the case of wine is that wine is inherently a patch.
All currently unimplemented features for wine are all "instability" in a certain way, especially in a wild market like video games.
As such Wine defines "stability" different than a user would experience.
Wine defines stability as: no regression. Something that worked in the past still works.
While from the user side "stability" means: "doing your primary job consistently."
The current design of the wine release program is as such that staging is better for new breakages(new games) and that stable avoids regression(old games).
The problem with "stability" in the case of wine is that wine is inherently a patch.
All currently unimplemented features for wine are all "instability" in a certain way, especially in a wild market like video games.
As such Wine defines "stability" different than a user would experience.
Wine defines stability as: no regression. Something that worked in the past still works.
While from the user side "stability" means: "doing your primary job consistently."
2 Likes, Who?
See more from me