-
-
Notifications
You must be signed in to change notification settings - Fork 842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CUSA00900 Bloodborne crashes on startup on Linux #1890
Comments
There was a problem with some versions. Is it possible to test again with the latest version? |
I had the same issue on
Compiled from source on nix with this in my system config file (as the current package version is nixpkgs.overlays = [
(final: prev: {
shadps4 = prev.shadps4.overrideAttrs {
src = pkgs.fetchFromGitHub {
owner = "shadps4-emu";
repo = "shadPS4";
rev = "a1a98966eee07e7ecf3a5e3836b5f2ecde5664b0";
hash = "sha256-lN+qXvf+rHlfZt7iT/De/tMvAQJpqLGOJxrv9z4tX5c=";
fetchSubmodules = true;
};
patches = [];
};
})
]; |
The command ~$ DISPLAY=:0 /path/to/Shadps4-qt.AppImage has helped me at least boot the game and get past the black screen crash. The game still is running horribly for character creation and then crashes after it. |
Tried again with newest version, exact same thing happens whether pro mode is enabled or not. |
Trying to run Bloodborne (CUSA00900) results in a crash with the following error:
[Debug] <Critical> signals.cpp:SignalHandler:85: Unreachable code!
Unhandled access violation in thread 'GAME_MainThread' at code address 0x56547a5e4f0c: Read from address 0x0
Tried enabling and disabling "show splash", using X11 instead of Wayland, using gamescope, unsetting the
DISPLAY
andWAYLAND_DISPLAY
variables.Specs: Ryzen 5 7600, Radeon RX 6700XT, Fedora 41, Kernel 6.12.5, Plasma 6.2.4 Wayland
EDIT: Upload log
shad_log.txt
The text was updated successfully, but these errors were encountered: