RPCS3 Forums

RPCS3 v0.0.2-3-c4066b9 Alpha

Quote:·E 0:00:11.444014 {rsx::thread} RSX: Invalid RSX method 0xc0c0 (arg=0xc0c0c0c0)
(in file C:\rpcs3\rpcs3\Emu\RSX\rsx_methods.cpp:36)

RPCS3 v0.0.4-6091-c5873880 Alpha | HEAD
The game freezes after pressing START.

RPCS3 v0.0.4-6279-f271b650 Alpha | HEAD
Ingame with libaudio.sprx.

Any updates on this one? :-)

RPCS3 0.0.13-11342-d1e78374 Alpha, Firmware version: 4.86, BLUS30650 version 01.05

Current status with default config is In Game.  Lots of hitching, with patches of smooth behavior.  Lots of things compiling that cause some of the hitching.

If your machine can handle it, GPU->Multithreaded RSX to Enabled gets rid of most of the hitching and the framerate smooths out to a nice solid 30fps.  If that's an acceptable requirement, and the below bugs found thus far aren't barring (and no game breaking bugs are found during a play through), i'd suggest this be moved to Playable.

One bug that effects both this game and Mass Effect 1 BLUS31139 is the character name entry screen.  It won't progress unless you modify the name.  I added a space to make it happy.


There's a couple missing shaders or textures (example here in from the first conversation choice in game)


That said, the framerate is smooth on my machine at 30fps even in combat and there don't appear to be massive graphical issues thus far (beyond the above)







I haven't played all the way through yet so no idea if there are major blocking bugs.

Intel Core i5-9600k
EVGA RTX 2070 SUPER XC Ultra Gaming
32GB G Skill F4-3200C16-16GVK

I decided to give this game a try as I had never played beyond the first game. Got it running pretty well, played about 7 hours without any major problems. Got to the end of the Stolen Memory quest and no matter what I try it always crashes as soon as Donovan Hock's chopper blows up. I've played through Demon Souls, Dark Souls, and Dead Space with no issues, this is the first game with progress blocking issues.

I linked a screenshot of the crash.

[attachment=28342]

Edit: Just wanted to update that I got past this sticking point by setting my Shader Mode to Legacy and turning Framelimit to Off. Since getting past this point, I set Framelimit back to Auto and Shader Mode back to Async Multi-threaded: haven't had a single issue occur in over 18 more hours of playtime.