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)
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Soulice
Oct 01, 2016 14:35
In 5.4.1 and still seeing this issue. Attached particle system to object and burst on collision, same pattern each burst
env_warby
Sep 06, 2016 22:46
i just upgraded to the 5.4.0f3 release build and its definitely in there i saw it immediately / first thing i noticed that was different.
Maverick
Aug 31, 2016 16:11
Still present in 5.4.0.p4
Ryan-Gatts
Aug 23, 2016 01:27
Still occurs in 5.4.0f3
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.