There should be some kind of error for spawning a scene handle without a `SceneBundle`.

[mintlu8]

What problem does this solve or what need does it fill?

This is very confusing because this "successes" in release mode and spawns the mesh in a broken state without transforms. On debug mode there are hierarchy errors regarding transform and visibility, but not present in release mode.

What solution would you like?

Log an explicit error for trying to spawn a scene without a Transform or Visibility component, even in release mode.

What alternative(s) have you considered?

Keep things as is.

[alice-i-cecile]

#1481 would present one possible solution to this problem.

A second query checking for this in the scene spawning system would work fine, but I'm not sold that this should be present in release. And in debug mode only, there's no additional benefit.

[mintlu8]

I think this still warrants a standalone warning since

• spawning other things like sprite or text without incorrectly will not display anything at all, which gives clear indication of an error occurring.
• it's a cheap check done once on a relatively expensive operation (spawning a scene)

I'm not sure how if or how we support release mode debugging so I won't comment on that.

[alice-i-cecile]

it's a cheap check done once on a relatively expensive operation (spawning a scene)

This is compelling! If we can figure out how to: a) not meaningfully slow down the happy path and b) ensure that we don't get spurious warnings when users are using scenes for non-spatial objects (think a preferences entity or something) I'm on board.