Indigo Renderer Forum

hey all, new release time.
I wanted to get the Multithreaded stuff out the door... because... well, it's just so cool (IMHO )

http://www.indigorenderer.com/montecarl ... _test1.zip

This is a stand-alone release, it includes all necessary files.
As usual, I may have broken some stuff, so keep an eye out

So Indigo is now fully multithreaded.. you can run an arbitrary number of threads per process.

Scene file changes:
Just one minor one, but it will break most scenes:
The background element now should only have 1 child, a spectrum element.
So e.g. should be changed to Also you can now have only one of background, skylight, or env_map.
If you want a black background, don't include a background element.

changelog:

* speedup with phong pow()s
* added bump mapping for specular mat
* Added multithreading
* Added -t switch to specify number of threads.
* nice error message on out of mem while building kdtree
* using doubles for pdf and radiance stuff
* added colour correction
* background element now takes a single spectrum child element
* can now have only one of background, skylight, or env_map
* made window size equal to render size
* changed default sky gain to 0.002
* changed bidir RR live prob
* decreased num warmup mutations by half

Ono-Sendai wrote:hey all, new release time.
I wanted to get the Multithreaded stuff out the door... because... well, it's just so cool (IMHO )

This is so cool!!!!!!!
Thanks a lot for your hard work dude!

*now testing

great work!

thanx ono!
it was so silent the two last weeks!

Thanx a lot for this fine update! ;o))


take care
psor

I did some quick & dirty benchmarks to test multithreting in 0.6 test 1:

I own a AMD X2 3.800+

1 Core 100%

2 Cores - 1 thread ~116%
2 Cores - 2 thread ~210%
2 Cores - 3 thread ~215%

Indigo seems to use my second Core also even if only 1 thread is defined.
Always when the log File gets Updated the second Core uses 10 to 15%.

I also recogniced, that using 3 threads raises Indigos Performance on my machine even more

Can somebody confirm my conclusions?

Well, when you set it to one thread, that means one thread that runs the MLT process, and another thread that does the tonemapping, gamma correction and display of the image buffer, which does take significant computation.
So it's really two threads.

Yeah.. i hacked a ~1.1 multiplier on the green component so that white actually maps to white under the sRGB etc.. transform.

ono, can i ask something? can you send these kind of announcements
also by e-mail to the forum members? thus, we'll know immediately
when a new version is posted...

yponomos wrote:ono, can i ask something? can you send these kind of announcements
also by e-mail to the forum members? thus, we'll know immediately
when a new version is posted...

Heh.. I think that would annoy too many people... especially if i get up to v0.6test7

thank Nick,
Very great work

Excellent as always..

I'm on the exporter.

Will colorcorrection work like before in the xml .. ?

Did the blend stuff go in there as well ?
So maybe i could do a blend mat for M2I..?

cheers

u3dreal

Hey, great!

Thx for the new version Nick!

And except for multithreading and all the other new feartures also for:

* made window size equal to render size

But:
Is it really correct, that the <rgb>, </rgb> stuff in <background> have to be defined twice?

<background>
<spectrum>
<rgb>
<rgb>1 1 1</rgb>
</rgb>
</spectrum>
</background>

Kind regards,
Tom

Dosen't work with Wine under Linux? Black screen all the time and there is no change in the .png file while rendering:(

greetz,
jurasek

Not able to get <env_map> to work with this release.

I've tried:

• exr's for both spherical & latlong (converted with hdr2env)
• & same for .float/.raw (converted from hdr with hdrshop)
• using the common kitchen_probe.hdr as well as others (for latlongs)...

consistently gives me this error dialog:


I hope its just something I'm doing wrong...