Indigo as ActiveShade Renderer?

[Sukrim]

I know, I know, Indigo is far from being "realtime" and it even needs some time for initialisation, wich could be a potential problem...

...but hypothetically, wouldn't it be nice to have Indigo as an ActiveShade renderer in Max (or other software as well) like vRay + final render plan to do for example?

I guess the biggest problem would be the initialisation before each rendering process, if indigo could be somehow made aware that only a small part of the scene changed and the geometry for example doesn't have to be loaded again this might even be possible. If you could somehow even distribute this process over LAN, then at least some quick material (shader?) tests could be done in a reasonable timeframe, as the resolutions won't be _that_ high.

Ono, Suavakas what do you think? Possible somehow or just a dream because indigo isn't coded with fast reations to small changes in scenes in mind?

[fishbowl]

There's something akin to this with LightWave as well, FPrime. It'd be interesting to see Indigo that tied in with apps, I think the closest regarding Indigo is via XSI at the moment, regarding integration.

Anyway...

+1

[fused]

it would be possible, but i guess not with the indigo standalone renderer.

only with an indigo integration via the commercial sdk (like its coming for xsi).

would be a nice thing, tho

[Sukrim]

But with the SDK + Indigo as a pure Max renderer it would be harder to use distributed rendering and so forth, right?

Would be great if the standalone renderer could be used (or abused?) that way though...
Does anyone know how other ActiveShade renderer work? I mean how they get their data and stuff...

[rgigante]

Guess indigo->UpdateScene()?
Only one(o) knows