After switching from 4.6.1 to 4.7.3 we noticed that our loading screens where not shown anymore.
It seems execution order inside engine loop has changed somewhat.
After setting up a loading screen via FDefaultGameMoviePlayer::SetupLoadingScreen() within gamecode that is called from UGameEngine::Tick(), next thing happening is FDefaultGameMoviePlayer::WaitForMovieToFinish() which detects movie is not running (yet) and shuts down loading screen. Only after that FDefaultGameMoviePlayer::OnPreLoadMap() is triggered which would actually start movie / loading screen.
A work-around for this is to set FLoadingScreenAttributes::MinimumLoadingScreenDisplayTime to >= 0.0 so that this condition is not fulfilled during first call to FDefaultGameMoviePlayer::WaitForMovieToFinish().
We haven’t heard back from you in a while, so I’m resolving this issue for tracking purposes. Please let us know if this is still occurring for you in 4.7.5, and we can continue investigating. Thanks!
I just switched to 4.7.5 yesterday so I did not test this before. Switching to a new version is not as easy for us as we work on Windows, PlayStation 4 and Xbox One. So updating to a new version takes about a day.
Before switching to 4.7.5 I took a look at all github commits between 4.7.3 and 4.7.5 and I did not see anything that seemed related to problem I reported. However I tested issue again and problem is still occurring. Did you succeed in showing a loading screen in a test project? Or can you point me to github commit that should fix problem?
Have you taken a look at full release notes for 4.7 release?
As stated in notes, this was our biggest release yet with a lot of changes made to Engine. Perhaps you can browse through these which can give you an indication of what could have caused your loading screens to change/not appear?
Let me know if you find anything worth noting pertaining to your issue specifically. If you are not seeing anything, we can continue to troubleshoot your issue and possibly escalate to a higher up developer.
I did not mean for you to search for that one commit that introduced problem in 4.7.
But since you recommended to switch to 4.7.5. there should be a commit in 4.7 branch that fixes problem. I was looking for that myself but found nothing - and after testing it, problem still remained.
Like I said there is a work-around but it does not work way it used to and I think work-around should not be necessary.
I am going to loop in some other support staff since this seems to be a code based project. I do know there were some code changes made to our framework with release of 4.7 which might require you to re-arrange your code.
Thank you for your patience while we attempt to troubleshoot your issue.
Is this issue still occurring for you? We have not been able to reproduce it yet here, but we may be setting things up slightly differently. If you are still experiencing this issue, would you be able to provide a small sample project demonstrating issue?
I will be marking this issue as resolved for internal tracking purposes, but please feel free to add a comment at any time to re-open it.
I did not mean for you to search for that one commit that introduced problem in 4.7.