Dragon Ball Z - Battle of Z [BLUS31314]

RPCS3 v0.0.3-5511-386ff781
game hangs shortly after starting with a "Access Violation Writing Location" error, doing things such as changing interpreter can shorten or lengthen the amount of time before the freeze, with the furthest being after the logos (before the intro, as screen fades to black). Using the same settings described in http://www.emunewz.net/forum/showthread.php?tid=177880

Using a Nvidia Geforce GTX970, with a Intel® Core™ i7-4790 CPU @ 3.60GHz | 8 Threads | 15.95 GiB RAM | AVX

As of testing this game on 09-02-17, It seems you can go in-game, but the graphical glitches are still too much to deal with in-game.



PC Specs:
CPU | AMD Athlon X4 860k
GPU | Zotac GTX 750Ti
RAM | 16GB

Rpcs3 0.0.3 - Dragon Ball Z Battle of Z Vulkan
https://www.youtube.com/watch?v=o9ORJ0I9HfE

A youtube video is not enough for a compatibility report please read https://forums.rpcs3.net/thread-196671.html we require a RPCS3 version identifier that includes the commit (easiest just to copy paste the full version info from the log). Finally we need the rpcs3 log file attached to your post otherwise the thread can not be moved.

In preparation for upcoming changes to the compatibility database, this thread is being moved to Playable. Due to other threads for the same media (Disc or PSN) already being in that category.

Tested with: v0.0.4-6252-a08e79f4 Alpha

Game no longer playable on newer builds.

Used rpcs3-v0.0.5-6957-af62c92b_win64 and game hangs at the "Bandai Namco Games" startup screen with this error:

Code:

F {PPU[0x1000000] Thread (main_thread) [0x00716a68]} MEM: Access violation reading location 0xbfffff38

Please see log attached in my post about the NPEB version.

Also tried NPUB, NPEB and BLUS versions, all gave same results.

Using older builds, like rpcs3-v0.0.5-6696-dca6f1f8_win64, the game works perfectly and full speed etc. All versions.