EmuNewz Network
Dragon Ball Z Shin Budokai - ULES00309 - Printable Version

+- EmuNewz Network (https://www.emunewz.net/forum)
+-- Forum: PSP Emulation (https://www.emunewz.net/forum/forumdisplay.php?fid=191)
+--- Forum: JPCSP Official Forum (https://www.emunewz.net/forum/forumdisplay.php?fid=51)
+---- Forum: Commercial Game Discussion (https://www.emunewz.net/forum/forumdisplay.php?fid=54)
+----- Forum: JPCSP - Playable Games (https://www.emunewz.net/forum/forumdisplay.php?fid=65)
+----- Thread: Dragon Ball Z Shin Budokai - ULES00309 (/showthread.php?tid=1274)

Pages: 1 2 3 4


RE: Dragon Ball Z Shin Budokai - ULES00309 - Zekro - 02-28-2013

(02-28-2013, 07:02 PM)nvidia 1996 Wrote: oigan soy nuevo en esto komo se descargan los juegoz

Translation:How do I download games
Answer:You don't,we don't support piracy here



Respuesta:No puedes,aqui no apoyamos la pirateria


RE: Dragon Ball Z Shin Budokai - ULES00309 - Ansatsuken - 01-23-2014

I lost my old savedata for this game when my HD got corrupted... then I tested it again with r3445 just now, with a brand new savedata. I went straight to Training Mode with normal form Goku and got no crashes (since I didn't unlock any transformations), but endless invalid memory address errors like these:

17:37:39 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B4 PC=0x088EAB08
17:37:44 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x088EAB2C
17:37:44 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500BC PC=0x088EAB44
17:37:45 ERROR memory - user_main - read32 - Invalid memory address: 0x4A656B74 PC=0x088EAB08
17:37:45 ERROR memory - user_main - read32 - Invalid memory address: 0x4A656B78 PC=0x088EAB2C
17:37:45 ERROR memory - user_main - read32 - Invalid memory address: 0x4A656B7C PC=0x088EAB44
17:38:51 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x08808ED8
17:38:55 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B4 PC=0x08809034
17:38:55 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x08808ED0
17:38:56 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B4B8
17:38:56 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x0880B4B0
17:38:56 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B364
17:38:56 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x088084D8
17:38:56 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B4B8
17:38:57 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x0880B4B0
17:38:57 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B364
17:38:57 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x088084D8
17:38:57 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B4B8
17:38:57 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x0880B4B0
17:38:57 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B364
17:38:58 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x088084D8
17:38:58 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x08808D14

These happened in the loading screen and each and every time I used a ki-based attack with Goku, and Goku only. No other character suffered from this issue.

Moreover, a friend of mine tested the US version and got no problem whatsoever, leading me to deduce that this issue occurs in the Japanese version only.

Can this be of any help?


RE: Dragon Ball Z Shin Budokai - ULES00309 - Hykem - 01-24-2014

(01-23-2014, 09:03 PM)Ansatsuken Wrote: I lost my old savedata for this game when my HD got corrupted... then I tested it again with r3445 just now, with a brand new savedata. I went straight to Training Mode with normal form Goku and got no crashes (since I didn't unlock any transformations), but endless invalid memory address errors like these:

17:37:39 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B4 PC=0x088EAB08
17:37:44 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x088EAB2C
17:37:44 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500BC PC=0x088EAB44
17:37:45 ERROR memory - user_main - read32 - Invalid memory address: 0x4A656B74 PC=0x088EAB08
17:37:45 ERROR memory - user_main - read32 - Invalid memory address: 0x4A656B78 PC=0x088EAB2C
17:37:45 ERROR memory - user_main - read32 - Invalid memory address: 0x4A656B7C PC=0x088EAB44
17:38:51 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x08808ED8
17:38:55 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B4 PC=0x08809034
17:38:55 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x08808ED0
17:38:56 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B4B8
17:38:56 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x0880B4B0
17:38:56 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B364
17:38:56 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x088084D8
17:38:56 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B4B8
17:38:57 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x0880B4B0
17:38:57 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B364
17:38:57 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x088084D8
17:38:57 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B4B8
17:38:57 ERROR memory - user_main - read32 - Invalid memory address: 0x4A1500B8 PC=0x0880B4B0
17:38:57 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x0880B364
17:38:58 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x088084D8
17:38:58 ERROR memory - user_main - read16 - Invalid memory address: 0x4A1500A2 PC=0x08808D14

These happened in the loading screen and each and every time I used a ki-based attack with Goku, and Goku only. No other character suffered from this issue.

Moreover, a friend of mine tested the US version and got no problem whatsoever, leading me to deduce that this issue occurs in the Japanese version only.

Can this be of any help?

Hmm, interesting. Could you please post the full log? INFO level should be enough (from when you start the game until these errors show up). Thanks!


RE: Dragon Ball Z Shin Budokai - ULES00309 - Ansatsuken - 01-25-2014

(01-24-2014, 09:38 PM)Hykem Wrote: Hmm, interesting. Could you please post the full log? INFO level should be enough (from when you start the game until these errors show up). Thanks!

Sure. Actually, I'm sending two log files.

.txt   log1.txt (Size: 47.57 KB / Downloads: 122)
In this first one, I encountered that ArrayIndexOutOfBoundsException from my previous save file, which occurred after I decided to choose the stage randomly in Training mode, leading me to believe that this problem is not related to transformations (as I thought before), but to stages.


.txt   log2.txt (Size: 84.64 KB / Downloads: 130)
In this second one, I chose the first stage like I usually do in Training mode (see the screenshot below), and the invalid memory address errors appear in the loading screen and each time I use a basic ki blast, also meaning that continuous blasts like the one depicted below feature this issue as many times as a ki blast attack is used. This issue doesn't occur when using a special move like Kamehameha or Spirit Bomb.

I hope these help.


RE: Dragon Ball Z Shin Budokai - ULES00309 - raziel1000 - 12-17-2018

98227db14a8907d18e42d558ebfdfbcdd96d0be0:

Game still works but bad sound

Code:
ERROR atrac3plus - CRI ADX Audio - Invalid number of quantization units: 29
INFO   stdout - CRI ADX Audio - ADXATR: failed sceAtracDecodeData ret=80630002  InternalError=0x0

Code:
ERROR atrac3plus - CRI ADX Audio - Invalid start bit
INFO   stdout - CRI ADX Audio - ADXATR: failed sceAtracDecodeData ret=80630002  InternalError=0x0



RE: Dragon Ball Z Shin Budokai - ULES00309 - raziel1000 - 12-20-2018

(12-17-2018, 08:52 PM)raziel1000 Wrote: 98227db14a8907d18e42d558ebfdfbcdd96d0be0:

Game still works but bad sound

Code:
ERROR atrac3plus - CRI ADX Audio - Invalid number of quantization units: 29
INFO   stdout - CRI ADX Audio - ADXATR: failed sceAtracDecodeData ret=80630002  InternalError=0x0

Code:
ERROR atrac3plus - CRI ADX Audio - Invalid start bit
INFO   stdout - CRI ADX Audio - ADXATR: failed sceAtracDecodeData ret=80630002  InternalError=0x0

FIXED!