Glitched lightmaps after long bake (some objects, sometimes)
Although I can easily find many topics about lightmap problems, I couldn't find anything related to this.
This is what I find this morning after a 5 hour long bake in production quality (100 bounces, scale 1, quality 6, smooth 0.9 - no .ini tweak). But yesterday I did 4-5 total bakes in preview/medium quality and this doesn't happen.
As the tittle says, sometimes, some object(s) will be glitched like this (not in all bakes), and I don't know why, while the UV unwrap is not ideal, it's not overlapping and has worked before, many times (Let's say I've baked that same object more than 40 times and it's the first time it shows up like this).
I had a situation where I had one object that would always get glitched like this, even though the unwrap seemed fine, it wasn't and I had to change and reimport the asset.
If I bake the whole scene again (which I will), probably this will disappear, this is somewhat annoying in preview/medium builds, but when it gets to production... it's never finished until I get it right.
Could someone help me understand what is happening here and how can I avoid it?
Thank you in advance! - John
PC Specs: - i7-5960X @3.00GHz - 64GB Ram - GTX1080 - Win 10
About the project: This is a big Arch viz scene with several apartments each with its unique decoration items (2 at this stage), the walls and floors are made with simple geometry but the scene has many objects with higher polycount than what it should be. I'm being very conservative with the sizes of lightmaps only with the largest floors/walls/ceilings having 1024 resolution, everything else 512 and under. Original geometry for apartments came from a BIM file, a careful cleanup was necessary but it was mostly focused on the interior walls and so on.
asked Apr 11 '17 at 08:53 AM in Rendering
So your project and its associated contents seems pretty far into its development, so reproducing this in order to determine what could be happening on my end is going to be difficult. What I can do is provide you with the resources to figure out how to resolve your issue.
Aside from this guide, you will need to simply use the tools we have built in to visualize and debug what could be causing this issue.
answered Apr 19 '17 at 05:43 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here