protonscr

Lucent Heart crashes upon entering world

protonopen appid 283060Game compatibility - Unofficial
ValveSoftware/Proton#3715 · opened 2020-04-01 by aljelly · updated 2020-04-01 · 2 comments · github · game page · search this game
Aaljelly 2020-04-01 github

Compatibility Report

  • Name of the game with compatibility issues: Lucent Heart
  • Steam AppID of the game: 283060

System Information

  • GPU: RX 580
  • Driver/LLVM version: Mesa 19.2.8
  • Kernel version: 5.3
  • Link to full system information report as Gist: (will supply if necessary)
  • Proton version: 5.0-5

I confirm:

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

Symptoms

The game crashes when you try to enter the game's world. Everything before (e.g. creating a character) works fine.

Unfortunately the game will hang after logging into a server if PROTON_LOG=1 %command% is added to the launch options of the game. This happens before one can try entering the game's world so I can't show logs for the specific moment where it crashes. Maybe I could try using specific Wine log options to get around this, I'll update if I manage to do so.

Reproduction

  1. Download the game (free) and launch.
  2. Allow the patcher to patch the game.
  3. Check for updates with the patcher, this could take up to 12 hours and it can crash during the process (it picks up where it left off though, so update progress is not lost).
  4. Launch the game, make an account, link to Steam account, relaunch the game
  5. Enter a server (just click "Enter", the default/first one is probably fine) (don't stay on this screen for too long as otherwise it will kick you off)
  6. Create a character (click "Create", bottom right, fill in character information with anything, don't hang around on this screen for too long either)
  7. Click "Enter" (bottom right again)
Aaljelly 2020-04-01 github

Update, the black screen hanging upon logging into server with PROTON_LOG=1 only happens when +seh is specified. Using user_settings.py and removing that channel from WINEDEBUG prevents the hanging upon server log in.

I've got 2 logs at the time of crash (when trying to enter the game world, no hang on server log in) with the following WINEDEBUG settings:

  • +timestamp,+pid,+tid,+debugstr,+loaddll,+mscoree,+relay,+msgbox,-seh (from what I remember)
  • +timestamp,+pid,+tid,+debugstr,+loaddll,+mscoree,+all,-relay,-snoop,-heap,-font,-msvcrt,+msgbox,-seh

The +relay one is 3GB (even with many RelayExclude and RelayFromExclude additions) and the non-relay +all one is 1.6GB. Here's the latter one first, download it and open it with less (right click and save link as):

https://aljelly.keybase.pub/linux related/steam-283060-norelay.log

Once in less, press End to go to the end of the file (cancel generating line numbers if it tries to, Ctrl + C), search for "msgbox" and then press Shift + N to search backwards. The msgbox trace line(s) will include something like "Client Crash!, Log File at...".

If the +relay one is wanted I'll upload that as well.

(Edit: I might also try using native DLL versions of libraries mentioned in the log around the time of crash like gdi, quartz, dsound, etc. to see if I can get it working. Might also help narrow it down if I can overload them one at at time and one of them works. I'll make a backup of the pfx beforehand.)

Aaljelly 2020-04-01 github

Native dsound alone seems to make no difference, native quartz alone crashes with a "Client Crash!" message box upon server login (before entering game world). Adding both native DLLs make the game hang on server login (but not crash with the message box).

Native gdiplus seems to make no difference.

I wonder if the game is trying to play a movie when it crashes? (there is a data/Movie folder with .wmvs) actually not sure if this has anything to do with it

Launch options