Lag spike first time i set level as visible but no more lag spike if i do it multiple times by hiding and rehiding… Only first time i get a hitch. All levels are loaded from the start but hidden at the start… i am triggering them to hide or show based on location with trigger boxes…
As i said it starts hidden, and first time i make a level visible it gives me a lag spike, but if i trigger it to hide and then trigger it to be visible again it is no lag spike (only first time…) why? Anyway to fix it?
Maybe the first time takes longer because it wasn’t visible so he might cache it for future views. You can maybe hack it by making it visible and then hiding it again on the loading screen.
On the level details you set all of the levels to be visible and on begin play you create an array of map names and make them all hidden with the should be visible you did previously.
Copy that and paste that into the level blueprint’s begin play event and connect the execution wire to the for loop. On the Make Array node you have a few None’s, replace them with your level names.
This doesnt seem to work for setting my sub levels invisible that are set by name… Seems like they all still start visible… this doesnt make anything invisible at all…