pixar

They can always share some of Hyperion with Pixar when Pixar is at a point to change things.

Resources are not shared between the two because Disney Animation is unionized where Pixar is not.

A company like Google, Microsoft, Pixar will certainly find plenty of good candidates on Stack Overflow.

Fifteen years ago, the modern parts of the Pixar animation system used Tcl/Tk for the GUI.

It can get messy when you take non union work from Pixar and use Union work at Disney Animation and vice versa.

They have some pretty cool papers on there, but the few landmark papers that Pixar published were all published in the 80s.

RIS is what Pixar are focusing on and rendering their movies with now.

Anyone have any insight as to why Disney would build a separate rending engine when they own Pixar and could use their renderman engine?

Alternatively, why not attribute the Pixar movies to their rendering engines?

The Pixar office campus model starts to become the norm.

The Pixar online library is a really great resource.

The global illumination tech used on monsters university was just standard path tracing with physically-plausible sharers - the first time pixar had used that instead of radiosity caching.

Also this includes pixar's "denoising as a post process" which is really amazing (and might even be applicable to cycles renders).

I am reading / listening to Pixar Founder Ed Catmull's "Creativity Inc" which is utterly brilliant and based around this topic too - and his take is that so much of these rules are platitudes.

Pixar wrote a path tracer in RSL for Monster's University, so Disney could have just used that.

Pixar recommends writing shaders in C++ now instead of in RSL, as C++ shaders are just way more performant right now.

Pixar has a whole team working on optimizing their code and whole team of researchers working on improving the importance sampling.