New game for MSX1 (Transball)

Page 18/20
11 | 12 | 13 | 14 | 15 | 16 | 17 | | 19 | 20

Par Imanok

Paragon (1200)

Portrait de Imanok

21-09-2016, 19:12

Maybe something connected to joystick port which is interfering?

Par Jipe

Paragon (1614)

Portrait de Jipe

21-09-2016, 20:21

yes a mouse can disturb joystick

Par ericb59

Paragon (1102)

Portrait de ericb59

25-09-2016, 20:20

Par Manuel

Ascended (19468)

Portrait de Manuel

25-09-2016, 20:42

santiontanon wrote:

yeah, that happens Smile . It happens because, right before the screen is being cleared, all the VDP registers are set back to their original value, and the interrupts that enable the "split screen" are reset, since split screen is not needed any more. You will also notice that all the sprites disappear right before the screen clear. It's not perfect, but it does the trick Smile

Why reset these scroll registers? If you would keep them intact, the problem would be solved, wouldn't it?

Par Imanok

Paragon (1200)

Portrait de Imanok

25-09-2016, 22:57

ericb59 wrote:

Physical release is available

http://www.ebsoft.fr/shop/en/home/55-transball.html

Did you finally discover why it didn't work properly in your TR, Eric??

Par santiontanon

Paragon (1805)

Portrait de santiontanon

28-09-2016, 05:00

Thanks a lot Eric!!!!! Very exciting!!! Big smile

Par ericb59

Paragon (1102)

Portrait de ericb59

28-09-2016, 15:13

after testing on jipe ´s turbo-r i saw all was ok.
But i don ´t know why i have this bug on mine

Par Imanok

Paragon (1200)

Portrait de Imanok

28-09-2016, 18:41

Santi, I don't know how does it affect to the bug reported by Eric, but when you read the joystick port 1 you do:

call RDPSG
and #af

I think you should use #bf instead of #af

Par santiontanon

Paragon (1805)

Portrait de santiontanon

28-09-2016, 19:17

Good catch Imanok! indeed that was #bf (fixed in github).

But I don't think that's the problem Eric was reporting, since for Eric the keyboard does not work either.

So, yesterday I started to suspect the problem with Eric's turbo-r is that it has a different keyboard matrix than the one Transball is expecting. Transball's code for checking the keyboard ("CheckInput" function in "transball-input.asm"), assumes that the arrow keys are in row 8, since looking at this article ( http://map.grauw.nl/articles/keymatrix.php ), I saw that was a good assumption. But perhaps there are other keyboard matrices that I am not accounting for, and Eric's turbo r happens to be one of those...

Par Grauw

Ascended (10768)

Portrait de Grauw

28-09-2016, 20:20

That's not the case.

Page 18/20
11 | 12 | 13 | 14 | 15 | 16 | 17 | | 19 | 20