neo0. wrote:IMHO, indigo became much more than just a simple rendering engine back when the we got the new UI.
If you know how to work with your 3D app and the exporter, you'll barley need the GUI. Once RealTime rendering is inside a 3D app (like in the new Max exporter) it will become obsolete to your workflow...
The point is basically that my Source File is the file of my 3D app! Tweaking and testing out of my 3D app is directly applied to my source file and therefor achieved progress! All the playing around in the GUI needs to be transfered back to my source file I work with. Since tweaking bump values or exponent map settings etc. can be really fast in the GUI, and results transfered quickly back to the source file thats nice!
The Problem starts with extended stuff you are requesting all the time!
Editing UV settings painting textures etc. is hard to transfer back to the source file, even impossible in some cases! Why should I do that?
If my client has some changes where I need to edit my source file, all the work in the GUI and saving to IGS is lost!!!
If I work on days on a scene for a client, I need ALL my progress to be in my source file, since changes are often wanted. Indigo is the renderer and the Exporter the important tool to set it up.