Note that for the Cycles wrapper there will be a lot of Cycles-specific, but the client concept is for having multiple parts access Cycles, and the client ID controls the actual access to Session and Scene, which are actual Cycles classes.
You don’t have to replicate the cilent concept, it maybe isn’t even that necessary, but I wanted to have it in so I don’t have to make big changes later on. As you already noticed, it is currently pretty much only used for assigning different loggers for different clients.
I suppose initially it won’t be all too much of an issue, and we could safely assume there will be just one ‘scene’ or instance of Indigo at one time. I am currently making that assumption in the wrapper anyway.
Chipping away at the Indigo wrapper: running Indigo from a C# script in Grasshopper.
The very basics are in (mesh export, scene settings, camera settings). I think I will focus on getting the wrapper fleshed out and cleaned up before stitching it into the render plug-in.
