As I mentioned in my earlier [http://bucior.com/antialising-polygon-edges-for-scanline-rendering/] posts [http://bucior.com/performance-analysis-of-lookup-tables-vs-calculation-for-a-buffer-coverage/] about anti-aliasing, I'm currently working on a Nuke rotoscoping plugin. The default Nuke rotoscoping plugin is really an artist's drawing tool. You can define polys or paint on the image to

My Perception Neuron [https://neuronmocap.com/] mocap system finally arrived last week. I ordered it after Siggraph 2014 last year. It's been a bit delayed, and it looks like the final price has increased dramatically since its Kickstarter (what I paid $340 for looks like it now costs

It's performance analysis and optimization time! Truthfully, this is one of my favorite parts of any project. Most of the time it ends up being a very rewarding experience. Although ironically it's rewarding inversely to how clever you were when you originally wrote your code. If

Anti-aliasing is something many of us take for granted these days. Certainly in the realtime world there are a number of well-known techniques using clever manipulation of graphics hardware (MSAA [http://en.wikipedia.org/wiki/Multisample_anti-aliasing%5D], FXAA [http://en.wikipedia.org/wiki/Fast_approximate_anti-aliasing], TXAA [http://en.