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_2.4.2_Setup.exe

Indigo for Windows 64-bit:
IndigoRenderer_x64_2.4.2_Setup.exe

Changelog:
2.4.2:
* Added aspect ratio locking
* Added selection tool, zoom to selection
* Added copy selection to clipboard
* Fixed zooming to centre on mouse pointer
* Disabled dock widget resizing
* Added light layer UI with colour temperature support
* Added css theme support
* Added wait_for_slave_frames_on_stop option to renderer_settings.
* Made --thread_priority and background mode tickbox change whole process priority.
* Added Network Manager to main Indigo distributions
* Disabled igs saving (pigs saving only for now)
* Added default_settings.xml to dist.

2.4.1:
* Handling IndigoDriverExcep's caused by failure of EXR or IGI saved. (fixes crash)
* Fixed bug with false self intersection with SSS.
* Discarding incoming network image frame if dimensions do not match master buffer dimensions.
* added verbose flag to control some output, set to false by default.
* Not caching kdtree to disk if less than N triangles.
* Better BVH Builds.
* Faster Kd Tree builds.
* Added UV tex coord generator affine transformations.
* Changed logging to append to log.txt as opposed to overwriting it.
* Prepending indigo base dir to nkdata path for network rendering fix.
* Updating host description in GUI earlier in network protocol.
* Added network_client_service executable to distribution
* Added network_client_service_manager executable to distribution

The Network Manager

The network manager does a couple of things:

The network manager can coordinate network rendering, by assigning slaves to masters.
It can be used instead of the old UDP broadcast system. The old UDP system had limitations in that it was difficult to do network renders on computers on a different subnet, unless the master hostname was explicity given on the command line. The new network manager gets around this problem - just configure each copy of Indigo to talk to the network master, and then whenever an indigo starts with network rendering enabled, the network manager will assign any free slaves on the network to that master.

To set up the network manager, first decide which machine you're going to run it on, and then record that machine's DNS hostname.
Then run the network manager on that computer.

Then on every computer you have Indigo running on, go to the install directory, e.g c:\Program Files\Indigo Renderer.
Copy default_settings.xml to settings.xml
Edit settings.xml, change the setting do_master_search_broadcast to false (to disable the UDP searching) and then set the network_manager_hostname value to the hostname you noted down earlier.
Save settings.xml

Then start a render with the network rendering button pressed. That Indigo instance should then show up in the network manager as a master.
Likewise, and slaves started should show up as slaves.


The network manager also does floating network licences, which is a new kind of Indigo licence, meant for easy administration of business deployments of 5+ Indigo licences. The floating licences are different from the current licences, so it's not possible to enter you current licence into the network manager.

Wonderful!
I was waiting for this!!! Thank you Ono, I'll report the bugs if I spot any!

I get this error: Tried registering the Indigo Network Manager and I got this:

Sweet! *off to play*

Finally a new Toy to play with :D Thanks a lot for this release!!

I just started and only had the same issue about the licence data with the Network manager.
At least networkrendering works fine for me and networkmanager finds master & slave,
but both are droping following message each 5seconds:
There is also a Problem with the light Layers!!!

Indigo sets them always to BlackBody 6500 and converts the color... so I loose my exported light settings -.-
Nothing gets detected, not RGB light not uniform, and also BlackBody with different Temp. gets converted to 6500.

Next evilness is breaking SubDiv finally even more than it was :P
Best seen for transparent materials:

Zom-B wrote:There is also a Problem with the light Layers!!!

Indigo sets them always to BlackBody 6500 and converts the color... so I loose my exported light settings -.-
Nothing gets detected, not RGB light not uniform, and also BlackBody with different Temp. gets converted to 6500.

Hey Zom-B!

No that is not an issue

Light layers do not respond to the actual colour(or temperature) of your light in your scene. Its a post process. Also, if you have a red RGB emitter, it doesnt turn you light layer red

fused wrote:No that is not an issue :)

It is m8, since you altering my light color output without my permission :P
renderings in 2.2.12 look different tinted than 2.4.2 now...

I had a issue in 2.2.12 for my renderslave where the networkclient started in indigo.exe doesn't get killed after closing, but stays in taskmanager crunching 1 core to death.

Now with 2.4.2 this is getting even heavier!

Closing my network client, it stays in taskmanager and grabs for 2 cores to burn them and also eats RAM each second like a pro:

Zom-B wrote:

fused wrote:No that is not an issue

It is m8, since you altering my light color output without my permission
renderings in 2.2.12 look different tinted than 2.4.2 now...

I'm not

Indigo 2.2 did that by using XYZ colourspace instead of RGB. So in fact it did that all the time and I now corrected that for you (XYZ (1,1,1) and RGB (1,1,1) are quite different).

I guess it would probably make sense to also offer XYZ for lightlayers, so users can have the "old" look. I will implement that for the next version then.

The 64 bit version works very well. Only the color adjustment is getting used to, but there is no problem. And the background mode now works with me.

OnoSendai wrote:* Added selection tool, zoom to selection

Found it, but the usage is quite uncomfortable atm... Integrating this with 2 icons to the zoom icons on the bottom right would be maybe more intuitive

OnoSendai wrote:* Added copy selection to clipboard

Hmmm.... how to do this... after doing a selection only "Copy image to Clipboard" is available from the edit drop-down.

Zom-B wrote:

OnoSendai wrote:* Added copy selection to clipboard

Hmmm.... how to do this... after doing a selection only "Copy image to Clipboard" is available from the edit drop-down.

oops, looks like this option is missing
it will be in the next version. sorry about that.

Zom-B wrote:

OnoSendai wrote:* Added selection tool, zoom to selection

Found it, but the usage is quite uncomfortable atm... Integrating this with 2 icons to the zoom icons on the bottom right would be maybe more intuitive

OnoSendai wrote:* Added copy selection to clipboard

Hmmm.... how to do this... after doing a selection only "Copy image to Clipboard" is available from the edit drop-down.

Why not only copying to the clipboard and let the paint program handle the crop?

Will there be a Mac build to play with?

pixie wrote:Why not only copying to the clipboard and let the paint program handle the crop?

maybe for quicker workflow in posting detail images in the Forum ^^

The interesting part about this region Selection is a now needed interactive region rendering ;-)