> For the complete documentation index, see [llms.txt](https://wiki.polymaker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.polymaker.com/polymaker-wiki/polymaker-wiki-zh/ji-chu-zhi-shi/fun-3d-printing-facts/over-extrusion-vs.-under-extrusion.md).

# 过度挤出与欠挤出

3D 打印中的过挤出通常比欠挤出更容易用肉眼发现。当挤出的耗材过多时，你常常会看到明显的迹象，比如鼓包、拉丝，或层过厚，仿佛耗材溢出或渗出到了预期边界之外。这些视觉线索——例如表面线条之间隆起的棱脊，或因材料过多而下垂的层——使过挤出相对容易识别。打印件表面可能看起来凌乱或尺寸偏大，这表明打印机推出的材料比所需的更多。

相比之下，欠挤出在视觉上可能不那么明显，但对打印强度的影响往往更严重。即使欠挤出的部件表面看起来还算可以，缺失或过薄的耗材沉积也意味着各层没有完全粘结，内部结构可能会很脆弱。这会导致打印件在受力时更容易碎裂、开裂或撕裂，因为耗材不足会削弱物体的机械完整性。层与层之间的缝隙或稀疏的填充并不总是能立刻被发现，但它们会显著削弱部件。因此，虽然欠挤出可能比过挤出更难一眼看出，但它对最终打印件的耐久性和功能性带来更大的风险。要避免这些隐藏的弱点，需要认真细致地监控打印质量。

这意味着仅靠目视检查可能不足以发现欠挤出，因此校准和仔细调试对于获得坚固、可靠的 3D 打印件至关重要。过挤出错误会从视觉上提醒你出现了问题，而欠挤出则可能在一开始看起来没问题的情况下，悄悄降低部件质量。

{% embed url="<https://www.youtube.com/shorts/tQy3ZthpDBA>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.polymaker.com/polymaker-wiki/polymaker-wiki-zh/ji-chu-zhi-shi/fun-3d-printing-facts/over-extrusion-vs.-under-extrusion.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.