Sweet! Thanks man.
Sweet! Thanks man.
if anyone is looking for an adapter that works with this, i just got this: http://cgi.ebay.com/ws/eBayISAPI.dll...=STRK:MEWNX:IT in today as a 2nd adapter, swapped it with the one that i installed using these directions and it worked perfectly. Just thought i'd share for anyone looking for a cheapo adapter that works. I think that seller might have had the same adapter for slightly cheaper btw.
:(
Well... that sucks. It appears Yahoo has pulled the plug on Geo-city's content, which had a LOT of good content on the internet. It sucks even more because even I don't have the original files. :/
I'll see if I can modify the 2-player version to one player.
I've been getting the itch to do some step-mania recently.
(Okay, now that I realized I can't modify the 2-player program, I think the most valid thing to do would be to plug in a regular playstation controller into the 2nd player slot and just leave it be. It might need to be calibrated. This should prevent the 'A' and 'W' flooding issue I remarked about earlier.)
Last edited by swbluto; 12-20-2009 at 06:12 AM.
actually, i think i have the single player one on one of my computers at home, i'll check when i get back home in a few weeks.
That'd be pretty nice.
I just confirmed, with the two player program and by callibrating the second playstation controller in addition to the dancepad, the single dancepad worked fine without glitching.
What I also foundout is that the newest dilong pu203 drivers (not the ones in my post, the one on the website) still has the same problem with simultaneous arrow presses, BUT, the reported values for left and right pressed at the same time and the values for none being pressed are the same meaning... there's no special tricks with the newest drivers. It looks like the original drivers I posted are the necessary kind. I'm starting to thank god I didn't put them on geocities.
I also found out that not all computers seem to operate the dilong playstation USB device correctly after the driver is installed, as I tried installing it on other people's laptops in order to postpone the need to drag the personal computer out. It would install with no problems, but it doesn't seem like it would operate the device (The red LEDs wouldn't turn on, and Windows didn't react to the device being plugged in). I don't know if this was due to insufficient USB power or some kind of weird operating system state configuration, but it looks like some computers are intolerant of the driver/device. The other programs do their job just fine. With this experience, I could see why some would experience difficulty in getting it to work.
I dug up the one pad program, here you go:
http://www.megaupload.com/?d=N4M0VSMU
Whoa, I didn't thought that solution I posted last 3 years ago will be a helpful contribution to the stepmania community. Thanks for the credits, swbluto.
As for some who still are trying to get their USB adapters and DDR mats/pads to work, I suggest you guys read and follow the instructions carefully. Up until now, I still get my DDR pad to work with stepmania on Windows 7 Ultimate 64-bit, so I don't see why you guys still have problems with it.
**Magic isn't omnipotent. Real magic is that little bit of courage you have.**
Okay, I know this post was written 4 years ago, but I just bought the same part and am having the same troubles with the keys not registering if the other one is pressed.
I tried to complete all the steps in this solution guide, but now it's like all the buttons on the mat are being pressed all the time. I did the solution twice to make sure I'd gotten all the steps right.
I'm running XP and DirectX9, using the drivers here (like yours, my disk didn't work) and the two mat program. I set up the mats so the key mapping was with the arrows for the primary mat and wasd for the second mat.
The configuring of the mats looked just like the guide says it should.
The only thing I can see that I didn't do is the uninstalling of the previous drivers because I didn't know where to find them.
If anyone's still watching this thread, can I get some advice? Is there a new thread I should look at?
Thanks
T
1) Unplug the USB adapter first if it's still plugged in, and unplug the dancepad connector from the USB adapter.
2) Uninstall the dilong driver(s)
3) Proceed to the detailed guide, and read THOROUGHLY (sorry, but I have to type it in bold to emphasize the importance of the guide) with an exception: instead of installing the dilong driver, use the generic USB gamepad driver from microsoft. In other words, skip the part where you have to install the dilong driver
1) just plug the USB adapter in, and without the dancepad connector in it, so make sure before doing it
2) wait for windows to detect the USB adapter
3) then proceed to the part where you have to calibrate the game controller (which is your dancepad)
I don't think it'll fail, as I didn't have any problems with the microsoft generic USB gamepad drivers. But in case it'll fail, try re-installing the dilong driver.
I'm still playing Stepmania (OpenITG, to be specific) with my trusty old dancepad (way back when I got a PSOne in late 2000) and the new dancepad I bought last 2 weeks ago (since the down arrow of my old dancepad no longer work and have to replace the foam inside which is kinda tedious), and I'm sure the guide that swbluto made (which is mostly based on my observations on making that darn adapter to work properly) won't let you guys down.
Last edited by Dj Ash 1983; 01-31-2011 at 08:40 AM.
**Magic isn't omnipotent. Real magic is that little bit of courage you have.**
Okay, so when I uninstall the drivers and follow the guide to the letter, I can get into the game and scroll through all the menus, but when I start playing a song, it plays itself. If I stand in the middle of the mat and frown at the screen, I still get 100% accuracy.
Thinking it might be a problem with the mapping, I mapped the mat back to the standard arrow buttons, I turned the smpremix program off and restarted stepmania. Exact same result. My conclusion is that I must be doing something in the calibration wrong but the calibration process looks exactly as this guide suggests it should.
Am I missing something stupid?