Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2022.3.59f1
6000.0.40f1
6000.1.0b8
6000.2.0a5
Issue ID
UUM-100781
Regression
No
Wrong shader appears when Particle System is added as a component
Steps to reproduce:
1. Create a new project
2. Create a GameObject (3D Cube, Sphere, Capsule)
3. Add a Particle System component to it
4. Observe the pink particles (wrong shader)
5. Create a Particle system as a GameObject (Right click in the Hierarchy > Effects > Particle System)
6. Observe the Scene view (Particle system has the correct shader)
Expected result: Particles appear with the correct shader and material when adding a Particle System component to an existing GameObject
Actual result: When adding a Particle System component to an existing GameObject, the particles appear pink (indicating a missing or incorrect shader)
Reproducible in: 2022.3.59f1, 6000.0.40f1, 6000.1.0b8, 6000.2.0a5
Reproducible on: Windows 11
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment