<p>Still don't have an actual answer as to why repairing the stl file didn't seem to work, but since my stl file was a combination of different stl files I tried repairing the individual stl files before combining them, which resolved the problem.</p>

CC BY-SA 4.0
2021-12-03T22:56:18.620Z
Are you printing multiple parts? Try selecting all, merge then slice.
Guest
CC BY-SA 4.0
2023-06-18T02:21:07.337Z
commenting to confirm that Selecting all then merging made it work to slice my stuff. I was adding generic cylinder to make a small ad-hoc support on my model
Frankenmint
CC BY-SA 4.0
2021-04-13T14:36:36.337Z
2021-04-13T14:36:36.337Z
Brent
<p>I tried to slice an stl file using the PrusaSlicer console and I got the <code>No layers were detected. You might want to repair your STL file(s) or check their size or thickness and retry.</code> message. I tried repairing the model with 3 different services and I still get the same error. When I load the fixed stl file into the PrusaSlicer gui, it doesn't say that the model is broken. How can the console and gui give 2 different results and how can I fix this?</p>
<p>Here's an image of the model being loaded into the gui version. It states that the model is broken but was automatically fixed.<br />
<a href="https://i.sstatic.net/264HH.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/264HH.jpg" alt="broken model" /></a><br />
Then I manually fixed the model using Netfabb and the model is no longer broken according to the gui version.<br />
<a href="https://i.sstatic.net/I2Cp3.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/I2Cp3.png" alt="fixed model" /></a><br />
Yet when I try to slice the repaired model using the console, it fails again.
<a href="https://i.sstatic.net/oDzi8.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/oDzi8.png" alt="error message" /></a></p>
<p>PrusaSlicer version is 2.3.0 on Windows 10.<br />
You can find the stl and repaired stl <a href="http://sendanywhe.re/I78RT83D" rel="nofollow noreferrer">here</a>.</p>

CC BY-SA 4.0
2021-04-06T16:30:57.677Z
Cura says, those files are perfectly fine..
Trish
CC BY-SA 4.0
2021-04-06T16:59:16.103Z
Yes I know that the files are fine, I don't get why the console slicer is still producing that error.
Brent
CC BY-SA 4.0
2021-04-06T19:26:19.587Z
degenerate faces are faces that do have no surface area... maybe internal geometry?
Trish
<stl><prusaslicer>
Still getting "no layers detected" after repairing model in PrusaSlicer console
Brent
# Still getting "no layers detected" after repairing model in PrusaSlicer console

(Asked by: username_0 on 2021-04-06)

I tried to slice an stl file using the PrusaSlicer console and I got the `No layers were detected. You might want to repair your STL file(s) or check their size or thickness and retry.` message. I tried repairing the model with 3 different services and I still get the same error. When I load the fixed stl file into the PrusaSlicer gui, it doesn't say that the model is broken. How can the console and gui give 2 different results and how can I fix this?

Here's an image of the model being loaded into the gui version. It states that the model is broken but was automatically fixed.  
[![broken model](https://i.sstatic.net/264HH.jpg)](https://i.sstatic.net/264HH.jpg)  
Then I manually fixed the model using Netfabb and the model is no longer broken according to the gui version.  
[![fixed model](https://i.sstatic.net/I2Cp3.png)](https://i.sstatic.net/I2Cp3.png)  
Yet when I try to slice the repaired model using the console, it fails again.
[![error message](https://i.sstatic.net/oDzi8.png)](https://i.sstatic.net/oDzi8.png)

PrusaSlicer version is 2.3.0 on Windows 10.  
You can find the stl and repaired stl [here](http://sendanywhe.re/I78RT83D).

**Tags:** stl, prusaslicer

> **Comments:**
> **username_1**: Cura says, those files are perfectly fine..  
> **username_0**: Yes I know that the files are fine, I don't get why the console slicer is still producing that error.  
> **username_1**: degenerate faces are faces that do have no surface area... maybe internal geometry?  

---

## 1 answers

### Answer by username_0 on 2021-04-13. Score: 2

Still don't have an actual answer as to why repairing the stl file didn't seem to work, but since my stl file was a combination of different stl files I tried repairing the individual stl files before combining them, which resolved the problem.

> **Comments:**
> **username_2**: Are you printing multiple parts? Try selecting all, merge then slice.  
> **username_3**: commenting to confirm that Selecting all then merging made it work to slice my stuff. I was adding generic cylinder to make a small ad-hoc support on my model  

---

