brute force and light cache

[oren]

hello all. i need little help
i have huge scene with lots of trees and cars and buildings... lots if camera for animation... the cars also move...
i want to go with brute force as primary and light cache.
i dud some test with bake light cache with "fly thru mode" but what i get is soft look of the trees.. look like thay lost gi and bounce alot...

my light cache setting is World mode samples 0.01... with filtering of 30.
i cant find any good tutorial about animation with brute force and light chace... style how to set it easy and RIGHT...
any help will be good.

[^Lele^]

Start from the defaults.
Then *just* set LC subdivs to 3000, and retrace threshold to 8.
Render away without a second thought.

p.s.: notice that is what the tooltips say. says the tooltips writer. ^^

[Pixelab]

says the tooltips writer. ^^

So, you are the little voice always giving me advices ? I have to thank you

[oren]

no need to bake the light cache ?? to avoid flickers?

all i need to worry is to the noise if the brute force?

[^Lele^]

no need to bake the light cache ?? to avoid flickers?

all i need to worry is to the noise if the brute force?

Correct.
From defaults, likely all you need to touch is the noise threshold to choose a speed/quality factor which suits you. Flickers in the LC solution would be apparent regardless of noise threshold/sampling quality (within reason.).

[^Lele^]

So, you are the little voice always giving me advices ? I have to thank you

Ahahah, you made my day: someone actually reads them!
I edited a few, for Max, as a very first job (GI/sampling, Color Mapping, chiefly.).

[oren]

Ahahah, you made my day: someone actually reads them!
I edited a few, for Max, as a very first job (GI/sampling, Color Mapping, chiefly.).

hey lele do you have facebook man?? its sound useful haha

[^Lele^]

hey lele do you have facebook man?? its sound useful haha

Ahah, i do, but i'd disappoint you there, i HATE it when work gets into the private, and i now have a very big target painted on my head, so i tend to add and ignore, or not add at all.
Forums is where it's at for this stuff.

[oren]

lele can you tell me why there is the option like fly thruhe and use "camera path" if is all can work smooth with just rise up the light cache subdive and the raytrace ?

[vlado]

lele can you tell me why there is the option like fly thruhe and use "camera path" if is all can work smooth with just rise up the light cache subdive and the raytrace ?

We didn't have the "retrace" and "leak prevention" options in older versions, so the fly-through and "use camera path" options were the only available solutions to avoid flickering in animations.

Best regards,
Vlado

[oren]

We didn't have the "retrace" and "leak prevention" options in older versions, so the fly-through and "use camera path" options were the only available solutions to avoid flickering in animations.

Best regards,
Vlado

so in vray 3.4 in case of using brute force i can ignore of fly through and any bake of light cache and go for 8 retrace and hit render? that all? and if i see any flickering its the time to check if the material is ok? or any other errors?

[vlado]

so in vray 3.4 in case of using brute force i can ignore of fly through and any bake of light cache and go for 8 retrace and hit render? that all? and if i see any flickering its the time to check if the material is ok? or any other errors?

More or less. I would also increase the light cache subdivs slightly to 2000 or 3000. There is some additional information here:
https://docs.chaosgroup.com/display/...nginanimations

Most of the settings are default now, except the subdivs and the retrace. Let me know if something is unclear.

Best regards,
Vlado