SpritesMind.Net

I think the order isn't the main thing here, but rather the amount of time you wait after setting TH=1. When you reset the ports (generally to 0x40/0x40), you are supposed to wait two vblanks before reading the port to get the TH=1 ID bits. I imagine that if you read TH=0 bits first, but waited two ...

I guess that's one reason why games with hacked in mouse code don't use Fusion as their emulator of choice in playing the game. I can't say I remember ever trying the mouse support in Fusion.

It's possible it's not the MCU that's too susceptible to noisy power (though that probably isn't helping it) but the optical part. If the lights fluctuate too much I could see it causing the photosensors pick up spurious motion (and hence causing the random values). Now I also wonder if there's eno...

Yeah, I just tried my ZT cable today and it works fine on the Nomad. As to dirty power rails, that might be the case. The Sports Pad uses an old MB88201 MCU to handle the trackball. Maybe it was susceptible to noisy power. The only thing on the Sports Pad that works on the Nomad are the two buttons,...

Nomad + Propad6 = ok Nomad + 3button pad = ok Nomad + Mega Mouse = ok Nomad + Phaser = ok Nomad + Justifier (both guns) = ok Nomad + Sports Pad = fail Doesn't work in SMS games from flash cart either, so I wonder if it's a power problem. Not enough current on the port to power the optical pickups, m...

I imagine Control mode is basically "emulate a D-pad"? Especially since the Master System controller calls it Control Pad (the term Direction Pad came with the Mega Drive). Oh, duh. Yeah. No wonder it doesn't decode like a trackball - because it's emulating the standard SMS control pad. That explai...

joytest.zip I couldn't tell you why it was hanging, but it was. And the new code fixes the issue. The new functions for checking and setting latched counters is a good idea in any case. Here's the joytest main.c file - I changed it a bit to make it clear that you can compile with it set to auto det...

Found the problem - you're using the vcounter in the vblnk callback for timing. When the light gun code sets the counters to latch, it hangs your code. If you disable the code that sets the counters to latch, everything's peachy... except the lightgun value varies quite a bit as the counters aren't ...

I dug out my TIMM, but I'm looking for the box with my light guns now. :D I'm inclined to think it's something interfering with the light gun resources in his code rather than the code itself. Certain things are needed for light guns to work. SYS_setExtIntCallback(externalIntCB); pb = (vu8 *)0xa1000...

Ugh... I'll take a look at it, but it means digging out my TIMM and the light guns. Now all I need is somewhere to put it... Are you sure about that date? The only change in the joy.c file around that time was a MINOR change to the mouse code on Dec 23, 2014. else my = md[4]<<4 | md[5]; if (md[0] & ...

A bit coarse, but not bad.

I like your extended mouse spec. While I like the idea of clamping the mouse move rather than having overflow, you need to keep the overflow bits for backwards compatibility. On mice that clamp rather than overflow, those bits will simply always be 0.

Sure. I'll plug one of my Logitech keyboards into the adapter and run my controller test app on my Saturn (how I found all the key mappings I put into libyaul) and see what happens.

Oh, yeah. That's much faster. And D0 doesn't matter or I wouldn't have put in the shift.

It IS a little bigger, so maybe you'd choose one over the other depending on space vs speed.

The SGDK thing is my fault... and not my fault. All the code I've seen for handling the mouse looks for those two F nibbles, so my code did too. This will work on any mouse that's 100% compatible... but won't work if someone makes something that uses those two nibbles AND doesn't return F by default...