Here's a stab at getting the shader ball working. It'll only be really useful once #24 is solved, as it runs into the same issue of not finding the BSDF socket output on shaders - though previewing shaders via a cclOutput node works as expected.
As part of this I've changed the display driver creation so it no longer expects an explicit "Interactive/Beauty" output name (as the ShaderView creates an output called "Beauty"). That commit also contains a fix for interactive outputs attempting to be written to images in batch renders.
Cycles doesn't seem to support using negative thread counts to render with all but those threads, so I've added support for that when we handle the ccl:session:threads option. It's in a separate commit, feel free to include it if you think it's useful.
Here's a stab at getting the shader ball working. It'll only be really useful once #24 is solved, as it runs into the same issue of not finding the BSDF socket output on shaders - though previewing shaders via a cclOutput node works as expected.
As part of this I've changed the display driver creation so it no longer expects an explicit "Interactive/Beauty" output name (as the ShaderView creates an output called "Beauty"). That commit also contains a fix for interactive outputs attempting to be written to images in batch renders.
Cycles doesn't seem to support using negative thread counts to render with all but those threads, so I've added support for that when we handle the ccl:session:threads option. It's in a separate commit, feel free to include it if you think it's useful.