Hello... I''ve experienced a wierd thing. I need to lock my surface and manipulate it manually. If I just lock the surface and run the loop that steps through all pixels (just index, no read/write) I''ve got around 160 FPS. When I add a line in the loop that gets the pixelvalue and stores it in a temp variable, my FPS drops to around 1.4! At first I thought that the compiler (Visual C++) removed the loop when it was empty, but without the loop I''ve got like 310 FPS... Pls help.... :| // Javelin -- Why do something today when you can do it tomorrow... --

Tnx

Hmm... yes I know... but I was under the impression that the surface video memory is copied to main memory when you lock the surface...

Do you have to copy by youself if you want to manipulate surface data it in main memory?



// Javelin
-- Why do something today when you can do it tomorrow... --