08-14-2017, 10:55 PM
Pages: 1 2
09-20-2017, 09:38 AM
RPCS3 v0.0.3-3-5c93ace Alpha | HEAD
AMD FX™-8320 Eight-Core Processor | 8 Threads | 4.00 GiB RAM | AVX
PPU : REcompiler
SPU : Recompiler
SPU Threads : Auto
Automatically Load Required Libraries
GPU : Vulcan
Geting from 30 to 57 FPS on my GTX 650. It depends on loaded map ^^
AMD FX™-8320 Eight-Core Processor | 8 Threads | 4.00 GiB RAM | AVX
PPU : REcompiler
SPU : Recompiler
SPU Threads : Auto
Automatically Load Required Libraries
GPU : Vulcan
Geting from 30 to 57 FPS on my GTX 650. It depends on loaded map ^^
02-09-2018, 01:51 AM
Game works perfect for me. I definitely think this game should be upgraded to playable, unless I'm missing something.
02-09-2018, 12:07 PM
Needs a proper report submitted for it to be moved.
02-09-2018, 09:33 PM
02-10-2018, 02:56 AM
Build: rpcs3-v0.0.4-2018-02-09-cce0ad0c_win64
It seems to run at full speed in multiple stages while others it doesn't. (60-40 fps)
Tested only on Vulkan.
Haven't found any other issues on my 8min playthough
Video: https://youtu.be/ZnAxG8XUurM
It seems to run at full speed in multiple stages while others it doesn't. (60-40 fps)
Tested only on Vulkan.
Haven't found any other issues on my 8min playthough
Video: https://youtu.be/ZnAxG8XUurM
03-30-2018, 01:56 PM
0.0.5-6605 (2c16ddd) Alpha, Haswell i5, 970GTX
- OpenGL
~52 fps
Missing GFX effects
Music and sound effects may stop playing in some stages
- Vulkan
Full speed
Missing GFX effects
Music and sound effects may stop playing
Crashes RPCS3 when exiting a fight to Menu
Both logs attached
- OpenGL
~52 fps
Missing GFX effects
Music and sound effects may stop playing in some stages
- Vulkan
Full speed
Missing GFX effects
Music and sound effects may stop playing
Crashes RPCS3 when exiting a fight to Menu
Both logs attached
11-19-2018, 03:17 PM
Build: rpcs3-v0.0.5-7504-634a5fa3_win64
Intel® Core™ i5-4670K CPU @ 3.40GHz | 4 Threads | 15.85 GiB RAM | AVX+
NVIDIA GTX 980
PPU : LLVM Recompiler
SPU : ASMJIT Recompiler
SPU Threads : Auto
GPU : Vulkan
Performance regression.
Went from a locked 60fps to ~30 fps.
Hit effects have disappeared. They were present in earlier October builds.
Intel® Core™ i5-4670K CPU @ 3.40GHz | 4 Threads | 15.85 GiB RAM | AVX+
NVIDIA GTX 980
PPU : LLVM Recompiler
SPU : ASMJIT Recompiler
SPU Threads : Auto
GPU : Vulkan
Performance regression.
Went from a locked 60fps to ~30 fps.
Hit effects have disappeared. They were present in earlier October builds.
04-22-2019, 01:26 PM
Build: rpcs3-v0.0.6-8004-258df80b_win64
i5-2500K @4.5GHz | 16 GB RAM
NVIDIA GTX 1060 6 GB
PPU : LLVM Recompiler
SPU : ASMJIT Recompiler
GPU : Vulkan
Not working properly.
~45 fps during intro video and menu
~30 fps during battle
Crashes "randomly"
i5-2500K @4.5GHz | 16 GB RAM
NVIDIA GTX 1060 6 GB
PPU : LLVM Recompiler
SPU : ASMJIT Recompiler
GPU : Vulkan
Not working properly.
~45 fps during intro video and menu
~30 fps during battle
Crashes "randomly"
08-14-2019, 07:40 PM
The fix I'm about to share is for Tekken 5 Dark Resurrection Online (NPUB30009), but hopefully it'll work for this game too. If you refer to this thread I had spoken to a developer that located the source of the game's performance regression and had been offered a solution. As a result, the game is now flawless for me on the latest build(8478), 60fps on all stages, not a crash in sight(at least from the decent bit I've played so far). All this on modest CPU specs as I have an i5 [email protected], 8gb RAM, GTX 1070. Hope this helps someone looking for a fix.
edit: newer updates of RPCS3 have changed the location of the "Maximum Number of SPURS Threads " option that you have to change from "Unlimited" to "3" in order to restore perfect performance. It is now located under the "Advanced" tab, so you no longer have to do the .ini edit to reveal the option in the usually hidden "Debug" tab.
edit: newer updates of RPCS3 have changed the location of the "Maximum Number of SPURS Threads " option that you have to change from "Unlimited" to "3" in order to restore perfect performance. It is now located under the "Advanced" tab, so you no longer have to do the .ini edit to reveal the option in the usually hidden "Debug" tab.
Pages: 1 2