You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a sprite is over bitplane graphics, the sprite is rendered one pixel too high and one pixel too far right. The sprite is overlapping the top or right borders by one pixel, and not reaching the bottom or left borders by one pixel.
Here's a simple joystick-controlled drawing program that illustrates the issue:
10 screen 0,320,200,5
15 sprite 0,1
20 x=100:y=100
30 pen 1
40 j=joy(2)
45 movspr 0,x+24,y+50
50 if j and 128 then dot x,y:j=j and 127
55 sleep 0.01
60 if (j=4 or j=5 or j=6) and y<199 then y=y+1
70 if (j=2 or j=3 or j=4) and x<319 then x=x+1
80 if (j=8 or j=1 or j=2) and y>0 then y=y-1
90 if (j=8 or j=7 or j=6) and x>0 then x=x-1
100 goto 40
Notice that the same program in text mode does not exhibit this issue:
15 sprite 0,1
20 x=100:y=100
40 j=joy(2)
45 movspr 0,x+24,y+50
55 sleep 0.01
60 if (j=4 or j=5 or j=6) and y<199 then y=y+1
70 if (j=2 or j=3 or j=4) and x<319 then x=x+1
80 if (j=8 or j=1 or j=2) and y>0 then y=y-1
90 if (j=8 or j=7 or j=6) and x>0 then x=x-1
100 goto 40
This nominally sounds similar to #132 or #289 but those issues are very old and I can't tell if they're actually the same, just related, or unrelated.
The text was updated successfully, but these errors were encountered:
Tested with ROM V920409 beta and dev core 0.97.
This problem also occurs when the mouse sprite is visible. It is more than a pixel off.
I wrote a little test program to illustrate the issue. You can paint pixels on screen while pushing the left mouse button. The position should be the upper left corner of the mouse pointer, which is not.
When a sprite is over bitplane graphics, the sprite is rendered one pixel too high and one pixel too far right. The sprite is overlapping the top or right borders by one pixel, and not reaching the bottom or left borders by one pixel.
Here's a simple joystick-controlled drawing program that illustrates the issue:
Notice that the same program in text mode does not exhibit this issue:
This nominally sounds similar to #132 or #289 but those issues are very old and I can't tell if they're actually the same, just related, or unrelated.
The text was updated successfully, but these errors were encountered: