Hacker News Reader

Comment by calini | Hacker News Reader

I'm going to 3D print so much dumb stuff with this.

They're still hesitant to show the untextured version of the models so I would assume it's like previous efforts where most of the detail is in the textures, and the model itself, the part you would 3D print, isn't so impressive.

I was going to comment on the same; these 3d reconstructions often generate a mess of a topology, and this post does not show any of the mesh triangulations, so I assume they're still not good. Arguably, the meshes are bad even for rendering.

Presumably, these meshes can be cleaned up using standard mesh refinement algorithms, like those found in MeshLab: https://www.meshlab.net/#features

Hopefully that's in the (near) future, but as of now there still exists 'retopo' in 3D work for a reason. Just like roto and similar menial tasks. We're getting there with automation though.

You can download a .glb file (from the HuggingFace demo page) and open it locally (e.g. in MS 3D Viewer). I'm looking at a mesh from one of the better examples I tried and it's actually pretty good...

You know I do wonder about this. If its just for static assets does it really matter? In something like Unreal, the textures are going to be virtualized and the geometry is going to be turned in to LODed triangle soup anyway.

Has anyone tried to build an Unreal scene with these generated meshes?

Usually the problem is the model itself is severely lacking in detail, sure Nanite could make light work of a poorly optimized model but it's not going to fix the model being a vague blob which doesn't hold up to close scrutiny.

Generate the accompanying normal map and then just tesselate it?

So don't use them in a context where they require close scrutiny?

hueforge

Reply on news.ycombinator.com