Right now, I'm also at a loss. The coded lab that I was using for my development is no longer accessible to me next semester. This means I need to start building my electronic kit from the ground up. I ordered a PIC programmer that did not work correctly (The PIC is the chip we are using). I will probably spring for a Warp13 programmer soon. I'm tired of not being able to work on programming for the PIC. (If you like electronics/coding, there is nothing better)
On a side note, someone mentioned a problem with ePSXe, and being able to switch controllers, etc. This raised a few questions in my mind. Would people like to have a keyboard encoder style controller adapter? I already have written my own keyboard encoder! One that changed the inputs from the NES, Genesis, SNES, N64, Atari, etc, to be the same inputs as their keyboard encoder? This is do-able, except for one major factor - Analog controls. It could also work as a joystick, but that only allows for 4 analog controls, via the game port.... I could concieve-ably encode it as mouse input... but someone would need to help me figure out how to fake a joystick as a mouse. (Probably not possible) However, this encoder would allow for the reading of the digital parts of Pads, and would stop the neccesity for reconfiguring the controllers to work for each system.
I saw this as a great benefit, since one person may want to use a console controller, where the other may want to use the joystick/buttons on the panel. On this option, you wouldn't need 2^x number of options, where x is the number of players on the panel.
This direction would not hinder the USB path, since the USB is done in 2 different stages, decoding the controller, and then sending to the PC. I am still very comitted to this project. I will hopefully regain my ability to program the pic microcontroller, so I can continue development of this project.
I will definately be adding 4 15 pin headers to my cab, so I guess I'd better complete the project, or else I'm going to look very very stupid
