I managed to get full resolution importing to work on a different computer. Is there a setting somewhere I need to change? Both computers have the same ram, GPU and CPU are comparable. Is SOlidworks performing some behind-the-scenes hardware check that there isn't a manual override for?
If you are using Scan to 3D ( I don't have it in my license) there is a setting or option that controls decimation.
Thanks for the response Chris,
Unfortunately that isn't the problem. I'm not using that feature. I'm going to open, select STL as file type, hit options, make sure solid body is checked. and then clicking open which imports the STL as a solid body.
If you are not using Scan to 3D, then there is no way SolidWorks can decimate the mesh. What could be happening, (and I'm speculating here) is that your mesh may contain surfaces and solids and imports differently based on whether the Solid Body or Surface Body option is chosen.
Can you post the mesh?
A SolidBody is limited to about 15,000 triangles. A Surface Body allows for more triangles, but its still a relatively small number, I have not tested the limit, but I believe it is under 100,000 triangles.
I cannot upload the mesh in question. It contains patient-identifiable information.
I think the problem might lie in how this scan was segmented from MRI data in comparison to the others. Surface and solid bodies lead to the same result: a surface body import with almost no triangles.
I'm testing other meshes right now from different scans - I'm getting away with about 40k triangles before Solidworks craps out on me on every other mesh I have on hand.
Just to note: I first bring the mesh into Meshlab. There I do the following:
Decimate to 25k to 30k faces depending on my computer hardware.
Remove all non-manifold vertices
Remove all non-manifold edges
Delete all self-intersecting faces
Fill all holes
Double check that none of the steps interfered with the results of previous steps.
Export to STL
Import as solid body to solidworks.
This pipeline has been working for me for every mesh I've thrown at since I began working with medical scans about a year ago. The fact that its failing now, for this single geometry, leads me to believe that the mesh might be inherently dirty to the extent that my established pipeline won't work on it.
That's interesting about scan to 3D. From what you're saying, I can essentially do a lot of the pre-processing there instead of in Meshlab. I'll have to take a look at that.
Actually, Scan to 3D does not have any functions to repair meshes, it can sample/decimate only. The purpose of Scan to 3D is to build SolidWorks surfaces from meshes rather than edit/repair meshes. As your data has organic forms, its usefulness may be limited.