# Brute Force Optimization questions... GI is so noisey but RGB looks fine?

**URL:** <https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795>\
**Category:** Render Theory\
**Created:** [August 4, 2015, 1:20am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795 "2015-08-04T01:20:38Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![emartin8907](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@emartin8907](https://forums.chaos.com/u/emartin8907)\
**Post date:** [August 4, 2015, 1:20am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/1 "2015-08-04T01:20:38Z")

</div>

Hi,

I am trying to optimize some render settings and have some questions…

Brute Force as Primary and Secondary is considerably faster than IM/ LC, and the RGB looks extremely similar.

When optimizing my settings I look at the Raw GI, Raw Reflection, Raw Refraction, and Lighting.. My Raw GI is _insanely_ noisey with BF/BF, but the RGB doesn’t seem to reveal this 😵‍💫

My question is- should I care? Normally when optimizing settings I would think that’s a problem but my RGB looks as clean as my IM/LC render. I’m just hesitant to use it for some reason! I’m so used to IM/LC and looking at these passes to tell me what to optimize 😛 If my Raw GI looked this noisey using IM/LC my RGB would look like total crap but for some reason I can get away with it in BF/BF?

Can someone shed some light on this for me?

Thanks,

Eric

---

<div class="post-metadata">

**Author:** ![vlado](https://avatars.discourse-cdn.com/v4/letter/v/779978/32.png) [@vlado](https://forums.chaos.com/u/vlado)\
**Post date:** [August 4, 2015, 1:42am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/2 "2015-08-04T01:42:17Z")

</div>

You should be looking at the “GI” element, not the “Raw GI” one. It’s normal that the raw GI is noisy - V-Ray optimizes its sampling based on the RGB output, and as long as this is fine, V-Ray doesn’t care how the individual raw render elements come out.

Best regards,  
Vlado

---

<div class="post-metadata">

**Author:** ![emartin8907](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@emartin8907](https://forums.chaos.com/u/emartin8907)\
**Post date:** [August 4, 2015, 2:51am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/3 "2015-08-04T02:51:03Z")

</div>

Thanks for the quick reply Valdo!

Ah silly me, I just did another render with normal GI and its considerably smoother than the raw gi.

Another question related to BF- why is it so much darker than IM/LC? I’ve tried upping the BF subdivs and depth to 128 & 32 and couldn’t get it back to how bright it was with IM/LC

---

<div class="post-metadata">

**Author:** ![super\_gnu](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@super\_gnu](https://forums.chaos.com/u/super_gnu)\
**Post date:** [August 4, 2015, 7:45am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/4 "2015-08-04T07:45:22Z")

</div>

id advise using BF and LC. this is the ideal choice these days. BF/BF is too slow for very little (no?) improvement in final image quality.

the reason BF/BF is darker than im/lc (or BF/LC) is that BF by default does 3 secondary bounces. even turning it up to 32 doesnt come close to LC which does 100 bounces by default.

you could turn BF secondaries up to 100 bounces and wait for a month, or just use LC like everyone else.

the reason “normal” gi ( do you mean IM /LC ?) looks smoother is its interpolated. if you are referring to BF/LC they its probably less noisy since the BF primaries are being calculated from a lightcache, which is interpolated and smooth, giving the BF engine less work to do to arrive at a clean image.

edit:

-ok i just understood you were referring to the “normal” gi pass, not another gi calculation method.

---

<div class="post-metadata">

**Author:** ![emartin8907](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@emartin8907](https://forums.chaos.com/u/emartin8907)\
**Post date:** [August 4, 2015, 3:19pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/5 "2015-08-04T15:19:08Z")

</div>

I normally stick with IM/LC myself but after some time optimizing this scene (exterior of a car lit only with dome light) I found BF/BF or even BF/LC is significantly faster and no noisier than IM/LC.

BF/BF was twice as fast, and BF/LC was about 30% faster still than IM/LC.

I tried upping BF GI Subdivs to 128 and it was still darker than IM/LC (still twice as fast though). Where are you saying to turn up BF secondaries? When I switch Secondaries to BF I lose any settings for secondaries except for the multiplier.

PS using 3.1

---

<div class="post-metadata">

**Author:** ![super\_gnu](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@super\_gnu](https://forums.chaos.com/u/super_gnu)\
**Post date:** [August 4, 2015, 4:23pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/6 "2015-08-04T16:23:11Z")

</div>

hm.. unless 3.1 is different than on max (im a max guy) you should have a “bounces” control in your bf secondaries. its default at 3 bounces. subdivs will make almost no difference to brightness.. its the bounces that are the issue. are you sure you are looking at the “expert” interface?

ive literally never heard of a case where BF/BF is faster than BF/LC, or IM/LC. there are geological processes that are faster than BF/BF whenever ive tried it. to be fair though ive not tried it since vray 3, since BF/LC works so well.

edit: ive just noticed your scene is an exterior car shot with a domelight, so Gi is extremely easy to calculate in this case… my experience is generally with architectural interiors.. youd never go near BF/BF with a bargepole.

---

<div class="post-metadata">

**Author:** ![emartin8907](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@emartin8907](https://forums.chaos.com/u/emartin8907)\
**Post date:** [August 4, 2015, 5:08pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/7 "2015-08-04T17:08:49Z")

</div>

In Maya there isn’t an ‘expert mode’ to reveal more control, that I know of at least? I know what you are talking about as I used Vray 3 in Max before too, I haven’t seen that option in Maya and didn’t think it existed in Maya. But I don’t see anywhere to control secondary bounces for BF so maybe I’m missing something?

---

<div class="post-metadata">

**Author:** ![vlado](https://avatars.discourse-cdn.com/v4/letter/v/779978/32.png) [@vlado](https://forums.chaos.com/u/vlado)\
**Post date:** [August 4, 2015, 5:24pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/8 "2015-08-04T17:24:28Z")

</div>

> [@TSR\_trix](#):
>
> But I don’t see anywhere to control secondary bounces for BF so maybe I’m missing something?

Take a look here:

> **[Chaos Docs](https://documentation.chaos.com/)**

There is a “depth” option which represents the number of bounces when using brute force as a secondary GI engine.

Best regards,  
Vlado

---

<div class="post-metadata">

**Author:** ![emartin8907](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@emartin8907](https://forums.chaos.com/u/emartin8907)\
**Post date:** [August 4, 2015, 5:35pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/9 "2015-08-04T17:35:02Z")

</div>

Hmmm BF/LC even with BF depth at 64 looks no different than BF/LC with depth at default of 3. Is there a way to get that same brightness/ intensity as IM/LC with BF/LC or BF/BF?

---

<div class="post-metadata">

**Author:** ![vlado](https://avatars.discourse-cdn.com/v4/letter/v/779978/32.png) [@vlado](https://forums.chaos.com/u/vlado)\
**Post date:** [August 4, 2015, 5:37pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/10 "2015-08-04T17:37:29Z")

</div>

> [@material setting 'use irradiance map' causes big differences in render results](https://forums.chaos.com/t/material-setting-use-irradiance-map-causes-big-differences-in-render-results/48066/5):
>
> Hmmm BF/LC even with BF depth at 64 looks no different than BF/LC with depth at default of 3. Is there a way to get that same brightness/ intensity as IM/LC with BF/LC or BF/BF?

It should have worked right away. Best to post a scene so that we can figure out what’s wrong.

Best regards,  
Vlado

---

<div class="post-metadata">

**Author:** ![emartin8907](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@emartin8907](https://forums.chaos.com/u/emartin8907)\
**Post date:** [August 4, 2015, 7:18pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/11 "2015-08-04T19:18:14Z")

</div>

> [@Clouds R&D](https://forums.chaos.com/t/clouds-r-d/46362/39):
>
> It should have worked right away. Best to post a scene so that we can figure out what’s wrong.
> 
> Best regards,  
> Vlado

Can’t share this scene I will try and make a test one today though- so BF depth of 64 should affect brightness compared to a depth of 3?

---

<div class="post-metadata">

**Author:** ![vlado](https://avatars.discourse-cdn.com/v4/letter/v/779978/32.png) [@vlado](https://forums.chaos.com/u/vlado)\
**Post date:** [August 4, 2015, 8:08pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/12 "2015-08-04T20:08:48Z")

</div>

> [@File Name Prefix Layer Override not allowed?](https://forums.chaos.com/t/file-name-prefix-layer-override-not-allowed/25862/7):
>
> Can’t share this scene I will try and make a test one today though- so BF depth of 64 should affect brightness compared to a depth of 3?

Only if you are using BF as a secondary engine. If you are using the light cache then no. But in any case BF+LC should be the same brightness as IM+LC

Best regards,  
Vlado

---

<div class="post-metadata">

**Author:** ![emartin8907](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@emartin8907](https://forums.chaos.com/u/emartin8907)\
**Post date:** [August 5, 2015, 4:24pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/13 "2015-08-05T16:24:01Z")

</div>

So I went to make a test scene and couldn’t recreate this. I went back to my problem scene, loaded the default render preset to reset everything, and now I’m not having this problem. Perhaps I was just tired…

Thanks!

---

<div class="post-metadata">

**Author:** ![beenyweenies](https://avatars.discourse-cdn.com/v4/letter/b/ac8455/32.png) [@beenyweenies](https://forums.chaos.com/u/beenyweenies)\
**Post date:** [August 14, 2015, 8:45pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/14 "2015-08-14T20:45:26Z")

</div>

Just wanted to add my own personal experience to this thread. BF/BF can actually be quite competitive in terms of speed, while producing much more reliable and consistent results (especially for animation work). But it all depends on your subject matter, format, and definition of “fast.” I’m mostly involved in HD product work, with the products typically placed in interior settings, and my target render time per frame is around 25 minutes.

For me, BF/BF speed is totally acceptable when setting Subdivs Mult to 0.000 (letting Vray control subdivs), cranking the Min Shading Rate (higher values gradually improve shading/texture/noise quality vs. antialiasing quality) to something like 20-30, and then gradually working the Adaptive Threshold from .020 down until the time/quality balance is acceptable, usually around .015. I’m also doing a slight amount of grain management in post.

---

<div class="post-metadata">

**Author:** ![emartin8907](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@emartin8907](https://forums.chaos.com/u/emartin8907)\
**Post date:** [August 14, 2015, 11:07pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/15 "2015-08-14T23:07:56Z")

</div>

Wow thanks for sharing beenyweenies!

I’ve been having faster renders/ lower noise with lowering my thresholds to .005 and keeping min shading rate at 1, as opposed to cranking min shading and keeping threshold above .01. I need to do more experiments though that’s interesting you’re going as high as 20-30 for your min shading rate and your thresholds that high.

FWIW im focusing on car exteriors right now just lit with dome.

Appears min shading rate has better success with interiors- [(not quite so) universal settings — PETER GUTHRIE](http://www.peterguthrie.net/blog/2014/3/not-quite-so-universal-settings)

---

<div class="post-metadata">

**Author:** ![beenyweenies](https://avatars.discourse-cdn.com/v4/letter/b/ac8455/32.png) [@beenyweenies](https://forums.chaos.com/u/beenyweenies)\
**Post date:** [August 14, 2015, 11:57pm UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/16 "2015-08-14T23:57:10Z")

</div>

Others can probably explain it better than me, but my understanding is that the Min Shading Rate controls whether samples go to antialiasing (lower values) or shading/noise (higher values). Far fewer samples are needed for antialiasing than shading, and moving this value up shifts the samples accordingly. It basically makes better use of the samples, reducing the need to drop the threshold so low, which is a much costlier way to achieve the same visual result.

This may be completely wrong, hopefully someone can clarify if it is.

---

<div class="post-metadata">

**Author:** ![joconnell](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/joconnell/32/36063_2.png) [@joconnell](https://forums.chaos.com/u/joconnell)\
**Post date:** [August 15, 2015, 11:26am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/17 "2015-08-15T11:26:08Z")

</div>

Yep - minimum shading rate is forcing that number of shading samples to be cast every time an anti aliasing ray is shot. The logic is that the anti aliaser only sees the final 2d image pixels when it’s doing it’s quality testing and it’s looking for differences in colour or brightness to smooth out - these differences or just “contrast” can be anything. It can be areas of detail in a texture, it can be the geometric edges of an object lying against each other, or the important on in the case of speed, it can be noise / grain in your shading. If you’ve got a totally flat plane in your scene (such as a floor or wall in an interior) there’s no geometric detail to worry about since it’s large single polygon areas, but if the light or material hitting that wall is noisy, the anti aliasing sampler sees that as noise and it’ll keep going through cycles of anti aliasing trying to clean it up. Say for example you have vray set so it’s only taking one light, gi and material secondary sample per anti aliasing ray, and it’ll take 50 of those secondary samples to clean up our wall. That means that vray has to shoot an aa ray to get one secondary sample for each, test it and see if it meets your chosen quality level. It won’t, so it shoots another aa ray to get another set of secondary samples, tests them, again fails our quality test and goes again all the way up to the 50 samples it needs. Now we have the option of using min shading rate and if we set it to 10 for example, every time vray shoots an aa ray, it’s forced to take 10 light, material and GI samples. If we do this, it’s only going to take 5 rounds of our sampling loop to get up to our 50 samples needed for a clean result. All of the overheads of the loop of sampling and quality testing take a little bit of time so you can get faster results by trying to kill off the loop of sampling earlier on.

There’s lots of stuff being looked at in this area right now to make it easier, it’ll be an interesting few months 🙂

---

<div class="post-metadata">

**Author:** ![jasonhuang1115](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@jasonhuang1115](https://forums.chaos.com/u/jasonhuang1115)\
**Post date:** [August 16, 2015, 5:39am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/18 "2015-08-16T05:39:56Z")

</div>

> [@3D People](https://forums.chaos.com/t/3d-people/48030/15):
>
> There’s lots of stuff being looked at in this area right now to make it easier, it’ll be an interesting few months 🙂

Thanks again for sharing, John. I have to say I love the above part the most…🙂

---

<div class="post-metadata">

**Author:** ![joconnell](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/joconnell/32/36063_2.png) [@joconnell](https://forums.chaos.com/u/joconnell)\
**Post date:** [August 16, 2015, 11:20am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/19 "2015-08-16T11:20:40Z")

</div>

> [@jstrob](#):
>
> Thanks again for sharing, John. I have to say I love the above part the most…🙂

I don’t think vlado is going to stop improving these things until people don’t have to think about any of the numbers at all 🙂

---

<div class="post-metadata">

**Author:** ![snivlem](https://avatars.discourse-cdn.com/v4/letter/s/e99b99/32.png) [@snivlem](https://forums.chaos.com/u/snivlem)\
**Post date:** [August 24, 2015, 3:31am UTC](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795/20 "2015-08-24T03:31:32Z")

</div>

> [@On another topic](https://forums.chaos.com/t/44143/2):
>
> Just wanted to add my own personal experience to this thread. BF/BF can actually be quite competitive in terms of speed, while producing much more reliable and consistent results (especially for animation work). But it all depends on your subject matter, format, and definition of “fast.” I’m mostly involved in HD product work, with the products typically placed in interior settings, and my target render time per frame is around 25 minutes.
> 
> For me, BF/BF speed is totally acceptable when setting Subdivs Mult to 0.000 (letting Vray control subdivs), cranking the Min Shading Rate (higher values gradually improve shading/texture/noise quality vs. antialiasing quality) to something like 20-30, and then gradually working the Adaptive Threshold from .020 down until the time/quality balance is acceptable, usually around .015. I’m also doing a slight amount of grain management in post.

wow, this is impressive “universal mode” alternative. Rather than letting materials do the subdivs and lights, this way has made a recent scene render so much quicker. Thanks for sharing it.

[Next page](https://forums.chaos.com/t/brute-force-optimization-questions-gi-is-so-noisey-but-rgb-looks-fine/54795.md?page=2)
