Prusa Slicer Mesh Problem (transparent edge(
When I slice with PRUSA slicer, there are some gaps on the edge:
here ist the Prusa-File:VertexProblem.3mf
this is the detail-view from the front:
other slicer has no problem with the stl-file:
I tried to "repair"
I tried to "make solid" in meshmixer
I checked the directions of the verticies -> no changes in PRUSA slicer:
Is this a known problem?
Thx for hints - Carsten
RE: Prusa Slicer Mesh Problem (transparent edge(
I posted over on your github issue but when i opened it i saw the same problem, but after using the fix through netfabb option thats available to slicer on windows 10 machines it does slice properly.
There's definitely something wrong with the model or netfabb wouldn't have made a difference but the fact that slicer isn't even showing any issues with it is a big problem.
RE: Prusa Slicer Mesh Problem (transparent edge(
Yes, a big problem. In my CAD the model is watertight, no open edges, non-manifold and the face directions are also ok.
Maybe there is a precision, acuracy, tolerance (i am working with 0.001mm) problem in PRUSA slicer.
RE: Prusa Slicer Mesh Problem (transparent edge(
The Blender 3DPrint toolbox shows 480 non-manifold edges. I assume this happened during export.
Windows 3D Builder (also Netfabb service) could repair it easily.
RE: Prusa Slicer Mesh Problem (transparent edge)
I have seen the problems in STL-File.
I tried to repair STL-File with Prusa slicer into an obj.File. That does not work. I am working on a mac. Does anybody knows a tool for my Mac?
RE: Prusa Slicer Mesh Problem (transparent edge(
RE: Prusa Slicer Mesh Problem (transparent edge)
@ lichtjaeger:
this solves my problem!
But not the Prusa slicer's:
a) why the error was not displayed in Prusa slicer?
b) and why does the Prusa slicer function "repair STL file" does not work?
I hope this thread is read by an admin, who will post it into the developers "corner".
- Carsten
RE: Prusa Slicer Mesh Problem (transparent edge(
There are a few near zero issues in P.Slicer where some cad tools like to use non-zero numbers for zero. Depending on the math library you may or may not see an error (division by zero when a number exceeds the library range, for example). You might try setting resolution in P.Slicer, see if that will 'catch' the errors.
All said and done, I've seen MeshMixer miss issues that NetFabb catches and fixes, too. So this isn't unique to Prusa.