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

Hi,
What could be a cause of getting pink shadows like that?
All the materials in the scene are based on standard built-in shader.
The pink color disappears only in ambient occlusion only mode.

 

Hi,
Your documentation doesn't describe in detail how the shader tweak> bicubic interpolation for lightmaps works. Does enable this option change the lightmaps themselves or Unity interprets the lightmaps in another way? Enable this option causes one of the shaders to issue an error and is purple, without this option it works normally.


Bake scene with render mode set to shadowmask is the most optimal solution, true?
Is it possible for characters (not static objects) to get shadows and cast shadows after baking with the shadowmask option? (the distance shadwomask option is not the optimal solution). Setup "Light probe mode" on L1 option does not help me. With the Unity lightmapper, you can achieve this effect with light probes. I'd like to get a similar one with your asset. How can I do that?

 

Not sure if it's been reported but when using Physically-based Sky in HDRP 12.0.0 (2021.2.0b8) the sky is black after baking:

 

Hi there, I'm really confused on how to get the HDRP shaders working. I have read the documentation but it doesn't explain/specify what shaders to use on the HDRP, it only says to use the ones found in the HDRPpackage. However, after trying them on the sample scenes, none of them are showing the lightmaps. Why is this happening? here are some screenshots of the weird behavior

 

Here's how it should look. Sorry for the double comment

 

I am wondering if there is template scene available like all example scenes with sponza, shadowmask etc. with properly setup URP >=11, Unity 2021.x and realtime shadows from point lights and spotlights, mixed properly with Bakery lightmaps?

 

Try to set the sunlight mode to mixed.
I experienced some issues with HDRP, too.
Pretty sure this great asset needs some more investigation in HDRP.

 

Hello,

I'm trying to use Bakery's volume system for the first time, but I'm getting weird 3D noise when moving an object through space :

This is using Bakery's latest Github version, with HDRP and Unity 2020.3.

I wonder whether it's some setting that is not set right on my end or just a bug... I'm not compressing or denoising the volumes.

Have a nice day,

J.S.

Edit : On an unrelated note, I can't use optix 7 denoising, as I get this error : "denoiser72 error : Unknown error (1)" (RTX 2060 with latets drivers), so I have to use Open Image Denoise which results in colored dots

 

You have an exposure problem here, probably because HDRP does not use the same light scale as the other pipelines, you are only seeing the reflection, and no diffuse lighting, which is probably why you can't see any lightmap. Make sure you have a proper sky volume, a strong enough directional light, and a post process volume with an exposure effect on it (try to tweak the settings).

 

Hi. Is it expected for Dominant Direction to work like this?
Cubes have the same materials, the same distances.

In complex casesthis is so annoying. The materials take on very strange colors.

Dominant Direction:


Baked Normal Maps:


Is there any workaround? We are really need the baked specular, it looks really awesome. Cannot use SH due to performance reasons (mobile hardware, SRP Batcher issue).

 

Hello.
I rendered it in Bakery, but the lightmap gave unusual results.
Just like the image, the lightmap looks like a striped pattern.

I've tried a few, but it always happens when I enable Denoise.
Is there a way to solve this?

 

It can affect GI precision captured by volumes. So it makes sense to set lightmap resolution to be similar or higher than volume resolution.

Shouldn't be a problem? Can you send me a project with this example scene (everything else can be stripped)? I'll check settings/versions, etc.

Didn't test the beta. A few times in HDRP history they flipped the Meta Pass vertically, resulting in a similar problem. Can you check if
- Opening ftUVGBufferGen.cs
- Finding "bool isHDRP = "
- Changing it to

bool isHDRP = false;

- Baking again

helps?

Yes. Apparently your world is just that big.
Consider not lightmapping every object, e.g. using probes or real-time lighting for trees and possibly everything except for interiors. Real-time lighting usually does an OK job with exteriors but fails to provide decent interior GI.

Hi, thanks What shader is that? Did you include BakeryMetaPass.cginc. It's weird if it caused this, as it doesn't declare unity_LightmapST on its own. Technically there is nothing preventing shaders with Bakery Meta Pass to be compatible with SRP batching.

Should work. "Contribute GI" + "Cast shadows" is enough for Bakery to consider it a shadowcaster. "Receive GI" option is unused (scale in lightmap = 0 is used instead https://geom.io/bakery/wiki/index.p....2FGI_without_having_a_lightmap_on_its_own.3F )
Maybe there is weird opacity map that makes it transparent?

 

Based or using the exact standard shader?
If your Skylight is not pink, it looks like your shaders look pink (shader error) when rendering Meta Pass. Are there any shader errors in console or when selecting shader assets? If you have RTPreview, it'll be super helpful to see how the scene looks there. You can also send me any small test scene as unitypackage or a project, and I'll debug it here.

Yes. It patches some built-in CGIncludes from the editor folder (it backs up original files so they can be always reverted).

Interesting. In post-2017 Unity versions this issue can be avoided with slightly different code, but I didn't do it for the sake of backwards compatibility. Try replacing UnityEditorFolder/Data/CGIncludes/ftrace.cginc with the attached version, and your shader will likely compile OK.
Basically the problem is using samplerunity_Lightmap, as if compiler decides your shader doesn't actually use the lightmap, it will remove the lightmap-related code; and then Unity will also unset the sampler and break the shader. Newer Unity versions allow defining custom SamplerStates within the shader, and this issue can be avoided by using a custom lightmap-independent sampler.

Enable Occlusion Probes: https://geom.io/bakery/wiki/index.php?title=Manual#Occlusion_probes

Alternatively, if you can use Volumes instead of light probes, and if you're on the Standard (or custom) pipeline, you can get even more detailed shadowing on dynamic objects using shaders supporting Volume shadowmask:

OK, for now I'll just hope it's gonna be fixed when it comes out of beta...

It looks like you're using default (very bright) HDRI sky intensity?
https://geom.io/bakery/wiki/index.php?title=Manual#Notes_on_HDRP.2FURP

I don't have it at the moment.

It'll be easier to understand what's going on by visualizing the volume on a large plane instead of the small sphere. This way you can see if the volume matches the scene.

Weird. Can you check what .denoiserlog.txt says after it happens?

No.
Can't repro this with default materials:



Looks OK on URP too:

What is your pipeline/shaders? Possibly it expects different sRGB flags on the direction map? Possibly you have some asset postprocessor script that changes the flag? You can try toggling it on the baked directional map assets and see if it helps.

Caused by this:





You can:
a) Update via the patcher (there is a workaround): https://geom.io/bakery/wiki/index.php?title=Github_access
b) Use an older driver without the bug (at least 460.79 was definitely OK)
c) Wait for the fixed driver
(Option A is currently the best one IMHO)

This bug only affects OptiX 6 and 7 when denoising lightmaps with 4096x4096 or larger size, using particular drivers. My workaround just currently splits them into 2048x2048 chunks.

 

Hi! sorry no, Actually I disabled the HDRI almost completely and no luck. What I noticed is that the point lights aren't working at all. There should be a point light there but the light maps are not picking it. Any idea of why this could be happening (it's HDRP)

 

I found the clue: it can be reproduced only on android platform. On PC platform everything is ok.

 

Looks cool!
I had the same, switched denoiser to "Open image denoise" and it was gone

 

thank you!
I was able to resolve this issue by downgrading the NVIDIA GameReady Driver from 472.12 to 461.72.

Thanks to guycalledfrank and Cascho01 for other solutions!

 

Okay, I set a bunch of exterior objects with light probes instead of lightmaps, and the lightmaps were reduced to 220. Something is something.

Now if I combine enlighten (real-time lighting) with bakery it will take maybe 12 hours to bake

 

Hi,

I have a problem when baking different scene with shared prefabs.

I'll try to explain: I have 3 scenes with a shared (nested) prefab. I load one scene at a time at runtime.
When I Render a scene, everything goes fine. Then I unload that scene (in Editor), load the second one and Render the second one. When I switch back to the first one, all the dynamic meshes (the one without "Contribute GI") have the same colors they have in the second scene. How can I fix that? :/

Another thing: I have the project on GIT and I work from different computers. When I Render from a computer and I push all of that, the lighting is broken in the second computer! How can I manage to preserve all the lighting between computers?

One thing I noticed, when looking in the "Lighting" tab in Unity, is that when I switch from different scene I see in the previews of the maps a mixed from the different scenes.

Thanks in advance, I hope someone can help me! ^_^

 

Hi, further elaborating on my question, here's a screenshot of my settings and proof that the previewer is seeing the light. However, after baking, the light is not visible at all (I'll drop the baked version in a second comment). What I'm I doing wrong? This is the latest tested unity according to the documentation of bakery

 

Here as you can see, after bake everything becomes super dark and I can't see anything. I've already tried reducing the exposure and the HDRI but no luck

 

Looks like it was affected by Lightmap Encoding property or some cache(?), after tweaking it to different values and return it back i cannot reproduce the issue. But i found a new one: on PC platform Dominant Direction with URPDirSpec shader graph looks oversaturated. On Android it looks normal. I created a fresh URP project (unity version 2020.3.16f) to reproduce the issue.

SH:


Dominant Direction:


Baked Normal Maps:

 

Scene on Android:


Same scene on PC (switch platform & re-bake with same settings):


Material example:


Unity 2020.3.16f, Bakery 1.9 (latest from store)

 

Thank you for the answer !
Here is what the volume looks like on a big plane.


As you can see, super noisy. I tried deactivating denoising, and it seems the issue is not with the volumes, but with the entire bake, although denoising hides most of it :



I'm using a pretty reasonable 14 texels per unit, 64 samples, 5 bounces... Baking indirect only, with a simple skylight

On the other issue, I can't seem to find the denoiserlog file, where is it located ?

Thank you

EDIT : I just tried tweaking the sample count and bounce amount, and it changes absolutely nothing on the result, so I feel like some of the settings on the bakery window are somehow ignored, it's very strange...

 

Hi everyone !

May be is such a classic error, but I'm stuck with this one ! I just want to start a bake to test for the first time Bakery...

This terrible error appear and I don't understand why ?
I update the driver of my graphical card. I'm on Windows 10, I've a 1060 Geforce GTX from Nvidia so....
I patch Bakery too...



When I launched the utility to detect optimal setting. This one appear.



Did you have this ? One time by the past.
I also tried to check the setting panel from the nvidia card.

 

Bug? If I set Receive Global Illumination to Light Probes, it will still bake a lightmap for the object.

 

First of all thanks for this great lightmapper, works very well on my Windows PC.

I have one question:
Would it be possible in the near future to use Bakery on my Macbook client and bake over network with my Windows PC?

 

So for some reason, having a area light as part of a prefab breaks the area light and makes it a black rectangle ?

I get a lot of really bizarre results.



Here I duplicated the area light in the window, applied it to the prefab causing the black rectangle.

Then I decided to move that area light and check rtpreview again.

Now i have the black rectangle, and an area light... This is very bizarre. I don't know if it's affecting my rendering.

As an additional note.



The issue of -1 x-axis scale is also still a problem. I remember this being fixed?

This should be the latest version, i used the patcher.

 

anybody have an issue with reflection probes baking out completely black exrs? not sure whats going on, I have the clipping distance set, layers masks set, objects set to static. Nothing, always black.

 

Is it safe to erase the ftracelog.txt? I have some source control issues with that file

 

Afaik it just logs what went on during baking and can be useful when troubleshooting errors.
You could exclude it via .gitignore.
.

 

@guycalledfrank
Hey there ! Regarding setting lightmap scale to 0 for receiving lightprobes, that basically works thx! But it seems to produce bugs when using that with bakery meta pass. Things get stripy, artifacty:

This is how it looks with lightmap scale set to > 0.0

Is that just a limitation of Bakery Meta Pass ?
Regarding my other Question:
I use additional stuff in my bakery meta pass, like a texture for noise and float for adjustments (i disabled those for testing in my first question). I declared those as properties but don't add them to my input.hlsl CBUFFER, because i dont need them for runtime. Also as far as i understand it the Bakery Meta Pass still uses cglab which seems incompatible with hlsl from SRP. And then unity tells me for example Material Property is found in another cbuffer than UnityPerMaterial (_BakeryMetaNoiseScale) and SRP Batcher = not compatible. Is there a way around that? I can just disable the Bakery Meta Pass in the shader for release build, but it's a minor inconvenience.

 

Hello everyone, Mr. F is sick Is sick and in a hospital, currently unable to reply to forum and Discord posts. He will answer your questions as soon as he gets back to normal.

 

Oh that's really sad to hear ! I hope he gets well soon ! Best Wishes <3

 

Get well soon. Gute Besserung.

 

I press bake then when the progress is at 100% it says "finished rendering" and just freeze, what to do ?

 

What does the fo log say? (

Editor > x64 > Bakery > .ftracelog.txt

)
Does it show any error message?

.

 

I assume by

Editor > x64 > Bakery > .ftracelog.txt

you mean

AppData\Local\Unity\Editor

but I don't have a x64 folder in there

 

@doodlinbee Inside your project
.

 

there doesnt seem to be any errors, I seem to run out of memory though but its just a guess

 

Get well soon, Mr. F

 

^ From me, too. Get well soon

 

Heyo, Frank!. I am getting this weird baking error on these pillars and fireplaces. Any ideas? Increasing the Tile Size doesn't seem to do anything.

 

im getting these horrible artifacts/ colored patches..ive attached screenshots of the renders and my settings...tried different things still doesnt seem to get rid of them...whats wierd is the preview app actually shows it clean...using rtx mode...all meshes have unity uv lightmapping ON...any thoughts appreciate!!

 

Look like compression artifacts. What if you set

Compression

to

None

on your lightmaps? Do these colored patches go away?
.

 

Get well soon!

 

Hello, I have met the same problem. Have you solved it?

 

Get well soon

 

Using Post-packing option causes errors with LOD grouped objects in a scene where baking Shadowmask with just a Direct Light that has the "Indirect and Shadowmask" Baked Contribution option. I am using a GTX 1080 with no RTX. Here is the sequence of errors.

 

where would you access the compression features for the lightmap if your not using unity light baking compression..that is unchecked but that shouldn't matter right...i dont see any compression settings..could it be the denoise?