I’ve found very weird behaviour in Load Stream Level node and I would like to ask about it.
I’ve been following this tutorial from Mathew Wadstein: HTF do I? Loading Screens using Level Streaming in Unreal Engine 4 - YouTube and actually everything is working fine. Well, everything except one thing. Sometimes I have to type in level name manually in the “Load Stream Level” node to make it load. If I connect name variable from game instance (containing level name) nothing happens. Screen gets black (from persistent level).
I was trying to find what is causing the problem but I failed unfortunately. Even “Print String” node (connected right before “Load Stream Level”) is showing proper level name, but still nothing is happening. Do anyone had same/similar problem before or know why is this behaving like this? Thanks for any help.
Print string is showing name variable straight from the global instance, and it’s the same thing that goes into “Load Stream Level”. Name is correct and it is a part of the persistent level (it’s main menu of my game and it works while loaded for the first time, when going back from mission - black screen -_- ). I have several more maps, all of them are loading in same way, and taking level name from global instance works perfectly. Problem occurs only with this specific level, that’s why it’s weird. I’ll dive into it after work, I hope it’s just my stupid mistake somewhere…
I got the exact same strange thing. While other levels can be feeded from a separate source ( FName variable at least, or my intended level managing system), one level just won’t load. The print node right behind is called nevertheless.
To load this one weird level, i have to write the name of the level into the node, while other levles work as normal with FName variable.
Is there a known solution to this problem meanwhile, or do i miss something?
Also, i think of creating a new level and move all actors over as a workaround. Is this a viable (or the only) solution?
Small update: creating a new level and moving all actors over isn’t solving the problem. It still can be loaded only if the level name is explicitly written in the Load Stream Level node, otherwise nothing loads. Its still just one of the levels that behaves in that strange way.
