Re: Screenshots

[XTF]

Yes, that was mainly done to improve performance. Several testers reported significant speed improvements after applying that change. It makes sense, because if a surface was in VRAM, Lock() has to transfer it all into system RAM before it can give you a pointer to it, and Unlock() has to push it back to VRAM...

Or lock() maps the video memory into the app's address space, which looks to be happening in my case. That's even slower.

and in some places the geniuses at WW draw stuff pixel by pixel, causing repeated lock/unlock cycles.

Ouch.

Why are you working with PNG? I'm pretty sure that a simple read/write loop into a 16 bit BMP will work faster than read/process/write into a PNG, doing image compression here feels like a waste of time to me.

PNG can be uploaded to the web as-is. XCC Mixer doesn't even support BMP.
Compression time is no problem.