4 ms·
This is a lot messier than it needed to be. The Classic controller port uses a well-documented I2C protocol, so you just need to sacrifice a cheap extension cab
by TillE 3y ago
This is a lot messier than it needed to be. The Classic controller port uses a well-documented I2C protocol, so you just need to sacrifice a cheap extension cable or whatever and wire that in.
http://wiibrew.org/wiki/Wiimote/Extension_Controllers http://wiibrew.org/wiki/Wiimote/Extension_Controllers
- deleted 3y ago[deleted]
- sp332 3y agoFrom the Ars Technica link I posted: dougg3 said his setup only successfully completed the level 1 to 5 percent of the time, an oddly low success rate for a system that's supposed to play with robotic precision.... "What I found is although the actual electrical pulses I'm sending to the controller are exactly the same length each time, verified on an oscilloscope, sometimes Mario doesn't jump," dougg3 said.
- th4tg41 3y agowouln't that suggest some sort of additionaly applied poll rate?
- CarVac 3y agoOr a desync between the game and the display. In Super Smash Bros Melee the game runs at 60 Hz but the display runs at 59.94 Hz... one frame in 1001 is simply not displayed.
- bluescrn 3y agoEven if it’s perfectly synchronised, there’s likely no guarantee of deterministic playback. Perhaps a background process is dealing with some network activity or other OS task and throws the timing off fractionally. Or maybe a disk access (even for something in the background like streaming music) takes fractionally different amounts of time per run and affects the precise time at which the input is polled.
- deleted 3y ago[deleted]
- dougg3 3y agoAh, that’s another interesting possibility. I definitely observed that the actual HDMI refresh rate is 59.94 Hz while playing Super Mario Maker, but no idea what the game’s internal frame rate is.
- dougg3 3y agoVideo creator here. You're absolutely right. On the other hand, it at least gave some data on exactly how the Wii Classic Controller in particular behaves. I'd be curious if the Wiimote by itself behaves any differently too. I still think my approach was easier than implementing the I2C protocol, even if it was much messier. You could theoretically even completely emulate the Wiimote in software too. I think some people in the TASBot community were taking that approach.