Say which objects cast a shadow and which receive one.
stageScene validates a light's castShadow and refuses shadow settings without it; the render inventory counts casters and its budget constrains that count. buildLight applies the flag and shadow camera settings, while applyRendererEnvironment sets the renderer shadow policy reversibly. This adapter supplies the remaining mesh participation flags; enabled maps and casting lights alone do not make a mesh participate.
That absence is not visible as an absence. A benchmark authored a fascia and
soffit band with a deliberate dark recess above the wall, and the darkening
reads as a shadow in every captured frame while being nothing but geometry
and material response to light direction. Building the appearance out of
geometry is what an author reaches for when the mechanism is missing and no
gate says it is missing.
The requirement asks for caster and receiver to be distinguished rather
than blanket-enabled, and the product knows the difference at exactly one
place, which is here. A model's parts are solids: they cast and they receive.
The standable surfaces under SPACE_GROUP_NAME are open patches for
structural guides and optional flat color. They neither cast nor receive.
A volume-free patch casting onto its own plane produces depth acne, and its
basic material has no shadow response. Objects without geometry are untouched.
Exported, and separate from buildScene, for the reason
applySceneFog is: a host that assembles its own scene graph — a
production's film page, which is what the offline renderer captures — must
make the same call, or it captures a production whose shadows were declared
and never drawn.
A scene that declares no shadows is unaffected. three.js compiles no shadow
code and renders no depth pass while renderer.shadowMap.enabled is false,
so these flags are inert until a production turns shadows on, and only such a
production sees its frames change.
Say which objects cast a shadow and which receive one.
stageScenevalidates a light'scastShadowand refuses shadow settings without it; the render inventory counts casters and its budget constrains that count. buildLight applies the flag and shadow camera settings, while applyRendererEnvironment sets the renderer shadow policy reversibly. This adapter supplies the remaining mesh participation flags; enabled maps and casting lights alone do not make a mesh participate.That absence is not visible as an absence. A benchmark authored a fascia and soffit band with a deliberate dark recess above the wall, and the darkening reads as a shadow in every captured frame while being nothing but geometry and material response to light direction. Building the appearance out of geometry is what an author reaches for when the mechanism is missing and no gate says it is missing.
The requirement asks for caster and receiver to be distinguished rather than blanket-enabled, and the product knows the difference at exactly one place, which is here. A model's parts are solids: they cast and they receive. The standable surfaces under SPACE_GROUP_NAME are open patches for structural guides and optional flat color. They neither cast nor receive. A volume-free patch casting onto its own plane produces depth acne, and its basic material has no shadow response. Objects without geometry are untouched.
Exported, and separate from buildScene, for the reason applySceneFog is: a host that assembles its own scene graph — a production's film page, which is what the offline renderer captures — must make the same call, or it captures a production whose shadows were declared and never drawn.
A scene that declares no shadows is unaffected.
three.jscompiles no shadow code and renders no depth pass whilerenderer.shadowMap.enabledis false, so these flags are inert until a production turns shadows on, and only such a production sees its frames change.