Cindigo 3.2.9 - Integrated Beta
Posted: Wed Mar 14, 2012 7:46 am
Cindigo 3.2.9 - Integrated Beta
for Indigo Renderer 3.2.9 and Indigo RT 3.2.9
Hi everyone,
after a considerable development effort the next-generation integrated Indigo for Cinema 4D is finally ready for release! "Integrated" here means it won't write anything to disk unless it has to (e.g. baked shaders), and that you can use Indigo within C4D. By not involving disk access, and working directly with the Indigo SDK interface, this allows for a much tighter workflow.
If you already have an Indigo Renderer licence you should be able to use it without problems (it picks up your existing Indigo licence). Indigo RT is currently not fully supported at the moment; you can still use it, but certain restrictions apply.
You'll find Indigo Renderer in the list of renderers in C4D's Render Settings window (for versions that have such a list) otherwise (version 10 and 10.5), you just add Indigo as a post effect, as per usual, and Indigo should then be used as the renderer.
There is also new tonemapping functionality that you can access through the "Indigo Renderer" menu in the Picture Manager (Picture Viewer).
The familiar scene export functionality was of course not removed and should work normally.
Support for R9.6 was dropped, as it's become a major hassle to support due to its outdated API (and the changes required for the newer versions).
Finally, please keep in mind that this is a beta release and that there are a good few issues left to fix (save often).
Please report any bugs you find, thanks!
[UPDATE] There is a new version, 3.2.9.1, which you can find here: http://www.indigorenderer.com/forum/vie ... 10&t=11491
for Indigo Renderer 3.2.9 and Indigo RT 3.2.9
Hi everyone,
after a considerable development effort the next-generation integrated Indigo for Cinema 4D is finally ready for release! "Integrated" here means it won't write anything to disk unless it has to (e.g. baked shaders), and that you can use Indigo within C4D. By not involving disk access, and working directly with the Indigo SDK interface, this allows for a much tighter workflow.
If you already have an Indigo Renderer licence you should be able to use it without problems (it picks up your existing Indigo licence). Indigo RT is currently not fully supported at the moment; you can still use it, but certain restrictions apply.
You'll find Indigo Renderer in the list of renderers in C4D's Render Settings window (for versions that have such a list) otherwise (version 10 and 10.5), you just add Indigo as a post effect, as per usual, and Indigo should then be used as the renderer.
There is also new tonemapping functionality that you can access through the "Indigo Renderer" menu in the Picture Manager (Picture Viewer).
The familiar scene export functionality was of course not removed and should work normally.
Support for R9.6 was dropped, as it's become a major hassle to support due to its outdated API (and the changes required for the newer versions).
Finally, please keep in mind that this is a beta release and that there are a good few issues left to fix (save often).
Please report any bugs you find, thanks!
[UPDATE] There is a new version, 3.2.9.1, which you can find here: http://www.indigorenderer.com/forum/vie ... 10&t=11491
changelog wrote:Cindigo 3.2.9
---------------------
* Added Radial splat filter.
* Added GPU switch.
* Added preview quality options.
* Fixed texture baking for non square resolutions.
* When an Indigo material is created, it is shown in the AM (because creating a C4D material does that).
Cindigo 3.2.8
---------------------
* The export now fully uses the SDK. In an internal rendering, nothing is written to disk (except for baked textures).
Cindigo 3.2.4
---------------------
* Only used materials are exported.
Cindigo 3.2.3
---------------------
* added tonemapping dialog back in. It's also now dockable.
* "Indigo Renderer" should now be in the external renderers list (in versions that support it).
Cindigo 3.2.2
---------------------
* fixed pigm import issue on Mac (failed to load textures)
* fixed "failed to bind material" bug
* fixed issue with relative texture paths in material previews
(I will look into improving that)