We are rebuilding a complex interior environment, with a combination of around 2000 RAW Images (Canon 5D MK4) and 8 laser scans (Faro Focus). Alignment and high quality reconstruction works well, very good percentage of photos and all scans aligned. The problem is as follows;
After unwrapping, texturing works really well on a small section of the captured area (app. 5 m2) but the same settings when texturing a larger area (200m2) produces blurry textures (i.e labels that could be read easily in the small area, cannot be determined in the large reconstruction region). Any advice on what we might do differently to maintain the quality level of the smaller reconstruction area?
If you add a distance between 2 control points it will make it easier to understand the texel sizing. The .000705 meter per texel is .705MM per pixel or “texel”. That isn’t meaningful if you have not defined a measurement in the software.
Sounds like a misalignment. I bet that for the small area the problematic images were not used, probably because they were less suitable. But for the larger area, they became neccessary and then messed up the result. How does the area look in the mesh? Is it slightly bumpy or rough?
Thanks for your fast replies Steven and Götz, I’ll try today with the measured control points and see how that goes. Here’s some more details and screenshots of the scene. Same data set with two reconstruction areas; the small section, and the a larger defined reconstruction area.
Large Area - Low Texture Quality
Small Area - Good Texture Quality
Large Area - Mesh Quality
Small Area - Mesh Quality
Large Area - Mesh Close Up
Small Area - Mesh Close Up
Maybe these screen shots will shed some more light on the issue. I will update soon with results from adding measured control points.
Hey Götz,
Yep you’re spot on. Turns out it is purely just a display issue; exported the mesh and textures of the large reconstruction region and visualised in Unity. Texture quality was great, on par with the display quality of the smaller area in RC. Any ideas on what might cause this? Something to do with our configured settings/hardware (see below)? Or just a bug?
