New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3DS Game Crash]Heroes of Ruin "RiftWalk" error. #707
Comments
Sounds like bad dumps, but we don't support piracy tools or websites. |
I just figured out why this is invalid. Nevermind. I'm updating the OP now with the proper required information. Sorry for the trouble! |
I actually misread this a bit, my apologies. I'll look into this. |
I confirmed this as an actual issue with Luma. While it's possibly due to laziness on Square Enix London's part, it will be looked into and fixed. Thank you. |
System model:
new3DS
SysNAND version (+emu/redNAND version if applicable):
Sys 11.2.0-35U
Entrypoint (How/what you're using to boot Luma3DS):
Boot9Strap
Luma3DS version:
8.1-557F205
557f205
Luma3DS configuration/options:
Default EmuNAND: (1 )
Screen brightness: (1 )
Splash: (Off )
PIN lock: (Off )
New 3DS CPU: (Off )
--
Autoboot EmuNAND: (Off)
Use EmuNAND FIRM if booting with R: ( Off)
Enable loading external FIRMs and modules: ( Off)
Enable game patching: (On )
Show NAND or user string in System Settings: (On )
Show GBA boot screen in patched AGB_FIRM: (Off )
Patch ARM9 access: (Off )
Set developer UNITINFO: (Off )
Disable ARM11 exception handlers: (Off )
--
Explanation of the issue:
After launching Heroes of Ruin and setting the following initial settings:
Enable Spotpass? NO > Enable User Generated Content? NO > Receive Notifications from Square Enix? NO
After selecting these options the following error is displayed on the bottom screen:
Error type: logged
Process ID: 41
Process name: RiftWalk
Process title ID 0x0004000000075100
Address: 0x003ec3dc
Steps to reproduce:
Launch Heroes of Ruin
Select NO on all three options.
Dump file:
Like @Hikari-chin mentioned in her most recent comment, this is an internal error thrown by the game itself and not Luma. Bad dump. Time to hunt down a physical copy, dump it, and test it.
The text was updated successfully, but these errors were encountered: