Search Issue Tracker
By Design
Votes
0
Found in
5.0.0f4
Issue ID
683862
Regression
No
Using or not using the 'new' keyword gives conflicting warnings in the Editor and when building to any platform
How to reproduce:
1. Open attached project
- Notice the warning upon compilation
2. Add a 'new' keyword after the 'private' keyword in the script
- The editor gives no warnings
3. Build to any platform
- Notice Unity gives a warning that 'new' is not necessary
For a simple workaround, please surround the offending code like this:
#pragma warning disable 0108
private Rigidbody rigidbody = null;
#pragma warning restore 0108
This disables (and then reenables) the Editor warning that says that 'rigidbody' is being hidden.
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
- Only the left screen is rendering when using Render Graph Fullscreen Blit in Meta Quest 2
- Context menu with the "Revert" option doesn't appear when pressing the right mouse button on a "Vector2" or "Vector3" property in the Inspector of a custom shader
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
skiplist
Mar 29, 2015 09:33
How come this is by design?