I have a simple minimap capture blueprint. It’s just a SceneCaptureComponent2D, linked to a render target asset, and set in orthographic mode.
I also use world composition, and the problem I’m seeing is that, when a sub-map contains this component, even if it’s centered on the landscape tile, the bounds for the landscape tile becomes gigantic.
Here are the bounds with the blueprint in the world, in the center of the tile:
I have not explicitly set any bounds on this component or actor, and I’ve even tried reducing the net relevancy distance (which I don’t use) to 0, and it’s still this big thing.
Here’s the setup of the capture component. (Note that the camera itself is rotated down 90 degrees, so it comes into the right orientation when I drop the blueprint in the world.)
This is super easy to reproduce. Add a SceneCapture2D component with orthographic size to a blueprint, add the blueprint to one streaming level, see the bounds of the level expand bigly, as seen above.
I’d like to add that the scene capture component doesn’t seem to have the “relevant for scene bounds” checkbox that actors with collision have, so there doesn’t seem to be a way to turn off the expansion of the level bounds this way.
So how do I make it reasonably-sized?
For what it’s worth, I don’t know why adding these actors expand the level bounds, and why there’s no flag to turn off that behavior on the specific actors.
I ended up setting the bounds manually, which is kinda onerous and cheesy, but gets the job done for now (and adds untold opportunities for future bugs and friction and forgetting to do it right.)
