Indigo 1.0.6

[OnoSendai]

Hi Suv,
one pass is easier to code, and it doesn't take any extra memory.
And as Psor points out, it does converge pretty fast.

[Pibuz]

Thank you so much!
You're SO fast: i'll keep it in mind when asking for anything else

Thank you again ONO!!!

[suvakas]

Hi Suv,
one pass is easier to code, and it doesn't take any extra memory.
And as Psor points out, it does converge pretty fast.

Hey,
Gotcha !
Ok. Sounds good then.
Can't test right now, but i'll try it as soon as i get home.

Ps. Doing alpha + final at the same time would be a bit more user friendly, since this is what most of the renderers do. For example user could turn on "Render alpha checkbox" and he gets an alpha output with the final image. If i would be new to Indigo, then this is the behavior I'd expect from a renderer. But that's just a minor issue I guess.

Maybe you can somehow auto-launch an alpha rendering right after the main thing gets closed? (just an idea)

[Kram1032]

nice

[alexmeyer]

Just to make things clear: it's not like I *need* render_region, (it might seem that way based on how much I've been testing it... ) I just think it's a neat feature.

BUT... it's still broken. It now renders the entire region (thanks ono), but it still freaks out when the numbers get too high. I'm trying it on a 1600x1200 image I have, and it gives the error below. My render_region settings (in the inifile) are:

Code: Select all

"enable_render_region" "true"
"render_region_x1" "785"
"render_region_y1" "830"
"render_region_x2" "920"
"render_region_y2" "980"

I'm assuming this has something to do with what you said the original problem was, that it's using the default 600x450 image size...

[Kram1032]

hum... a wrong check? This assumes, that your biggest possible render region would be half the actual render size...

What about using this check:

Code: Select all

IF x1 <0 OR y1 < 0 OR x2 < x1 OR y2 < x1 OR x2 < ImageWidth OR y2 < ImageHeight
THEN "_put in useful Error message, here"

Maybe, you could also simply throw out a warning, if one of the values goes over the border, that it's replaced by the last possible extreme. If _2 is smaller than _1, you still could give an error

[OnoSendai]

dammit, thanks for the tip AlexM

[kadajawi]

I love render region. It's great for determining if the texture will turn out ok or if the exposure is ok, or to see if the DoF is ok etc. (simply things you would notice when the rendering cooked for many hours). Very useful, saves a lot of time when testing. Wouldn't want to miss it

It would be neat though if you could resume with render regions. I mean you start an image, and then resume with just a region. So you can give all the CPU power to a noisy region when everything else is clean already. Maybe it's hard to implement though.

[alexmeyer]

@kadajawi: You can.

It'll resume it, BUT it'll only resume the render_region (the rest is still blank). So you still have to composite it over your first render. But yes, you can do that.

Hope that's understandable...

[kadajawi]

Oh, ok, didn't notice that, probably because the region renders too fast.

[alexmeyer]

Exactly

[dougal2]

I know this has been mentioned, but the BiDir off thing seems to be only with Physical sky. Using just a meshlight, it worked fine with BiDir on.

[jeffr]

The alpha output is a big thing. Just what I was wanting. Thanks

[dougal2]

this is odd. never seen indigo render like this before.
What's with the black lines above and below the specular highlights ?

[Kram1032]

It's due to the new MN-sampling...
Ono didn't clamp the values or something (according to lyc)
I think, a higher super sampling factor will remove them...
Or you can simply switch back to Gaussian sampling