Problems with instantiating baked prefabs

I've found that the type of light doesn't matter, or even if you use different lights for your prefab and main scenes. What seems to be most important is that light map settings are the same in all scenes. However, I did run into a different problem (see here), batches and SetPass calls go up with baked prefabs.

 

Just changing

UnityEditor.Lightmapping.Bake()

to

UnityEditor.Lightmapping.BakeAsync()

won't work, as the code below that line will execute immediately, without waiting for the bake to finish.
Instead, the code below the async call should be moved to a

Lightmapping.completed

callback.

 

This has to be done automatically by default inside engine, why should I brake my head with custom scripts and settings to get it work? Tell me! This is ridiculous...

 

For now, it's just how it is. I understand your frustration, I really do. But let's focus on figuring out how to do this, assuming it's even possible.

I for one haven't managed to get this working yet

 

Some workflow ...
https://unity3d.com/how-to/light-baked-prefabs-on-mobile

Bakery is working too for me.

 

Does anyone have a working workflow for 2018.3?

 

I do exactly that and the object is as in image 1, but in play mode it looks like in image 2. how do I fix this ??

this script seems to work perfectly with everyone on the internet, except me: c


(translated by Google)
(Unity version 2018.3.11f1)

 

Hey guys, trying to figure out what's going on. I am using the GUI editor version with the "png" fix, this is how my prefab looks normally with everything baked:





However if I apply the lightmaps in another scene when I drag and drop or when I just instantiate it, I get this:




Seems like the mapping is all wrong, the circled area seems to be the actual lightmap (the blue dot is the emisive part of the small lightmap).

Any ideas what could cause this? Any help would be greatly appreciated!

Note: Android build, Probuilder objects, lights settings:

 

Which version of unity are you using?

 

2019.1.3

 

Same here, see above. Found a solution yet?

 

Have you exported the probuilderized object as an asset or an obj?

 

Built in renderer

I'll try that when I get home, will let you know if it worked.

 

Update: seems Probuilder 'forgets' UVs when part of a prefab, so if I click generate UVs in each individual probuilder mesh inside the prefab, then apply the lightmaps saved from the plugin, then it works.

Thanks guys for the help, will try to figure out now how to streamline pro-builderizing these prefabs with ease

 

Update: Light probes don't work sadly, as stated above in other posts. I know this is by design, but can you guys maybe reconsider fixing this in future releases or adding native support for it?

 

Really glad to see this issue being resolved after 4 years. Ah no, sorry, my mistake. Thank god it's nothing important.

 

9 pages of people trying to get this working :^) oof

 

Hi guys. If you have problems with instantiating lightmapped prefabs (after building the app) –
just read this: https://blogs.unity3d.com/ru/2018/05/14/stripping-scriptable-shader-variants/
And this: https://answers.unity.com/questions/675273/where-is-the-lightmap-on-definition.html

 

Hi all. We are experiencing the same issue after upgrade the project to LWRP (2018.4). All the backed prefabs show broken lighting (big dark parts).
From what @Mr-Rouf mentioned, we thought it's LWRP strip some passes of the shaders (but we don't know which ones). We try to use the code below as the hack but I'm not sure it works:

Code (CSharp):

1. bool StripUnusedPass(ShaderFeatures features, ShaderSnippetData snippetData)
2.        {
3.            if (snippetData.shaderType.ToString() == “Vertex”)
4.                return false;
5.            if (snippetData.passType == PassType.Meta)
6.                return true;
7.            if (snippetData.passType == PassType.ShadowCaster)
8.                if (!CoreUtils.HasFlag(features, ShaderFeatures.MainLightShadows) && !CoreUtils.HasFlag(features, ShaderFeatures.AdditionalLightShadows))
9.                    return true;
10.            return false;
11.        }

If any one has better solution, please share with us.

 

Anyone figured out how to get this working? :')

 

thank you thank you very very much

 

If you are at Unite, can someone please have a chat with the gfx team about this.
I have work arounds for all the problems but they are an utter ball ache.
The current changes to separating the lighting which have been started in 2019.3 still not not address the issues with procedural levels.