Indigo Renderer Forum

Working towards the final 0.6 release.. here's test 3
Please post about any bugs found.
This should be a fully functioning release, as opposed to 0.6 test2.

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

Changelog:

* don't alloc and free buffer on tonemapping
* fixed broken stuff from 0.6 test2
* path tracing mode resurrected and is now progressive - can be run forever.
* sky_gain disabled for now
* other stuff probably
* fixed halt_time not working

nice to hear from you Nick and thanks a lot for new release !

One small question, do you have a formula or link about relation of blackbody-temp and energie?

regards zuegs

thanks for a new release with fixed stuff !

please check if program creates tree_cache directory , I've just tried with first xml I've found and seen lot of messages like "Failed to open file 'tree_cache/1510505112.tre' for writing." , when I created directory manualy and restarted , it created caches in it .... (I am working on local disk with admin rights so I guess that it should work)

Thanks eagle, I've uploaded a new version with an empty tree_cache dir.

I've got much more white noise with v6t3 than v6t2 or v5 will try other scenes and settings...

Super Awsome!
I'm Going To Render My Scenes SO HARD!

zuegs wrote:I've got much more white noise with v6t3 than v6t2 or v5 will try other scenes and settings...

Hmm.. what kind of mats?
Might have busted the importance sampling

I get quite abit of white noise too...
On all kinds of materials

EDIT: There is most white noise when I use BlackBody Mesh Light, it seems...
EDIT2: I get it with RGB Mesh Light too...
Haven't tried Sunlight or Rectangle Light

I'm using much phong and some diffuse... when i compare v6t2 and v6t3 i see quite more contrast in v6t3 (gamma?) and a lot of white dots on my gray diffuse wall... (btw exr output still clamped at <=1.0)
I go to try some simpler scene first befor...

Can u post an example comparison, with the 0.6 test 1 render as well?

zuegs wrote:(btw exr output still clamped at <=1.0)

tonemapped or untonemapped exr?

Oh yeah.. there is some burn-out now in the Reinhard tone mapping, which gives more contrast.
This will be a configurable parameter next release.

we have a shutdown function ? ... thank you - top work!
it is also much faster isn't it? at the moment i can test it only on the computer of a friend of mine.

Ono-Sendai wrote:

zuegs wrote:(btw exr output still clamped at <=1.0)

tonemapped or untonemapped exr?

tonemapped exr with linear or reinhard seams to clamp, untonemapped exr still very small 14kB (when tonemapped is 2000kB)

zuegs wrote:

Ono-Sendai wrote:

zuegs wrote:(btw exr output still clamped at <=1.0)

tonemapped or untonemapped exr?

tonemapped exr with linear or reinhard seams to clamp, untonemapped exr still very small 14kB (when tonemapped is 2000kB)

Well, tonemapping clamps as part of the process, so that's desired behaviour.