Interesting, but somehow it still behaves more like Wayland than X11: a call to XGetImage (not supported by Wayland but working fine on X11) causes the game to crash.

View this comment - View article - View full comments

I was wondering if anyone with Wayland can confirm that the game doesn't crash at startup...
I still haven't tested it locally (I've got X) and the steam deck for whatever reason lies and reports X as well, so I'm not 100% sure my Wayland detection code works (need to tweak a few window creation params to avoid crashing).

View this comment - View article - View full comments

It was! Hopefully there are no more major problems, but there's still time to catch more bugs and do the fixes before we release the actual demo.

View this comment - View article - View full comments

Good news! Valve fixed the configuration of the playtest on their side.
What does it mean? Joypad input now works on all versions!

View this comment - View article - View full comments

Quoting: ForgeOh, I have a Steam Deck LCD for projects and a Steam Deck OLED that I do my gaming on. Not quite willing to mail one to you, but I'd be happy to get you remote access and a bit of shared presence, schedules permitting.

That would be incredibly helpful, thanks for offering!
Let's talk about it on our Discord [External Link] (or please send me a PM if you prefer a different way to communicate).

View this comment - View article - View full comments

Quoting: tfkDesktop hacking effect?

Yes, I've pushed an update so you should be able to see it the next time you start the game.
The same update (0.520) also adds support to Steam Input (allowing gamepad controls on Linux too), except that I have only been able to turn it on via Steamworks for the full version of the game (unreleased) but not on the playtest.
Looks like there's some bug/missing feature in the playtest config system on Valve side :(

So for now we're out of luck, unless Valve's support comes back to me with a solution.

View this comment - View article - View full comments

Quoting: emphyI do seem to be getting the same slowdown that others have reported. Starts off smooth as butter, but performance gets really bad fairly quickly.

Latest linux mint xfce (so: no wayland), with an rx6600. I will check later if a newer kernel could alleviate the issue.

Ah, so it's starting to look like an AMD-specific rendering slowdown then. Hopefully I'll be able to get to the bottom of it on my own system.
BTW, I've just managed to add a special feature that's been Windows only so far: the desktop hacking effect that occurs the first time one starts the game.
I'll be curious to hear what you think, will post an update here when it's uploaded!

And as far as Steam Deck goes, I don't think it's as simple as exchanging the X&Y of the window... I'm afraid I need to get my hands on one of those bad boys if I want to get the game working properly on it, so it will be a while.

View this comment - View article - View full comments

Quoting: SchattenspiegelIt does start fine now in native mode (had to switch compatibility mode to 'scout' for the first start, but that is a steam issue after using proton before) Game seems to work nicely otherwise, but the sewers still have the slowdown issue with CPU load in the high 90s and GPU load in turn going toward single digit. Same behavior has been previously observed with Proton.

Ok, will keep investigating.

Quoting: tfkEdit: Tested on Destktop Mode. The window's width and height are swapped. The engine does not recognize that the screen on a Steam Deck is rotated. Like with a phone. That's why it probably doesn't want to display an image in game mode.

Ah, sounds like you found something interesting there. I didn't know about that... to be honest I didn't do any research into Steam Deck itself, I just tried to wing it with the Linux build but clearly further steps are needed.
Better if I also switch to KDE Plasma (according to this page, it's what the Deck uses: https://partner.steamgames.com/doc/steamdeck/testing [External Link] )
Thanks!

View this comment - View article - View full comments

At this point in time, a game needs to work both on x11 and Wayland.
I know SDL very well and if things turn out too ugly I'll possibly end up using it.

Anyway, I pushed an update to the playtest that should hopefully solve the startup issues related to badly portable binary. (Got myself Ubuntu 20.04, switched from gcc 13 to Clang 16 [can't go any lower than that] + libc++ and packaged the dependencies).
Would be very useful to know if it now works fine in native mode for the people who were unable to start it previously (Steam Deck anyone)?
It's probably still gonna fail on much older systems though - but that's ok I guess.

View this comment - View article - View full comments

Sounds like I need to do some serious Wayland testing myself... thanks for letting me know.
Btw, if you press backspace in game you'll get a live perf graph - it should tell you whether the slowdown comes from the rendering (most likely) or something else.

View this comment - View article - View full comments