Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f3
Issue ID
961550
Regression
No
[ParticleSystem] Contradictory warnings in Visual Studio and Unity console
Reproduction steps:
1. Download project "SmallMultitool.zip" and open in Unity
2. Open script "UIParticles"
3. In line 7 delete keyword "new" (observe warning - firstError.png)
4. Write the "new" keyword in the same place
5. In Unity press File -> Build & Run
6. Observe warning in Console (secondError.png)
Actual: contradictory warnings in Visual Studio and in Unity console (see pictures and Notes)
Expected: unified warnings
Reproduced on: 5.6.4f1; 2017.1.2p2; 2017.2.0f3; 2017.3.0b6; 2018.1.0a1
Note:
Visual Studio - `UIParticles.particleSystem' hides inherited member 'Component.particleSystem'. Use the new keyword if hiding was intended.
Unity console - The member `UIParticles.particleSystem' does not hide an inherited member. The new keyword is not required
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
- 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
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.