Skip to content

Move all engine demos into standalone technical examples - #1

Merged
SpectralDragon merged 4 commits into
mainfrom
codex/procedural-rig-technical-example
Nov 4, 2026
Merged

SpectralDragon merged 4 commits into
mainfrom
codex/procedural-rig-technical-example

Conversation

@SpectralDragon

@SpectralDragon SpectralDragon commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Collect all eleven engine Demos projects under Examples/Technical: the procedural skeleton study plus A2UIForm, AndroidDemo, LinuxSmoke, MovieMaker, Navigation, Physics2D, SpineNative, SpinePreview, Sponza and SpriteInstancingValidation.

  • Add ten standalone SwiftPM packages with explicit source/resource membership and pinned remote engine dependencies. Windows Spine/MCP local overrides remain explicit opt-ins.
  • Pin packages and the Sprite XcodeGen spec to engine extraction commit a624ccded0a050fddc24ccfbb8079dfb8032805c in Ada PR #207.
  • Move native launchers and preserve executable Git modes/LF endings. Keep generated builds, logs, captures and machine-local state ignored.
  • Bundle Sponza camera-route metadata while keeping its large dataset external. Preserve the Android resource-bundle name and Sprite WASI reactor/export flags for the new packages.
  • Preserve upstream Spine assets and license notices; omit stale Package.resolved files.
  • Keep Technical outside catalog.json. Its four public items, website/Studio recommendations and catalog release archive inputs are unchanged. The validator rejects technical paths, including normalized ./ and ../ aliases.
  • Document project-specific commands and explicit engine/examples checkout variables. Add a manifest/source/resource/product validation command.

Validation

  • Public catalog validates; two exclusion tests pass.
  • Ten package manifests evaluated using actual SwiftPM, with source/resource existence and engine product checks. This does not build or resolve every platform application.
  • Compiler-free procedural recipe generation and independent GLB checks passed.
  • Python lint/compilation, Bash syntax, shell Git executable modes and diff checks passed.
  • Cross-repository checks: 16 Android tooling tests, four SDK staging tests and 25 offline guides passed; external Sponza validation staging preserves camera tests and assets.
  • Independent migration review found no remaining concrete issues after correcting path handling and preserving linker settings.

Full native/device/WASM execution and complete engine/Studio validation remain separate and unverified. Technical packages are opt-in developer tools, not all editable Studio game projects. The engine removal is tracked separately in PR #207.

Technical section

@SpectralDragon
SpectralDragon marked this pull request as ready for review November 4, 2026 10:55
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-04T11:28:56.237333Z c33c6e2 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dea1aec56f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

entities:
- id: camera
name: Camera
enabled: false

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Enable the playback camera in both example scenes

When running the committed scene, its only camera entity is disabled, so the authored camera and its environment settings cannot participate in runtime rendering despite AdaRender.Camera.isActive being true. Sources/Game.ada contains no code to enable it or create a replacement. This prevents the documented open-and-Play flow from displaying the intended preview independently of an editor-provided camera. Enable this entity in both Walk.ascn and Showcase.ascn, which has the same disabled-camera setting.

Useful? React with 👍 / 👎.

@SpectralDragon SpectralDragon changed the title Add opt-in technical examples and procedural AdaScript rigging study Move all engine demos into standalone technical examples Nov 4, 2026
@SpectralDragon
SpectralDragon merged commit 74f0702 into main Nov 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant