Yeah, that would work too. I solved the problem for the moment by re-assigning my keys in Fusion, of course that helps none for hardware. As long as there is a run button to the left of a jump button, I don't really care. I like the idea of B for run and A/C for jump, although I never use A to jump on an MD game unless I have no choice, so many years of using debug on the Sonic games has hardwired C as my default jump button.
Also, did you ever look into the input issue with player 2? Perhaps your joypad init code was a bit buggy? I helped someone debug a problem like that once, and with fixed init code the buttons worked right.
The jump button must be to the right of whatever the NES B-button is mapped to
On an MD 3-button controller that makes B, C the best choice.
on my NES controllers, I have swapped A and B... more to do with an habit, since I got some clone controllers for my Famiclone that were like MD 6buttoners, where A is A, B is B and Z is A+B, and XYZ are turbo buttons... my fav controller and 12 years playing with that definitely burns something into your mind(and fingers)
knightwarrior wrote:I wish it was "A" Run "B" Jump "C" Run
But B+C is fine
Do a SMB2j Port..But the Mapper 4 Hack
Over on Devster's forum, Mairtrus wrote:- According to Sik (he said it first...), now in main screen the number of players is selected with the Up/Down buttons. Now the A and C buttons does the same function. Plus, the joypads are initilized properly, so now the joypad 2 works in Fusion (an I guess in real hardware too)
For the record, world 36 no longer crashes, although it does not behave the same as the NES version. You get an underwater 3-4, which upon completion acts like you've beat the game, setting the hard mode flag and enabling the world select.