Jump to content



0

Batari, quick question


No replies to this topic

#1 jbs30000 OFFLINE  

jbs30000

    Moonsweeper

  • 459 posts

Posted Thu Nov 3, 2011 3:46 AM

View Postbatari, on Thu Jul 28, 2011 1:33 AM, said:

Collision detection:
* Pixel-perfect collision(player#,player#) where # is 0-9, for any two real or virtual player sprites (doesn't support NUSIZ changes yet, sorry.)
* A kernel_option controls an in-kernel read of a standard hardware collision register (example: set kernel_options collision(player1,playfield) will return the y-coordinate where the first such collision occurs, so you can later figure out what sprite it was.) Value is returned in temp4 after a drawscreen.
How does temp4 work? I tried playing around with it but I don't quiet get it I guess. Thanks.

Edited by jbs30000, Thu Nov 3, 2011 11:17 PM.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users