Search Issue Tracker
By Design
Votes
0
Found in [Package]
9.0.0, 8.1.0, 8.0.1
Issue ID
1243954
Regression
No
[HDRP] System is not interested in this transform errors are thrown continuously on CTRL + Z after removing Light component
-On undo one extra light component added on the Direction light game Object.
-The system is not interested in this transform errors are thrown continuously on Cntrl + Z after removing Light component from Directional Light.
Steps to repro:
1. Create a new HDRP Project.
2. Hierarchy > Select Direction Light.
3. Inspector >Remove Light Component.
4. Press Control + Z.
Actual Result:
The system is not interested in this transform errors are thrown in the console.
Expected Result:
No error in the console.
Reproducible in:
2020.2.0a10, 2020.1.0b8, 2019.3.0f3 with Package Version: 9.0.0, 8.1.0, 8.0.1, 7.1.8.
Environment:
Occurring on Windows 10 & Mac 10.15
Stack trace:
NullReferenceException: Object reference not set to an instance of an object
UnityEngine.Rendering.HighDefinition.HDAdditionalLightData.UpdateBounds () (at library/packagecache/com.unity.render-pipelines.high-definition@9.0.0-preview.13/runtime/lighting/light/hdadditionallightdata.cs:2590)
UnityEngine.Rendering.HighDefinition.HDAdditionalLightData.OnValidate () (at library/packagecache/com.unity.render-pipelines.high-definition@9.0.0-preview.13/runtime/lighting/light/hdadditionallightdata.cs:2287)
UnityEngine.Rendering.HighDefinition.HDAdditionalLightData.Migrate () (at library/packagecache/com.unity.render-pipelines.high-definition@9.0.0-preview.13/runtime/lighting/light/hdadditionallightdata.migration.cs:174)
UnityEngine.Rendering.HighDefinition.HDAdditionalLightData.Awake () (at library/packagecache/com.unity.render-pipelines.high-definition@9.0.0-preview.13/runtime/lighting/light/hdadditionallightdata.cs:2390)
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler()
System is not interested in this transform, SetSystemInterested may only be called on transforms that are set interested.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
UnityEditorInternal.InternalEditorUtility:SetCustomLightingInternal (UnityEngine.Light[],UnityEngine.Color)
UnityEditorInternal.InternalEditorUtility:SetCustomLighting (UnityEngine.Light[],UnityEngine.Color)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
System is already interested in this transform, SetSystemInterested may only be called once.
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler ()
If the system is getting enabled, then it can't have any previous changes registered
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler ()
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 is a known issue and there is an ongoing effort for 2020.2 to solve it. This also applies to Camera and Light component, nothing we can do. Closing as won't fix. Should be solved in 2020.2 for the cutoff