Emulator Issues #8731
open
Project M - infinite "Invalid Read from to ..." error messages with AXNextFrame hook type
0%
Description
Game Name?
Super Smash Bros. Brawl (Revision 1)
Game ID?
RSBE01
What's the problem? Describe what went wrong in few words.
Warning message will pop up after running Project M for a while, like "Invalid Read from to 0xffffffbc PC = 0x801cba80", etc. and I can only end Dolphin's process.
What did you expect to happen instead?
Project runs properly all along.
What steps will reproduce the problem?
- Follow this guide for creating (1GB) virtual SD card for Project M https://wiki.dolphin-emu.org/index.php?title=Virtual_SD_Card_Guide
- Use Project M fullset - Homebrew OR Hackless method for 3.5 or 3.6b from http://projectmgame.com/en/download
- DSP LLE is preferable for homebrew apps, so enable it.
- Try to launch Project M with vanilla Brawl disc image.
- Battle for ~4 minutes
I've tested on two PC's, ripped Brawl in WBFS and ISO, same result. I've tested many developer builds, and the problem apparently introduced in 4.0-5531.
Files
Updated by JMC4789 over 9 years ago
- Priority set to High
- Milestone set to Current
- Regression set to Yes
4.0-5531 -> https://dolphin-emu.org/download/dev/8cc6e5cff9cff74483c3cc939f1bc7c934570549/
The problem could be caused by many things.
Updated by rukariosake over 9 years ago
Just checked similar issue with Sonic Riders and I tried the workaround mentioned in there (speed up disc transfer rate) and it worked.
I wasn't able to open properties window for the Brawl in WBFS format (Unhandled exception). I will probably make another issue report for it later.
Updated by JMC4789 over 9 years ago
So... we're at an impasse. We need miracle coders to show up.
Updated by JMC4789 over 9 years ago
Just a question, with SUDTR off, does disabling panic handlers lead to a crash?
Updated by dieujusteschadracsc1 over 9 years ago
where is it do you find "speed up disc transfer rate" ?
Updated by JosJuice over 9 years ago
Right-click on a game and open the properties.
Updated by rukariosake over 9 years ago
Now receiving invalid read/write even when SUDTR is enabled in latest Dolphin builds...
Dunno which build caused it
Somewhere 4.0-6970 and older
Updated by rukariosake over 9 years ago
Has nothing to do with latest Dolphin builds, only 4.0-5531 I think.
I used my old Brawl saves that my Wii had it for long time and invalid read/write error becomes more common (consistently occurs in 4 min battle like usual) even with SUDTR enabled.
I will do more testing later...
Maybe invalid read/write all due to disc and save read being too slow?
Updated by rukariosake over 9 years ago
OH RIGHT! Been overclocking Wii CPU to 400% by accident. My bad...
Updated by JosJuice over 9 years ago
If you suspect that this is caused by the disc reads are too slow, try this PR. It's supposed to improve the accuracy of disc timing for Wii games, but we're not too sure how accurate it actually is. http://dl.dolphin-emu.org/prs/pr-1900-dolphin-latest-x64.7z
Updated by JosJuice over 9 years ago
- Milestone deleted (
Current)
I'm going to remove Milestone-Current from this for the same reason as issue 8725. I don't know how to fix the issue, I don't think anyone else does either, SUDTR is an acceptable workaround, and we need to get 5.0 out. I'm going to leave the Regression tag on for now since this never was broken in the past unlike Sonic Riders, but there's probably some underlying issue that versions before 4.0-5531 simply happened to work around. If anyone wants to have the Regression (and Priority-High?) tags removed, feel free to.
Updated by Lucario about 9 years ago
Apparently hooktype set as 7 (AXNextFrame) will cause invalid read/write in 4 min battle, while hooktype as 1 will not. It's up to you to label this issue as invalid or transform this into "AXNextFrame" issue.
Updated by JosJuice about 9 years ago
- Subject changed from Project M - infinite "Invalid Read from to ..." error messages to Project M - infinite "Invalid Read from to ..." error messages with AXNextFrame hook type
- Priority changed from High to Normal
- Regression changed from Yes to No
I don't know whether the issue is valid, so I'll leave the status at New.
Updated by pauldacheez about 9 years ago
DSP LLE would probably fix this if it's hooking on something DSP-related.
I'll leave this open in case it's fixable in DSP HLE.
Updated by Lucario about 9 years ago
I remember I've tried other DSP modes, all same
Updated by Lucario over 7 years ago
- File Dolphin code -6.png Dolphin code -6.png added
- File Wii code 0.png Wii code 0.png added
Dolphin doesn't display this verbose screen in GPU backend other than SoftwareRenderer
Now I'm trying SoftwareRenderer, etc and run for 4 minutes battle in-game because I'm curious, noticed different error code between Dolphin and real Wii
It's somewhere between Smash Stack n Project M Launcher
Updated by JMC4789 over 7 years ago
It'll show up on hte hardware backends with RealXFB.
Updated by Lucario over 7 years ago
Okay, the verbose screen will show up with XFB as real (XFB as virtual untested)
It appears this code doesn't mean a thing.
Project M doesn't crash anymore with DSP ROMs dumped from Wii.
Updated by JMC4789 over 7 years ago
We emulate an up to date IOS; that exploit will no longer work.
Updated by JMC4789 over 7 years ago
- Status changed from New to Working as intended
Some Exploits won't work, but the crash doesn't happen. Good enough for me.
Updated by JMC4789 over 7 years ago
- Status changed from Working as intended to Accepted
Oh well. I read it too fast.
Updated by Lucario over 7 years ago
Sorry, I'll be back when I find the definitive culprit...
I assumed it'll never crash because I've got past 4 minute mark, apparently it's when I'm actually playing, not battle with only CPUs. Though the real Wii can run fine with all CPUs.
That reminds me, I have issue with another game I haven't opened ticket for it, it's controller related, though it doesn't crash but lag. It's really weird issue.