Indigo Renderer 2.4.2 Released
Posted: Tue Apr 13, 2010 7:08 pm
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.
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.