It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Sphinx and the Cursed MummyLinux Version(23 posts)(23 posts)
(23 posts)
Pages:
1
2
This is my favourite topic
Posted February 25, 2018
Well? Game starts here with open-source drivers on Intel IvyBridge, but after trying to start a new game I got always a crash with "intel_do_flush_locked failed: Input/output error". Thought you should notice that Mesa 17.0.5 and the game seem not compatible at all. Could you please have a look on that?

EDIT: Also the Windows-version is not working with Wine. Seems complete unplayable with free software / drivers and only really working with proprietary drivers!
Post edited February 25, 2018 by hendrick100
Posted February 28, 2018
avatar
hendrick100: Well? Game starts here with open-source drivers on Intel IvyBridge, but after trying to start a new game I got always a crash with "intel_do_flush_locked failed: Input/output error". Thought you should notice that Mesa 17.0.5 and the game seem not compatible at all. Could you please have a look on that?

EDIT: Also the Windows-version is not working with Wine. Seems complete unplayable with free software / drivers and only really working with proprietary drivers!
Hello!

At the time of release we confirmed that Sphinx and the Cursed Mummy runs with Mesa drivers on Intel and AMD video cards that we use on regular basis for QA. Feel free to contact our support team for further help: https://support.gog.com/
Posted February 28, 2018
avatar
hendrick100: Well? Game starts here with open-source drivers on Intel IvyBridge, but after trying to start a new game I got always a crash with "intel_do_flush_locked failed: Input/output error". Thought you should notice that Mesa 17.0.5 and the game seem not compatible at all. Could you please have a look on that?

EDIT: Also the Windows-version is not working with Wine. Seems complete unplayable with free software / drivers and only really working with proprietary drivers!
avatar
linuxvangog: Hello!

At the time of release we confirmed that Sphinx and the Cursed Mummy runs with Mesa drivers on Intel and AMD video cards that we use on regular basis for QA. Feel free to contact our support team for further help: https://support.gog.com/
Did that and got the feedback that there is no further support for a libre derivate of Arch Linux. Using Hyberbola with 3.3 (Core Profile) Mesa 17.0.5. The game starts, main menu is looking good, but after starting a "new game" the screen stays black and the game itself crashes after some seconds. Got only the feedback to install the 32bit-libraries, but that's already done because other games work and it looks irritating because even games like Dark Souls and Dark Messiah of Might and Magic work under Wine. The last one even with all settings on maximum!

Even testing under Trisquel does not work at all on comparable system with same components: The game itself crashes on systems with Intel Ivybridge (known as Intel HD 4000) and even though newer graphic cards also need proprietary signed blobs to work (as known for AMD and NVidia already).

Seriously: What systems did you use for testing? With Intel Haswell, Broadwell or even newer?
Post edited February 28, 2018 by hendrick100
Posted March 11, 2018
Hi, @hendrick100! Looks like we are hitting a driver bug in the open-source Intel OpenGL drivers. Here is a reddit thread talking about the same issue. Maybe you can contribute a backtrace or coredump:

https://www.reddit.com/r/linux_gaming/comments/81t838/sphinx_and_the_cursed_mummy_freezes_at_intro/dv58l72/

In any case looks like reverting to the December release fixes it for most. The problem only seems to be triggered at the intro/starting a new game. So after completing the intro you can just run the latest version.

Also, just so that you know. I developed the Linux port of Sphinx exclusively in Arch using the radeon Mesa drivers.

Let me know if that helps.
Posted March 13, 2018
Sorry, but it seems that the patching-routine is only available in one direction and there is no way back for now. I've tried to unpack the patch, but it is done with controlling hashsums. Would be better to have the concurrent versions of the binaries and files included!

EDIT: Even with modifications in the gameinfo-file the patch-routine won't work at all. :(

EDIT2: Another test with decompressing both files: Available patch and the concurrent installation-package with trying to rebuild manually using the included xdelta3. No success. Thanks, GOG: A complete unusable game with a complete unusable patch. Well? That was the last purchase from my side here. :-) Of course a patch goes only in one direction, but there is even no fallback with binaries for testing purpose.
Post edited March 13, 2018 by hendrick100
Posted March 13, 2018
I have sent you a friend request so that we can talk. Let's see if we can fix it for good, shouldn't take long.
Posted March 13, 2018
avatar
Swyter: I have sent you a friend request so that we can talk. Let's see if we can fix it for good, shouldn't take long.
Got it. Thanks for the request!
But first things first: I appreciate your engagement here. Big thanks from my side and it doesn't matter if we could fix it adhoc. It's just not good in such cases having only the newest versions for download and I hope GOG take another approach for patching.
Posted June 09, 2018
Just a quick heads up. I already talked with @hendrick100 about it, but the the Linux driver freezes have been reported to Mesa3D (https://bugs.freedesktop.org/show_bug.cgi?id=105755) and glslang (https://github.com/KhronosGroup/glslang/issues/1315). I forgot to initialize a loop in the dynamic lights shader that was added post-launch in January, it didn't cause any issue under Windows and its proprietary OpenGL drivers or the proprietary NVIDIA Linux drivers, but it caused infinite loops in the Intel and NVIDIA/nouveau (not on amdgpu, radeonsi or r600) back-ends of Mesa3D.

Various players have confirmed that the issue was fixed in the 2018.03.28 version.
So if you play the latest GOG version it should work fine.

Let me know if that helps.
Post edited June 09, 2018 by Swyter
Pages:
1
2
This is my favourite topic
Community
Sphinx and the Cursed MummyLinux Version(23 posts)(23 posts)
(23 posts)