09-20-2017, 01:52 AM
10-11-2017, 04:17 AM
Broken. Crash as soon as the game starts on latest builds.
F {PPU[0x1000000] Thread (main_thread) [0x01944414]} MEM: Access violation writing location 0x0
https://ci.appveyor.com/project/rpcs3/rp...0.0.3-6398
F {PPU[0x1000000] Thread (main_thread) [0x01944414]} MEM: Access violation writing location 0x0
https://ci.appveyor.com/project/rpcs3/rp...0.0.3-6398
10-11-2017, 10:35 AM
tried on revision 11/10/2017 today
game does nothing
F {PPU[0x1000000] Thread (main_thread) [0x01944414]} MEM: Access violation writing location 0x0
game does nothing
F {PPU[0x1000000] Thread (main_thread) [0x01944414]} MEM: Access violation writing location 0x0
03-28-2018, 07:32 PM
Hey guys,
Any updates on this?
Any updates on this?
03-29-2018, 05:36 AM
On the US version:
I can start Tackle Alley for a few secs before getting a MEM: Access violation.
Also as you can see, the recent changes by KD-11 regressed the game (two screen effect).
Same behavior observed in the arcade game Backbreaker Vengeance.
I can start Tackle Alley for a few secs before getting a MEM: Access violation.
Also as you can see, the recent changes by KD-11 regressed the game (two screen effect).
Same behavior observed in the arcade game Backbreaker Vengeance.
03-29-2018, 10:19 PM
Half-screen isn't a regression kd-11 basically removed some ugly work-around that caused a couple games such as this one to not render properly. However since kd made the code more accurate this is not a regression. I'm sure it will be fixed eventually, though.
07-18-2018, 12:47 AM
The half-screen issue is fixed as of last month, this may be playable now.
07-18-2018, 02:32 AM
Sadly, not quite yet.
Vulkan is broken gfx:
https://github.com/RPCS3/rpcs3/issues/4775
OpenGL doesn't really have that issue, but runs anywhere from 100% to 65% speed.
Also, the game is not stable and will spit out a mem error after a few mins of play (timing varies). I couldn't find a fix for that yet.
Vulkan is broken gfx:
https://github.com/RPCS3/rpcs3/issues/4775
OpenGL doesn't really have that issue, but runs anywhere from 100% to 65% speed.
Also, the game is not stable and will spit out a mem error after a few mins of play (timing varies). I couldn't find a fix for that yet.
01-15-2019, 12:38 AM
01-15-2019, 04:56 PM
Game should be mostly playable now. Needs WCB on to avoid cache issues, and WCB+Blit to fix VK regression. SPU LLVM is also broken, so in general you have perf issues with fixed gfx or full speed with gfx issues atm.
Only runs at 60% speed though because:
Needs WCB to avoid this issue (big speed hit):
https://github.com/RPCS3/rpcs3/issues/5020
VK is broken without Blit (big speed hit) - Opengl doesn't need Blit but is just slow:
https://github.com/RPCS3/rpcs3/issues/4775
And SPU LLVM is broken (was fine before):
https://github.com/RPCS3/rpcs3/issues/52...-453853442
If any of those gets fixed, perf might be fine and then playable (I'm on a i7 6700k @4.5, Nvidia 1080,16 gb, Win10).
Backbreaker Vengeance is the same (same engine).
Only runs at 60% speed though because:
Needs WCB to avoid this issue (big speed hit):
https://github.com/RPCS3/rpcs3/issues/5020
VK is broken without Blit (big speed hit) - Opengl doesn't need Blit but is just slow:
https://github.com/RPCS3/rpcs3/issues/4775
And SPU LLVM is broken (was fine before):
https://github.com/RPCS3/rpcs3/issues/52...-453853442
If any of those gets fixed, perf might be fine and then playable (I'm on a i7 6700k @4.5, Nvidia 1080,16 gb, Win10).
Backbreaker Vengeance is the same (same engine).