Search Issue Tracker
By Design
Votes
0
Found in
5.6.0f3
Issue ID
953056
Regression
No
Setting ParticleSystem.CustomDataModule data mode to Vector or Color causes GetCustomParticleData/SetCustomParticleData to fail
Steps to reproduce:
1.Open attached “ParticlesCustomDataTest.zip” Unity project
2.Open ’Test’ scene
3.Enter Play mode
Expected results:
Sound effect is played once every time a particle appears
Actual results:
Sound effect is played repeatedly for every particle because CustomData Vector4 value for each particle was not set or was overriden
Reproduced in: 2017.3.0b2, 2017.2.0f1, 2017.1.1p3, 5.6.3p4, 5.6.0b1
-------------------------
By design:
Enabling Vector or Color module causes it to write its own values to the custom data arrays, overwriting anything set by the user
Comments (1)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
GearKlik
Jan 17, 2018 02:41
Can someone explain how this is "By Design"? I think its a valid feature to set my own custom vector/color data and track it per particle.