Open Level node shows black screen with throbber in packaged game

In packaged game (I tested on Android) Open Level node shows black screen with default throbber in right bottom (in picture below). It is not an issue for me, but I’d like to customize this screen a little bit, just change throbber image to my own. Is there a way to change something in this screen?

When you use OpenLevel, usually a Widget is being opened to display this loading screen.
You can search up the widget and customize it. It works like any other widget.

When OpenLevel is done, from the execution pin, you could remove the widget. Or from a Begin Play (in the player for example), you could use the “Get All Widgets of Class” node to find any loading widgets and then remove them from parent.

I think it is miscommunication, I don’t place this widget, it is appearing automatically after calling Open Level node and automatically removed after loading is done.

If its there “out of the box”, it would mean that this is a pre-made project.
Can you share more information about your project?

I did a bit of research and found a place of problem. I have level with sublevel with a lot of objects and sublevel has options init loaded and init visible. In this case after load parent level I see screen load screen from my first message.

So, When I have moved all objects to one level, remove sublevel and black screen with loader don’t appear

I wish there is just an option to remove it completely when you place the open level node, not sure why Unreal thought everyone would want that and not have an easy way to change it. i’m not going to mess with my sub levels because they are setup correctly so how else can I remove the throbber?

The open level node is an engine source code file, I can’t open it and see which widget is being created so I can’t remove that throbber. Do you know which widget it is within the engine folder by any chance? thanks.

anybody?

So I didn’t really understand what the solution meant, after many hours now i realise what he meant lol, it was being caused by the fact i had ticked initially loaded in the levels detail panel for my “lighting” level, to fix this simply load through the level blueprint so it’s not a blocking load.