Search Issue Tracker
Fixed in 5.4.1
Votes
65
Found in
5.4.0b11
Issue ID
782232
Regression
Yes
Two independent Particle systems appear to be using the exact same seed for randomisation
How to reproduce:
1. Open attached project
2. Open scene particles.unity
3. Play the scene
- Note how the coloured particles and the black particles appear to be moving in the exact same patterns
- This happens even if the particles aren't parented/childed to each other
- The particles in both separate systems should be moving in different ways
- Reproduced in Version 5.4.0b11 (323b0238353b), Version 5.4.0b6 (2c3d6b93e789)
- Not reproducible in Version 5.3.4p1 (e89f89413a91)
Comments (65)
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
- Baked Lightmap ”View” button text is aligned incorrectly
- Lightmap Asset icon changes colours after Baked Lightmap Viewer window is opened
- VideoClipImporter preset not applied when applying Preset Selector on already imported video clips
- Frame Debugger gets disabled when any Editor window is maximised and minimised
- TextMeshPro InputField view is not updated when OnEndEdit is triggered
isbeorn
Aug 19, 2016 07:09
Does 'Workaround is possible' mean that there is a workaround? What is it? Giving the particle systems new seeds doesn't seem to make any difference.
isbeorn
Aug 19, 2016 06:28
I'm also suffering from this. In 5.4.0f3.
Dimetrock
Aug 18, 2016 07:38
- bug is present in 5.4.0f3
Laious
Aug 15, 2016 16:49
Same for me... It was working fine on 5.3
Louis-N-D
Aug 05, 2016 21:38
Filed a bug for this in the final 5.4 release and it got flagged as a duplicate of this bug. Just wanted to confirm here that the release version of 5.4 definitely still exhibits this bug.
Louis-N-D
Jul 29, 2016 19:03
Yep. Upgraded to the 5.4 release last night and this suddenly reared its ugly (and very repetitive) head.
ifurkend
Jul 17, 2016 15:10
Still there in 5.4.0f1. You seriously think this is a proper Release Candidate without fixing this bug?
RadTT
Jul 11, 2016 23:47
Just ran into this after updating from 5.3 to the latest beta release. Was working fine in 5.3. Currently using 5.4.0b25
Firlefanz73
Jul 03, 2016 16:01
Still in 5.4.0b24.
Firlefanz73
Jul 03, 2016 15:07
Still in 5.4.0b23.