a wall = no wall?

[Jonathan]

I tell you what I like, is when you manage to 'grind' perpendicular to the tip of a wall, which then can't be beat. Um, looking kinda like...

TipGrind.png

Takes very good aim. AI happen to do it more than people.

I just wish there wouldn't be so much quantization in my input and display. That would make it more reasonable and sets excellent timing apart.

Edit: added quote; got a new page.

[Z-Man]

I just wish there wouldn't be so much quantization in my input and display. That would make it more reasonable and sets excellent timing apart.

Ditto. I wish input events came with a timestamp, and display technology would move away from fixed refresh rates and move to a 'whenever the app has a new frame ready' model. Hmm. Maybe the input timestamp problem can be solved with a dedicated input gathering thread.

[madmax]

I tell you what I like, is when you manage to 'grind' perpendicular to the tip of a wall, which then can't be beat. Um, looking kinda like...

TipGrind.png

Takes very good aim. AI happen to do it more than people.

Hah! I was about to mention this. I'm always when I can't outgrind those.

[Jonathan]

Ditto. I wish input events came with a timestamp, and display technology would move away from fixed refresh rates and move to a 'whenever the app has a new frame ready' model.

In fact OS X timestamps events. Not sure if it's any good though.

For display, I found out about CVDisplayLink. It provides a callback at vertical blank with timestamps, including the nominal display time. That would be the most stable thing you can get out of the display. Gets you perfect vsync too, without clogging the pipeline at all or dropping the occasional frame. I think it beats fences.

But how would you use these effectively from SDL?