Bakery - GPU Lightmapper (v1.95) + RTPreview [RELEASED]

Ok sure - though it seems the Unity one is pretty accurate (you can see the shadows falling pretty closely on each checker).

Great! That did it! What is happening though with this option? Because I was always using 'Force On' because - from the docs, "If disabled, and the scene is too big, Bakery may go out of memory."

 

Magic. It can slow down rendering a bit, but also make huge maps fit into memory.
I've just sent a PM for you to investigate why it breaks on your scene.

 

To all people still experiencing crashes on large scenes or lmrebake errors - try updating this file:
https://drive.google.com/file/d/1p1Hv_SMQNxKdLkXhouCoRNhELt0mLs9z/view
Should be in Assets\Editor\x64\Bakery

 

Hi @guycalledfrank,
Are you aware of a difference in anything related to the lightmap between the 2018.2.2 and 2018.2.6? I had a scene working perfectly in the first one but now it looks like the UV generated are different so everything is messed up.
I've checked the changelogs but saw nothing related to that, but when I open the project with 2.6 I can see it's re-importing and doing something on all the meshes with the generates UV lightmap box checked.

 

Not really, 2018.2.2 was the last version I tested it on.

Perhaps they changed something about renderer lightmap scale/offset. Does rebaking the scene help?

 

I just tried the "Reimport" option for the model and it seems to fix the issue. So basically the UVs were the same but with an offset.

 

Good to know!

Does anyone want to test LOD support before the release? Send me a private message.

 

A hacky as heck solution, but you could give all surfaces a small amount of emission?

 

@guycalledfrank Does every child mesh of a lightmap group selector require its own lightmap group selector? I have two groups of individual meshes, each group needs its own separate lighting even though the groups sit very close together and would be contributing to each other's lighting otherwise (technical constraint). I'm attempting to do this with the lightmap group selector(s) and bitmask properties. I have it very close to behaving how I want - except since each child mesh per group has its own lightmap group selector so it seems like I may be doing something wrong?​

Interesting idea, I'll definitely see how that works out. Thanks!

 

This looks really good!!! It would be a nightmare to make a good unwrap out of this and have a proper resolution for normal lightmap bake...not to mention the render times would go up !!! Really curious to try this out!!

 

Well vertex lightmaps are already out, you can try them since 1.1

 

guycalledfrank, there's something wrong with the shadowmask mode. The first screenshot is Bakery, the second one is progressive lm:


This test scene has 8 mixed point lights with Bakery point light on each marked as Shadowmask.

And I got an error when I duplicate some light and change its color:


ArgumentException: Getting control 13's position in a group with only 13 controls when doing ExecuteCommand
Aborting
UnityEngine.GUILayoutGroup.GetNext () (at C:/buildslave/unity/build/Modules/IMGUI/LayoutGroup.cs:117)
UnityEngine.GUILayoutUtility.DoGetRect (UnityEngine.GUIContent content, UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption[] options) (at C:/buildslave/unity/build/Modules/IMGUI/GUILayoutUtility.cs:425)
UnityEngine.GUILayoutUtility.GetRect (UnityEngine.GUIContent content, UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption[] options) (at C:/buildslave/unity/build/Modules/IMGUI/GUILayoutUtility.cs:385)
UnityEngine.GUILayout.DoButton (UnityEngine.GUIContent content, UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption[] options) (at C:/buildslave/unity/build/Modules/IMGUI/GUILayout.cs:34)
UnityEngine.GUILayout.Button (System.String text, UnityEngine.GUILayoutOption[] options) (at C:/buildslave/unity/build/Modules/IMGUI/GUILayout.cs:27)
ftPointLightInspector.OnInspectorGUI () (at Assets/Editor/x64/Bakery/scripts/ftPointLightInspector.cs:355)
UnityEditor.InspectorWindow.DrawEditor (UnityEditor.Editor[] editors, Int32 editorIndex, Boolean rebuildOptimizedGUIBlock, System.Boolean& showImportedObjectBarNext, UnityEngine.Rect& importedObjectBarRect) (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:1374)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

Masks are clipped where there is no light. Are these points or spot lights? Is this abrupt ending actually visible on the final image?

EDIT: I'm testing a similar scene right now (lots of overlapping points) and found that problem. Investigating now!
I assume there are warnings in console like "Light Point Light can't generate shadow mask (out of channels)."?

This is some kind of Unity UI bug - I don't know why it happens, and it's harmless, ignore it.

 

yeahh already bought it ...but still didnt had time to really try it out

 

I'd like!! please send to xgits@outlook.com

 

Found the problem and fixed:



Will include this fix in the newer version, and can send a quick patch to you.

 

Hi.

I have not yet managed to complete a successful process. The errors are diverse and I try to reduce them by interpreting the messages ... but I can not.

First of all it gives me an error when exporting the scene:

I thought it was UV problem so I modified the options. After this, the process "Exporting scene - finishing objects" began. But it's never over.

Once a message "error creating texture" (or something similar) appeared
Then I got an error in ttrace or similar

I have arrived at "rendering lightmaps - preparing" but I have not managed to advance further.

I have an i7-4790 with 16GB RAM and NVIDIA GTX 1060 6GB

I have also had memory occupation problems. 13 GB Unity! doing the processes.

The fact is that I have tried several times changing parameters and other things, but without success. So I have no choice but to come to you and ask how to solve this.

Thank you very much.

 

Currently yes. I'm thinking of updating the lightmap group stuff for the upcoming version.

Currently that means -> 2 Lightmap Group assets and the Selector component on every child with one of 2 groups selected.

So... do you want them to NOT affect each other? In this case, Groups won't help. What you can do is to separate them into different scenes, bake individually and then put back together.

Bitmask will allow you to filter lights from being applied to lightmaps, so it kinda works, yeah, but it won't affect GI propagation.

Generally no, it's not wrong. But I'm going to add a new mode to the selector, so it won't require it.

Does it also happen with example scenes?

 

Hi, i have some problem - every time when i bake my scene, on "Exporting scene - adjusting UV padding..." step unity recalculate UV2 coord with UnwrapCL.exe. It is very long for my scene. Can i skip this step or disable recalc UV2 every time?

 

@guycalledfrank I think I have run into a bug on the Mesh Light. We use a mesh that has 2 materials (i.e. with sub-mesh) with only 1 being emissive (set as Light Bakery). When I use this mesh it causes an error in the build. It works if there are 2 materials on a single mesh, just doesn't work with sub-meshes.




It doesn't seem to be handling the second material correctly since it isn't emissive or have a correct texture on it for a bakery light.

 

I have same error too sometimes, but a little different text:

ArgumentOutOfRangeException: Argument is out of range.

Parameter name: index

System.Collections.Generic.List`1[System.Collections.Generic.List`1[System.String]].get_Item (Int32 index) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Collections.Generic/List.cs:633)

ftRenderLightmap.UpdateMaskArray (Int32 LMID, System.String lname, UnityEngine.Light ulht, Boolean denoise) (at Assets/Editor/x64/Bakery/scripts/ftRenderLightmap.cs:4289)

ftRenderLightmap+<RenderLMDirect>c__Iterator3.MoveNext () (at Assets/Editor/x64/Bakery/scripts/ftRenderLightmap.cs:3885)

ftRenderLightmap+<RenderLightmapFunc>c__Iterator2.MoveNext () (at Assets/Editor/x64/Bakery/scripts/ftRenderLightmap.cs:2466)

ftRenderLightmap.RenderLightmapUpdate () (at Assets/Editor/x64/Bakery/scripts/ftRenderLightmap.cs:1923)

UnityEditor.EditorApplication.Internal_CallUpdateFunctions () (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:191)

After reload project i get another error:

InvalidOperationException: Operation is not valid due to the current state of the object

System.Collections.Stack.Peek () (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Collections/Stack.cs:321)

UnityEngine.GUI.EndScrollView (Boolean handleScrollWheel) (at C:/buildslave/unity/build/Modules/IMGUI/GUI.cs:1414)

UnityEngine.GUI.EndScrollView () (at C:/buildslave/unity/build/Modules/IMGUI/GUI.cs:1408)

ftRenderLightmap.OnGUI () (at Assets/Editor/x64/Bakery/scripts/ftRenderLightmap.cs:824)

System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222)

Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.

System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:232)

System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MethodBase.cs:115)

UnityEditor.HostView.Invoke (System.String methodName, System.Object obj) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:295)

UnityEditor.HostView.Invoke (System.String methodName) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:288)

UnityEditor.HostView.InvokeOnGUI (Rect onGUIPosition) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:255)

UnityEditor.PopupCallbackInfo:SetEnumValueDelegate(Object, String[], Int32)

 

@guycalledfrank The issue that @CaptainMurphy is having looks very similar to what was happening to me, (the sci-fi internal wall panels) where I have multiple materials on a mesh only one of which has emissive maps on it.

I fixed it personally by re-exporting the OBJ from blender with "separate mesh groups" however there is probably a bug somewhere there which is causing this underlying problem.

 

I got around it by adding a try/catch around that section that does the f.write() and just having it do a write to 0 if it fails.

 

Some tests.
This is mobile game so all in gamma and low resolution. Love the quality))

 

Rendering time 190sec on gtx1070!

 

Yes you can. It's the "Adjust UV padding" checkbox in Advanced settings. It utilizes built-in Unity unwrapper (which is slow) to modify UVs. If you disable this step, you may get leaks at UV chart edges. When it's enabled, it may re-unwrap stuff every time "texels per unit" or LMGroup resolution changes.

Seems like a bug, yeah. Will investigate. Probably don't use Light Meshes with multi-materials for now.
Also in your case it's not the best idea anyway, as you don't want to emit light from metal.

That seems like a bug too, but just today I changed shadowmasking code a bit, and I think it shouldn't happen anymore. I can send you a patch to test.

Nice!

 

Thanks, Yes, it`s will be good...

 

After swapping all of the lights to use the mesh instead of a point light I now get an error baking the scene.




After hitting OK I get this:


I am going to try cutting the detail level down some to see if it bakes at a lower setting.

 

Sent you a PM.

Ouch. Is it caused by a particular Light Mesh?
Can you try disabling the Selfshadow checkbox on all Light Meshes?

 

I tried both on and off for self shadowing. It appears to be something with the GI pass that causes the issue. If I turn the GI passes to 0 it will bake ok, albeit a bit too precise.

 

But it didn't happen before you changed the lights? Or were there any other changes?

 

I ended up giving up on that route and instead made a cubemap cookie for the lights since point lights were baking fine. In order to cut down on processing I made the cookie have the blurring already in it so there was less casts for lighting.






Down from 31 hours Enlighten bake time to around 18 minutes. Definitely an improvement!

 

Nice! You can also try increasing Shadow Spread on lights to make shadows blurrier. On point lights this value represents the radius of an imaginary sphere from which shadows are cast.
Mesh lights should still work though. If you'll be able to narrow this problem down to a specific mesh causing the crash on GI, it would be immensely helpful!

 

Nice job! Yes, please send me the fix. Thanks!

 

Done!

 

Had the problem aswell, can you send me the fix too? Thanks!

 

And done.

 

guycalledfrank, thanks, it helped, but I ran into another problem. Shadowmask is bigger than a point light range with Bakery (top), and with PLM it looks good. Because of this, some lights are not baked.

Light Point Light can't generate shadow mask (out of channels).

So it should be?

 

Hmm, I think I know why it happens. Will try to fix.
Is it even a real scene? More looks like a test specifically designed to make my code fail

 

Shadows seem to work now but I am still getting weird artifacts on the walls and ceiling.

 

Just sent you both another patch.

 

Hi guycalledfrank,
Thanks for your awesome plugin, but there's one problem which bothers me for awhile.
When I switch from Unity, I notice there's shadows from point light which was disabled on Unity light by choose shadow type to 'No Shadows'.
Is there any way to disable shadow like Unity did?

 

more cutout may crash unity editor? may be 20

 

I avoided all kinds of non-physical behaviour originally, and shadow-less lights are an example of that.
There is a way you can still hack it for Direct lights - by setting Samples to 0, but I'm not sure it will work correctly for other lights.

Edit: Actually - try this little patch:https://drive.google.com/open?id=1J4cDvF5nK6WrynHgGodBI9Mo9KA7QU-2
You should be able to get shadow-less Point/Spot Lights with it by setting Samples to 0 too.

Do you mean you have many different cutout materials, and it crashes? When? What is the error message?

 

Here is a test project, SetAlphas or GenerateAlphaBuffer may crash editor

 

Thanks! Can reproduce. Investigating now.

 

Found the problem. Please replace this file: https://drive.google.com/open?id=1m0fS3tKtWKf4EjtLEmOHZ8zsI14i9ZvP
It should be in Assets\Editor\x64\Bakery
I recommend restarting Unity before replacing, as it can lock previously used libraries from overwriting.

 

May be It's a simple scene with a plane and several point lights for quick baking lightmaps.

Thanks again!

 

Just added one hacky option everyone was asking about:



Can be set per-light. Will be in the next release.

 

Here is a current bake run. Getting much closer to a final product, and the bake times are crazy short compared to Enlighten. I think my last hurdle is going to be getting the curtains to work like I want with light transmission/shading, but otherwise it is looking great.

Spoiler: Updated Screenshots from the Beta