Indigo 2.4 - Don't Make Me Think

[PureSpider]

"Complex layer masking thing" isn't so complex at all, I use it every day, all the time, for pretty much every layer in an image.

+1... whats hard about using the alpha image as a layer mask?

[pixie]

In this regard I would like to see some sorts of a bridge system where Indigo would, if the scene was equal object wise, accept different attributes and change those accordingly. While it might be not much of a problem loading a small scene all together,it would make a great difference in big ones... always towards an on-the-fly change philosophy, not anything that may goes against unbiased one.

[Soup]

That was quite the confusing post pixie But I think I know what you mean, Blendigo and SkIndigo both have quick export features that exports super quick and is great for fast iterations of material changes and things like render settings and camera movement.

[pixie]

That was quite the confusing post pixie But I think I know what you mean, Blendigo and SkIndigo both have quick export features that exports super quick and is great for fast iterations of material changes and things like render settings and camera movement.

Cindigo had it too back then, still I was aiming a step forward. I'll try to be a bit more clear.

Indigo isn't a studio and never aimed as such, people are used to their workflow in their native 3D app, where they edit materials, model objects, indigo attributes, whatever... yet each time the scene gets exported it all starts over, even if some few changes are made, whether it is a small change as using another env map, some tweaking in the table own material, or more extreme as on adding or removing some object to/from the scene.

It would be nice if there was a way to keep the scene alive and create a bridge between the exporter and the indigo app, so the scene could be tweaked in the 3D app and the changes reflected in Indigo, by tweaking material values, adding/removing objects to the scene.

[Soup]

hmm.. even if you did it real-time while Indigo was rendering, the render would have to be restarted anyway. The current render would get all messed up with changed data.
But I see what you mean. Like IPR in maya (interactive ...p render).

If you had Indigo running with the 3d package, like mental ray has been done, then sure, that would be possible. But it doesn't seem at all practical at the moment. Maybe 4.0

[pixie]

hmm.. even if you did it real-time while Indigo was rendering, the render would have to be restarted anyway. The current render would get all messed up with changed data.

No doubt about it, still it should take much less time to restart a scene then currently it takes, even with the fastest approaches.

[dougal2]

I thought that kind of integration is what the indigo SDK is all about. Seems Nick has that set up as a separate commercial enterprise, so I wouldn't expect to see it as part of the mainline exporters soon.

[benn]

The Indigo SDK doesn't really help that - the time is spent in reparsing the xml and rebuilding the scene. We are aiming to solve this later in the year with IndigoSG (Indigo scenegraph) which will allow changing of many indigo scene parameters without rebuilding the whole scene. The render will restart of course, but it will take only 0.1 seconds to restart the render, not 2 minutes of scene reparsing time.

[pixie]

The Indigo SDK doesn't really help that - the time is spent in reparsing the xml and rebuilding the scene. We are aiming to solve this later in the year with IndigoSG (Indigo scenegraph) which will allow changing of many indigo scene parameters without rebuilding the whole scene. The render will restart of course, but it will take only 0.1 seconds to restart the render, not 2 minutes of scene reparsing time.

These are great news! But is this a different product or integrated into the indigo family as Indigo Material Editor is?

[neo0.]

Just to clear things up, Alpha masking is by no means the most difficult thing you can do with photoshop, but keep in mind, everything is relative. To the uninitiated, it can be pretty confusing, but nothing could be more simpler than having a button in indigo that says "Set background image."

Frankly, there are other advantages to it. If you load in your background image and you see a problem with it, you already know. You don't have to wait another 5 minutes to find out. Plus, if the background images were an actual part of ingigo, they could be part of the scenes physically accurate simulation. For example, a background image might be placed by indigo outside a window, which would let it simulate all the refraction, reflection, etc depending on whatever material you were using.

Also, mapping options would be neat.. For example, flat mapping, or spherical mapping..

[StompinTom]

If you load in your background image and you see a problem with it, you already know. You don't have to wait another 5 minutes to find out. Plus, if the background images were an actual part of ingigo, they could be part of the scenes physically accurate simulation. For example, a background image might be placed by indigo outside a window, which would let it simulate all the refraction, reflection, etc depending on whatever material you were using.

Yes, of course, but you were referring to being able to swap the background image in the middle of a rendering, as far as I understand. You can already set a background image and have it reflect/refract.

[Soup]

Check out the tutorial I made just for you Neo0
Here

[PureSpider]

Plus, if the background images were an actual part of ingigo, they could be part of the scenes physically accurate simulation. For example, a background image might be placed by indigo outside a window, which would let it simulate all the refraction, reflection, etc depending on whatever material you were using

Those things are called "Environment map" or even "Background material"...

[neo0.]

Wow, thanks, soup. This is awesome!

[Polyman]

It would be really great if the 2.4 version would support CUDA and OpenCL.