Skip to content

Report renderer-only scene intent and reject unsupported execution requests #887

Open

Description

@JeanPhilippeKernel

Context and problem

M2 implements a renderer-only standalone path; StandaloneRuntimeApplication::ShouldSimulate() keeps gameplay simulation disabled. Issue #873 also asks the runtime to report RendererOnly intent and inactive simulation data explicitly, and to reject attempts to request unsupported execution. The behavior and reporting contract has not been verified end to end; the existence of a disabled simulation flag alone does not establish that users and callers receive an unambiguous result.

Work

  • Audit the standalone and editor-hosted cooked-scene entry points, scene reconstruction and diagnostics. Identify what is rendered, what authored gameplay/actor/physics/audio data is retained but inactive, and what requests for execution are currently expressible.
  • Define a clear, stable representation or diagnostic for renderer-only loading and inactive services at the appropriate caller/user boundary. Distinguish intentionally inactive optional data from required unsupported capabilities.
  • Reject any explicit request to activate an unsupported required service before publication; report the reason and preserve the outgoing scene and request outcome. Do not add gameplay services or claim M3 Play support as part of this task.
  • Document how the runtime API and launch path communicate their supported mode, and keep compatibility with the existing source/editor loading policy.

Acceptance and verification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2High priority — next sprintarea-renderingenhancementNew feature or requesthelp wantedExtra attention is needed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions