Mention enable MMU in the DSI Exception message (Invalid read from ###/Invalid write to ###)

This has been possible for a long time now (see https://dolphin-emu.org/blog/2016/09/06/booting-the-final-gc-game/#side-effects-of-a-hardcode-rewrite), but it seems like people still aren't aware of it.
This commit is contained in:
Pokechu22
2025-08-12 15:38:49 -07:00
parent 72ef27c157
commit dfbf39c768

View File

@@ -1273,8 +1273,20 @@ void MMU::GenerateDSIException(u32 effective_address, bool write)
// DSI exceptions are only supported in MMU mode. // DSI exceptions are only supported in MMU mode.
if (!m_system.IsMMUMode()) if (!m_system.IsMMUMode())
{ {
PanicAlertFmt("Invalid {} {:#010x}, PC = {:#010x}", write ? "write to" : "read from", if (write)
effective_address, m_ppc_state.pc); {
PanicAlertFmtT(
"Invalid write to {0:#010x}, PC = {1:#010x}; the game probably would have crashed on "
"real hardware.\n\nFor accurate emulation, enable MMU in advanced settings.",
effective_address, m_ppc_state.pc);
}
else
{
PanicAlertFmtT(
"Invalid read from {0:#010x}, PC = {1:#010x}; the game probably would have crashed on "
"real hardware.\n\nFor accurate emulation, enable MMU in advanced settings.",
effective_address, m_ppc_state.pc);
}
if (m_system.IsPauseOnPanicMode()) if (m_system.IsPauseOnPanicMode())
{ {
m_system.GetCPU().Break(); m_system.GetCPU().Break();