> 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/da-yin-ji-qiao/hou-chu-li/shang-se.md).

# 上色

### **3D打印件底漆涂装**

为了给打印件上漆，先使用哑光灰色底漆或底漆填充剂。确保零件已完全组装、打磨平滑且无杂物。使用压缩空气或强力吹风机清除残留灰尘。

**涂装流程**:

1. **环境**：在通风良好的室外区域或带防护篷布的喷漆房内作业。
2. **喷涂技巧**：从……处喷涂一层轻薄、均匀的涂层 **距离6–12英寸** 以避免流挂。
3. **干燥时间**：让 **2小时以上** 让底漆在上漆前固化。

**底漆填充剂的优势**:

* **表面精修**：干燥后打磨（例如800–1200目）以消除细微瑕疵。
* **多步骤平滑处理**：涂抹底漆填充剂、打磨、清洁并重复，直至获得近乎无瑕的表面效果。注意，过度打磨可能会损伤精细细节。

### **上漆技巧**

**喷笔喷涂**:

* **优点**：可实现均匀覆盖和渐变阴影；非常适合大面积表面。
* **局限性**：与手工上色相比，对复杂细节的表现不够精确。

**手工上色**:

* **使用场景**：适用于小区域、细线条或细节部位（如眼睛、纹理）。
* **画笔选择**：高质量的细笔刷能提高精确度。

**涂料选项**:

* **丙烯颜料**：价格实惠且易于购买；要实现顺滑涂装需要练习。
* **模型漆**：颜料浓度更高，可获得专业效果。
* **透明保护面漆**：最后喷涂缎光或高光透明漆，以封固并保护漆面。

**材料考量**:

* **柔性线材**：避免使用丙烯颜料，因为它们在弯折时会开裂。请改用专用柔性涂料。
* **干燥时间**：耐心至关重要——操之过急会导致结块或纹理不均。

**技能提升**:

* **练习**：尝试渐变、遮蔽和叠涂，以打磨技巧。
* **教程**：研究专业指南，学习诸如眼部细节刻画或纹理复制等复杂任务。

**总结建议**

* **底漆**：对漆料附着至关重要；底漆填充剂可提升表面质量。
* **工具选择**：结合喷笔喷涂（大面积覆盖）和手工上色（细节处理）可获得最佳效果。
* **材料注意事项**：将涂料与耗材特性相匹配，以防止开裂或剥落。

最后，许多人受益于一段名为“GalactiCustoms: 1/6 Paint Tutorial: Obi-Wan Kenobi- Pt 3 Eyes”的YouTube教程视频，它为眼睛上色提供了宝贵见解，并显著提升了我所上色零件的外观。

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


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.polymaker.com/polymaker-wiki/polymaker-wiki-zh/da-yin-ji-qiao/hou-chu-li/shang-se.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.