General News and accouncements regarding the Indigo render engine
-
OnoSendai
- Posts: 6241
- Joined: Sat May 20, 2006 6:16 pm
- Location: Wellington, NZ
-
Contact:
Post
by OnoSendai » Fri Aug 31, 2018 9:00 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 64-bit:
IndigoRenderer_x64_4.2.19_Setup.exe
Indigo for Linux 64-bit:
IndigoRenderer_x64_v4.2.19.tar.gz
Indigo for Mac OS X (10.9 - ):
IndigoRenderer4.2.19.dmg
Indigo RT for Windows 64-bit:
IndigoRT_x64_4.2.19_Setup.exe
Indigo RT for Linux 64-bit:
IndigoRT_x64_v4.2.19.tar.gz
Indigo RT for Mac OS X (10.9 - ):
IndigoRT4.2.19.dmg
Changelog:
4.2.19
* Improved high quality BVH build for GPU a little.
* Fixed missing specular reflections from double-sided thin material on GPU in some cases.
* Remember the last selected render channel, so if we restart rendering, we can still show the selected render channel.
* Improved handling of layer and channels names during EXR loading.
* Added 'Save Un-tonemapped Image', 'Save IGI for resuming' and 'Save Layers And Channels' to Render menu
* Added save_render_channels_exr render setting
* Added -channels command line option for saving render channels
* Made the environment be white for the depth render channel.
* Fixed issue with info overlay not being drawn on saved images in some cases.
* Fixed bug causing tiling-based ghosting issues when rendering with multiple GPUs.
* Fixed crash when changing material or object mask names when render is not running.
* Added 'show CPU devices' option to options dialog. When unchecked (which is the default), CPU OpenCL devices are not displayed in the device selection widget.
* Increased max fstop in UI to 1000000.
Fixes bug where changing any camera setting in a scene with fstop > 128 resulted in the effective fstop being set to 128.
* Fixed 'crash' on GPU when rendering render channels in some cases.
* Fixed render regions not working for saving render channels.
* Fixed crash saving images during subsampling at start of render.
* Added support for 32-bit TGAs.
* Fixed not being able to select render channels for display when AD is enabled.
* Fixed alpha being incorrectly displayed when AD is enabled.
* Improved weighting of render channels in some cases
* Changed clamping of saved render channels so non-beauty render channels aren't clamped to >= 0.
* Added support for saving render channels in a single, combined EXR file.
* Added 'Combine into single file' option for saving render channels in options dialog.
* OpenCL: Added support for backface emission.
* Can now change aperture size (fstop) on spherical camera.
* Fixed updates to aperture diffraction not being reflected on camera changes.
* GPU: Added support for more complicated kinds of emission, for instance emission shaders, blend materials with emitting children etc..
* Added --cpuonly flag to Benchmark.
* Fixed faces emitting from backside if a mirror transform is applied to them in some cases.
* Fixed arch glass to be more similar to specular materials when rendering render channels.
-
Attachments
-
-
-
pixie
- Posts: 2332
- Joined: Sat Dec 29, 2007 4:54 am
- Location: Away from paradise
- 3D Software: Cinema 4D
-
Contact:
Post
by pixie » Sat Sep 01, 2018 1:28 am
swell!
-
zeitmeister
- Posts: 2010
- Joined: Tue Apr 22, 2008 4:11 am
- Location: Limburg/Lahn, Germany
-
Contact:
Post
by zeitmeister » Sat Sep 01, 2018 8:04 pm
Fantastic!!!!!
-
Lal-O
- Posts: 346
- Joined: Wed Sep 23, 2015 7:09 am
- Location: México
- 3D Software: SketchUp
-
Contact:
Post
by Lal-O » Sun Sep 02, 2018 11:10 am
Cool !!!
Trying right now. I have an extensive project that I am working on so ... it seems that I will be able to thoroughly test this new version.
Thank you!!!
-
Lal-O
- Posts: 346
- Joined: Wed Sep 23, 2015 7:09 am
- Location: México
- 3D Software: SketchUp
-
Contact:
Post
by Lal-O » Sun Sep 02, 2018 12:43 pm
After my first test with this new version i must say that .....OpenCL is not working for me ( just like the 4.2.18 version, that is why i still keep the old 4.2.14 version ). There is no progress in the rendering screen even when the progress bar keeps running.
I also have found that any change freezes indigo and if i try to close indigo it gives me a crash.
I don't have any problem with the 4.2.14 ( it only gives washed out colours sometimes , no major peoblem : ) ) .
I attach a cuple images comparing both versions ( 4.2.19 and 4.2.14).
PD. This new release is " problematic " ( in my case ) only by using OpenCL.( By the way...Why did you guys eliminate the option to choose the CPU in the OpenCL section? I will lose that little "extra" power that the CPU gives when using OpenCL-CPU AND GPU at same time...Right? :P ).
Cheers!
-
Attachments
-
-
-
Zom-B
- Posts: 4700
- Joined: Tue Jul 04, 2006 4:18 pm
- Location: ´'`\_(ò_Ó)_/´'`
-
Contact:
Post
by Zom-B » Tue Sep 04, 2018 1:31 am
There is a good chance that all your issues are related to using your CPU as an OpenCL device.
Please deactivate it and double check if you still have these problems.
The Devs disabled CPU OCL by default, because it is a source of problems with lack of driver support and instability and bad scalability on many systems. People start posting in the Forum with issues that they don't connect to this feature...
-
OnoSendai
- Posts: 6241
- Joined: Sat May 20, 2006 6:16 pm
- Location: Wellington, NZ
-
Contact:
Post
by OnoSendai » Wed Sep 05, 2018 1:02 am
Hi Lal-O,
First thing, to make sure your CPU device is disabled, please try unticking and then ticking the tickbox for your Nvidia GPU.
This will make sure the CPU device is not enabled (otherwise it might still be enabled, but just not listed as a device).
Then please confirm just the Nvidia device is being used, by looking in the render log (in the renderer settings widget)
It should say something like
'OpenCL code for main program on GeForce GTX Titan X built' and hopefully nothing about your Core i7.
-
pavoda
- Posts: 188
- Joined: Tue Dec 20, 2016 10:05 am
Post
by pavoda » Wed Sep 05, 2018 3:09 am
Hi, i have same problem.
Start indigo rendering in some scene, but screen is still black...time runing but sampless not. If I disable OpenCL - render run OK and image go to progres. If I enable OpenCL back, the error dialog is appeare....Version 4.2.14 was more stable in this case.
-
Attachments
-
-
-
-
Zom-B
- Posts: 4700
- Joined: Tue Jul 04, 2006 4:18 pm
- Location: ´'`\_(ò_Ó)_/´'`
-
Contact:
Post
by Zom-B » Wed Sep 05, 2018 6:04 am
Hey Pavoda, disable the unneeded OGL preview, it eats up your GPU RAM, then try again.
For the Scene that renders for 2min without any output the render log would be very interesting...
Last edited by
Zom-B on Wed Sep 05, 2018 10:54 am, edited 1 time in total.
-
pixie
- Posts: 2332
- Joined: Sat Dec 29, 2007 4:54 am
- Location: Away from paradise
- 3D Software: Cinema 4D
-
Contact:
Post
by pixie » Wed Sep 05, 2018 6:08 am
It would be nice that when opencl is used one could stop a scene and have the memory released, and then continue where one left.
-
pavoda
- Posts: 188
- Joined: Tue Dec 20, 2016 10:05 am
Post
by pavoda » Thu Sep 06, 2018 11:12 am
Zom-B wrote: ↑Wed Sep 05, 2018 6:04 am
Hey Pavoda, disable the unneeded OGL preview, it eats up your GPU RAM, then try again.
For the Scene that renders for 2min without any output the render log would be very interesting...
-
Attachments
-
-
pavoda
- Posts: 188
- Joined: Tue Dec 20, 2016 10:05 am
Post
by pavoda » Thu Sep 06, 2018 11:20 am
this is also interesting...same scene, another versions
-
Attachments
-
-
-
Zom-B
- Posts: 4700
- Joined: Tue Jul 04, 2006 4:18 pm
- Location: ´'`\_(ò_Ó)_/´'`
-
Contact:
Post
by Zom-B » Thu Sep 06, 2018 9:24 pm
Hey Pavoda, how much system RAM do you have?
Can you monitor the RAM usage during Indigo start and check if it hits the limit?
The BVH building for the GPU is done on System Memory and can sometimes peak quite high values,
settling way lower when the build is done.
Who is online
Users browsing this forum: Ahrefs [Bot], Majestic-12 [Bot] and 26 guests