Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
3
Found in
2017.3.0b6
2018.4
2019.4
2020.3
2021.2
Issue ID
962800
Regression
No
RuntimeInitializeOnLoadMethod is not called if it is part of nested class that is in a namespace
How to reproduce:
1. Open the attached "Runtime_Bug.zip" project
2. Click Play
Expected results: 'No Namespace - Inner', 'No Namespace - Outer', 'In Namespace - Inner', 'In Namespace - Outer' is printed to the Console
Actual results: 'No Namespace - Inner', 'No Namespace - Outer', 'In Namespace - Outer' is printed to the Console
Reproducible with: 2018.4.34f1, 2019.4.28f1, 2020.3.11f1, 2021.1.10f1, 2021.2.0a19
-
HarvesteR
Feb 05, 2021 23:04
Just ran into this today (unity 2018.4.30). Thought it was a bit weird.
I understand if this behaviour is by design, although it would be neat to hear the reasoning behind it (just curious). Possibly worth adding a few words about this in the docs?
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
- [Linux] Packman options to add package from Git URL doesn't always show the window directly below the + button
- Editor redirects to a broken page when pressing question mark "?" in the Inspector window
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
- "Cyclic Prefab nesting not supported" error window is thrown when trying to nest two sibling prefab variants
- Prefab copies are generated every frame and exceptions are thrown when its dragged into the Scene view
Resolution Note (fix version 2022.1):
Fixed in version 2022.1.0a2
Resolution Note (fix version 2021.2):
Fixed in 2021.2.6f1
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.9f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.12f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.29f1