Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
9.0.0, 8.2.0.
Issue ID
1263053
Regression
Yes
[HDRP] SerializedObject target has been destroyed error is thrown on resetting Screen Space Reflection in Settings Volume
SerializedObject target has been destroyed error is thrown continuously on resetting Screen Space Reflection in DXR Settings Volume.
Steps to repro:
1. Create a new HDRP template project
2. Windows > Render Pipeline > HD Render Pipeline Wizard.
3. Select "HDRP + DXR" > Click on "Fix All".
4. Restart The Editor > Select DXR Settings Volume.
5. Inspector > Volume > Screen Space Reflection > Change its property.
6. Reset from the burger menu.
Actual Result:
A game object can only be in one layer error in the console.
Expected Result:
No error in the console.
Reproducible in:
2020.2.0a18, 2020.1.0b16 with 8.2.0.
Working Fine in:
2020.2.0a18 With Package Version 8.1.0
Environment:
Occurring only Windows.
Stack trace:
SerializedObject target has been destroyed.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
The issue is caused by the defaut volume profile being referenced from the package and being read only as a result.
This behavior has changed with latest versions where we now use scene templates. In this case the volume profile for new scenes is always in the asset folder and thus the issue won't occur anymore.
As such we won't fix this problem in older packages.