LEARNING GUIDE

Camera composition order: do not advance render-only state twice

draft illustrative

Origin: original-commentary · review: draft · snapshot: 3ba1c69afc74a97f-7fcd0798fd6ea455

The release documentation carried by the metadata describes camera composition

as a tick-phase operation. The exact wording and source location remain tied to

the pinned records; this note paraphrases it so it is clearly original

commentary rather than imported upstream prose.

When a camera is composed as part of the normal scene tick, a later render pass

should consume that settled view. Calling composition again from repeated

portal rendering can advance or overwrite state that should be observed only

once. If a custom pass renders without ticking the scene, an explicit compose

step may be necessary, but that branch must be tested independently.

Keep the distinction visible:

`ComposeView` is a declaration about camera-view preparation.

`UpdateSceneCamera` copies camera settings into a scene-camera object.

`RenderToTexture` is a separate render-to-target operation.

Their names do not prove a particular order in the installed build. The

workflow and source evidence should be read before using them together.

Constraints and verification

Evidence hash: afdbf5cb11590440a0f458f2e0b905779b9b037cc22116a10943affa475872ff
Compile/runtime verification: illustrative

method:Sandbox.CameraComponent:ComposeView()
method:Sandbox.CameraComponent:UpdateSceneCamera(Sandbox.SceneCamera,System.Boolean)
method:Sandbox.CameraComponent:RenderToTexture(Sandbox.Texture,Sandbox.Rendering.ViewSetup)