Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
969475
Regression
Yes
Particle system custom data at does not change at run time
Steps to reproduce:
1. Open user attached project
2. Run the scene
3. Notice the yellow emitted particles
4. Change the value of "datalist" in CustomDataForScript.cs file at line "dataList[i] = new Vector4(0.6f, 0f, 0f, 1f);"
5. Run the scene and notice the color of particles has not changed
Expected result: the color of the particles should change
Reproduced in: 2018.1.0a4, 2017.3.0b10, 2017.2.0p2, 2017.1.2p3, 5.6.4p3, 5.6.0a6
Not reproduced in: 5.6.0a5, 5.5.5p1
Regression since: 5.6.0a6
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
Add comment