Try replacing the spaces with _underscores_ or format your naming inCamelCase. Now I think the reason your material to obj link is broken is because of the spacing in your file naming. More photos which are as sharp as possible and with a higher resolution and studio lighting would improve the surface reconstruction. The reason your model is a bit blobby is that the surface properties of your subject are relatively feature poor, not providing a lot of information to Zephyr to reconstruct with, which requires you to work harder to get compatible results to reality. Hey Shopgeezer, in Zephyr you don't have the 3D light turned on, you're only seeing the flat un-illuminated texture map - To see the actual 3D geometry in Zephyr you need to click on the lightbulb icon in the tool-bar. So why did the presenter's mesh in the video look fine in MeshLab, and my mesh file looks like a pile of whipped cream? What are the materials definitions that MeshLab is looking for? Is this a problem in the export function in Zephyr? I followed all the options that the presenter in the video used. All of it seems to be the "white material". My object in MeshLab looks like a blob of clay. A default white material is used where no material was available". " Some materials definitions were not found. obj file but when I opened it in MeshLab I got the following error: His mesh in MeshLab looks just like it did in Zephyr, same colours, textures etc. In the video the presenter then exports the mesh as a. I managed to get a good looking textured mesh made in Zephyr. I did exactly what the presenter did in the video. I followed the online Workflow tutorial video as I created my own mesh. I took 50 photos of my subject, 43 of which were accepted by Zephyr.
0 kommentar(er)
