How are the objects in your game able to move (is there rotation), and what shapes will they be? (circles, rectangles, or something else?)

I don't mind at all ^^ And probably the biggest question is; Do you only have objects colliding with the map, or do they also collide with eachother?

I don't mind at all ^^ And probably the biggest question is; Do you only have objects colliding with the map, or do they also collide with eachother?

Just one character to deal with the physics-based collisions is all. There will be enemies that walk around, but I can use a different method for those enemies.

Basically what I've come up with is this: every cycle of the main game loop, after drawing the map (with smooth-scrolling - you'll see why that's a problem in a sec) but before drawing the main character (who is effectively one pixel in size), check to see if the byte below you (found in L6) equals 255 (a straight line of 8 bits). If it is, bounce.

So the code goes something like this: (X and Y are the main character's coordinates, inflated by 256)

Repeat getkey(15)

.Game Logic, movement engine, et cetera. A bunch of crap that works, basically.

ClrDraw
.Draw the tilemap only, not the character or anything
.After that is done...
.set some temporary variables.

Y/256->A
X/2048->B
.X is divided by 256 and then by 8 (256*8 = 2048)

If {A*12+B+L6)=255 or ({A+1*12+B+L6}=255) or ({A+2*12+B+L6}=255)
                            or ({A+3*12+B+L6}=255) or ({A+4*12+B+L6}=255)

.bounce
End

End

The code works well, however, not with the concept of smooth-scrolling (which I absolutely cannot do without). When I check the byte below the character, to see if it's 255 (which means all bits in the byte are set, thus causing 8 consecutive filled in pixels below the character), it doesn't work unless the horizontal offset (for the smooth-scrolling) is divisible by 8. When it's not divisible by 8, the byte(s) below the character are split between two bytes, and I'm only checking one byte.

My two solutions (I don't like either of them): 1 - use a boatload of Pxl-Test() commands (which I don't really want to do - it'd be slow and a pain in the neck) or 2 - check two bytes below the character, although that would also be a pain and it wouldn't necessarily work all the time (with the way I'm thinking of doing it.

Any other solutions?



Also Qwerty, Builderboy : Could you explain a little more in depth what you posted (reffering to the PM)?

Theoretically, you could completely avoid the issue of falling through blocks if you had a super-optimized engine, that had its terminal velocity set at 1 px per frame. Then any slower would be delays, not skips......

Thoughts? It's probably insane to expect on an 84+

Would you be able to push multiple objects that way? It seems they'd get stuck next to each other.

 +1 for epic screenshot response and using the " " emoticon

Quote from: Builderboy on September 03, 2011, 04:53:11 pm

Holy crap.

Well said.

Builderboy, do you remember what that screenie was from?  I remember it from something.  Was it Zedd?