Indigo 1.0.5

[OnoSendai]

There's a rather severe bug with the render region being in the wrong place in some cases, which I've fixed for the next release.

[alexmeyer]

[OnoSendai]

Yup, thanks to Alex M for pointing it out

[Kram1032]

[OnoSendai]

That's exactly how it works! Now you got it!

Of course you could ask right now, why he did not do it like this ...

Code: Select all

<splat_filter>mn_cubic</splat_filter>

Code: Select all

<downsize_filter>mn_cubic</downsize_filter>

... but then he probably would say:

So take it like ...




take care
psor

The reason is simple: if I want to extend the filter types to take extra parameters, then it's good if they're XML elements and not strings.

[psor]

Thanx for explanation Nik!

btw. you broke the v1.0.5 ... look into the sun! "Overflow" bug ...
happens with aperture_diffraction enabled!
And something is wrong with the way the obstacle map is working.
I'll prepare a bug report later ... first I need some hours sleep. ;o))



take care
psor

[d_emis]

i've been trying to use indigo to render one of my projects from sketchup and the whole thing is taking so much time to render and the wuality is still a bit blury....is there something i am missing here? some kind of setting i am not using?

[Kram1032]

You're missing the unbiasedness of Indigo Unbased renderers will always take long to render images. The higher the resolution, the slower. The bigger the scene (dimension-wise) the slower. The more polygons (at least, if you don't have enough RAM), the slower. The more complicated materials (in this scene especially the quite pure white walls, etc...) the slower

And maybe, the blurriness comes from the filter...