Roofer & ScanPatch
Hey, I’ve been working on a 3D scan of a roof and the mesh keeps getting all tangled up. Do you have any tricks for keeping topology clean while still getting a solid, functional build?
Keep it simple. Start with a good edge‑loop grid, build the main shape with quads, then add detail. Don’t let extra edge loops pop out where they don’t belong – that’s what makes the mesh tangled. If you need a ridge or a vent, cut a clean loop first, then sweep the faces out. Always check for non‑manifold edges or overlapping vertices; a quick merge by distance can fix a lot. When you finish the base, use a cleanup tool to remove stray polygons, and do a quick test render to catch any bad topology before you lock it in. That way you get a solid, functional roof without all the mess.
That’s solid, but remember to keep the edge‑loop density uniform—if one area is twice as dense it’ll pull the topology down. Also, always lock the outliner before you start sweeping; a stray vertex in the wrong layer can cause non‑manifold edges that pop up only after you bake the modifiers. A quick check in the edit mode: enable “Non‑Manifold” and “Limited Dissolve” to catch issues early. Then, when you merge by distance, set the tolerance to the smallest pixel size you need—anything larger and you’ll lose that fine detail you’re trying to preserve. Keep those UVs straight, and the mesh will stay clean and ready for a smooth bake.
Got it. Keep the edge loops even, lock the outliner, check for non‑manifold and use limited dissolve. When you merge, pick the tightest tolerance that still keeps the detail. Straighten those UVs and you’ll have a clean mesh ready for a smooth bake.
Sounds like you’ve got the workflow down. Just remember to always double‑check the normals after a merge—if any flip, the bake will look like a bad scan. And keep a folder of the old versions just in case you need to roll back a tweak. Happy cleaning!
You’re right, normals can ruin a bake if they flip. I’ll keep a backup folder of every version and double‑check them after every merge. Thanks for the reminder.