Whitelist Request

Nope, the game still shows an empty black screen, even on 3.7-7.
Twiddling with config enables a windowed mode, which renders OK, but since the game runs in native 800x600 it is unplayable on HighDPI screens.

Sure: https://gist.github.com/mdindoffer/be753f4c3b564cf355a33d67d4acc127

Highly doubt it - the game is old, DX8 I think. Newer Mesa/LLVM would not do much of a difference.
I will try anyway.

Just as expected, broken exactly as before with black screen even on Mesa 18.2.1 obtained via the recommended ppa.
Updated system info: https://gist.github.com/mdindoffer/b2b4b0604800cba4dc301508c3deb360

That's odd. It runs like a native game for me. I didn't change anything at all:

@aboutafter must be somehow specific to your setup. 9 out of 12 reports on SPCR state the same thing:
https://spcr.netlify.com/app/46500

I have managed to run this in my system with somewhat of a hack.

Hardware: LENOVO Thinkpad T460 with HD Graphics 520
Software: Ubuntu 19.04, KDE plasma 5.12.7, Steam Proton 4.2

Trick is to put a configuration file in it's app folder with the name player.ini with a single line:

1024 768 32 0 BaseCMO.cmo

Note found the trick from this video: https://www.youtube.com/watch?v=huBFIIzlvQE

So, far everything seems to work flawlessly.

@titonbarua This forces the game to run in a windowed mode, not FS, rendering it almost unplayable on high DPI screens.

For me this game had the usual, broken behaviour (black screen), had to create ini file to force it to window mode.

@aboutafter Can you repeat if it still works well out of the box for you with newer Proton and drivers?

No, it doesn't work any more for me. I triple boot (OpenSUSE Tumbleweed, KDE Neon and Manjaro) for testing Proton and I need to modify the player.ini if I want to see the game.

And yes, a non-resizable tiny window is not the way to play the game. I wonder why it worked correctly the first time though.

Does not work even in windowed mode, tried Proton 6.3-6: steam-46500.log

The same black screen.

Replying to https://github.com/ValveSoftware/Proton/issues/1689#issuecomment-507166335

With this workaround and by using proton 5.13-6 I was able to start the game with graphics intact. Since the window is tiny on a high-dpi screen it is not enjoyable to play, though.

With 6.3-6 the game only shows a black screen either by using the standard full screen setting or the windowed mode workaround with the player.ini file. Sounds and music are fine though. The game also shows a black screen with proton 5.13-6 when started in full screen mode without the player.ini workaround. I am running Arch with Nvidia and one 1440p and one 1200p screen.

I was not able to get this game to run at all even on Windows 10, so this might be a tough one.

hi @kisak-valve please find the requested files in the attachement and the system info in the gist.

https://gist.github.com/raikirii/76dc642bbf0a59ac4d032c72fe82d01a

steam-46500-6.3-7.log
steam-46500-proton-5.13-6.log

With this workaround and by using proton 5.13-6 I was able to start the game with graphics intact. Since the window is tiny on a high-dpi screen it is not enjoyable to play, though.

I can confirm this runs on 5.13, and you can use Gamescope to scale the game window up.

steam-46500.log

With dgVoodoo2 game works on Proton 7.0-3, but you have to create player.ini config file as mentioned above, and run with WINEDLLOVERRIDES="D3D8.dll,D3D9.dll,D3DImm.dll,DDraw.dll=n,b" %command% launch options. dgVoodoo2 config file can be edited manually, no need to run config program. Although I haven't managed to increase window size or run game in fullscreen mode.

This is a game bug rather than a Proton bug, but running through Proton gives you the potential to work around it rather than leaving it broken or nagging Microids to fix it, which are the only options for your Windows customers.

In-game, the cutscenes work fine (once you've done the requisite mystic rituals outlined in other reports to have it not be a black screen and not be a tiny window). In the game's menu there is the option to view those cutscenes again; most of those work, too. However, the "cylinder" cutscenes do not work - instead asking the user to insert the Syberia DVD. Obviously the user does not have a Syberia DVD if the game is bought through Steam. An oversight from the developer not using the correct path when they packaged up the game for the release on Steam. However, since everything about the game's environment is essentially pretend when the game is run through Proton, you do have the option of passing the appropriate files even when they're accessed using the wrong path; just a case of mapping a pretend DVD path to where the content actually is.

It's a relatively minor issue in a game that's probably not getting a lot of new sales, but it is a nice game to play on the Deck: it's necessarily running through gamescope there which sorts out the window/resolution issue, and the game's native resolution isn't far off the Deck's native resolution so rescaling that small number of extra pixels is perfectly fine, and the controls are good (and the Deck is great for point & click adventure games in general). If Steam automatically created the text file that the game needed and picked a working Proton version, it would be an entirely flawless experience out of the box, other than this minor cutscene path oversight from the developer.

There is no hack to fix the cursor?

For a game with a 800x600 resolution, it is best enjoyed on the deck.

Proton 5.13, steam overlay off and the player.ini file setup.

Anyone having artifacting problem when using gamescope?
The game itself is clear of artifacts when not using gamescope, so when it's not on fullscreen.

https://github.com/ValveSoftware/Proton/assets/41633661/2d0801ca-6c6c-46d6-ba68-1ad07531e5c2

OS: Arch
DE: Gnome 44.1
Display server: Wayland
Compositor: mutter

The game crashes when entering a new scene. Also, when switching window using Alt+Tab, the game become black with only the player left.

I got a log trace and from what I understand, the issue seems to be caused by libnvidia-glcore

steam-46500.log

• OS: Fedora 40
• DE: Gnome 46
• Display server: Wayland
• GPU: NVIDIA GTX 1060Ti
• NVIDIA Driver Version: 560.35.03
• Proton version: 9.0.3

@kisak-valve Even with this, I'm still getting the same error. I'm curious to see if someone with AMD GPU has the same crash.

Also, I'm not sure if this related or not, but I got the same error while playing an old version of Minecraft (1.12.1) when trying to enter full-screen

# JRE version: OpenJDK Runtime Environment (8.0_422-b05) (build 1.8.0_422-b05)
# Java VM: OpenJDK 64-Bit Server VM (25.422-b05 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libnvidia-glcore.so.560.35.03+0xa387cc]

So I'm pretty sure the bug comes from NVIDIA or MESA drivers

@Aurnytoraink by scene do you mean any change that would change the background? Like leaving the hotel's lobby, for example. If so, that doesn't crash the game here with my amd card.

Regarding the alt tab issue, I can see that one here, the background disappears and only the player and a few objects remain, a workaround for this is using gamescope.

@Aurnytoraink by scene do you mean any change that would change the background? Like leaving the hotel's lobby, for example. If so, that doesn't crash the game here with my amd card.

I also tried to play on the integrated GPU of my AMD Ryzen, and I see no issue, except the alt-tab thing

I had the same bug as some people here reported, which is that the game would play the intro videos but would give you a black screen with sounds of the main menu playing afterwards. You can seemingly interact with the menu items behind though...

Like titonbura suggested in their comment, i created a player.ini file in the game's folder, but while in their experience it worked with a resolution higher than 800x600, i had to downscale it to that one exactly, thus writing in the newly created file:

800 600 32 0 BaseCMO.cmo

I also had to change the Proton version to 5.0-10, as the default Proton version wouldn't work.

I had to upload my system report to another pastebin service because Github was misbehaving for some reason... It should stay up on their server without time limits, but i'd suggest saving it just in case.
Here it is.