Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.4.0b1
Issue ID
756699
Regression
No
Particle System created at runtime mismatches between Editor and Standalone
1. What happened
Particle System created at runtime mismatches between Editor and Standalone. For standalone it looks broken.
2. How we can reproduce it using the example you attached
- Open scene 1
- Play it and observe the expected behaviour. (PS is created from script attached to camera)
- Exit Play mode and build project with the scene (or, for Mac, run the executable '1' from within attached project folder)
- Run the executable
---> Resulted particle system produces only 1 particle at a time; that single particle moves at much slower speed than particles in 'original' PS.
Looks like that's not a regression - issue reproducible even in 4.7.0. Beforehand that wasn't quite an issue as a user wasn't able to do much with PS at runtime. But now (as of 5.3) almost everything can be configured at runtime.
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