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 64-bit:
IndigoRenderer_x64_4.0.64_Setup.exe

Indigo for Linux 64-bit:
IndigoRenderer_x64_v4.0.64.tar.gz

Indigo for Mac OS X (10.9 - ):
IndigoRenderer4.0.64.dmg


Indigo RT for Windows 64-bit:
IndigoRT_x64_4.0.64_Setup.exe

Indigo RT for Linux 64-bit:
IndigoRT_x64_v4.0.64.tar.gz

Indigo RT for Mac OS X (10.9 - ):
IndigoRT4.0.64.dmg

Changelog:

4.0.64
* Fixed issue with glossy transparent and specular materials sharing the same medium.
* Added better progress indication for OpenCL program building.
* Updated bundled 3ds Max plugin to 0.7.1.
* Updated bundled Blender plugin to 4.0.8.
* Updated bundled C4D plugin to 4.0.64.
* Updated bundled SketchUp plugin to 4.0.61.2.
* Added new example scenes from competition.

4.0.63
* SDK: Added setThreadPriority to Renderer.
* SDK: Allow halt request to be sent again after update.

4.0.62
* Fixed a few crashes in SDK.

Has pos(OS) been fixed?

zeitmeister wrote:Has pos(OS) been fixed?

no.

OnoSendai wrote:

zeitmeister wrote:Has pos(OS) been fixed?

no.

Rofc (RollingOnTheFloorCrying)

Hi Juju, The devs are having some time off at the moment. That, to me, seems like a feature that might not benefit that many in the Indigo user base. Maybe it can be included with all those other render passes that have been requested though?

Hi guys.
I have been testing a bit this new update and i've found a few issues with it:

1)Weird/different effects with alpha/transparency maps in tree models while usin OpenCL mode, it seems like duplicated or darker textures.(I can share the scenes if you like to). All fine with CPU. :)

2)Screen gets dark everytime i face straight to the sun ( this did not happen in past versions ),but if i orbit the model then the "problem" gets solved.

3) Sometimes the screen "freezes" while orbit the scenes ( even with low or very light scenes/models.
https://www.indigorenderer.com/forum/do ... &mode=view ).

4) (This is not really a problem) How to get access to the competition scenes ? :P

I am using the latest version of everything (Indigo, SkIndigo and drivers).

My best regards.

Cool, thanks for summing up what you found.

1) Looks like that might be due to your GPU path depth setting (8). Each time a ray of light passes through a transparent material, that counts as a "bounce". CPU rendering uses many thousand by default, you might wanna try increasing the GPU path depth to something like 32 or 50 and see if that helps.

2) That might be due to Reinhard tonemapping - the sun is so bright that Reinhard automatically exposes your image way down. This shouldn't happen with Camera, Linear or Filmic.

3) I've also noticed this in rare occasions. Should probably help to disable and reenable GPU rendering, but this is most likely a bug.

4) You should be able to find this in "Example scenes" in your Indigo application path somewhere. :)

4) On windows the scenes are in the indigo install dir, under testscenes. Most likely: C:\Program Files\Indigo Renderer\testscenes

Oscar J wrote: ↑

Fri Dec 29, 2017 8:48 am

2) That might be due to Reinhard tonemapping - the sun is so bright that Reinhard automatically exposes your image way down. This shouldn't happen with Camera, Linear or Filmic.

Thx for the reply Oscar J

1)Problem solved by increasing the path deph :)

2) I've tested the file again and it worked like charm ( whitout changing anything ).
I've made a few test with other settings (all tonemappings,CPU,OpenCl and so on) but nothing changed,all works as it should...Fine. Couldn't replicate the problem.
At very first time i thought that get darker image was an indigo camera response (like any real camera would do it ),but it wasn't.

3) Yeah , it does not always happen.



Thx for the help :)

I've also noticed that indigo wont display the right amout of cores coming from the GPU...My GPU has 3072 cuda cores and indigo only displays 24...( It could be that i'm confusing things :P ).

fused wrote: ↑

Fri Dec 29, 2017 10:20 am

4) On windows the scenes are in the indigo install dir, under testscenes. Most likely: C:\Program Files\Indigo Renderer\testscenes

I've found them! It is really nice to see that my "ROOM" scene is part of this new release. Thank you !

Yeah I got real creative naming some of the scenes that didn't have a name

Feel free to suggest a better one, and I'll get it into the next release

Lal-O wrote: ↑

Fri Dec 29, 2017 2:25 pm

I've also noticed that indigo wont display the right amout of cores coming from the GPU...My GPU has 3072 cuda cores and indigo only displays 24...( It could be that i'm confusing things :P ).

https://us.hardware.info/reviews/5974/2 ... y-and-more

"These cores are then divided across 24 so-called Streaming Multiprocessors, which are blocks of 128 cores that are all performing the same task at any given point in time."

I think that might be what Indigo is displaying. :)

Oscar J wrote: ↑

Fri Dec 29, 2017 12:31 am

Hi Juju, The devs are having some time off at the moment. That, to me, seems like a feature that might not benefit that many in the Indigo user base. Maybe it can be included with all those other render passes that have been requested though?

I hope they have a good rest and come back refreshed. Thanks for the good work team!

Oscar, being able to do accurate light simulations with the accurate corresponding illumination reports (yes, it's a little more than just another render pass) could make the software usable / available for use to a whole new user base, not mentioning adding another arrow in the bow of the current user base, especially so if they're into architectural rendering.

If you've had a look at what the renderings look like from the industry standard illumination simulation applications* (let's just say it's not even in the same neighborhood as Indigo) you'll realize the opportunity here. One will save on the additional effort to setup lighting in two different software programs, making sure they're setup similarly / correctly and comparing rendering outputs. Not to mention that the illumination simulation applications* seem to still be CPU-bound only.

* = not to be confused with everyday rendering software