Mesh error when baking lights

Hey guys,

I get these errors about once a second when I try to bake my lights and the bake never finishes.

Line 215 in Verify - Geometry geom c4fab7362f4dc00cea6f77d7ddf7f9cb: Index 45 has value 41 that reads non-finite value nan in channel 4, element 0

Line 229 in Verify - Geometry geom c4fab7362f4dc00cea6f77d7ddf7f9cb: 18 components out of 3030 total are non-finite

Line 215 in Verify - Geometry geom dee631821ad753ec9d9551c1fc86df9d: Index 41 has value 170 that reads non-finite value nan in channel 4, element 1

Line 229 in Verify - Geometry geom dee631821ad753ec9d9551c1fc86df9d: 4 components out of 450 total are non-finite

[PathTracer] Failed to add geometry for mesh 'pb_Mesh-30610'; mesh contains non-finite values.

Any ideas what's going on here? I tried to google these errors but nothing came up. The issue started for me on 2020.2.4f1 and continues on 2020.2.5f. I'm using the Universal Render Pipeline 10.3.1 with Pro Builder meshes (4.5.0). I'm running MacOS 11.2.1

Any help/leads on how to resolve this would be greatly appreciated!

 

I actually just found out what the problem was. I had some broken pro builder prefabs in my scene that needed to be updated after I had changed the material on it.

 

I'm getting the same thing now after trying to bake the lighting.

I suspected ProBuilder's causes problems in a different section in Unity and I've reached a point where I don't really need it anymore so I decided to completely remove it from my project.
That's actually helped my other issue but this "non-finite values" issue still persists.

After doing some testings I realize this issue disappear after unticking "Contribute Global Illumination" under Lighting in the MeshRenderer component as shown below.
Regardless of having a reflection\light probes in the scene.. whenever "Contribute Global Illumination" is ticked, I get those errors when trying to bake.

BTW That mesh was generated using Dreamteck's Splines 2 asset, baked and then saved as a unity asset file.
Then I composed a new prefab out of it and also using it as the mesh collider.

Edit: The issue still persists when simply dragging the asset file to the scene, so it's not related to it being a part of a prefab or a mesh collider.

 

On which version this issue is fixed? I'm using LTS

 

Cool thanks I'll upgrade to 2020.3.8 when it'll be released

 

Hey guys, I ran into this problem again on Unity 2020.3.8f1 and Pro Builder 5.0.3. I tried the "reimport all" option but that didn't help. Is there a way to search Unity to find what the problematic pro builder meshes are?

For example can I search for this geometry in the inspector?
"Line 215 in Verify - Geometry geom 412f49a43edc2d1fbb4385d3a9a33e00: Index 6 has value 8 that reads non-finite value inf in channel 4, element 0"

If not, how else can I debug this?
Thanks.

 

Hey thanks for getting back to me. I'm running Unity 2020.3.10f1 now and the issue still persists. I tried using both Progressive GPU and CPU. The only difference is that GPU only gives 1 error:
[PathTracer] Failed to add geometry for mesh 'pb_Mesh-459464'; mesh contains non-finite values.

It still fails however. All my other scenes bake just fine with CPU and use the same probuilder prefabs, so I'm really not sure why this one scene refuses to bake. Any tips/advice as to how I can debug this? If I have to manually inspect every probuilder object its going to be a nightmare, is there a way to isolate the ones that are causing the issue? Thanks.

 

Hi Pema,

Thanks for the script. However, I couldn't get it to work. After plugging in the name of the affected mesh on line 9 and trying to open the FindProblemMesh window I get this error:
NullReferenceException: Object reference not set to an instance of an object
FindMesh.FindProblemMesh () (at Assets/Scripts/Utils/FindMesh.cs:14)

Seems like its suggesting that the mesh name I gave it doesn't exist for some reason.

 

I'm getting this issue with a file imported from Sketchup when trying to bake lightmaps

"[PathTracer] Failed to add geometry for mesh 'Mesh StairStep'; mesh contains non-finite values."

Sometimes if I edit the mesh a little it will fix itself and other times not. Sometimes I change one mesh and then it says another mesh (which was previously not a problem) is now a problem.

Using progressive GPU and CPU in 2020.3.13 and 2020.3.14 (and 2020.3.12).


Edit: I may have fixed it by adding a different material in sketchup to the meshes which were having problems. I don't know why that would fix this but it's baking...

 

This is wrong though, it happens in 2021.1 and all 2021.2 betas

 

We have some users getting these errors on meshes made in Sabre CSG. 2020.3.14f1

"[PathTracer] Failed to add geometry for mesh "; mesh contains non-finite values."

Is there a bug report already started for this?

 

Any update on this?

 

2021.2.0b3 bakes fine. 0b4 doesnt, 0b5 didnt test yet, 0b6 will be testing very soon after it installs and let you know

 

It will completely halt the lightmap bake. It makes it seem like it's still going, but then it will bake forever. It will not go away until all faces of the mesh in question have a material/better UV(?).

Where can I file the report/Is there already a ticket open for this that I can add to? I can probably include a model that will trigger the error.

 

Okay I've reported it with a small project replicating it, issue: 1356776. The folder submission is recursive right?

 

Good to know! Still occurs in 2020.3.16f1 unfortunately.

 

Hi Pema-Malling,
Unfortunately the only solution that worked for me was restoring the project from a previous backup. The only thing that I can think of that seemed to cause the issue in the first place was updating pro builder to 4.5.0. I wish I had more info on what caused this problem. Hopefully you guys can get it resolved. Thanks!

 

Hello everyone,
I just got the exact same problem in Unity 2020.3.17f1 with ProBuilder 4.5.2.
After checking, I saw that ProBuilder was updated to 5.0.3. Should I try the updated version first, or just file a bug report @Pema-Malling ?

 

I submitted a bug report and project for it already that reproduces it 100%

 

I submitted mine now: Case 1365591

 

Hello, I had this issue too. The solution I found for my probuilder mesh (once I found which one threw the error) was to use the probuilder tool "UV Editor".
First, I selected all the faces of the mesh using "ctrl+a", and then I opened the uv editor. Next, in the actions panel I pressed the button "Reset UVs".
Finally, I just had to select the object again (in the editor) and use the probuilder tool "Lightmap UVs" to re-generate the UV2 (I guess?). Then, the ligthmap baked without any errors.

 

I had this issue in Unity 2019.4.31f1, after updating probuilder to current version, I have sent off a bug report: IN-7501

@Pema-Malling I tried your code to find the object the mesh was part of but nothing happened when I clicked "Find porblem mesh"