customizable player loading progress screen #40
Conversation
The look of the player's loading screen can now be customized by defining a custom operator that draws it and defining a property called "LoaderProgressOperator" with the operator's meta ID in ProjectSettings.json. The operator will then be rendered instead of the normal loading bar, with t=0 seconds at the start of loading and t=1 second at the end.
no more fatal exceptions if the GUID is malformed or the operator .mop is missing
The time for the custom loader operator is now mapped differently: instead of 0...1, it's -1...0. This makes it more natural to work with: Now, the loader is conceptually running in the second just before the demo (except that this "second" may in reality take much longer than that). It no longer overlaps part of the timeline. This also makes seamless transitions from the loader into the first scene easier.
by default, it's empty of course :)
Includes the explicit Camera operator work-around against broken default camera settings.
|
Hi KeyJ, |
|
Ok, the code changes itself are fine. I think I would have removed the hardcoded progress bar and put this in an operator too and this one set as default operator to use for progress visualization. Anyhow this can (or not) be done later. This only leaves the merge target branch that would need to be changed. |
|
I selected master instead of develop because master is currently ahead of develop, making develop look like an abandoned branch. But if you want, I can still rebase to develop and make a new PR. |
|
Hmm for me it looks like both have the same state: |
|
I'll do a new PR based on develop now. |
The look of the player's loading screen can now be customized by defining a custom operator that draws it and defining a property called "LoaderProgressOperator" with the operator's meta ID in ProjectSettings.json. The operator will then be rendered instead of the normal loading bar, with t=-1 seconds at the start of loading and t=0 second at the end.
Reasonably comprehensive documentation is included, including information about the two things that don't work properly, namely missing updates in the "pre-caching" phase at the end of the loader and broken default camera settings that need to be worked around.