Search Issue Tracker
Fixed in 5.4.1
Votes
0
Found in
5.4.0b24
Issue ID
815127
Regression
Yes
LightProbes.GetInterpolatedProbe causes an error
1. What happened
I get an error when calling LightProbes.GetInterpolatedProbe. Here is the error:
NullReferenceException
UnityEngine.LightProbes.GetInterpolatedProbe (Vector3 position, UnityEngine.Renderer renderer, UnityEngine.Rendering.SphericalHarmonicsL2& probe) (at C:/buildslave/unity/build/artifacts/generated/common/runtime/GraphicsBindings.gen.cs:2089)
2. How we can reproduce it using the example you attached
You just need to load Assets/TestScene.unity3d and press play in the Editor. It gets the error in the Editor and on a device.
This issue is a regression as it does NOT occur here:
Version 5.3.1f1 (cc9cbbcc37b4)
Thu, 17 Dec 2015 13:01:19 GMT
Branch: 5.3/release
Occurs on:
Version 5.4.0f1 (c6df7519ab13)
Mon, 11 Jul 2016 22:27:03 GMT
Branch: 5.4/staging
as well as the google daydream preview release:
5.4.0b24 (18776a17bc62)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment