Greetings!
I have the following blueprint function:
I’m using it to spawn instances of a level, like this:
When I’m executing this function all seems to work alright, as long as I’m passing Locations along X axis, for example: (1000, 0, 0), (2000, 0, 0), (3000, 0, 0) and such. When I pass anything along Y axis, like (0, 1000, 0), the level does not spawn, and as soon as I close the game the entire editor stops responding. There’s no error in log and debugging the blueprint also didn’t report anything wrong.
What’s even stranger, the crash doesn’t happen always, but only if the Y-offset level is loaded in any other order, but the first.
Few examples:
-
levels spawned from (0,0,0) and then along X axis
-
single level spawned along Y axis
-
level spawn on Y axis and then 3 more spaned along X axis
If more than 1 level is spaned along Y axis, the editor stops responding. If a level is spawned along Y axis in any other place than first in the chain, the editor stops responding, too.
In those scenarios, only the first level will spawn. Even in a situation when the Y-align level would be, for example, 4th in the chain, only first level will spawn and the editor will freeze when the game is closed.
No, I don’t really believe that it’s indeed the problem of axis, but that’s the simplest way from me to explain the problem. For the life of me I cannot figure out what could be causing a problem like that, though.
I’ve attached a LevelSpawning.zip archive with an example project.
I hope someone will be willing to explain what’s it is I’m doing wrong.