the shrouds r definitely different, one is left and one is right so the tabs r on opposite sides. The stems r probably identical, just flipped over.
what r u using to compare them?
Yes you are correct I can see the models in SU 2015 and and its entity vol. report is what I used to compare the volumes I noted above. You can use the model info statistics to get info on edges and faces.
I posted info on solid model above. Did you confirm it is solid and reduced polys?
The STL models you are using should raise red flags to you. It does not mean they are bad but where made for different use than what one would want for SU.
I do not think you have stated what the ultimate use is , but when you download models make sure you have a clean model to start with because it will save you lots of grief.
Hello @ruggb In the future, it may be easier to upload your model into 3D Warehouse and then share the link. Then people can download it and poke around much easier.
1 Like
Ruggb:
I used the stl files you posted, did not open in SU, but used netfabb free version issued by Shapeway and the results is the file is reported as solid by that approach 
Hi, I haven’t opened the files, however, I believe I don’t need to as I have been having this same issue for ages (years). I have written to the my vendor support and anyone else I could without any significant “solution”. I believe it is due to lots of small geometry. I usually get this issue when I scale up components(s)/groups and intersect them. So what I do is take a copy of the component, scale it up by 1000 (this makes working in decimal or metric easier as you can still fudge length intuitively), make my intersections and changes and then delete the upsized component. Then on the original resultant Asmaller component, I explode it and make it a component again. This usually fixes the issue about 90-95% of the time (not 100%).
Alex
1 Like
alexkara;
Glad it works for you.
FYI
Here is quote form Wikipedia :" An STL file describes a raw unstructured triangulated surface by the unit normal and vertices (ordered by the right-hand rule) of the triangles using a three-dimensional Cartesian coordinate system. STL coordinates must be positive numbers, there is no scale information, and the units are arbitrary"
The stl files I noted above I opened in Netfabb without going thru SU, with out any scaling etc. and it opened ok and showed as solid.In Netfabb that is.
NetFabb is from Shapeway, the free version of the same program they use to support their 3d printing business. I downloaded after arggub told author about problem so they may have made changes =>. version control? In the program (NetFabb)they have set the units to mm. I have not tried to open in SU, but if you watch the stauts on left corner there some apparent extensive processing going on to load in SU.
Sounds like you are doing things correct except scaling by 1000 may not be enough, depends on the model?
Yes, my assumption is that the files r OK as dnld but must be imported into SU @x1000 (meters). I think the whole issue of SU breaking the model after that had to do with the particular file I was dnldg as the other copy of the same file did not give that problem. However, both indicated OK when I tested them with 2 diff plugins. Just another ghost I guess…at least the ghosting file has been removed.
thx for your help
Generally speaking .stl files are great for exporting from sketch for 3d printing etc but are not great for importing into sketchup.
You can draw something in SU, export as .stl and print beautifully. But import the same .stl file back onto SU and you will often find problems with it.
I’m replying to an older thread here as it directly pertains to my issue. I have a model that I have created for 3D printing, but which was not imported as an STL - everything in the model was created in SketchUp using normal tools. The model was created at mm dimensions and then scaled up to meters when I ran into problems creating small details (an insane limitation in this day and age but whatever). The interior front face of this model was created as an intersection between a curved face and pushed geometry. I ran an intersect faces and removed the leftover bits to create holes through the curved geometry.
The component shows solid, exports as an STL without problem, and prints as expected. However, since performing the intersection on the curved face I am now prompted to “Fix” my model every time I save. If I say “fix”, the model is irrevocably broken. Several faces and edges are removed and endpoints that used to connect no longer line up.
This is pretty frustrating as I’m stuck with this prompt now every time I save the model, and if I ever accidentally click two of the 3 buttons presented to me, SketchUp trashes the model rendering it unsolid.
I must have done something goofy here but I can’t figure out what steps to avoid in the future. Download link for the model in question: http://svideo.org/ExampleModel.skp
This behavior persists in SketchUp 2018 - When modelling for 3D print, not importing STLs, I still occasionally run into a situation (usually after using the solid modeling tools) where SketchUp insists upon “fixing” my model, only to irrevocably mangle the geometry. Objects that were solid and exporting fine become unsolid and full of surface borders and misaligned vertices.
Is this ever going to be addressed?
Well @Allen, whatever input/insight we can offer on when SU wants to ‘fix’ something will depend on your model. Someone will need to examine the file before anyone can offer any advice. Upload a problem file here via the Upload button, or drag a file into the message box.
It’s the same model as before which is still linked in the post directly above the one you’ve replied to, but I’ve experienced this behavior several times on several models. The common thread appears to be solid object operations against curved surfaces.
I can’t tell what causes these errors, but your model looks good. So, the problem must be elsewhere in the file.
Try this, don’t let SU fix the model, instead, right click on the object and save as (a new file).
The clutter of makerbot components in the file may be a factor, I don’t know. It’s good practice to keep the model as clean as possible from the start.
Shep
1 Like
Holy cow - THAT WORKS! Thanks man, this has been driving me nuts for ages.
Sadly those come with the default “3D Printing” templates included w/ SU.
Due to the size of the model, it’s obvious you tried to accommodate SU’s working size range for modeling operations by scaling up the model - it’s larger than what you will print. BUT it may not have been large enough for the intersection operation you did with the Solid tools.
Next time this occurs, try Scaling up even more so any resulting compound curve edges would be longer than 3/16". If zoom in close enough to see the gap and draw in the missing edges, all the faces will appear.
The fix dialog gave a report saying there was an issue enclosing the face with the small geometry.
Results of Validity Check.
The start and end vertices are identical for CEdge (51622)
Entity CEdge (51622) should be erased - done
The start and end vertices are identical for CEdge (51497)
Entity CEdge (51497) should be erased - done
The start and end vertices are identical for CEdge (51662)
Entity CEdge (51662) should be erased - done
The start and end vertices are identical for CEdge (51683)
Entity CEdge (51683) should be erased - done
The start and end vertices are identical for CEdge (51668)
Entity CEdge (51668) should be erased - done
The start and end vertices are identical for CEdge (51647)
Entity CEdge (51647) should be erased - done
Edges are not connected in CLoop (51492) for CFace (51491)
Loop 0 of CFace (51491) is an invalid outer loop
Entity CFace (51491) should be erased - done
Edges are not connected in CLoop (51617) for CFace (51616)
Loop 0 of CFace (51616) is an invalid outer loop
Entity CFace (51616) should be erased - done
Edges are not connected in CLoop (51638) for CFace (51637)
Loop 0 of CFace (51637) is an invalid outer loop
Entity CFace (51637) should be erased - done
Edges are not connected in CLoop (52034) for CFace (52033)
Loop 0 of CFace (52033) is an invalid outer loop
Entity CFace (52033) should be erased - done
Edges are not connected in CLoop (52072) for CFace (52071)
Loop 0 of CFace (52071) is an invalid outer loop
Entity CFace (52071) should be erased - done
Edges are not connected in CLoop (52207) for CFace (52206)
Loop 0 of CFace (52206) is an invalid outer loop
Entity CFace (52206) should be erased - done
Edges are not connected in CLoop (52261) for CFace (52260)
Loop 0 of CFace (52260) is an invalid outer loop
Entity CFace (52260) should be erased - done
3 Likes