No layers detected when slicing through console ?
Hi,
I have been trying to slice a model through the command line. Its works fine with a clean STL.
Bbut I have to generate an STL file that typically needs repair before slicing. Once repaired through Netfabb or other software, the PrusaSlicer GUI 2.3.3 does not detect any errors in the STL and can slice the model correctly with my configuration file.
However, when slicing the repaired STL through the command line, I get the following error message. I have tried many different repair operations and software, the STL file seems clean yet the slicing keeps failing.
What configuration parameters could I tweak to make it work ?
Or what else should I check in my stl file that could prevent a proper slicing ?
I also tried converting to other file formats that are more robust (amf, 3mf...) but to no avail...
Error message :
[2021-11-01 13:43:49.174969] [0x000056d8] [debug] TriangleMesh::repair() started
[2021-11-01 13:43:49.272933] [0x000056d8] [debug] TriangleMesh::repair() finished
[2021-11-01 13:43:49.273933] [0x000056d8] [trace] TriangleMeshSlicer::require_shared_vertices - start
[2021-11-01 13:43:49.274933] [0x000056d8] [trace] TriangleMeshSlicer::require_shared_vertices - stl_generate_shared_vertices
[2021-11-01 13:43:49.281954] [0x000056d8] [trace] TriangleMeshSlicer::require_shared_vertices - end
[2021-11-01 13:43:49.438969] [0x000056d8] [debug] TriangleMesh::repair() started
[2021-11-01 13:43:49.442956] [0x000056d8] [debug] TriangleMesh::repair() finished
[2021-11-01 13:43:49.442956] [0x000056d8] [trace] TriangleMeshSlicer::require_shared_vertices - start
[2021-11-01 13:43:49.442956] [0x000056d8] [trace] TriangleMeshSlicer::require_shared_vertices - stl_generate_shared_vertices
[2021-11-01 13:43:49.443931] [0x000056d8] [trace] TriangleMeshSlicer::require_shared_vertices - end
[2021-11-01 13:43:49.466933] [0x000056d8] [info] Staring the slicing process. WorkingSet: 58MB; PrivateBytes: 48MB; Pagefile(peak): 48MB(77MB)
10=> Processing triangulated mesh
[2021-11-01 13:43:49.467934] [0x000056d8] [info] Slicing objects... WorkingSet: 58MB; PrivateBytes: 48MB; Pagefile(peak): 48MB(77MB)
[2021-11-01 13:43:49.468933] [0x000056d8] [debug] Slicing objects - region 0
[2021-11-01 13:43:49.581967] [0x000056d8] [trace] TriangleMeshSlicer::require_shared_vertices - start
[2021-11-01 13:43:49.581967] [0x000056d8] [trace] TriangleMeshSlicer::require_shared_vertices - end
[2021-11-01 13:43:49.630968] [0x000056d8] [debug] TriangleMeshSlicer::slice
[2021-11-01 13:43:49.630968] [0x000056d8] [debug] TriangleMeshSlicer::_slice_do
[2021-11-01 13:43:49.633933] [0x000056d8] [debug] TriangleMeshSlicer::_make_loops_do
[2021-11-01 13:43:49.633933] [0x000056d8] [debug] TriangleMeshSlicer::slice finished
[2021-11-01 13:43:49.634933] [0x000056d8] [debug] TriangleMeshSlicer::make_expolygons in parallel - start
[2021-11-01 13:43:49.635932] [0x000056d8] [debug] TriangleMeshSlicer::make_expolygons in parallel - end
[2021-11-01 13:43:49.637957] [0x000056d8] [debug] Slicing objects - append slices 0 start
[2021-11-01 13:43:49.637957] [0x000056d8] [debug] Slicing objects - append slices 0 end
[2021-11-01 13:43:49.638932] [0x000056d8] [debug] Slicing objects - removing top empty layers
[2021-11-01 13:43:49.638932] [0x000056d8] [debug] Slicing objects - make_slices in parallel - begin
[2021-11-01 13:43:49.638932] [0x000056d8] [debug] Slicing objects - make_slices in parallel - end
[2021-11-01 13:43:49.639933] [0x000056d8] [debug] Slicing objects - fixing slicing errors in parallel - begin
[2021-11-01 13:43:49.639933] [0x000056d8] [debug] Slicing objects - fixing slicing errors in parallel - end
No layers were detected. You might want to repair your STL file(s) or check their size or thickness and retry.
No layers detected...
Additional note :
When converting STL to AMF from the GUI (not the console), the slicing works (see https://github.com/prusa3d/PrusaSlicer/issues/5029)
However I need the process to be automated so it's not a good solution as it does not work when exporting to AMF from the console, but this could point towards the source of the problem..?