Ask Eric to test the version with #bf anyway. It could be an unexpected side effect
The weirdest keyboard matrices are of the Philips VG-8000/8010. It's completely off. Even some early Konami games get confused by it (pressing 1 and 2 isn't working on these machines in these games).
ok, thanks guys! I just updated the release with Imanok's fix (haven't changed version number, since it was a 1 bit change ). Same link as before: https://github.com/santiontanon/transballmsx/releases/tag/1.3.2
ok, thanks guys! I just updated the release with Imanok's fix (haven't changed version number, since it was a 1 bit change :)). Same link as before: https://github.com/santiontanon/transballmsx/releases/tag/1.3.2
I tested your latest version, but it does not fix the problem on my own Turbo-r :-?
Hi Eric, I will write a little test program later today and send you, to run on your Turbo R, to figure out what is the problem. I still suspect is the keyboard matrix.
santiontanon: all turboR's have the same keyboardmatrix...
Eric what is your machine? Maybe someone else could try to reproduce the issue on the same msx model
I wrote this very quick and dirty ROM to test the keyboard Matrix: https://dl.dropboxusercontent.com/u/3303662/km.rom
Eric, if you have the chance, could you run it, press the arrow keys, and tell me where in the matrix do you see the little "x" that appear when you press the arrow keys?
Almost the same in Basic:
10 ' Keyboard Matrix Tester 20 ' 30 CLS: DEFINTA-Z: POKE &HF3DB,0 40 ON STOP GOSUB 130 50 PRINT"Bit 76543210" 60 FOR R=0 TO 10: PRINT"Row ";HEX$(R+1): NEXT 70 FOR R=0 TO 10 80 L=PEEK(&HFBE5+R)XOR255 90 FOR B=0 TO 7 100 IF L=2^B THEN LOCATE 6,1+M: PRINT" ":LOCATE 13-B,1+R: PRINT"o":M=R 110 NEXT B: NEXT R 120 GOTO70 130 POKE &HF3FA,PEEK(&HF3F8):POKE &HF3FB,PEEK(&HF3F9):POKE&HF3DB,1:LOCATE 0,8:END
This shows the last key pressed in matrix.
I made the test with your test program.
Here the results
X/Y
Left : 8/8
Down: 7/8
left : 5/8
up : 6/8