Search Issue Tracker
Fixed
Fixed in 2022.2.7f1, 2023.1.0a26
Votes
0
Found in
2022.2.0b16
2023.1.0a23
Issue ID
UUM-21543
Regression
No
RuntimeInitializeOnLoadMethod documentation is incorrect and lacking helpful information
This is all the docs we have now:
"Allow a runtime class method to be initialized when a game is loaded at runtime without action from the user.
Methods marked {{[RuntimeInitializeOnLoadMethod]}} are invoked after the game has been loaded. This is after the {{Awake}} method has been invoked.
*Note:* The execution order of methods marked {{[RuntimeInitializeOnLoadMethod]}} is not guaranteed."
It does not mention the various options of callbacks
There is no info on the execution order of the callbacks.
Incorrect info:
* This is after the {{Awake}} method has been invoked.
* The execution order of methods marked {{[RuntimeInitializeOnLoadMethod]}} is not guaranteed.
The documentation was not updated when [RuntimeInitializeLoadType|https://docs.unity3d.com/ScriptReference/RuntimeInitializeLoadType.html] was added. Which is hooks that invalidates above documenation.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Log shader compilation does not give info on which shader instance had a variant compiled
- Label text overflows its rect when resizing the Game view in Free Aspect
- UI Toolkit Slider value defaults to min value when the initial value is set in the UXML file
- The Player hangs when unloading a scene using the UnloadUnusedAssets() method
- [iOS] Too many texture parameters error is thrown when running on devices that support the number of parameters
Add comment