RPCS3 Forums

RPCS3 v0.0.2-3-6548807 Alpha
Black screen only.

Which game is this? MotorStorm: Complete, or the standard game, MotorStorm (no 'Complete')? Complete is the Japanese re-release.
EDIT: It is supposed to be MotorStorm. Please change the name to 'MotorStorm' only, Complete was only made for Asia.

RPCS3 v0.0.3-3-882e949 Alpha
LLVM + ASMJIT

Fails trying to load the Video... attract.m2v



W {PPU[0x1000000] Thread (main_thread) [0x00e6dec0]} sys_fs: 0xc0000006: 0x20, 0x10, 0x18, “/dev_bdvd/PS3_GAME/USRDIR//gui\video\attract.m2v”, 0x0, 0x80010003, 0x0
W {PPU[0x1000000] Thread (main_thread) [0x00e6eee4]} sys_fs: sys_fs_stat(path=“/dev_bdvd/PS3_GAME/USRDIR//gui\video\attract.m2v”, sb=*0xd003fc98)
E {PPU[0x1000000] Thread (main_thread) [0x00e6eee4]} 'sys_fs_stat' failed with 0x80010006 : CELL_ENOENT, “/dev_bdvd/PS3_GAME/USRDIR//gui\video\attract.m2v” [1]
W {PPU[0x1000000] Thread (main_thread) [0x00e6dec0]} sys_fs: 0xc0000006: 0x20, 0x10, 0x18, “/dev_bdvd”, 0x0, 0x80010003, 0x0
W {PPU[0x1000000] Thread (main_thread) [0x00e6eee4]} sys_fs: sys_fs_stat(path=“/dev_bdvd”, sb=*0xd003fbc8)
W {PPU[0x1000000] Thread (main_thread) [0x00e6eee4]} sys_fs: sys_fs_stat(path=«NULL», sb=*0xd003fc98)
F {PPU[0x1000000] Thread (main_thread) [0x00e6eee4]} MEM: Access violation reading location 0x0

RPCS3 v0.0.4-6269-58d8d126 Alpha
Intro


Some people managed to get ingame, but for me it would just hang after clicking play on the title screen.

Ingame as reported in the US version thread
https://forums.rpcs3.net/thread-197784.html

Nov 7 2018 build #5314 we can select a car and enter a race. After the countdown the game locks up.

v1831240.0.5-7593 Alpha [2018-12-20]

In game, can play for a few minutes, then freezes.  Progress is good! 

RPCS3 0.0.6-7807-4c72f7c1 Alpha

This game has improved vastly over the past months. The game no longer crashes, and can be ran with the faster PPU / SPU settings, yielding a mostly stable 30fps on my system, up from the previous 4-5 fps and crashes 9/10 times.
I imagine it'll be more difficult to run with playable framerate on systems with slower CPUs, however.

There are still occasional framedrops and various visual bugs.
Some of the visual bugs can be quite jarring. In some stages, the cars will inexplicably judder back and forth (possibly a motion blur problem?).
So even if it was possible to run this stably on an i5 or i7, I think the current visual bugs still land this in the "ingame" category.

Vulkan (1280 x 720)
Write Color Buffers on
PPU: LLVM
SPU: LLVM

CPU: i9-7900X @4.2Ghz
GPU: GTX 1070Ti
RAM: 32GB



This is an unedited Shadowplay recording.
Feel free to use this footage.

I saw heavy juddering too, but only in various windows appveyor builds. On linux, in v0.0.6-8034-be6d9af1 (built with clang7 -march=native) I saw no single judder at all, so it might be an OS/compiler-specific issue.
Linux log: https://drive.google.com/file/d/1MC1Uv27...sp=sharing
The similar situation I observe with Condemned 2: Bloodshot, which heavily flickers on windows, but doesn't flicker at all in my local linux builds.

Here are some of the issues still remaining in the Windows build using the settings mentioned above: (tested on 6-1-2019 build)

- Vehicle warping back and forward. Happens at the beginning of every race, and randomly throughout the race. Maybe a float position math function issue?

- Textures on the vehicle and on the ground will randomly warp in and out or textures will become corrupted for a few seconds.

- Music can sometimes pause for a millisecond randomly throughout gameplay.

- Playing on 1080p instead of the native 720p will make the game loading take at least 3x longer than normal, and races start 3x slower.

- Mud and fire 2d textures from the vehicle are not transparent.

- Fences on the Mudpool track will randomly turn blue and green at the start of the race.