> Thanks for the explanation. I wasn't picky when looking for changing bits that were > related to outputs. I just cast a wide net and went with whatever came up first. I'll > go back and try and do it right this time. > > For what it's worth, I didn't follow the existing fan example because it uses a > legacy write handler which I figured would be bad form and as far as I can tell it > doesn't work. Maybe I'm wrong in this, but I don't see the existing outputs changing > at any point during testing or gameplay.
I looked into this, he's right!
Your original prop cycle implementation just had one led and a fan output. That worked beautifully.... I used it to start my output adventures a couple of years ago. Now it's got several lamps hooked up (which work fine afaict) and although the fan output is still there, it appears to be dead. I bound it to a xinput rumble pad via mamehooker in case the change was too quick for me to detect and nothing. Oddly enough I think the fan output is coming out of the led output now because if I bind that to a rumble device I get the graduated rumble (based on pedal speed) that you used to get from the fan output. Actually if you pause the game, the fan output drops out completely and won't come back until your restart mame... proving that the state isn't changing at all.
I haven't looked at the source yet, but it's your baby R. Belmont... you might want to take a look.
|