Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.0b22
Issue ID
807907
Regression
No
Particle.Stop() shows wrong state
Steps to reproduce(not always reproducible):
1. Open "TestScene" project in Unity 5.4.0b23.
2. Press play button in toolbar.
3. Hold arrow buttons to guide white ball off screen. While you are doing it press "p" button rapidly to disable/enable particle systems( Check Gui box in upper-left corner for all of the information you need).
--- Side note: To get better idea what you should see, watch this gif: https://i.gyazo.com/8bc01e6874191b0eb97fc67c93a9a155.mp4
Expected result: Local particle systems function "Particle.isStopped" should act accordingly with pressed "p" button when the ball is outside the screen.
Actual results: Local particle systems function "Particle.isStopped" always stays in false state unless you enter camera view.
Side notes:
--- Sometimes "Particle.isStoped" starts working properly.
--- If you open Scene view window while you are running this project, "Particle.isStoped" will work properly until you cross scene view screen borders (https://i.gyazo.com/a5a1dad9624e78d0200a56fe92f8959c.mp4).
Reproduced in: 5.4.0b23, 5.4.0b22, 5.3.5p3, 5.3.5f1.
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
- [Android] Texture Compression default texture format is set to PVRTC when building via script BuildPipeline.BuildPlayer
- [Android][GameActivity] APK built with Development Build enabled gets flagged as having Malware
- Default name of manually created Global Light 2D GameObject differs from the one included in the initial project Scene
- Option for "Acceleration Structure Build Flags" cannot be toggled when Lightmaps have been Generated for a Mesh Renderer
- Lights in Batch keep resetting to 0 in the Light Batching Debugger when a new GameObject is created and the mouse cursor is hovered over the Inspector window
This is a duplicate of issue #800868