Tiled Bitmap in C API

SDK Get Help
1

Hello, first post here:

I'm reading through the docs, and I can't seem to find the correct way to draw only a small rect/tile from a bitmap.

I tried the following:

playdate->graphics->setClipRect(posX, posY, charSize, charSize);
playdate->graphics->drawBitmap(bitmap, 
    posX - (animIndex * charSize) - ((charIndex % 16) * charSize * 2), 
    posY - ((int)(charIndex / 16) * charSize), 
    kBitmapUnflipped
); //Basically, moving the whole image around to land on the clip rect
playdate->graphics->clearClipRect();

I know there's this: playdate->graphics->tileBitmap
But it doesn't seem to do what I want to achieve.

Should I be using sprites? If so, then how can I tile them?

2

Generally I prefer to use bitmap tables to draw parts of an image, but that requires all of the sub-images to be laid out in rectangles of the same size. If bitmap tables are not suitable for your purpose, then what you are doing should work. The only thing I'm not sure about is the math in (animIndex * charSize) - ((charIndex % 16) * charSize * 2) and ((int)(charIndex / 16) * charSize). But since I don't know how your spritesheet is arranged, I can't say for sure. You say that it doesn't do what you want, but what does the code actually do?

3

I'm not sure about is the math

It cycles through these characters using the D-Pad, each with two frames of animation (image is cropped)
creatures_copy

It's just a test, really. What I'm wondering is if there's a (more straighforward) way to draw a scene from a spritesheet, without having to split the image.
playdate->graphics->tileBitmap seems to draw only the top left rect of the image afaik.

And I know I shouldn't be worrying about performance right now, but it's already at 49FPS with only one character on screen. I've seen whole games and more complex demos running at 50. Perhaps it's because the image is "big" (1536x1968).

4

Ah, I misunderstood your original post. So the setClipRect code does actually do what you want? If you are worried about optimization, I guess you could convert the division and modulus to bit shifting operations since they are power of two. The compiler optimization might do that automatically, I'm not sure.

In your case, I don't see any downside to using bitmap tables. It's basically a convenience feature that allows you to access a spritesheet by index. You don't really have to "split" the images, unless I am misunderstanding your use case.

As for tileBitmap, I think that is just for repeating a bitmap multiple times in a rectangle, not for drawing part of a bitmap.

1 Like
5

I totally misunderstood how bitmap tables were supposed to work. I assumed I had to add bitmaps one by one. I completely missed the part on setting a postfix for the spritesheet. Going back and forth between Lua and C is a pain, it's explained a lot better in the former. I also forgot I was clearing the whole screen each frame.

Now it works flawlessly. Thanks!