Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
4.3.0b1
Issue ID
563828
Regression
No
ScriptableObjects seem to serialize their private collections unless they are explicitly marked as NonSerialized
ScriptableObjects seem to serialize their private collections unless they are explicitly marked as NonSerialized. MonoBehaviours don't suffer the same problem.
Instructions:
Open "Bug Scene" and watch what is logged to the console. That message comes from ScriptableObjectWithBug. Logger calls the relevant method in ScriptableObjectWithBug. Logger calls the same method in MonoBehaviourWithNoBug, but MonoBehaviourWithNoBug, as can be implied from its name, works as expected.
1 Open attached project
2 Open scene "Bug Scene" and press play
- notice message "ScriptableObject is broken" in console
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment