You broke nothing so long as you manually unload levels, or you do not rely on the fact that “starting again will start clean” in any way shape or form.
I’m guessing that the proper way to handle calling the flush anyway would be to move the functions where they should be - in an Async method where the processing doesn’t cause blocking of any sort.
It would work, because as you demonstrated by commenting things out, stuff works even if the function call never existed…
Idk what edjit at Epic is coding level loading stuff in a game blocking thread in the first place to the extent they even comments to the effect of having to “wait”… but then again, there is your proof - for the nth^n time - that epic doesn’t know what the f they are up to…
Just chalk it off as yet another reason anyone and everyone should just stay away from world Partition…
World composition sure has its issues, but none of them are this basically flawed…
Either way, kudos for sharing.
Even if you should go back and just use world composition instead 