More people. A few twins, random walking/idling, random facing away or towards the camera.
Got lazy with the walk... so if you look closely, they have similar arms for now, no swinging arms, and they actually only step with one leg.

More people. A few twins, random walking/idling, random facing away or towards the camera.
Got lazy with the walk... so if you look closely, they have similar arms for now, no swinging arms, and they actually only step with one leg.

As I said on Twitter, looks legendary!
Thanks so much! I hope it turns out well!
Some new game mechanics including slopes!

Little sneak peek into a new scenery.

What the Crow opening title and first few seconds of gameplay.

Charge bow and... is that a six legged rhino triceratops beetle?!

It very much looks like it might be!
These titles both look so good.
I’m blown away by what you’re doing with this game. Can’t wait. Hopefully you’re making some dope music to go along with it haha
These look really good! Have you come up with creature names? How about Rhinotlops?
Thanks Adam and your help on the forum for flickering and quantizing. Do you have any tips on how to do this while following a player? Seems that because i'm quantizing the objects that parallax, the camera following the player on a easing function is causing stuttering. Trying to figure out a way around that and tried removing the .5 to round down, but that doesn't help.
Thanks for your interest! I could try making some music, but with just being myself for programming and designing the game, I might have to just use free music to save time.
Thanks! No names at the moment. Nice name!
Do you have a GIF showing the problem?
Generally the best way to quantize for anti-flicker is to do the rounding at the last moment before rendering, never storing the rounded values. Tracking the UNrounded values internally. That way rounding never accumulates to cause stutters or wrong speeds.
And also, round each object independently of others. Some may round up, some down, some may not change.
EDIT: yes, it looks like you’re rounding the camera, not the individual objects. One rounding for everything won’t work.
I don’t know in your case how easy it would be to do that. Can you track and update positions for everything un-quantized, but don’t draw using those directly—quantize them all at render time?
(Also FWIW horizontal stripes won’t ever flicker for horizontal movement... but I know you have some vertical too, and stripes really only get you one gray level.)
Another possible issue I see: quantizing to 2px increments solves flicker for 2x2 dither patterns, but only REDUCES it for larger patterns. Some of your patterns like the undersides of the big background rocks look to be 4x4—and in a configuration that quantizing won’t even reduce.
I know it would be a lighter tone, but if you used instead a 2x2 pattern with one light pixel, it shouldn’t flicker art all. (But I also don’t see a big problem with a little flicker on certain things you’re not looking directly at often.)
Alternatively, how would that 4x4 dark gray look if the 2 white dots were aligned horizontally in a single row? A stripey look? Then quantizing would stop ALL horizontal flicker. (I would suggest not quantizing the vertical on the rocks then... except that would make the 2x2 checkered parts of the rocks flicker.)
These little mountains in the background and even the player (when running) actually stutter back and forth–especially at slower speeds. You can't see it quite in the player, but can see it in the biking animation as well as if I slow the player down to a walk speed.
I think this is less of a flicker and more that they are moving to the left, then to the right, then left again.
![]()

I'll take some time to chew through what you just mentioned. I think I tried doing it with individual objects, but will take a look again.
The 4x4 pattern I custom made as it seemed to flicker the least. I think in your previous tips, you mentioned the number can be changed from 2 to 4 depending on the dither. I'll give that a try as well.

Thanks for your help!
Yes, you can use a larger number—but then the objects will “jump" in increments of that many pixels... so unless things are moving fast, that could look jerky.
It’s like a grid-snap in a graphics program essentially.
Jerking back and forth does sound like cumulative rounding errors of some kind, so that’s what I’d investigate: I see those most distant rocks in the background doing that. (Viewing a GIF in Mac Preview is how I step frame-by-frame.) If their internally tracked position is moving smoothly (fractional pixels ideally) and then that is rounded JUST to render, there should be no back-and-forth.
Good luck! It looks great as is! But I know what it’s like to want to fine tune some little glitch I’ve noticed...
I've always enjoyed scenery in animated films or games with tall grass. There is something quite nice about them. Wanted to add one to Midnight Raider as well. They don't blow in the wind or move when the player walks through then, but we'll see...

One thing that has bugged me for quite some time was that in closer up shots, the player has a ponytail, but in gameplay, it looks like two little spikes. I've added additional animations in nearly all player states to make the hair flow a bit. I especially enjoyed creating the hair movement when the bow is fully charged to give an extra effect.
