Search Issue Tracker
In Progress
Under Consideration for 6000.0.X
Fix In Review for 6000.1.X
Votes
0
Found in
6000.0.21f1
6000.1.0a1
7000.0.0a7
Issue ID
UUM-83161
Regression
Yes
Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
Reproduction steps:
1. Create a new 3D (URP) project
2. Close the Editor window
3. Move the “Library/PackageCache/com.unity.render-pipelines.core” folder to the “Packages” folder
4. In “package-lock.json” set “com.unity.render-pipeline.core” version to {{[file:com.unity.render-pipelines.core|file://com.unity.render-pipelines.core/]}}
5. Open the project
6. Open the Graphics window (Edit > Project Settings > Graphics)
7. Open the Build Settings window (File > Build Settings)
8. Make sure “Development Mode” is enabled
9. Press “Build And Run” button
10. Observe the Player Console output
Expected result: No errors are thrown
Actual result: Serialization errors are thrown: {{A scripted object (probably ...) has a different serialization layout when loading. Did you #if UNITY_EDITOR a section of your serialized properties in any of your scripts?}}
Reproducible with: 2023.3.0a18, 6000.0.21f1
Not reproducible with: 2021.3.44f1, 2022.3.49f1, 2023.3.0a17
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Note:
- This issue is closely related to UUM-76007 case, but was deemed to be another problem.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Draw Renderers custom pass doesn't work with SSGI
- WebCamTexture does not set the requested resolution when used in WebGL
- Editor default Stylesheet/Matching Selector buttons in Debugger don't do anything
- Graphics.DrawMeshNow stops rendering Render Texture after a few frames when viewed in the Player
- New selector in Matching Selectors displays as on line -1 in debugger
Add comment