three2em Posted October 24, 2015 Share Posted October 24, 2015 Hello again, So I've been wracking my brain over a bug (?) I'm having. I noticed that the position of the ball (which I'm using as the player's missile) is always 1 pixel behind where it should be, even though the timing of it's positioning algorithm is exactly the same as the positioning algorithm for my sprites. So I dug closer and began taking note of where the ball was positioned after a RESBL call (scan cycle - pixel position) and noticed that when I did a RESBL at the exact same scan cycle as RESP0/1, the position of the ball was always 1 pixel before the sprite. Could this really be? Is there an explanation for this? Thanks. Quote Link to comment Share on other sites More sharing options...
+SpiceWare Posted October 24, 2015 Share Posted October 24, 2015 Yes, that's how it is. I touch on that in step 11 of my blog series Collect. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.