Search Issue Tracker
Fixed in 4.3.2
Votes
0
Found in
4.3.0f4
Issue ID
577450
Regression
Yes
"Prewarm" on non-looping particle systems causes duration issues when reanabling
To reproduce:
1. Import attached package
2. Open "TestScene". It contains a few particle systems under a parent particle system and a script for enabling/disabling the system.
3. Enter play mode - wait for the particle system to disable itself and them press "Activate Particle Again"
4. Notice how the duration of the effect is considerably shorter (except for one particle system which is has it's simulation space set to world)
5. Go through the three child particle systems and disable prewarm. Press the button again - everything works fine
Note: this seems to affect only local simulation space particles
Does not occur with version 4.2.2f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment