Rendering errors on Dragon Ball Raging Blast 2 Demo [NPEB90287]

[woj1993]

If you play game for the first time as (goku super sayan or Dabura) it will throw many unknow command errors and there will be many graphical glitches (especially on goku) for example:

Log+shaders cache+shaders log:
Dragon Ball Raging Blast 2 Demo Schaders+Logs.zip
Also if you try to reload it will trow many other RSX errors (this log)[it crashed before going into game]:
Dragon Ball Raging Blast 2 Demo.zip
My CPU is Intel(R) Core(TM) i5-2300 CPU
@ 2.80GHz.
RAM:4GB
GPU: ASUS NVIDIA GT440 1GB GDDR3 OpenGL
Edit: Dabura has more interesting error: RSX: Texture unit 3 is sampled as both a shadow texture and a depth texture
Dabura Log:Dragon Ball Raging Blast 2 Demo Dabura Schaders.zip
P.S. If something else is needed tell me.

[AniLeo]

Needs retesting on latest master.
If someone has a more recent GPU please test this game on both OpenGL and Vulkan to see if the issue is there.

needinfo: Testing on Vulkan + Testing on OpenGL with modern GPU

Also, forum thread needs updating: https://forums.rpcs3.net/thread-173766.html

[woj1993]

@AniLeo I tested in on master (Date: 11-10-2017) and it stil has the same errors.
Log: RPCS3.log.gz
Sorry I can't help you with more recent GPU tests but from what I see error was on Vulcan too (watch last video from forum thread. He tested it on NVIDIA GeForce GTX 1050 Ti 4 GB and test was on 20-09-2017).

[AniLeo]

Clothing still flickers and there's RSX method flood, probably a corruption issue

[MarioSonic2987]

@benderscruffy
Shadows are working with a GTX 970 in both backends:

[MarioSonic2987]

@benderscruffy No. It doesn't require any special setting. It could be an AMD-specific bug.

[kd-11]

Probably caused by the same issue as #6701 (Bad AMD drivers for old cards). Same suggestion applies here; give linux+mesa a try.

[woj1993]

@kd-11 I want to ask: Do you want/need RSX Capture?
If so how to do it?

[kd-11]

For memory corruption? No. That just means the emulator is in a broken state. Even if I replayed the capture on a real PS3 it would still be broken.
EDIT: Has this bug still evident in its original form? If not, update.