Quoting: scaine

Quoting: whatever

Quoting: pleasereadthemanualcan you fix it yourself?

My guess is no.
They can test all they want, but unless they're willing (and capable) to contribute to WINE/Proton I don't see how this can work.
The game is now officially unsupported in Linux. That's why they removed the native version.

I think Valves take on this is that it's actually supported, but by Valve, not overkill.

I'd like some clarity from Valve on that though. Devs can say they "commit to get it working on Proton", but as pleasereadthemanual asks above, what does that really mean? Who's on the line if you buy that game, play it for 10 hours, then the dev screws it up and it stops working?

Realistically, by Valve's own refund rules - no one is one the line. After 2 hours / 2 weeks of buying, that's all the protection you realistically get from buying anything on Steam "Native" or not. They've only given refunds outside of that in special cases.

View this comment - View article - View full comments

Quoting: ripper81358Great to see that the MESA devs are able to allow for Raytracing support. However i guess the "out of the box" support will still be limited to games that use Vulkan as the graphics API.

Shouldn't be since it worked for Control which is DX12.

View this comment - View article - View full comments

After some more testing, one thing I have found on Steam Deck is that you can use the built-in gamepad controls. However, they only seem to work correctly in battles. The entire menu / lobby and god selection seems to not work with gamepad controls. So you can use touch screen, emulated mouse input or hold the STEAM button to activate mouse cursor. Seems this is a problem even on Windows going back years [External Link].

Article updated.

View this comment - View article - View full comments

Quoting: GuestI just spent all last night dragged in by some friends who got a sudden interest in the game, some good timing on this working. Desktop controller seems to work for me after setting the Enable Steam Input override in controller settings (rather than Use default) for the game; after that the game recognized it. My DS4 works fine now with no custom layout needed.

I have the exact same issue across Fedora and Steam Deck. The gamepad controls only work in battles, not in the main menu / lobby. Disabling / Forcing On Steam Input makes no difference on desktop (you can't do that in Gaming Mode on Steam Deck).

View this comment - View article - View full comments

Quoting: Farmboy0I get this error too sometimes but SteamVR works anyway.
One way to get rid of it I found is to delete ~/.steam/root/config/steamvr.vrsettings
Make sure you are on stable SteamVr the beta currently has problems.

Sadly that did not help in this case.

View this comment - View article - View full comments

*me remembering being killed by the boars quite a few times when first starting* :whistle: :whistle:

The difficulty absolutely isn't for everyone, and even some bits that aren't "difficult" can certainly be a challenge for people. Valheim is quite a brutal game, and anyone saying differently probably has played it a long time now.

Their upcoming upgrade with difficulty sliders should solve the early rough starts for people to learn it more.

View this comment - View article - View full comments

Quoting: melkemindThis is a game I'm definitely not going to play on the Steam Deck. I'll likely play it on my TV. While I'm glad Linux creators are making Steam Deck content, it would be nice if someone was still running tests and doing benchmarks on desktop Linux for games like this.

Well, this article is clearly for people wanting to run it on Steam Deck. For desktop, I noted in my original article it was running fine.

View this comment - View article - View full comments

Quoting: undeadbydawn

Quoting: Liam Dawe

Quoting: undeadbydawnHalls of Torment is also excellent (the native build is currently bugged, so use Proton)

I just did a full game with the Native build without a problem...

Shield Maiden War Hammer did zero damage over 4 runs, making the 'Direct Hits' achievement somewhat tricky. Worked perfectly under Proton, allowing me to hit 100%

Have you reported the issue to the developer?

View this comment - View article - View full comments

Quoting: CGull

Quoting: Liam DaweIf it was financially worth it, they would do it and they would have kept it up with other changes in the background. Debate the finer details of what it all would entail, and what they should have done, but the reasoning is exactly as I said and anyone saying otherwise at this point is deluded.

As the renowned Dr. Pangloss teaches, this is the best of all possible worlds. It follows that no company would ever do anything unwise or unpleasant, unless it was to do something even wiser and more pleasant. If they removed the ability of a large number of existing customers who bought a game as Linux native, they must have had sufficient reason. No game publisher can ever be criticized for anything it does in this, the best of all possible worlds.

But doesn't this argument mean that nobody should ever write Linux native games? And can't we extend the same argument to cover other software as well? If we have Proton, why do we even need the Linux userland? The entire purpose of Linux is to run Windows applications.

It’s not complicated. Game devs and pubs are a business in it to make money. Linux isn’t worth it enough to support Native. See my video [External Link] for more.

View this comment - View article - View full comments

Quoting: undeadbydawnHalls of Torment is also excellent (the native build is currently bugged, so use Proton)

I just did a full game with the Native build without a problem...

View this comment - View article - View full comments