Search Issue Tracker
Won't Fix
Votes
2
Found in
2020.3
2020.3.11f1
2021.1
Issue ID
1342983
Regression
Yes
Billboard Particle System not visible when in Player built using Unity Cloud Build
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. Inspect the Particle System
4. Make a local standalone build
5. Inspect the Particle System again in the built Player
6. Upload the project to Collab
7. Make a Unity Cloud Build
8. Download the finished build from Unity Dashboard
9. Inspect the Particle System again in the built Player
Expected result: Particle System is visible and appears the same as in the Editor and the locally built Player
Actual result: Particle System is not visible and has missing Tangent Stream data
Reproducible with: 2020.1.0a11 (as far as UCB goes), 2020.3.11f1, 2021.1.9f1
Not reproducible with: 2019.4.28f1, 2021.2.0a21 (lowest UCB 2021.2 stream version), 2021.2.0b3
Notes:
- Not reproducible when building project locally
- Error in the Player.log, "Metal: Error creating pipeline state (Particles/Standard Surface): Link failed: The type of fragment input user(TEXCOORD0) does not match the type of the corresponding vertex shader output"
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2022.1.X):
It seems the issue is not reproducible in 2021.2 and higher. Please consider upgrading to a newer version.