> For the complete documentation index, see [llms.txt](https://doc.playturbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.playturbo.com/playable-tools-feature-changer/feature-changer-faq/material-effect-issues.md).
# Material Effect Issues
#### **Q1:** For the template "[Piano tiles](https://playable-portal.mintegral.com/common-viewer/mindwork-view.html?url=https%3A%2F%2Fmmp-cdn.rayjump.com%2Fmindworks-interactive-ads.html%3Furl%3Dhttps%253A%252F%252Fmmp-cdn.rayjump.com%252Fgm%252Ft%252F20001202%252F12795%252Fpv%252F24%252F05%252F07%252F663a169d21ef4%252Fproject.html%253Fpreview%253Dtrue%2526itavideo%253D2%2526vconsole%253D0%2526mw_test%253D0%2526ptloading%253D1%2526loading%253D1%26mw_test%3D0\&orientation=undefined\&name=%E7%BB%8F%E5%85%B8%E9%92%A2%E7%90%B4%E9%94%AE\&language=undefined)," I want to replace the three cover images in the "Failure page sound prop icon" slot, but they all seem to be the same. Why can't I make different replacements?
**A:** You can **copy the project to "Content Editor"** and enter Scene 3 to replace the different cover images individually. *(Tip: When using Template Feature Creation, if you encounter limitations in adjustments, try switching to Content Creation to make changes, as this can solve most issues!)*
#### Q2: In the template "Triple Match Puzzle", I want to hide 2 elements so that only 3 types are displayed on the canvas, but during the preview, clicking on the blank area still triggers the elimination effect.
**A:** It's important to understand that adjusting a layer's "Show" or "Hide" in the template project only affects visual presentation and is not linked to the gameplay logic of the template. This issue arises because clicks on hidden layers are still registered during the preview.
It is recommended that you adjust the gameplay of the playable by modifying a series of gameplay parameters within the template. If you want to hide certain layers, try to hide those that are unrelated to interactive operations.
#### Q3: After replacing the main character (Protection object) sequence in the \[Draw to Help] template, the character appears tilted in the preview — why?
**A:** This is likely related to the replaced **Scene Terrain** asset. The actual visible pixels of the terrain image define the terrain’s rigidbody. When the image is changed, the rigidbody adapts accordingly. If the center of the new terrain is too narrow, it may cause the rigidbody to be pushed out of place, leading to the character tilting.
**Suggestion:** Use a flat and even terrain image, or ensure the center area of the terrain has sufficient width.
#### Q4: In Feature Creation, I’ve hidden some image layers (turned off the eye icon), but after copying the template to the Content Editor, they still appear — why?
**A:** This is due to the platform’s logic. We recommend locating and hiding the corresponding layers again directly in the Content Editor.\
\&#xNAN;*Please Note: If you can’t find certain layers, they may be inside the “Gameplay Template.” Please refer to the* [*FAQ*](/playable-tools-content-editor/content-editor-faq/asset-issues.md#q1-after-making-the-playable-material-and-inputting-the-product-information-for-the-associated-promo-7) *for more details.*
---
# 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://doc.playturbo.com/playable-tools-feature-changer/feature-changer-faq/material-effect-issues.md?ask=&goal=
```
`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.