australiatrio.blogg.se

Stretchblt vs copyimage
Stretchblt vs copyimage








stretchblt vs copyimage

Having hardware acceleration is not mutually exclusive with having unaccelerated offscreen memory DCs. That is done only for operation that actually draw to device DC's of course (after all, it's Graphics Device Interface). Show me proof if you can.Īctually, GDI is often hardware accelerated. Have you ever tried to copy memory from OpenGL to GDI or vice versa? Can't do it in hardware. If GDI functions were hardware accelerated, then that means the device context (hDC) is also hardware accelerated, which also would mean you could create a hardware accelerated offscreen memory hDC that could be used with OpenGL, etc. On ATi cards (at least the ones I've tried), it is not accelerated and is dog slow, managing only 5fps or so when stretching a simple bitmap from 640x480 to 1024x768.

stretchblt vs copyimage stretchblt vs copyimage

On nvidia cards, StretchBlt is hardware accelerated and is very fast. StretchBlt can be fast and it can be slow. Now that I took the time to manually figure out where those clipping planes should be when I 'zoom in' on my bitmap, StretchBlt() works extremely fast. It seems when I first used StretchBlt() a month ago I must have been using it inefficiently (without the clipping values etc) so I was under the impression it was really slow.










Stretchblt vs copyimage