Need Help Running Project M 3.6 [Not for Netplay]

[Greg]

I was pointed to this guide (http://afriendlyfox.com/2013/07/22/proje...-emulator/) and asked for help on here (http://smashboards.com/threads/need-help...lay.418329)

I have pictures on the second link, but I've had no success. I deeply appreciate any advice that can be given.

[Helios]

By the way, that guide is outdated. non-netplay is a bit easier now and requires fewer steps, and netplay without respinning a brawl ISO is actually possible now.


Use a development version [color=#333333]4.0-7465 [/color]or newer (Needed for some features - also because 4.0.2 is two years old and is trash)

1. Add your Brawl ISO to dolphin. Right click on it after it's in the list and set to default ISO.

2. download Gecko OS from here. Add the boot.elf (located in Gecko1931\Gecko1931\HBC\Gecko1931\ in the zip file.) in the download to Dolphin (You can put it in the same folder as the ISO if you'd like). Click Refresh in Dolphin. It should show up in the game list. This is a new feature.

3. Follow the steps 4 through 8 in that guide you posted.

4. In dolphin config > Wii, make sure "Insert SD card" is checked.

5. Boot Gecko OS from the gamelist. Run project M.

Let me know if you have questions about that feature.

[Greg]

I tried with a more up to date version, before trying the exact version you stated, but it always ends with a "Not Responding" dialog after it says "Reading DVD Stats"

[Kurausukun]

This didn't occur to me over on Smashboards, but are you sure your ISO is a good dump? Check the md5 and see if it matches a verified good dump.

[Greg]

Hello stranger!

I've computed the MD5 Checksum, but how would I find the verified version? If you can't tell me, I'll search the depths of the internet.

[shockdude]

Did you set SSBB as Dolphin's default ISO? In dolphin, right-click SSBB and set as default ISO.

[Greg]

Yeah, it's set as default.

[Greg]

I found this site (http://www.gametdb.com/Wii/RSBE01) stating that the checksum would either be:
d18726e6dfdc8bdbdad540b561051087
52ce7160ced2505ad5e397477d0ea4fe

Concerning, since my disc is:
5a73d6f1049a92143bb0eb7f7af7ebc8

So it's likely something to do with the MD5 checksum. Is there any action I can take from there, or am I at a dead end? If the latter, I wonder how the Project M ISO builders never picked up on this...

[JosJuice]

Redump the disc and see if you get a different MD5. Remember to enable dual-layer dumping.