Open GoogleCodeExporter opened 8 years ago
The above is from:
As CPU renderers are usually fill-rate limited (CPUs suck at SIMD and memory
bandwidth), they tend to segment the scene spatially into dirty areas, and
redraw
only those. After all, if you're only highlighting a button, it's a waste to
redraw
the whole scene. But a scene with an animated background and translucent
foreground
objects has effectively the whole drawing area as its dirty area (e.g. animated
wallpaper, transparent windows in front.)
The usual way the speed up full-screen animation is to segment the scene into
layers
and composite the layers using a GPU. Compositing the layers will be very fast
since
GPUs have massive fillrate, and you only have to redraw changed layers. Compiz,
Aero
and Quartz Extreme all use this method - the compositor draws all window images
to
screen on every frame, but window images are only updated when the window
contents
have changed.
For a window manager, doing layer compositing is easy, because the layers are
pre-defined. For an arbitrary 2D scene, it's more difficult.
Original comment by Ilmari.H...@gmail.com
on 12 Mar 2008 at 5:58
I would think this should be too hard... i might try to work on a patch
Original comment by crgod...@gmail.com
on 17 Jul 2011 at 5:32
Original issue reported on code.google.com by
Ilmari.H...@gmail.com
on 12 Mar 2008 at 5:57