Linux port or Proton?

[Compatriot]

Please and thank you

[CrashSerious]

I am running on Linux, under proton. 9 months later-- today. I am getting the same crash, I think. The "Play game" animation taunts me for a a while and I can't look around. Then I can move around a minute or more later. After clicking it (when I am able and can 'look around' then the next menu shows-- the window closes the minute I click start game. I think the process is still running though becasue I have to 'Stop game' in steam to get it to stop the process. running 'ps aux' shows that the game is running as well.

[maschere]

I recently got a Steam Deck and have begun investigating the issue. The game starts just fine, I can even hit "Play Game" on the virtual laptop and enter the games Main Menu. To my surprise, the whole Python interaction seems to work just fine: The pyjop python module loads correctly in the backgrounds - I can briefly see the python shell pop up. Though once I select an actual level to play, the Deck's screen turns black and nothing further happens. No crash. Nothing. I can then only close the game. I looked into the proton logs - but I do not see anything pointing me in the right direction what might be wrong. These are the last lines of my proton log, if anyone with more Linux / Proton knowledge has an idea what might be going on, I'm all ears.

2840.390:0120:0124:fixme:win:GetPointerDevices (0000000000B9EF34 0000000000000000): partial stub
2840.390:0120:0124:fixme:system:NtUserQueryDisplayConfig flags 0x2, paths_count 0xb9ef00, paths 0x1304006be300, modes_count 0xb9ef34, modes 0x130400561d80, topology_id (nil) semi-stub
2840.390:0120:0124:fixme:system:NtUserDisplayConfigGetDeviceInfo Unimplemented packet type 11.
2840.390:0120:0124:fixme:ui:uisettings2_get_TextScaleFactor iface 00000000337527B8, value 0000000000B9EE10 stub!
2840.409:03b8:0618:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2840.409:03b8:0614:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2840.409:03b8:0610:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2840.412:03b8:061c:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2840.515:0104:0118:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
2840.515:0104:0118:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000B159C0, 10002, 000000000193F8A0: stub
2840.608:0104:0118:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
2840.608:0104:0118:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000B15FB0, 10002, 000000000193F8A0: stub
2844.566:03b8:062c:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2855.848:0120:0264:fixme:process:CreateProcessInternalW Unsupported attribute 0x20007.
wine: using kernel write watches, use_kernel_writewatch 2.
wine: overriding CPU configuration, 8 logical CPUs, host CPUs 0,1,2,3,4,5,6,7.
2855.962:0630:0634:trace:seh:sigsys_handler SIGSYS, rax 0xffff, rip 0x600000000005.
2855.962:0630:0634:trace:seh:install_bpf Seccomp filters already installed.
pid 9526 != 9525, skipping destruction (fork without exec?)

[Patola [Linux]]

Publicado originalmente por maschere:

I recently got a Steam Deck and have begun investigating the issue. The game starts just fine, I can even hit "Play Game" on the virtual laptop and enter the games Main Menu. To my surprise, the whole Python interaction seems to work just fine: The pyjop python module loads correctly in the backgrounds - I can briefly see the python shell pop up. Though once I select an actual level to play, the Deck's screen turns black and nothing further happens. No crash. Nothing. I can then only close the game. I looked into the proton logs - but I do not see anything pointing me in the right direction what might be wrong. These are the last lines of my proton log, if anyone with more Linux / Proton knowledge has an idea what might be going on, I'm all ears.

2840.390:0120:0124:fixme:win:GetPointerDevices (0000000000B9EF34 0000000000000000): partial stub
2840.390:0120:0124:fixme:system:NtUserQueryDisplayConfig flags 0x2, paths_count 0xb9ef00, paths 0x1304006be300, modes_count 0xb9ef34, modes 0x130400561d80, topology_id (nil) semi-stub
2840.390:0120:0124:fixme:system:NtUserDisplayConfigGetDeviceInfo Unimplemented packet type 11.
2840.390:0120:0124:fixme:ui:uisettings2_get_TextScaleFactor iface 00000000337527B8, value 0000000000B9EE10 stub!
2840.409:03b8:0618:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2840.409:03b8:0614:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2840.409:03b8:0610:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2840.412:03b8:061c:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2840.515:0104:0118:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
2840.515:0104:0118:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000B159C0, 10002, 000000000193F8A0: stub
2840.608:0104:0118:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
2840.608:0104:0118:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000B15FB0, 10002, 000000000193F8A0: stub
2844.566:03b8:062c:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"
2855.848:0120:0264:fixme:process:CreateProcessInternalW Unsupported attribute 0x20007.
wine: using kernel write watches, use_kernel_writewatch 2.
wine: overriding CPU configuration, 8 logical CPUs, host CPUs 0,1,2,3,4,5,6,7.
2855.962:0630:0634:trace:seh:sigsys_handler SIGSYS, rax 0xffff, rip 0x600000000005.
2855.962:0630:0634:trace:seh:install_bpf Seccomp filters already installed.
pid 9526 != 9525, skipping destruction (fork without exec?)

Ah, so there's hope this can be fixed... Nice! I just thought you had abandoned the attempts. Indeed, reading the proton log can be quite difficult, and there are a number of extra flags that can be providing via the environment variable WINEDLLOVERRIDES (there's a wine wiki page explaining it in details), so the best is to get that onto the bug report because valve employees, specially kisak-valve (you should mention him with a @ saying you're the game programmer) can tell what's important and of note there. The bug report is here: https://github.com/ValveSoftware/Proton/issues/7539

I did in a moment of frustration wrote a bad review of this game, because I want to play it so much. I'll delete my review right now, because I strongly want this game to succeed and run on Linux.

[uNiels 💗]

FWIW, when I try the game through Proton on all my Linux machines (laptop as well as desktop, but even older than my Windows machine and weaker graphics hardware, though still NVidia non-integrated graphics), the game either complains about too little VRAM (Why does the game need so much? No other games I play does this) or sometimes it starts and then soon just crashes to desktop without indication.

[̋̊̑͂͆̅¢h³MÏǪ£ Ør9]

For what it's worth protondb is a good place to start getting the proton community active in helping to solve proton problems.

[uNiels 💗]

Publicado originalmente por ̋̊̑͂͆̅¢h³MÏǪ£ Ør9:

For what it's worth protondb is a good place to start getting the proton community active in helping to solve proton problems.

I wouldn't outright call it a Proton problem, though, just because it doesn't work there.

Proton/Wine must do a lot of stuff to get native Windows apps to work on a different platform.

For example, the game likely uses DirectX, which is a Windows-only API. So Proton/Wine must use a wrapper and work really hard to map DirectX calls to the native graphics API. That's not always 100% possible, due to some very different paradigms.

To solve this, it would be more desirable for the game to use Vulkan, for instance, if that's possible at all. The Vulkan API is cross-platform (and modern with good performance characteristics), so it would be much more likely to work without hitches on all platforms.

[JoxerTheMighty]

I just realized I somehow never left a review for this game, even though I love it, fixed that now.

Tried with latest stable Proton, Proton Experimental and the latest Proton-GE and same story, I get to the menu, I see a preview of the levels but the game crashes when trying to load one.

I am really looking forward to Linux support, as I don't have Windows anymore these days and want to play more of this

[maschere]

A brief update: I figured out how to deploy my development build on the Steamdeck to try a few things. Turns out I can successfully start any level in the game, if I set the game to directly start in this level. So for some unclear reason, the level transition does not work (it does if I use Unreal console commands to change the level). Really strange.

[maschere]

Good news everyone. I found the issue - a little inconsistency between Windows and Proton: My game spawns a separate Python process and saves the handle. This all works as expected. Sometimes I forcibly close this Python process using

TerminateProcess(
    _In_ HANDLE hProcess,
    _In_ UINT uExitCode
    );

In my calling code, I did **not** check whether hProcess is valid or not and it was indeed sometimes called with a NULL handle. This did not cause any issues under Windows. In Proton however this crashes the whole game. I fixed this by checking for a valid handle and it now seems to work. I will do some further tests and push an experimental branch this week.

[iambiguity.tv]

Publicado originalmente por maschere:

Good news everyone. I found the issue - a little inconsistency between Windows and Proton: My game spawns a separate Python process and saves the handle. This all works as expected. Sometimes I forcibly close this Python process using

TerminateProcess(
    _In_ HANDLE hProcess,
    _In_ UINT uExitCode
    );

In my calling code, I did **not** check whether hProcess is valid or not and it was indeed sometimes called with a NULL handle. This did not cause any issues under Windows. In Proton however this crashes the whole game. I fixed this by checking for a valid handle and it now seems to work. I will do some further tests and push an experimental branch this week.

Will this be on the pre_release branch under Beta?

[maschere]

Yes, I just pushed version 0.7.3 to the pre_release branch.

[iambiguity.tv]

Publicado originalmente por maschere:

Yes, I just pushed version 0.7.3 to the pre_release branch.

This version works for me! No more crashing.

[Falli]

Publicado originalmente por maschere:

Yes, I just pushed version 0.7.3 to the pre_release branch.

Just wanted to give my feedback: It works now, I can finally start with the first level 😲 At least I can play it now when I'm back home from my holiday, I'm totally excited

[Patola [Linux]]

Thanks! I confirm it is working now on Linux!

[Heitor Villa-Lobos]

Publicado originalmente por maschere:

One player had the most recent playtest running under Linux using an emulator. Not sure which one. I'll look into.

Emulator blows!

Please give us a native build for GNU/Linux!

There is no joy running M$ SpywareOS.