![]() ![]() obj export capability - which I have used and it works quite well. It also tends to group the object structure by material or object, so your OBJ can end up as a single mesh entity. ![]() I've used SimLab Composer as well and that too is very good (SimLab used to provide the file translators for Keyshot), but sometimes it messes around with object scale and action centres, making subsequent reuse a bit tricky. At SolidWorks World Luxology showed a CAD importer that converts the CAD data directly to 4 sided polygons - which makes downstream editing much easier.įor working with SolidWorks, Modo is a good option for conversion to. In reality most systems don't do that, but apply a course mesh conversion across the whole part. Ideally a file importer will convert the NURBS data to a mesh intelligently - so on small tight radii, a few faces, on a large smooth surface, lots of faces. This creates all sorts of issues in the render or animation app. For example, many direct native file SolidWorks file importers use the display mesh saved with the SolidWorks file - which is just a pile of triangular faces. The problem with exporting from SolidWorks (or any CAD system) is that the resultant mesh file will be based on triangles. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |