Emulator Issues #599
closed
EFB copy to RAM crashes r2276
0%
Description
Game: Paper Mario 2: The Thousand Year Door
Dolphin Version: Win32 build r2276
OS: Win32 Vista(Tweaked for compatibility and speed)
Primary Settings:
http://img3.imageshack.us/img3/1825/settingspd3.gif
Using OpenGL plugin,
EFB copy to GL texture works fine, while EFB copy to RAM causes the
following error message:
http://img26.imageshack.us/img26/6564/crashnm5.gif
The crash occurs after confirming the following dialog box(when the event
ends):
http://img3.imageshack.us/img3/539/cmp1pj4.gif
Additional information: I've tried each setting with safe and unsafe
texture cache. This is an unrelated issue, but a screenshot of the unsafe
texture cache is here(note the extra pixels, appear to be placed on the
very top right or left of some textures):
http://img6.imageshack.us/img6/6853/cmp2py8.gif
Trying to stop the emulation in any case causes dolphin to crash
completely(unhandled exception).
Updated by AHeinerm about 15 years ago
Another small thing I've noticed: The option to HLE the bios all the time is not
saved when the configuration dialog is closed.
Updated by Anonymous about 15 years ago
- Status changed from New to Questionable
does this still happen?/Can anyone else duplicate?
Updated by Nintendo-Daniel about 15 years ago
Yeah, still happens in r2666 for me when EFB copy to RAM option is selected. EFB copy
to GL texture works fine, as said by the previous poster above. :)
Updated by sl1nk3.s about 15 years ago
Is this the only game which crashes with copy EFB to ram or is there others ?
Updated by AHeinerm about 15 years ago
Don't know. Still crashes on r2745.
Log:
E: * Warning: Read from invalid memory region (0x7c6102ca)
Updated by AHeinerm about 15 years ago
Ok. The crash occurs because of issue 360.
Updated by Anonymous almost 15 years ago
- Status changed from Questionable to Duplicate
Updated by marcus almost 15 years ago
how does that figure? all the thing in issue 360 does is return the bounding box of
an object on the screen. What does an invalid memory region have to do with it? The
bounding box function is not even used until several minutes after the place where
the screenshot was taken.
Updated by AHeinerm almost 15 years ago
I'm over 9000 percent sure that the X-Naut is copied right after that message (logs
prove). The issue in 360, returning the INCORRECT value of the bounding box has
incorrect results as well, which includes the crash in this issue.
Updated by marcus almost 15 years ago
ok. If you've done your research, I'm fine with it. I hope ector can get that
bounding box working correctly sometime soon.