I can run my 3.60+ backups patched for cfw3.55 using mmDM but my problem is creating a save game file... My ps3 hangs everytime I try to save a game.
Ever experienced this???
I need all the help I can guys... its driving me crazy since this morning...
List updated now with the following games added:
- Rage - Update 1.01
- Rayman Origins
- Shadows of the Damned
- AC Revelations - 1.04 N0DRM Update
- MGS HD Collection - 1.03 N0DRM Update
- Prince of Persia - The Forgotten Sands - Update 1.01
Instead of me being a complete and total dick and a prick, I should be on my best behaviour!
I just wanted to add that mmDM does not modify the PARAM.SFO to 3.55 like multiman does, on the fly. So if you know you have the correct eboot fix and it asks for an update of firmware version upon loading, be sure to check if your PARAM.SFO is set to 3.55 or lower. I ran into this problem earlier with El Shaddai: Ascension of The Metatron. Since I had never loaded it from within Multiman before trying it with ProDG TM/mmDM, I received a requires firmware update to 3.56 error. So I checked the PARAM.SFO and changed it from 3.56 to 3.55 and it worked perfect.
Just thought I'd add this for people who encounter this issue and since this thread is for getting games working with mmDM/ProDG TM, this bit of info can be just as important as all the file moving we've seen with some of these problem games.
Going to potentially be a bit slow with testing and fixes today, changing my PS3 internal with a 1TB drive, so lots of backing up and all to do.
Trust, encouragement, reward, loyalty... satisfaction. That's what I'm... you know. Trust people and they'll be true to you. Treat them greatly, and they will show themselves to be great.
I just wanted to add that mmDM does not modify the PARAM.SFO to 3.55 like multiman does, on the fly. So if you know you have the correct eboot fix and it asks for an update of firmware version upon loading, be sure to check if your PARAM.SFO is set to 3.55 or lower. I ran into this problem earlier with El Shaddai: Ascension of The Metatron. Since I had never loaded it from within Multiman before trying it with ProDG TM/mmDM, I received a requires firmware update to 3.56 error. So I checked the PARAM.SFO and changed it from 3.56 to 3.55 and it worked perfect.
Just thought I'd add this for people who encounter this issue and since this thread is for getting games working with mmDM/ProDG TM, this bit of info can be just as important as all the file moving we've seen with some of these problem games.
Will definitely add this to the A-Z guide! Cheers!
Instead of me being a complete and total dick and a prick, I should be on my best behaviour!
gDrive, can you please add to the OP that all games are tested with OFW DEX 4.21 - thanks.
Trust, encouragement, reward, loyalty... satisfaction. That's what I'm... you know. Trust people and they'll be true to you. Treat them greatly, and they will show themselves to be great.
A-Z Index updated, with both White Knight Chronicles games, the Tom Clancy games, Tomb Raider Trilogy, Syndicate/The Saboteur/The Orange Box and the Tony Hawk games added to the list, alongside NeilJames' protip.
Instead of me being a complete and total dick and a prick, I should be on my best behaviour!
I don't really know if this issue is due to ProDG TM/mmDM but I figure I'll put it here since I am loading the game with mmDM.
I had an issue with FFXIII-2 where at the beginning of the game, right after the Lightning Prologue, the first fight that Serah & Noel encounter, Serah would only start with 4 HP and Noel with 10 HP. I can't give any reasons as to why this occurrence took place but it did. I have theories but nothing concrete. Maybe I will try to recreate the issue later to verify the fix.
The only thing that allowed me to start with normal HP was deleteing all GameData/SaveData associated with FFXIII-2 and removing the Theme I had installed from FFXIII-2 as well. This was ok for me since I hadn't even played the game so I wasn't losing SaveData. After removing all the aforementioned data, I installed the 1.06 Update/N0DRM fix, booted the game and all went well.
There may be some cause on my end that I will try to reproduce the error but in the meantime if this freak occurrence happens to anyone else, hopefully this helps a bit.
Originally Posted by Omnomnom
Reply With Quote
