burnin wrote:Basically, if there was an option to import some standardized file formats (ie. obj, fbx, abc...) into Indigo Renderer, Blender plugin would be mostly useless. Since now it creates nothing but confusion, problems.
Conversely, I've relied on it for the past few years for its simplicity and intuitive-ness for most of my arch. viz work, to great and profitable effect.
Yes, a link between Indigo Renderer and Blender - so that adjusting material / background / camera parameters in Indigo would also update them in Blender - would be a very great next step, but it's hardly useless at the moment.
FakeShamus wrote:oh, yeah I guess I've never used this kind of set up. Don't you still have to re-export for every variation? I generally tweak and swap background settings in Indigo directly and then go back to match the settings in Blender (not ideal, but...). I was just thinking in terms of people who are used to cycles, having the world option would be more intuitive. but I see the benefit of keeping both options.
Yeah, you still re-export, but I try to avoid any tweaking in Indigo, once things are far enough along. You're absolutely right: it's not ideal, and I also often tweak stuff in Indigo, then copy those setting back to Blender, but once materials, lights, and views are setup the way you want them, reproducing a set of images with modelling / scene updates is much quicker if you can hide / unhide groups of lights, including backgrounds. This is primarily in projects where you're doing incremental model / design updates, and the image set has to otherwise be identical in terms of view and lighting. It's easy to miss stuff if you have to change everything each time, instead of turning groups off and on.
Of course, having the both options would be best :)