Indigo Renderer Forum

This is a Beta release.
If you spot any bugs or problems, please make a post about them in this thread.
Thanks!

Indigo for Windows 32-bit:
IndigoRenderer_3.2.1_Setup.exe

Indigo for Windows 64-bit:
IndigoRenderer_x64_3.2.1_Setup.exe

Indigo for Mac OSX (10.5 - 10.7):
IndigoRenderer3.2.1.dmg


Indigo RT for Windows 32-bit:
IndigoRT_3.2.1_Setup.exe

Indigo RT for Windows 64-bit:
IndigoRT_x64_3.2.1_Setup.exe

Indigo RT for Mac OSX (10.5 - 10.7):
IndigoRT3.2.1.dmg

Changelog:
3.2.1
* Bundled SkIndigo-3.2.1-Installer.exe
* Fixed problems with null materials and bidir.
* Added save_png option to RendererSettings
* Improved error messages for invalid emission scale or IES material names.
* Fixed zoom combo box order.
* Faster tonemapping.

I'm sorry to repeat.... the "render settings" tab has a problem!
I tried on E8400-xp, E6550-vista64, Atom330-vista, Atom230-seven. It disappears when starting Indigo (anchored in the layout or not, is the same)

:)

Null materials work like a charm now!
Post Aperture Diffraction still seems to be very slow... there might be some need for improvement.

zeitmeister wrote:Post Aperture Diffraction still seems to be very slow... there might be some need for improvement.

I can second that.
My test-scenario for this is a 800x450 render with SS4 takes 900MB to render.
Switching PostPro AD on, the RAM usage raises to 4.3GB (!!!1!) and Indigo only keeps working on 1 core for ages!

Please multithread the PostPro AD and finally apply it after doing SuperSampling, otherwise its useless and only good to hang your system...

Confirming single-threaded post aperture diffraction here.

Something else a little nasty:

rendering with a "halt parameter" and a "image save period":

halt condition reached => no autosave!
instead => waiting for save period!
even after stopped rendering the image gets re-saved each XX seconds until end of time.

Autosave for animations in the Q looks good, but the last image seems to behave like above!

I would suggest that reaching halt parameter (for a still image) the image doesn't get stopped, but paused!
Also raising the halt parameter in the GUI and continuing should be possible here...

for sure no show-stoppers, but still something thats "looks strange" to me.

Zom-B wrote:Switching PostPro AD on the RAM usage raises to 4.3GB (!!!1!) and Indigo only keeps working on 1 core for ages!

This.

Zom-B wrote:

zeitmeister wrote:Post Aperture Diffraction still seems to be very slow... there might be some need for improvement.

I can second that.
My test-scenario for this a 800x450 render with SS3 takes 900MB to render.
Switching PostPro AD on the RAM usage raises to 4.3GB (!!!1!) and Indigo only keeps working on 1 core for ages!

Please multithread the postPro AD and finally apply it after doing SuperSampling, otherwise its useless and only good to hang your system...

Hi Zom-B,
You are quite right, although I did some work on the creation of the aperture diffraction filter, the actual application is still quite slow and memory intensive. I'll try and speed it up, but it's quite tricky

OnoSendai wrote:I'll try and speed it up, but it's quite tricky :)

Speed isn't the main concern, but RAM usage disqualifies PostAD as a option for a lot of my projects :/

Another small detail:

The scene specific metadata don't get displayed in the Indigo GUI, only the scene span.
Cindigo for example sets these metadata in the igs:

Hi guys!
..is it only me, or the tonemap changes done during the rendering are not autosaved in the image?

I need to manually save the render to get the light layers' colour corrected!

Disable the medium for a material and indigo crashes.
Medium isn't added to scene list but adding a new medium from toolbar then adds both to the list.
Pause render, then change material settings or whatever and the render starts, but still shows paused.

...and red dots strangely appear in my basic testscene.
See attached! Thanks guys!

A allergic reaction to the lack of super-sampling Pibuz ^^
GPU mode?

Pibuz wrote:...and red dots strangely appear in my basic testscene.
See attached! Thanks guys!

That is odd.. works fine for me. As Zom-B asked, are you using GPU?