#And baking lights on this setting took
minor zinc
FFS!
First - Way to high Resolution for Terrain!
You have 3GB of Lightmaps, thats horrible 😄
Can you show me how the lightmap looks in the Editor Debug VIew?
minor zinc
As you can see there, something is wrong with your Lightmap UV i think. You can see the MASSIVE pixels there.
Did the merging of your mesh create a new mesh in the project folder?
minor zinc
And how did you calculate 3GB of resolution?
you have 1206 files of 1024x1024 pixels
karmic horizon
you have 1206 files of 1024x1024 pixels
👀 👀 👀 👀 oh
karmic horizon
As you can see there, something is wrong with your Lightmap UV i think. You can ...
Let me check
No it doesn't look like it
But the massive pixels must mean UV unwrapping problem
minor zinc
Yep. Thats why i ask.
karmic horizon
Anyway I can fix this in Unity? Or I have to take this to blender?
minor zinc
If you klick on the Mesh in the MeshFilter of your merged Terrain, is this linked to the a mesh in the project folder?
Like here?
minor zinc
Hmm.
How does the Lightmap look like, if you click the stones there and open the lightmap?
You can open the preview t here and have a look on it
Im away for a while now.
What i would suggest is:
- For the first bakes, reduce the resolution from 60 to something like 5. (speeds up bake time)
- Test your lightmap on just your merged stones (disable the rest of the scene)
- Check if the Lightmap UVs are correct (i dont think so)
- You could fix this in unity, but it seams the merge didnt create a new mesh. So it may be possible, that you have to export this into blender and create a Lightmap UV for the stones.
- Or maybe your merge tool has a setting to create UVs on its own.
If you didnt get a good result in an hour, im back 😄
karmic horizon
Hmm.
How does the Lightmap look like, if you click the stones there and open th...
I'll try everything else ❤️❤️
minor zinc
You can open the preview there and check for possible issues (like overlapping uvs) I guess after your merge the UVs of your stones, the UVs are overlapping there
karmic horizon
They actually aren't 👀
It actually looks like a good UV
I'm considering deleting the merged objects and using unmerged. Because the purpose of merging is to reduce Draw calls. And it's not even reducing it that much. The merged meshes are like huge cliffs, how much are they going to reduce, 10-15 draw calls?
alpine trail
I'm considering deleting the merged objects and using unmerged. Because the purp...
Which render pipeline are you using?
karmic horizon
None so I guess URP
Know this please, I didn't make this project. I'm actually just joining
alpine trail
None would mean built-in render pipeline
karmic horizon
So I'm checking most of the things as you guys ask
karmic horizon
None would mean built-in render pipeline
Yes
alpine trail
Did you check UV overlap and texel validity using these debug views
karmic horizon
Uh, nope. I don't know what that is
alpine trail
Uh, nope. I don't know what that is
Can you see those options in the dropdown
alpine trail
Kinda bad but way less worse than I expected
What about texel validity
alpine trail
That explains the blocky artefacts we see
karmic horizon
The awkward lights?
alpine trail
Yes
The red parts are surfaces that are exposed to geometry backfaces, which leads to light ray termination during baking
karmic horizon
Meaning the faces are facing the wrong direction?
alpine trail
That, or maybe more likely they are facing faces that are facing in the wrong direction to be specific
karmic horizon
Yes that's exactly what it looks like
Thanks so much man/miss/bro/sis
I think with all these issues, might as well use unmerged objects. Might as well use the unmerged objects. Merging is creating more problems then helping.
alpine trail
You may have multiple rocks overlapping there
For example if some nonmerged rocks remain after merging
karmic horizon
No, there aren't any other rocks.
alpine trail
Anyhow I don't recall how exactly draw calls work in BiRP but if your cliffs are set as Batching Static then I'd assume they're merged into one draw call automatically anyway
karmic horizon
Yeah so might as well use the objects with good UVs, this method is looking like a hassle for the value it's providing
Thanks alot! Really helped
alpine trail
As suggested earlier it's best to use a low resolution values when doing non-final bakes (but not low max resolution)
But when lowering resolution do check what the minimum lightmap resolution is as defined in mesh lightmap UV generation settings