/prog/ 2012 challenge

Brothers and sisters,

As the end of the year comes closer, and we reflect on what has happened on /prog/ this last year, we have to admit that we did not accomplish very much. Perhaps in our private lives, yes, but here on /prog/ we have spent the majority of the year trolling, meta-trolling, complaining about it and going nowhere in particular. If we look at our community I'm going to say we have very little to be proud of: /prog/ kinda sucks.

I say we change all that. I say in 2012 we band together and prove that /prog/ is better than it has ever been before just by making it so. That we can come to /prog/ with an expectation of lulz and wisdom. I'm willing to make the effort, who's with me?

ITT post your new years resolutions for /prog/, I'll start:

* If I have nothing substantial to say I will sage it.

>>8

yeah, I suppose it would come down to locating the point at which the collision occurred, and then checking to see if that region of the face was affected by the special paint. I think a geometric approach for this would be easier than a texture based on, but maybe it could be done well. The geometric approach could be implemented pretty easily on the cpu side, and if GPGPU is already being used for collision detection and resolution, then it probably wouldn't be too bad to extend it to support this behavior.