Documentation Scope

Guides and reference entries are updated separately. Before following a guide or using a reference entry, read the version, build, and edition limits stated there. Use Using This Manual to find the page for your task. Tutorials and Recipes take you through complete builds.

Development builds can share a version label even when an update changes the controls. When a page differs from your installation, record the build you’re using along with its version and edition. Those details help identify the behavior.

What the Reference Covers

Use Technical Reference to look up engine entries: Actions explain inputs and results; Events describe triggers, filters, and context fields. Object Components covers property paths and supported Object types. For the related workflow, follow the Resource Directory link to the guide.

Edition, dimension, and feature visibility determine which choices are offered, and optional packs can add their own entries. Read the entry’s requirements. Before leaving a field blank, check its description; the meaning varies between entries.

Examples and Images

An example check establishes a result for its tested setup and build. Reference entries and examples need separate checks.

Images capture a particular project, and their visible values may belong to that example. Read the field description to find the default. Figure labels locate the controls.

Report a Mismatch

When a page and engine differ, send the details through the available support channels. Include:

• The page URL, the instruction or field that differs, and the steps you followed.
• Your engine version, edition, and downloaded build.
• What you expected and what happened.

For a runtime problem, include a small project that reproduces it. Keep the setup focused, say which Scene to open, and describe the action that triggers the result.