Laydock 2 Last Attack (screen 12 at beginning of intro demo)
Starship Rendezvous Special Stage Michelle (“just testing! honestly!”)
M-Kid demo (nice screen 10/11 graphics)
I suppose there is some timeout, like if you don't flip pin 8 for a certain period of time, the sequence resets to the first value the next time you flip pin8.
Yes, you might be right... Unfortunately at the moment I'm not next to my real MSX to test this theory... To my mouse implementation I added 3ms timeout just in case... I didn't test if my original mice implemented that... At least I've not read about time timeouts.
Or, maybe the sequence resets when you write to the port but keep pin8 unchanged.
Do you understand what I mean?
No, not really... How do you expect the mouse to notice what you do if you don't actually do anything that could be noticed? I know that PSG internally "knows" what you did, but I can't think any method how it could teleport this information to mouse.
No, not really... How do you expect the mouse to notice what you do if you don't actually do anything that could be noticed? I know that PSG internally "knows" what you did, but I can't think any method how it could teleport this information to mouse.
So, that leaves only the timeout possibility.... The mouse resets the sequence some time after the last pin8 change.
But, how much time???
Laydock 2 Last Attack (screen 12 at beginning of intro demo)
Starship Rendezvous Special Stage Michelle (“just testing! honestly!”)
M-Kid demo (nice screen 10/11 graphics)
Grauw, where is the best place to find trusty MSX2/2+ software (including those)?
msxarchive.nl
Great!
Can someone point me to a place to download the complete System ROMs to make all the machines work in BlueMSX?
I have the emulator but only a few machines work.
Just go to the blueMSX site, then to the Resource page. Also mentioned in the blueMSX manual.
Guys, regarding the mouse hardware interface ...
... Is there any timeouts involved?
In openMSX we're currently using a timeout of 1.5ms. We don't know the exact value, and it might be different for different mouse models. Though this value seems to work well (no timeout or a too large value caused problems).
In the openMSX source code you can find some comments with background info about how we came to this value.
[quote=wouter_
In openMSX we're currently using a timeout of 1.5ms. We don't know the exact value, and it might be different for different mouse models. Though this value seems to work well (no timeout or a too large value caused problems).
I ended up using 3ms like NYYRIKKI suggested. The BIOS seems to read always below 1ms.
Did you have problems with this value (3ms)?
(no timeout or a too large value caused problems)