Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2018.4
2019.4
2020.3
2020.3.12f1
2021.1
2021.2
2022.1
Issue ID
1344356
Regression
No
Error appears in the Console when using the Default Particle System's textures as the Shape Texture
How to reproduce:
1. Open the attached '1344356.zip' project
2. Open the SampleScene
3. In the Hierarchy select GameObject > Particle System
4. Observe the Console
Expected result: There are no errors present
Actual result: The 'Ensure Read/Write is enabled on the Particle System's Texture.' error appears in the Console
Reproducible with: 2018.4.36f1, 2019.4.28f1, 2020.3.13f1, 2021.1.14f1, 2021.2.0b2, 2022.1.0a1
Note:
- The issue is also reproducible in a build
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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a6
We are going to handle this automatically now, like we do for meshes. i.e. any textures used in this particle slot will automatically be marked as read/write when making a build, so users no longer have to worry about setting it correctly.
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b11
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.22f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.20f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.32f1