Bug Indirect Lighting Controller has no effect in 2020.2

Hello, I just upgraded my project from 2019.4 to 2020.2 and the Indirect Lighting Controller doesn't seem to work anymore (no effect at all, whether it's set to 0 or 1000). Used to work perfectly fine in HDRP 9.2.

The Indirect Lighting Controller is quite necessary to avoid shadows to be pitch black so it's kind of really important for it to work... Are you guys (@SebLagarde) already aware of this situation...?

More info:
I use a Physically Based Sky with a single directional light and no baking/light-mapping of any sort. Again, everything was working as expected in 2019.4.16f1.

 

Alright I see now where this comes from. It seems in 2020.2 the Visual Environment section of the Sky and Fog Volume (the one that has the Physically Based Sky info) demands that Ambient Mode be set to ON (and then "Dynamic" in my case) in order to see the effect of the Indirect Lighting Controller.

That same checkbox could be left to OFF in 2019.4 and caused no problem with the Indirect Lighting Controller (its effect was still visible).

So I don't know if the bug was in 2019.4 or is in 2020.2 but that's the crux of the issue here...

 

I am having the same issue. I do not understand much about lighting but if I understand the second bullet correctly I found this:

Both settings were "None." After changing the settings to what is shown in the screenshot, my scene went from this

to this:


So the indirect lighting appears to be working now, but it is really ugly. I can mess with exposure in my volume but the skybox gets too dark if I lower exposure. It is kinda like the indirect lighting is too intense or something. I would like to hear if this fixes the indirect lighting problem for @Seith as well, and if this fix causes the same overly bright scene issue.


(my eyes are bleeding oof ouch)

Is this relevant to the original question or am I just not understanding how to do lighting?

 

Hi @JansM, thanks for your reply.

To answer your question, I'm using HDRP 10.2.2 (the one included in 2020.2.0f1).

And you were right. During the project update the profile was somehow reset. I restored that so now I can uncheck Ambient Mode (in the Visual Environment part of the profile) and Indirect Lighting still works correctly!

So thank you for that!

Actually the project updating process also created another issue with Ambient Occlusion: In my window layout I can see both the scene cam view and the game cam view, and the ambient occlusion of the scene cam was overlaid over the game cam (and vice-versa!). Which you can imagine looked really weird.

The only way I found to fix it was to remove the Ambient Occlusion override and then re-add it again. At that point the system was able to assign AO to the proper cameras.

 

@JansM Sorry I don't have a screenshot of the bug since I fixed it by removing the Ambient Occlusion from the post-effect profile entirely (and then added it again). The effect was simply that the AO pass was composited over the wrong camera view (Game AO -> Scene view and Scene AO -> Game view).

In other words it was clearly a side-effect from Unity upgrading the project.

 

I don't really know what I'm doing, but I kept those points in mind and pressed buttons for a while and now it works. Thanks for the help!