RiME (493200)

[NoXPhasma]

Compatibility Report

• Name of the game with compatibility issues: RiME
• Steam AppID of the game: 493200

System Information

• GPU:GTX 1080
• Driver/LLVM version: nvidia 396.54.09
• Kernel version: 4.18
• Link to full system information report as Gist: https://gist.github.com/NoXPhasma/9ed85e6b0602b656c812acd013ee121f
• Proton version: 3.16-3

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-493200.log

Symptoms

• Game crashes after a few minutes
  • can be fixed by disabling esync
• Gamepad (XBOX One S) doesn't work properly
  • button and axes binding is messed up
  • buttons seem to repeat on hold
  • triggers force camera movement forever
  • can be fixed by installing dinput8 and set it to native
• Audio is messed up (crackling and stopping sounds)
  • can be fixed by installing xact and set xaudio2_7 to native

Reproduction

• Start the game and try to play, after a few minutes it will crash
• try to play with the gamepad

[ABelliqueux]

I confirm these issues and workarounds work.
Game is semi playable with shadows on low and textures on medium, AA FXAA or TXAA.

EDIT: I noticed I need to go in the Parameters menu before beginning a game in order for the graphics to show (the nightsky with stars). Else, it only displays full screen colors.

The pause menu sometime crashes and I have to Alt+F4 out of the game.
Xbox360 gamepad works fine. Xbox360 gamepad seems to suffer the issues mentioned above.

System:
GPU:GTX 1050
Driver/LLVM version: nvidia 410.66
Kernel version: 4.14.77 ( MANJARO )
Proton version: 3.16-3

Not sure my input is useful...If you need logs, I can provide if you tell me where to look.

[kisak-valve]

Hello @NoXPhasma, since disabling esync makes a difference, please run ulimit -Hn and confirm that it is a high value and not 4096.

[NoXPhasma]

@kisak-valve ulimit -Hn reported indeed only 4096. I raised it to 1048576 and confirmed that ulimit -Hn reports that value. However, the game still crashes with esync enabled.

steam-493200.log

[dubigrasu]

I have the system already set to 1048576, but with esync enabled the game also crashes with the same "buffer overflow detected".

[ryao]

I cannot reproduce the esync issue. I have an issue with the mouse where I cannot turn a full 360 degrees. I am using libinput 1.10.7. Installing dinput8 didn't solve it for me. I did not probe further.

[zfigura]

36865.503:0025:006a:trace:module:MODULE_InitDLL (0x7fed7a450000 L"secur32.dll",PROCESS_ATTACH,(nil)) - CALL
*** buffer overflow detected ***: Z:\media\daten\SteamApps\steamapps\common\RiME\SirenGame\Binaries\Win64\RiME.exe terminated
36865.504:0025:006a:trace:seh:NtRaiseException code=80000101 flags=1 addr=0x7fee2b604e97 ip=7fee2b604e97 tid=006a`

This looks suspiciously like a broken setup, but regardless let's see if there's something wrong with esync here. Can you please provide a log with +esync added to the debug flags?

[NoXPhasma]

@zfigura Sure, the whole log file is now over 250MB, so here's a short cut out with the most interesting stuff: steam_493200_short.log

And here the full log file: https://mega.nz/#!XAcwza4B!MHAYrKxCPlsKOl3Ewm_eShEFeAqrUArPSxqqol-jYYs

[NoXPhasma]

Because it was requested on Discord, I tried to run it with Steam stable and by that with the old runtime version. But it also crashes when esync is enabled.

[dubigrasu]

As I said earlier, I also have the game crashing with a "buffer overflow detected" on my Ubuntu 18.04, with esync enabled.
However, on my second system (Steamos) the game works normally even with esync enabled.
Both systems have DefaultLimitNOFILE=1024:1048576 set.

If needed:
Ubuntu sysinfo: https://gist.github.com/dubigrasu/b6456765ed79f04dbe7c575f002a3fa6
Ubuntu steamlog (+esync): http://s000.tinyupload.com/index.php?file_id=01539556292600246335
Note that I'm receiving the message:

*** buffer overflow detected ***: Z:\home\steam.steam\steam\steamapps\common\RiME\SirenGame\Binaries\Win64\RiME.exe terminated

only in steam console, not in the steamlog.

SteamOS sysinfo: https://gist.github.com/dubigrasu/eea0535232350fb64d6032ec0ec00b51
SteamOS steamlog* (+esync): http://s000.tinyupload.com/index.php?file_id=57794387178359264464

*On SteamOS I played a bit longer to make sure the esync crash doesn't occur, and the steamlog files are pretty big (up to 400MB), so I have the uploaded files archived first with 7z.

Related to this, I have noticed the same behaviour with at least one other game (Seven: The Days Long Gone), as in: with esync enabled the game crashes on Ubuntu, but works perfectly on SteamOS.

with esync enabled the game crashes on Ubuntu, but works perfectly on SteamOS.

Perhaps differences in packages? I wonder if the Steam flatpack version would change anything here.

I'm finding that errors in the log can be a bit misdirected and of course there are errors that can be ignored but its difficult to say which can or can't be.

[ryao]

I just made a fresh wine prefix for Proton 3.16-5. The game crashes on an unimplemented function:

wine: Unimplemented function secur32.dll.AcquireCredentialsHandleW called at address 0x7b44af1c (thread 0067), starting debugger...
27500.568:0024:0067:trace:seh:start_debugger Starting debugger "winedbg --auto 36 5748"
ERROR: ld.so: object '/home/richard/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
27502.454:0024:0067:trace:seh:call_teb_handler handler at 0x7bcbebf0 returned 1
Unhandled exception: unimplemented function secur32.dll.AcquireCredentialsHandleW called in 64-bit code (0x000000007b44af1c).

I have not tried it in a while, so I don't know if this is a regression caused by a game update or a regression in Proton's wine.

[unit73e]

Game seems to work fine with the latest Proton.

System Information

• GPU: AMD R9 380
• Driver/LLVM version: Mesa 18.3.1
• Kernel version: 4.19.12
• Proton version: 3.16-6 Beta

Fixed

• The game does not crash. I did not disable esync.
• I did not experience any sound issues.

Not Fixed

The PS4 controller is not working properly. So far I found these issues:

• Pressing up or down moves on the menu moves much more than excepted
• Pressing the triggers will either zoom or rotate forever

From my experience many games mix joystick api with evdev and this could be the case.

[mimattr]

Game seems to work fine with the latest Proton.

@unit73e Agreed, the application appears to work as expected with Proton 3.16-6 Beta except analog gamepad input is not interpreted correctly/overly sensitive (tested on Steam Controller and official wired Xbox 360 Controller).

steam-493200.log

Steam System Information