I actually did find a solution, and that for me it was caused by messages being printed to screen early when a level was loaded.
In shipping builds, there is no issue because printing to screen is disabled.
For a quick fix and testing for development builds, there is the option of disabling screenmessages via a “DisableAllScreenMessages” console command on GameInstance initialization.
A more solid fix would be to just make sure nothing is printing to screen at the beginning of a map load.
4 Likes