Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Resolved [Bug Report] Tales of Rebirth [NTSC]
#1
# Pcsx2 version: pcsx2-r720
# Cpu eerec on, vurec0 and vurec1 on, MTGS on
# Plugins used: Gsdx 594 SSE2 0.1.14, SPU2-x 1.1.0
# Description:
The game freeze after open a treasure box.
However, if you talk to a NPC first and then open the treasure box, you can bypass this bug. (I wonder if this has to do with elf file...)
The attach memory card will help to replicate the bug.
Just load the save, enter the mountain, and you will see NPC and many treasure boxes nearby.


Attached Files Thumbnail(s)
   

.7z   Mcd001.7z (Size: 24,45 KB / Downloads: 121)

Sponsored links

#2
# Pcsx2 version: pcsx2-r1358
# Cpu eerec on, vurec0 and vurec1 on, MTGS on
# Plugins used: GSdx 1357 SSE2 , SPU2-x 1.1.0

Treasure box Bug
Sometimes game freeze at battle finish (black screen)
Enter & leave cave,village,etc freeze too (black screen)
In battle some time all characters loss voice and sound effects.
#3
# Pcsx2 version: pcsx2 0.9.6
# Cpu eerec on, vurec0 and vurec1 on, MTGS on
# Plugins used: Gsdx 1.14 SSSE3

With or without speed hack: The game sometimes crash, and freeze (black screen)

# Graphical problem: (not with ZeroGS 0.97.1 but it lags A LOT when there are japanese symbols)

With DX9 (DX10 crash)


[EDIT]
With the last GSDX version 1.15, i have 0 graphical bug and can play on DX10 Harware mode, BUT any interlacing make the game crach, in SW mode there isn't this problem, but it's not as fast and nice; the console is spamming: "m_merge is NULL!"
Still crash sometimes It's hard to play with the screen shaking.


Attached Files Thumbnail(s)
       
#4
Has anyone found a patch or workaround or some other type of way to avoid this bug. Cant really play a game that you cant open chests for hehe.
Ive tried all available versions and the bug persists in all of them.

Thanks
#5
According to the wiki, this game has been playable since version 1.1.0 r5754.

Thank you for your report.
This bug report has now been marked as Resolved since it has been fixed on our code base.

This thread will now be closed and moved to the resolved bug reports subforum.




Users browsing this thread: 1 Guest(s)