Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b3
Issue ID
907383
Regression
Yes
Particle System component breaks if scripts are recompiled while the component is open in the Inspector
To reproduce:
1. Open the project, attached by tester (particlesComponentBug.zip)
2. Open "testScene" scene if not already open
3. Select Particle System game object in the Hierarchy
4. Open script.cs and change Update to Start
5. Return to Unity, make sure the Particle System game object is selected and Inspector window is open
6. After compiling, observe the Particle System component
Expected: Unity compiles code normally without breaking the Particle System component
Actual: Particle System component becomes broken if it is open in the inspector while Unity compiles scripts
Reproduced in 2017.1.0b2, 2017.1.0b3, 2017.1.0b4
Did not reproduce in 2017.1.0b1
Regression introduced in 2017.1.0b2
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