Add loading details to loading screen

[epicEaston197]

Is your feature request related to a problem? Please describe.

Right now we only have the loading bar telling us details on the loading progress

Describe the solution you'd like

I want a bit of text at the bottom of the loading bar that tells me what is being initialized

Describe alternatives you've considered

Things like ResoniteModLoader and monkey loader do this

Additional Context

Requesters

@epicEaston197

[Frooxius]

We want to keep this screen clean for majority users.

The text might make things more confusing to users.

[LeCloutPanda]

Well for the average user it would be a bit too much and become confusing but what about those who want to see what's going on? from a debug stand point as well it could be nice to see what stage stuff is hanging at rather then going through the log file instead of just having a live preview.

What if we had an option for it under Misc? because personally my self and I am sure a lot of people would like to see what things are doing during runtime.

[Frooxius]

For debug standpoint, you should always use logs and not rely on visuals - they contain more information and are more up to date.

There's not really any benefit in having the visual.

Settings are complicated - they require the engine to be loaded... which it's not during loading process. So making that work requires more engineering effort - and I don't see any need for this that would justify putting that engineering time into this.

[epicEaston197]

I wouldn't use this feature for debug purposes I just think it looks neat it's like getting a small sneak peek under the hood but nothing more

[AmasterAmaster]

I would say having more information to show is beneficial, even if it is daunting to new users, for the reason of when Resonite decides to freeze, it will show exactly the point where it froze because the text will reveal it on the loading screen. This helps pinpoint where we can show the devs where the application hung when trying to load/initialize. But this is just my opinion with the programmer mindset.

@Frooxius and yes, debug logs are way better for this, but at least having more verbose text reassures that the user would not complain in the wrong direction (as it would clearly show where and when, instead of the user "guessing" what happened).