Search Issue Tracker
Fixed
Fixed in 9.0.0
Votes
0
Found in [Package]
9.0.0, 8.1.0
Issue ID
1244017
Regression
No
[SerializedReference][Prefab]Unable to apply changes on Custom Pass prefab instance in Overrides window
-Unable to apply changes on Custom Pass prefab instance in Overrides window.
-ApplySingleProperty copy state error: SerializedProperty could not be found for customPasses.Array.data[0].m_Name is thrown in the console.
Steps to repro:
1. Create a new HDRP Project.
2. Hierarchy > Right Click > Volume > Custom Pass > Create its prefab.
3. Hierarchy > Custom Pass > Custom Passes > Add DrawRenderCustomPass.
4. Change Priority value.
5. Override Window > Select Custom Pass Volume Script > Apply.
Actual Result:
- Unable to apply changes on Custom Pass prefab instance.
- ApplySingleProperty copy state error in the console.
Expected Result:
- Changes can be applied on Custom Pass prefab instance.
- No errors in the console.
Reproducible in:
2020.2.0a10, 2020.1.0b8 with Package Version 9.0.0, 8.1.0, 8.0.1, 7.3.1.
Environment:
Occurring on Windows 10 & Mac 10.15
Stack trace:
ApplySingleProperty copy state error: SerializedProperty could not be found for customPasses.Array.data[0].m_Name. Please report a bug.
UnityEditor.GenericMenu:CatchMenu (object,string[],int)
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
- [Android] Neither of the callbacks are called when several videos with VideoPlayer are spawned on the target on the Google Pixel devices
- Texture2D memory allocation size is significantly increased when running on iOS device
- No data received in Profiler when connecting to WebGL Player without "Autoconnect Profiler" option enabled
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
Resolution Note:
This no longer occurs in 2020.1.0b12 nor latest 2020.2 alpha.
Resolution Note (fix version 9.0.0):
This no longer occurs in 2020.1.0b12 nor latest 2020.2 alpha.