Nex Machina (AppID: 404540)

[NRG-R9T]

Compatibility Report

• Name of the game with compatibility issues: Nex Machina
• Steam AppID of the game: 404540

System Information

• GPU: RX 580
• Driver/LLVM version: Mesa 19.1.0/LLVM 9.0.0
• Kernel version: 4.15.0-45-generic
• Link to full system information report as Gist: https://gist.github.com/NRG-R9T/4a6d6bd1306617139e130e701cc755a5
• Proton version: 3.16-6

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-404540.log

https://gist.github.com/NRG-R9T/955635010a1c2b8da6db7be15887d31e

Symptoms

1. It runs perfectly after tweaks (PROTON_NO_ESYNC=1) for 7 Minutes, then freezes the whole PC everytime! I used a stopwatch while I run it for the log provided with this report.
2. It doesn't connect to the online servers too. Screenshot here: https://steamcommunity.com/sharedfiles/filedetails/?id=1654846001

Reproduction

1. Try to play Arcade (Experienced) for more than 7-10 Minutes
2. The Online Arena will be shown as Server unavailable at the main menue.

[Thyre]

I'm having these issues as well. Seems like the game filles the whole RAM during gameplay resulting in freezes because the operating system is swapping.
When I tested it 16 GiB of RAM were filled in about 10 minutes. Maybe some kind of memory leak in combination with Proton? I don't remember having these issues with Windows.

[NRG-R9T]

About the second, not so disturbing problem I found out in the meantime: The Online Arena was shut down by the publisher.

[ipr]

There's a regression with this game: starting a new game from main menu will result in black screen and game never actually finishes loading a level.
I remember this used to work in Proton 6.x? Currently using Mesa 22.0, kernel 5.16.14

Using PROTON_USE_WINED3D=1 works but framerate is very low.

steam-404540.log

[kisak-valve]

Hello @ipr, can you retest and confirm that this game works as expected with an older release of Proton? I'm only really interested in confirming that there's a Proton-sided regression compared to a system change before I add the regression label.

[ipr]

Hello @ipr, can you retest and confirm that this game works as expected with an older release of Proton? I'm only really interested in confirming that there's a Proton-sided regression compared to a system change before I add the regression label.

I tried 6.3 earlier but it did not work, even controller did not work.

But I tested again and with 7.0 I need to have PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 as well as PROTON_USE_WINED3D=1 to make it work. 6.3 does not get into main menu with these.

Edit: now I got into actual game with 6.3, without those options. But controller does not work.

It's a really mixed bag of different options.

[ipr]

Ok, I'm getting into game with 6.3 when I have Steam input enabled. It does not load the level if Steam input is disabled.
Either way, controller does not work with 6.3

Controller works with 7.0, but level does not load unless I specify the three options, which causes bad framerate.
Somehow it seems horribly random if the game works or not.

[ipr]

One more case: with Experimental, level loads when I specify: PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1
Framerate is not good (seems worse than with 6.3) but at least it loads and while controller is operative..

[maxjaudio]

ProtonDB users seem to be getting the best results with the following launch options:
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PULSE_LATENCY_MSEC=60 %command%

[ipr]

Updating that it is playable with Proton 8.0 but you still need to have PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 in launch options.

[Vash63]

Updating that it is playable with Proton 8.0 but you still need to have PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 in launch options.

How long did you test it for? The memory leak is gradual, did you play for at least 30 minutes to an hour?

[ipr]

Updating that it is playable with Proton 8.0 but you still need to have PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 in launch options.

How long did you test it for? The memory leak is gradual, did you play for at least 30 minutes to an hour?

At least game isn't stuck loading a level and you get to play a level. So at least that much.