Ok then, thanks for the clarification. Lets see if that fixes it.

When you get to the actual game, specifically the bit with the money moving and all, you'll want to take advantage of double buffering; for now, though, you should be fine just staying on one side of the LCD. To do this, you can use the real(8,1 command to set the side of the LCD being drawn to; if you set it to the side you're currently looking at, you won't have to worry about setting the UpdateLCD argument to 1.

There we go! Fixed it all up, and I have multiple walriis on screen! Now to code erasing, and throwing the coin!

Bump!

So, I got sprite erasing down, there's just a little flickering, and the rectangles I used to erase aren't tall enough. Easy enough to fix! Except the flickering, how would that be fixed? Any help there? Would I have to switch sides of the screen or something?

I haven't gotten around to drawing the player, so that's gonna happening tomorrow. If you don't' know yet, the player will be a purple mouse cursor.

Anyways, screenshot!


EDIT: I fixed up the display issues with the sprites,there's just flickering to think about. Should I get rid of it though? It kind of gives the illusion of flying/flapping.

Bump

Welp, I have the updated screenshot, but I kind of lost inspiration for today, making the walriis populate the screen much less. So, I'm gonna add the cursor to the spritesheet and code movement.

Then we'll see how I can do this.


EDIT: Updated Spritesheet! There's gonna be a little surprise in there...



EDIT 2: Welp, there's a problem. How am I going to erase the player sprite? The background is, well, very colorful. I can't use real(7,9 either. What should I do? Create a sprite that uses the same patter as the background to erase the player sprite.

EDIT 3: DJ informed me of real(5,3 so that problem is solved. Also, its seems like I am doing something wrong with the pic index.


Code:

Does not display the cursor right. So what am I doing wrong? It seems to be 3,4,11,12.

Thats about it for today!

Well, the pic index start should be 0, not 1. And I'm not sure where you got 3,4,11,12 from-- it would be 32,33,40,41 because the spritemaps are sorted column-first.

oops, I didn't update the spritesheet image. Here it is:



This is what happens to the sprite. Ignore the bottom 3 copies


EDIT: I fixed everything, per Wrights suggestion, I changed the StartPicIndex to 0 from 1. So yeah, now its time for redrawing the background after the player moves.

bump.

So I am needing help! I am using a VERY crude way to display and erase the walruses. I think it needs to be totally rewritten. I want it to display the walruses for 3-5 seconds each, and then erase. So any suggestions on how to optimize and change the code?


Code:


And I can't figure out how to use the draw background command, hence the blue after the mouse cursor.



Well thats weird. The blue doesn't show up after the mouse cursor, but it does that on my calc, and I think the versions are the same.

Thanks in advance!

How is the game suppose to work? Are five walrus shown at one time or just one moving around?

You are supposed to throw money at walruses, but the walruses are not really displaying how they will. They will display at random for 5 seconds, then disappear.

How many walruses will be on the screen at once?

5, of course

Update your version of Doors to fix the background problem. Use the buffer to eliminate flicker by drawing the background on both sides. For the cursor, use another variable to hold the old sprite location. Draw the cursor (switching the buffer) then delete the cursor at the old location regardless of a button press or not.

Ah, I have forgot to update Doors on my calc, but it is updated on wabbit. :\

Also, there won't be that much flicker, as the sprites will only be erased every few seconds, rather than milliseconds

So the above screenshot isn't that accurate, and I should have a good one tomorrow.

Bump



Code:


So now There are random blue lines everywhere and walrii only displays once.

Any suggestions for that? I haven't had much time to look at it, so please bear with me if its a silly mistake.

bump, again

Just recently resent everything to my calc, without changing a thing, and there seems to be corruption. When displaying the sprites, the Walrus becomes white, and the mouse becomes green. I remade the spritesheets, but it still occurs, That led me to the conclusion that my code was the problem. But, I didn't change a think to do with displaying sprites! Any help here?



Code:


File: zip

It sounds like you set up a color offset with real(0,3,5) somewhere, but I don't see that in your code. Can you explicitly set a color offset of 0 at the beginning just to make sure that's not related?

It's not just you; write real(0,3,5,0) at the beginning of your program to fix it. I think Doors messes it up, since it happens to me even right after a RAM clear.

I believe my post above suggested the same idea. However, if this is a persistent problem, tr1p1ea and I need to deal with it. Thanks for the confirmation that this may be an outstanding bug we need to fix.

Welp, that fixed it
Now, I think I'm gonna have troubles with sprite collision.

Count, I know understand.

How would I check if sprite at A,B with a W/H of 16 meets another at D,C with a W/H of 16?

real(4,6,1,A,B,16,16,C,D,16,16 is what I get. Is that correct? If they do collide, they would return 1 to ans right? To check multiple sprites at once, would I need multiple real(4,6 commands?