Light probes losing realtime GI data on load?

Hi everybody!

I already created a bug report for this, but while I wait for some kind of confirmation there, I thought I would ask here to see I've done something to cause it, or if anyone knows of a workaround for it.

What I'm seeing is that right after I bake my lighting for my scene, light probes will illuminate dynamic objects with light coming from all the light sources in the scene, but when I build to exe, or load a different scene and come back, they're suddenly only lighting using data from emissive objects with the Global Illumination mode set to "Baked" and ignoring them if the mode is set to "Realtime".

In this test scene the blue sphere on the left is "Baked", the red sphere on the right is "Realtime". The cube is a static object, and the smaller sphere is a dynamic object being lit by light probes. I'm baking using the progressive light mapper at the default settings.

This is what it looks like immediately after I bake the lighting.

After I load another scene and return, or I try to run the game as an exe, it becomes this...


I first ran into it in 2017.1, I think. I tried updating to the latest 2017.3 build to fix it, and it didn't help.

 

Similar problem. I have walls with a 'static' flag. Directional Light, a couple of Point Lights, all in Realtime Mode and Realtime GI turned on.
And I have the doors (which is dynamic objects), that lits with Light Probes.
When I bake light everything is good, but when I build the project, these doors are going to black in runtime and in Editor too, until I recompute GI.

Please, attention to this. What can I try?

Unity 2018.1.1

 

Baked light with Light Probes working good...

Realtime GI and moving objects. Is that possible at all?

 

Partially solve this problem following:
Make my point lights in Baked mode, what takes to me some additional GI for my objects (more brightness).
Then add one more point lights layer for just doors in Realtime mode (Culling mask - just one layer).

 

Still same issue...

 

Same for me BUT only when I use progressive lightmapper.

 

Same issue here with progressive + Realtime GI. This also gives issues with LOD cause they uses lightprobes for the lower res models.

i'm using Unity 2018.3.5f1

When I bake the lighting it looks good.

Then I save the scene and reload it and get this:

The cube is not static, and it looks wrong. My LODs greater than LOD0 looks black so the transition is terrible, and I noticed the light probes looks also black.

Obviously this is a test scene, I'm having this issue with a big production scene which takes 16+ hours to bake, so this is a real big pain...

Have anyone found a solution for this problem?
@Erasmus-Crowley Have you had any feedback on the bug report?

 

you can watch

but remember it very different in practice

 

I wanted to post an update to this in case anyone is struggling with this problem and comes across this post. I was curious if any progress had been made on it, so I just loaded up the project that I used in the original post to reproduce this issue in Unity version 2019.4.8f1 and this problem still exists.

My original bug report was closed as a duplicate issue, but I was forwarded to this bug report instead.

https://issuetracker.unity3d.com/is...y-mode-when-baked-and-realtime-gi-are-enabled

To summarize, the issue was closed with a resolution of "Won't Fix". The description says, "This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause."

Looks like this bug is just going to be around forever, unfortunately.

 

They won't fix because real time GI is enlighten and they depreciate that and stopped paying them. SO you need probably to go bake GI only or find another solution for real time.

 

Does anyone know if using Bakery will fix it?

 

No it won't, bakery just bake.

 

I'd say this is a pretty major bug then, especially that it is in a LTS release.

 

Like I say, it's predicated on enlighten, they revoked the license to enlighten, therefore enlighten cannot offer support for integration. It's not a bug, it's an artifact of depreciation. People have been ranting about the lack of low end GI solution like enlighten, while unity is trying to roll out their own high end GI based solution of full raytracing or nvidia's rtxgi sdk (based on ddgi).

 

I personally reported this bug nearly 3 years ago. There were others who reported it before me. This issue predates Unity's decision to retire Enlighten. Unity's fix is apparently to replace Enlighten entirely. I understand that.

I don't understand why you're arguing that it's not a bug though. It shouldn't matter if Enlighten is deprecated, because deprecated systems can still have acknowledged bugs.The resolution of the bug might be "won't fix" or "can't fix", but it's still a bug.

 

Now that there has been an announcement that Realtime GI with Enlighten is no longer deprecated, and it looks like it's going to be with us for a considerable amount of time in the future... Is there any chance that we might get someone to take another look at this issue?

 

That's nice but will this actually be fixed? I only just noticed this bug today and it makes my scene look like total crap. Using Enlighten to bake lightmaps is not an option. It looks terrible compared to progressive lightmapper, and it's entirely CPU bound so it takes way too long.
Furthermore, if this is to be fixed, will it be back-ported to LTS versions of Unity? E.g. 2018 LTS, 2019 LTS? Or will it only be fixed moving forward, forcing those of us on previous LTS versions to continue to suffer with no realtime GI?
Would love to see a complete replacement for Enlighten realtime GI.

 

Thank you very much, that's very good to hear.
Even if it takes a while to fix, it's very good to hear it's being worked on actively. Thank you for taking the time to provide this information!

 

So I'm not sure if this is the same bug or not, but I'm using 2020.3.9 LTS and when I enter playmode, either my RealtimeGI checkbox gets unchecked (making me unmaximize/pause, recheck it, unpause), or more recently, my entire lighting of the scene seems to be changing when I hit play. I'm only using real time GI, nothing is baked. When I hit play, everything gets brighter, and even turning off all my lights still has the game being lit ... something funky is going on with the GI I assume. This persists until I redo the GI.

The entire product I'm working on is dependent on realtime gi just working normally, so I'm hoping this gets stabilized soon ... I'm trying 2020.3.10 now, but it sounds like its an ongoing issue.

 

Attached are two pictures, the "before" is in editor after the realtime gi is finished, and "after" is when I hit play. What on earth is going on >.<. 2020.3.10f LTS still doing this.

I added another "no_lights". Notice, there are 0 lights turned on, no post processing, no reflection probes, etc ... and everything is still lit. It all turns black when I clear the baked light data, as it should. Somehow, when I hit play, my GI seems to become some sort of base-line for the scene, then lights + actual realtime GI are added to that, or something.

Okay ... more testing. I can clear my baked data. Turn off RealtimeGI. But when I hit play, now it does the opposite of what it did earlier today ... it TURNS IT ON by itself, and then does a weird bake automatically making everything super bright. Even when I have no baked data and its turned off.

[Edit -- Making a new scene fixed this. Holy moly, bad bug ... glad thats all it was.]

 

I'm experiencing this bug in Unity 2021.2.0b12, looks like this bug is alive

For me, I set up a scene like this:



This is right after baking lightmaps with mixed lighting and realtime GI. Everything looks good.

The Sphere is the only thing that isn't Static, it's supposed to be placeholder for my character.

Then as soon as I enter play mode:



The sphere just goes black on the side where there's no direct light pointing at it.

It's unbelievable this bug has existed for so long. I'm going to report this bug with my project files attached to hopefully help the devs repro this and fix it. I suggest everyone else do the same to help the devs solve it

 

I've run into this thing right now. Lots of fun.

Coupled with inabilty to properly prefab lightmaps I'm wondering if I am supposed to run my own lightmapping system.

 

There's now a resolution note added to the issue tracker page, it's looking like this is not going to be fixed until sometime in the 2022.x product cycle. That's absolutely crazy, it's a pretty important feature no? Is there at least some kind of workaround in the mean time?

 

Running in to this problem as well, very problematic. Why exactly is something this important postponed?

 

lol, a year later, still no resolve, amongst other seriously horrible light probe issues, and now its only being looked at for 2022... ?

i Swear, some of these bugs are left in intentionally to prevent anything serious unless you paying for that elevated support. 'facepalm / tinfoil hat etc etc'. (Looks at nav mes issues across every major LTS, Custom Lists etc... O,o ).

Ok, tinfoil hat off. /Resume.

Note: Like this lovely gem, which pops on attempt to async retetrahedralize light probes after a scene change...bug?? I dunno, shrug. Its unity.. errors not very descriptive , and points no where, including a Google search which turns up 'Whooops'. meh. Hence, i ended up here.

Code (CSharp):

1. Assertion failed on expression: 'offsetIndex != -1'

 

Is this going to be fixed in 2022.1.x because we are using a plugin which relies on UnityEngine.Networking, but that has all been removed from 2022.2 So it turns out we are stuck because light probes are not working and we can not switch to 2022.2b because the plugin update will take time ?

 

Hi i'm on version 2022.1.19f1 using latest URP

Actually in our case we are not using Realtime GI
Anyway Light Probes are still not working with baked lighting

That's in edit mode


And that's in play mode. Both spheres and some of the objects in the back that are not baked are not lit by Light Probes

 

Hi,

Thanks for that Lightmapping Troubleshooting Guide page, i've never come across it ! It did the job !
it's the LightProbes.Tetrahedralize(); method was actually needed as the scene is loaded Additively !

Cheers !

 

I also encounted this problem. Here's my situation:
I have 3 scenes, scene_Base, scene_A and scene_B.

* I will load scene_Base firstly and then load scene_A in additive way, and set scene_A as active scene.
(At this moment, light probes in scene_A works fine.)

* Then I will unload scene_A and then load scene_B in additive way.(scene_Base will always exist).
In this moment, light probes of scene_B become all black. However, it works fine when I open scene_B in Editor mode.

Do you have any ideas?

I'm using Unity 2021.3.2f1, HDRP 12.1.6

 

Thank you! This works for me.

 

Have same problem it seems like unity messed something again (I encounter that problems with additive loading since 2017 version) Hope it will be fixed. Did you maybe resolved it? It seems like lightprobes are overrides in playmode from some reason. Did you have lightprobes on Scene _base?