Common Issues

Input system

⛔ Problem: When the scene starts, nothing happens - there is no effect from touches. This often occurs on first use.

✅ Solution: Most likely, the issue is with input. Open the InputController component inside the effect prefab and set InputSystemType to Old/New, depending on which one you are using. Make sure there is an EventSystem in the scene; if not, create one. See Core Components > Input Controller.

Textures, rendering, visuals

⛔ Problem: In the build on mobile, the effect created with SparkleSpawner is not visible, even though it displays correctly in the PC build and in the Editor. Either there is no effect at all, or some particles appear square.

✅ Solution: This happens because the texture used as a particle is corrupted and cannot be read correctly. Locate the SparkleSpawner component → Sparkle Textures list and remove the corrupted texture. Using trial and error, try to identify which texture is breaking the build. Once the problematic one is found, it needs to be replaced. Open it in Photoshop and re-import it into the project as a new file. It’s better to use a 256×256 resolution (or a multiple), like the other textures in the system.

⛔ Problem: In Built-in/HDRP, the shader effect displays with glitches, while in URP it works correctly. This especially affects shaders with complex calculations for animating multiple particles (for example, the Fireflies).

✅ Solution: If this shader is your own implementation, try simplifying the math behind generation, animation, and fading. If it’s one from the collection, first try switching the Game → Maximize On Play or making a build (the Inspector preview can affect how it’s displayed in Play Mode). If the issue persists, let us know and we will adjust the shader.

Remember that the developers are available and can assist you personally if needed.