Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
1011101
Regression
No
Object reference is set to an instance of an object in Visual Studio but Unity fails to detect it
Reproduction steps:
1. Download user's project and open in Unity
2. Enter Play mode
3. Open ReferenceBase script
4. Put breakpoint on line 105 (var useReference = ReferenceValue != null)
5. Press Attach to Unity in Visual Studio
6. Select the Game view and press up arrow
Expected: useReference is set to true because the ReferenceValue is not empty
Actual: useReference is set to false
Reproduced on: 5.6.5p2; 2017.1.3p2; 2017.2.2p1; 2017.3.1p4; 2018.1.0b11; 2018.2.0a4
Note: If manually setting useReference to true, after returning ReferenceValue value error appears in the console
Error message:
"NullReferenceException: Object reference not set to an instance of an object
Edge.UnityStandard.ReferenceBase`1[System.Single].get_Value () (at Assets/Scripts/Base/ReferenceBase.cs:106)
TestFloat.Update () (at Assets/Scripts/TestFloat.cs:17)"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment