This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Post Reply 
 
Thread Rating:
  • 3 Votes - 3.67 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sonic The Hedgehog [BLES00028]
08-06-2017, 06:50 PM
Post: #21
RE: Sonic The Hedgehog [BLES00028]
Testing the game yet again especially after all the changes as of late and it still seems to have the same issue (see attached for logs)

libaudio.sprx
libfs.sprx
libio.sprx
libresc.sprx
libspurs_jq.sprx
libsre.sprx

Seems to crash at:
F 0:00:09.052200 {PPU[0x1000000] Thread (main_thread) [0x00e2ab64]} MEM: Access violation reading location 0x0


Settings:
PPU Decoder: Interpreter (precise)
SPU Decoder: Interpreter (precise)
Manually load selected libraries
Enabled SPU Loop detection
Graphics Render: Vulkan
Audio Out: XAudio2

(08-02-2017 08:45 PM)basic.wizard Wrote:  I'm probably way off here, but it could be worth building this PR to see if it gets any further. I can't figure out how to compile RPCS3 properly so I'll leave it up to someone more knowledgeable about this.

I haven't tested this though. So maybe this fixes the issue? Can anyone test?


Attached File(s)
.zip  BLES00028-v0.0.3-5-30aea2d.log.zip (Size: 161.91 KB / Downloads: 0)
Find all posts by this user
Quote this message in a reply
09-22-2017, 04:29 PM (This post was last modified: 09-22-2017 04:30 PM by irixion.)
Post: #22
RE: Sonic The Hedgehog [BLES00028]
RPCS3 v0.0.3-3-8e66e71 yields the same results. Looking at the log, there's a lot of size=0x0. Perhaps that's related to the "bad compression" errors we're seeing?

Edit: Noticed there's no github issues page. Would this error qualify as an issue?
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)