Can conform it works full speed.
It froze for me once when i alt+tabed douring a cutscene but that can be on my end.
I just restared from the last checkpoint. Nothing bad.
my steam info:
https://gist.github.com/Zero86Sk/d629f657c1ae861c36657cdf238a7765
Runs fine here, you have to double alttab to go into desktop. DS4 controller is being properly mapped.
https://gist.github.com/daasuharo/d83c92ac04a9bd0c5edfc359c3c5a4de
Castlevania : Lords of Shadow Ultimate Edition - crash at start up
Issue transferred from https://github.com/ValveSoftware/Proton/issues/1960.
@darkpumpkins posted on 2018-11-13T22:51:34:
steam-234080_chunk.log
I had to take a piece of the log cause it reached more than 70Mb ....
The game doesn't launch at all. i try with all version of proton, with a GTX 970 and a GTX 1070 ti on both gnome-shell or openbox Window manager.
Just run the game with any version of proton.
Found in the 2018-12-11 white list update.
Tested with proton 3.16-4 and 3.16-16. It is working fine. One line from the user log is particular interesting.
50214.785:0008:0009:warn:module:load_dll Failed to load module L"gameoverlayrenderer.dll"; status=c0000135
It's either a problematic installation or the module indeed failed to load on specific setup.
got the same issue on proton 4.2.3, Ubuntu 18.04
System Informaton
GPU: RX480 8G
Driver/LLVM version: Mesa 18.2.2, LLVM 7.0.0
Kernel version: 4.18.0-15-generic
Link to full system information report as Gist: steam-234080.log
Proton version: 4.2.3
The issue seems pretty straightforward:
ERROR: ld.so: object '/home/kirgahn/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Don't know why it complains about the library being compiled for amd_64, perhaps related to the prefixes wine_arch being x86_32?
Edit:
bit more in detail:
wine: Unhandled page fault on read access to 0x00000000 at address 0x432d65 (thread 0009), starting debugger...
346445.343:0008:0009:trace:seh:start_debugger Starting debugger "winedbg --auto 8 140"
ERROR: ld.so: object '/home/kirgahn/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
346446.139:0008:0009:trace:seh:call_stack_handlers handler at 0x7b4853f0 returned 1
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00432d65).
This seems to crash proton
Right. The dll ignored error is due to LD_PRELOAD with different architecture. This shouldn't cause a error besides a warning.
Is there a clean way to override the steam runtime LD_PRELOAD path?
I've tried to pass the 32bit gameoverlayrenderer.so using the steam launch properties with both LD_PRELOAD and LD_LIBRARY_PATH to no avail.
The 64bit binary is fed to the game anyway, probably due to the fact that the amd_64 distro of the steam runtime is included before the game launch options.
Is there a clean way to override the steam runtime LD_PRELOAD path?
There is no need. As I said, that will cause a warning and that's all it does. It's not the problem why this game crashed.
The game no longer crash at startup ( and seems to work pretty good ).
=> Proton version 3.16-4 ( selected by valve )
LOG:
steam-234080.log
Crash on startup, no window
@shoober420, same assessment as https://github.com/ValveSoftware/Proton/issues/764#issuecomment-600590478.
LOG:
steam-234080.log
Works great out of the box.
The game works like a charm with Proton 7.0-6 up to 10.0-4. I did not test older versions. Using Proton 11.0 and experimental (bleeding edge) the game emits an extremely loud buzzing noise that won't stop and increases in volume until the game is closed.
GPU: AMD Radeon RX 7900XTX
Driver/LLVM version: Mesa 26.1.4
Distro version: CachyOS
Proton version: 10.0-4
Steam System Information: https://gist.github.com/Mr-nUUb/4aa8587c32a6a5dbdf8dc70e876eb7f2 (german)
@Mr-nUUb I haven't been able to reproduce the issue. Could you add PROTON_LOG=+tid,+seh,+mmdevapi,+winmm,+driver,+msacm,+midi,+dsound,+dsound3d,+xaudio2,+xapofx,+dmusic,+mci,+pulse,+oss,+alsa,+coreaudio,+timestamp %command% to the launch options, reproduce the issue, then upload the log from your home directory?
@codeweaverwill Here's the log of Proton Experimental Bleeding Edge. I use a virtual 7.1 surround setup (pipewire filter chain) with an equalizer preset for my headset. Don't know if that matters.
proton experimentalx1 2026-07proton 11.0x1 2026-07proton 7.0-6x1 2026-07proton 4.2x1 2019-04proton 3.16-4x1 2019-01gameoverlayrenderer.dllx1 2019-01
Works fine for me. Pls add to whitelist. My specs - https://gist.github.com/GriefNorth/7f4820f319fda7e45ff44c5b83c20cd0