Yesterday I installed a controller port mod on my Famicom Classic so that I can use any of the NES Classic compatible controllers. Here are the instructions I followed:
Below are a few photos and here's the description for them:
1. The Famicom Classic does not have a "controller port" on it like the NES Classic does, so if you want to connect either an NES or SNES controller to the Famicom Classic, you can't without doing this mod.
2. Just like the original 1980s Famicom, the Classic comes with the controllers hard-wired into the console. And I mean hard wired. It's not a controller port inside the case, they are attached via a connector right on the board!
3. Another reason for doing the mod is that, keeping in with the theme of having the console be "mini" in order for the controllers to fit into the slots on the sides, just like the original console, the controllers also had to be shrunk down, which makes them almost unusable. They are "cute" absoultely, but not practical for playing games.
4. That being said, I used one of the left over extension cord connectors to convert the mini Famicom controller so that I can plug it in and use it if I ever wanted to. Interestingly enough, these controllers ONLY work on the Famicom console and not on the NES mini.
I'm working on getting Atari 8-Bit set up in RetroPie using the Atari800 emulator and most everything seems to be working just fine except for this:
My WASD keys don't deliver any input at all. I've tried multiple keyboards, checked to make sure they aren't currently bound to joystick controls in the emulator and I assume there is somewhere in the emulator which is binding them to "movement" but I can't seem to find it.
So right now, any game that requires pressing "S" to start, like the Scott Adams adventure games, I can't do anything with because my "S" key doesn't work.
I've scoured Google looking for solution but it seems there aren't many people who have set up Atari800 on the RetroPie because it most certainly isn't the most user friendly of emulators.
Anyone else run into this same issue and found a solution? Thank you in advance for your help!
- What about people who only own an Expansion Module #3? Would the new forum only be for topics relating to stand-alone ADAMs or would it include topics for the ColecoVision expansion module?
- What about Development posts? The ColecoVision programming forum is a great resource to those who are homebrewing or programming on any of the Coleco machines. Should those ADAM specific posts, like this one for example: http://atariage.com/...mming-question/be split into a new ADAM forum or stay in the ColecoVision Programming forum?
Arguably, the ADAM is considered by most outsiders (aficionados aside) as an extension of the ColecoVision which the Expansion Module #3 literally is. The above is not necessarily my personal opinions one way or the other, but just some information to think about before we go splintering into another sub-forum. Would that actually help or hurt the ADAM community? As I said before, the decision is completely yours!