Hmm, I had overlooked [FONT=courier new]StaticMeshComponent’s [FONT=courier new]GetLocalBounds function. Not sure how I missed that, but oh well. That’s probably the function that Aoredon is looking for. Thank you for pointing that out.
As for the use case … the issue isn’t knowing the size before spawning, it’s knowing the size *without *spawning. I see this mostly happening with procedural generation that has optional content. For instance, let’s say you have a blueprint that creates a dungeon room and its decorations. The level designer places the blueprint in the world and sets the size of the room. The blueprint takes care of filling the room with tables, torches, and other decorations. Before the blueprint can place a decoration in the room it has to know if it can fit (due to the room’s size and other decorations it already spawned). It could randomly pick a decoration, spawn it, get it’s size, and then possibly delete it if it doesn’t fit. But, it would be better to avoid the spawning if the object isn’t going to be used.
But, I agree with you, this isn’t a typical use case.