[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] image.load() -->> array?
Ian Mallett wrote:
At 900fps, then, at max, the frame was rendered 1/900th
of a second ago. If, however, your frame rate is 60fps, like your
refresh rate, the frame was rendered 1/60th of a second ago.
I doubt that human reaction times are anywhere near good
enough to notice a 1/60 second difference in timing.
But either way, 1/59 of a second after rendering the
last frame, the image is going to be nearly a whole
frame out of date. If you're relying on millisecond
precision for your shooting, you're already in trouble.
With motion blurring, one can do that with OpenGL; it's called
"Fullscreen Antialiasing".
That's not the same thing -- FSAA smooths adjacent pixels
in a single frame, whereas motion blurring is about
smoothing between successive frames.
That's one way you could make use of your 900fps, though --
render several frames and blur them together.
That's assuming you wouldn't rather just use the power
to render a boatload more polygons instead, or some other
fancy effect.
--
Greg