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.
An instance of a class that is derived from a class that is derived from MessageBase doesn't call overridden Serialize() method
Steps to reproduce:
1. Open attached project
2. Open up 'blah.cs' script and notice that Msg class is derived from MessageBase and has Serialize method overridden. MsgEx class is derived from Msg class and on Start, the Serialize method is called through MsgEx instance.
3. Open and play 'Untitled' scene
Expected result: "Serialize" should be printed out in the console indicating that Msg.Serialize() method got called
Actual result: No message is printed to the console and Serialize() does not get called
Workaround: Overriding the Serialize() method in MsgEx class so that it simply calls to base.Serialize() itself.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- [Linux Hub] A new instance of the Hub does not have a Taskbar icon
- Mesh Inspector becomes slow to use when inspecting a large Mesh with Blend Shapes
- [Metal] GfxDeviceMetal::CreateComputeProgram does not check inputs
- The Modes button of the the SerializedField MinMaxGradient is not clickable in the Inspector when indentLevel is more than 0
- Input.GetKey for Left Shift returns true when Right Shift is held down and Left Shift is pressed (and vice versa)