Well, it starts on Steam Deck. But I only hear the audio. The display shows the rotating Steam logo and that's it. Need to do further testing in desktop mode.

Edit: 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.

View this comment - View article - View full comments

Quoting: mitridasSounds 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.

Ah! I'll try that.

View this comment - View article - View full comments

Still getting the slow down, I'm afraid. AMD RX 6800 XT. Wayland.

View this comment - View article - View full comments

Something like "Our own engine, handcrafted in-house".

The slowdown, could that be a Wayland thing? I can test this theory this evening. I realized that the NVIDIA machine runs on X11 and the AMD machine on Wayland.

View this comment - View article - View full comments

Nice! I think that shipping the libs in the game directory works. I copy over libs from the Ubuntu dirs of my Steam install to games which miss libs. That works too.

View this comment - View article - View full comments

Steam Deck (OLED) time. Did not launch. But I know why. The game needs three libraries which are not available on SteamOS by default.

libc.so.6: version: GLIBC_2.38
libm.so.6: version: GLIBC_2.38
libstdc++.so.6: version: GLIBCXX_3.4.32

Best option is to include these three `.so` files in the root of the game. The `ldd` command says that the rest of the libraries are there.

Edit:
Not seen the game on screen yet, but a few pointers towards Steam Deck verified status.

1. Readability. The game has text balloons, key indicators and train station names which are referred to, which the player has to follow. My initial feeling is that these texts need to be bigger to be readable on smaller screens. The main menu is OK as far as I can gather.
2. The Steam Deck Controls need to work. It is possible to map buttons to in game key presses, but I think Valve has a section in their SDK to properly support the Steam Deck controls.
3. I didn't see any places where text input was needed, other than the feedback box and the numerical input fields for the sound volume. The latter should really be replaced by sliders so a user can navigate via the d-pad, select with A and use the d-pad again to change the values.

View this comment - View article - View full comments

Quoting: mitridas

Quoting: tfkFirst test done on a i7 6700, 16GB, NVIDIA 4060ti. Fedora 39 KDE spin. No issues. Left my feedback in game.

Next test will be on my AMD 6800XT system.

Cheers, I received both of your in-game feedbacks. A bit puzzling that with the 6800XT it slows down - it runs pretty smoothly on my 6500XT which is supposed to be slower :/

Yes. First time I experienced this on my system. Switching RSync off doesn't fix it. I'll do a quick search for similar issues with games. Maybe its something obvious.

Edit: oh yeah, And when loading a new section, for a split second I see the last frame being displayed.
Edit 2: Sound did sound better, that was a problem on my end. I quickly connected headphones via an audio extension cable and that didn't do the sound quality any good.

View this comment - View article - View full comments

Second test done on a i7 6700k, 32GB, AMD Radeon 6800XT 16GB. Fedora 39 KDE spin. No issues starting the game. Do experience a slow down after 57 seconds. Its not an FPS drop. The rendering just gradually slows down. Also the timer slows with the same pace. Left my feedback in game.

Next test will be on my Steam Deck OLED.

View this comment - View article - View full comments

First test done on a i7 6700, 16GB, NVIDIA 4060ti. Fedora 39 KDE spin. No issues. Left my feedback in game.

Next test will be on my AMD 6800XT system.

View this comment - View article - View full comments

Quoting: mitridas

Quoting: tfk...
More interesting I find the question what exactly needs testing?

I'm a developer and I can always appreciate precise parameters so I can focus on the important bits.

One thing I would want to test myself is how the game behaves on Fedora Linux.
...

I'm glad you asked!
We're interested in the following:
1) Issues that seem OS-related. For this reason, just validating the basic functionality (if the game even starts at all) on as many distros as possible, especially anything that's not Manjaro or Ubuntu (used during dev). So Fedora would be great.
2) Issues that could be graphic drivers related. We did a good amount of testing on different GPU vendors and model for Windows, but not on Linux.
4) Trying on Steam Deck would be also very interesting, as we don't have one at the studio. But I foresee input problems with that one for the time being
3) In addition to that, any feedback about any aspect of the game itself will be very useful :)

A good way to report something, or simply tell us whether you like the game or not, is the Feedback page integrated in the game's main menu. Otherwise you can post something here, or contact us at "support at pixelrats.com"

Ok. I'm off work in a few hours. I'll do some testing then.

View this comment - View article - View full comments