The above video goes away if you are a member and logged in, so log in now!
ESR - Some games allow no controller input HELP!!!
ESR - Some games allow no controller input HELP!!! –
I know ESR questions and bugs have more-or-less been "done to death" but I have trawled these forums and have not come across any answers to my particular problem.
Recently I bought a bunch of pre-owned PS2 games, and I ripped them to my HDD, Patched with ESR Patcher and burned to a spanking new DVD+R (Verbatim's). I intend on giving my kids the originals to play in their bedroom and keeping the back-ups in pristine condition for myself. Anyway, enough of a back story... I have a couple of games with a strange bug, i have seen people posting the problem elsewhere but never seeming to get a satisfactory response.
Anyways, 2 games i have BOTH have the same problem. They are "Burnout: Dominator" and "Need for Speed: Underground 2". Both backups load without issue and get to the first option of the game (Burnout asks me to select 50/60Hz mode, NFS queries Language). I cannot advance further from here as the controller is not responsive, it is as if my pad isnt even connected.
I have tried booting with different options in ESR, and tried with my original Sony PS2 DualShock controller, and my kids 3rd party cheapy controller, as well as one from an old PS1 that I have laying about but none of these pads will control the games mentioned.
Its simply bizarre! Can anyone suggest a solution? It seems that the pads aren't at fault as they work 100% with my other backups, and i have tried re-burning each game (I now have 3 versions of each) and every one does the same. Each game verifies 100% against its original ISO image.
I really hope that there is some proposed solution to this problem, if not I will cry!
Any help gratefully received, and if a solution is already posted on these forums then I appologise - I HAVE searched but come up with nothing
It might be an issue with IOP memory size. There might simply be not enough space left to load the libpad once every other module is loaded. The memory allocated by esr module itself is quite different for different games (actually, it depends on IOPRP image version, AFAIR 2.50+ shouldn't use more than 5-6kB, while earlier versions could use even as much as 50-60kB, depending on situation and exports used - sometimes it's enough to stop some module from loading or allocating its pool of memory). There are games like Melty Blod Act Cadenza (or whatever the game name was) that didn't work if the memory trace was bigger than ~3.5kB (but it was a relatively new game, using 3.00+ IOPRP, IIRC). Can't really say anything specific without further testing, but I'm not going to get back to ESR development .