"Model contains non-textured triangles" error
Another day, another challenge :)
I was trying to fix some holes in my model using Meshmixer for re-import and re-texturing.
Process as follows:
- Export model from RC
- Import into Meshmixer
- Add a primitive surface over the surface of the model with holes
- Do a boolean combine
- Export as .obj
- Import into RC (with the properly renamed .rcinfo file)
- Error
Not an expert in Meshmixer, so maybe the process is not correct.
Any thoughts or suggestions would be greatly appreciated.
-
Hi Tim,
my guess is that you exported a textured mesh, is that so?
If yes, and you try to import the new one under the old name, then I guess RC complains because there is a different geometry in the mesh and the UV.
If you import it with a different name, then RC won't look for an UV. You only need to tell RC if the coordinates relate to grid or world during import, which usually works just fine...
-
Hey Gotz,
The re-import was under a different name. However, the old .rcinfo file was used and renamed same as the new file. Standard procedure I've followed before.
After some trial and (mostly) error, I think the problem was with how Meshmixer exports components/shells. It appears "boolean join" doesn't actually combine the individual meshes, which may be the problem, but not positive about that.
However, if the meshes/shells have "combine" and "make solid" operations performed on them, then the export seems fine, but Meshmixer does some optimization on the final mesh that often changes the shape drastically.
Still working through that. Will report any useful findings.
-
Hi
i'm having the same problem when i import an OBJ from maya, no matter the name of the files. i have tried with and without the rcinfo file, same result
i have also tried with a texture file linked to the mtl, still not working
i have tried with the obj converted in FBX and it make RC crash instantlyhow can i make it work please ?
best
-
maybe try exporting/importing single pieces of geo to trace which part of your model the error is coming from? I mesh>combine everything in Maya before exporting since my model is usually made up of many separate parts. I came across this error and traced it back to a simple piece of geo that had messed up uv's (I had been transferring uv attributes between meshes that I guess weren't exactly identical). just had to re-UV that part and it imported fine
Please sign in to leave a comment.
Comments
4 comments