Kartoffel@ thank you! I'll give it a try!

Best regards!

Oh I forgot to add: There sometimes were problems that removing a bmap didn't work properly after it was used as a rendertarget. After a few times of recreating the rendertaret directx throws an error. I'm not sure under which conditions this happens, though. (maybe when not removing everything properly, so the rendertarget is still referenced somewhere from the graphics api and not removed as a result. just a wild guess.)

I am sorry, I wanted to do some tests before answering but forgot it in the way. Better late than never

The main idea was to set the largest render target from the beginning and modify the views size only, instead of rebuilding everything each resolution change. As spected, there is no need of deleting anything. The rendering chain, main cameras render target inclusive, survives to a resolution change, and also to a blank level load as long as I tested it. Very few changes were needed to acoplish the goal. I added two functions that build and remove the whole rendering chain too. I guess that the negative side-effect comes from the fact that the whole render targets are cleared before rendering, a bunch of not visible pixels are also cleared on windowed video modes. Nothing to worry about, I think. Maxime when you leave render targets in peace forever.

pixelation01.zip

Salud!

Hey man!

It works pretty great! Thank you very much for your time! The only thing I can notice so far is that 'axe' effect sometimes is blinking or chancing it's length, is that related to pixelation, what do you think?

Edit: nahh, it seems that it's just related to framerate

Best regards!