What’s changed in Iron Grid.

• An unavailable saved model leaves the selection empty and asks you to choose explicitly. It no longer substitutes another model.
• Your exact saved choice is restored when it becomes available again.
• Focused selection checks and native builds passed.

Validated in the local development build. This change is not announced as part of the current 0.1.9-alpha installer.

• The workbench provides compact and expanded layouts, searchable Problems, and theme-readable tabs.
• Inline suggestions and Explain, Rewrite, and Fix actions preview code before you accept it. Accepted changes use normal Undo.
• Suggestions are checked against the current project, source buffer, and selected range before applying. Editor, Roslyn, live request, and Undo checks passed.

Validated in the local development build; no new installer was published for this checkpoint. Connected assistance uses Smelty usage.

• Export settings and reports show the unsigned-build warning. Choosing Release or Shipping alone does not request signing.
• Sign for distribution uses the game developer's own configured publisher identity. The editor's signature does not sign exported games.
• The signing workflow checks the game, installer, uninstaller, dependencies, and final package receipts. It rejects failed signing instead of quietly publishing an unsigned result.

Local development checkpoint, not a new published installer. Signed end-to-end acceptance still requires an explicitly authorized developer identity and qualification of unsigned dependencies. Windows controls whether a recipient gets a warning or a block.

• DirectX 11, DirectX 12, and OpenGL now use the same authored-color, linear-light, exposure, and display conversion contract in the checked built-in lit path.
• Real GPU reference cases and packaged-player checks passed on all four forced rendering backends.
• An OpenGL depth-clear issue was also corrected.

Validated development checkpoint; no new installer published. This does not establish full lighting, shadow, terrain, or representative-scene parity across backends, and startup performance remains under review.

• Smelty retains the original request, saved progress, and later instructions during corrections or account renewal. Built-in character-controller playtests no longer require an unrelated script change.
• Free-account tasks use included usage and additional Smelty Tokens without the old task-count limits. Stopping a task retains saved work and records usage already incurred.
• Rig Studio conversion preserves supported imported skinning, joints, UVs, and embedded animation clips. Model previews and material changes keep the data needed to render the character.
• Exported games get fixes for standard materials, health and UI values, Shift/Control/Alt input, and checks that animated vertices actually move.

The replacement installer is still 0.1.9-alpha. If you already have that version, download and run the replacement manually. Focused Smelty, editor, and exported-game checks passed; broader scene and hardware testing is ongoing.

• C# and visual-script builds use the compiler and .NET runtimes bundled with the editor. Release and Shipping exports no longer need a developer checkout or a machine-wide .NET SDK.
• Exports check the actual game executable and bundled tools. If publishing an export fails, the previously delivered game is preserved.
• Hosted Smelty tasks use included usage and additional Smelty Tokens, without the former monthly task/edit counts or separate per-task spending caps. Usage accounting and service spending limits still apply.
• Smelty supports selecting text across messages and activity results, with clearer work summaries and fixes for rig attachments.
• The launcher has refreshed artwork. A new editor profile follows Windows light or dark appearance; saved preferences take priority.
• Downloads validate release details, feedback has size and account limits, and website dependencies include security updates.

This is an alpha testing release. Hardware and content coverage vary, and large world-building scenarios still need performance work. Paid Smelty upgrades and asset generation are not open for purchase.

• Native .igstage assets now use schema 5. Importing targets that format; retired V4 migration code and old .stage fixtures are removed.
• The profiler measures the active Runtime view. A performance test scene covers baseline, large static scenes, physics, and mixed content.
• The Stage grid reuses its fading rings. Timing separates rendering, presentation, and Vulkan work to help locate hitches.

These are repeatable test scenarios, not published FPS claims. Fresh measurements on real hardware remain necessary.

• C# can read local and world positions and rotations through the object hierarchy. Incremental rotation uses degrees without rebuilding the pose from display angles.
• Rotation conversion was corrected around an angle that previously caused problems, with checks in the editor.
• Move snapping starts disabled and uses one metre by default. Ctrl toggles it during a drag; Reset Snap Defaults restores the standard settings.

For existing C# projects: raw RotationX/Y/Z/W access was removed. Use the vector and quaternion properties and recompile.

• Before writing C# that depends on the engine API, Smelty checks the current SDK types and documentation.
• Corrections retain completed checkpoints and stop repeated failures within explicit limits.
• Keyboard input and capture preparation were repaired. A Smelty-authored C# Snake game passed fourteen gameplay checks, with controls checked in the editor.
• Expanded task plans can be copied so you can read the objective and work steps.

Smelty’s connected service updates separately from the engine download. This checkpoint did not announce a new installer.

• Repeatable tests now cover more animation clips, state machines, rigs, terrain, and foliage.
• Checks for animation dependencies and packaged projects are stronger.
• Smelty’s world-building reports distinguish created content, saved content, and results actually checked in Play mode.

Large animation, terrain, and forest requests still need more testing. Small passing samples don’t cover every content combination.

• More representative rig shapes received focused behavior checks.
• UI and Visual Scripting tests cover more authoring scenarios.
• Smelty’s plan-first scene building and playable Pong workflows were exercised.

The checks apply to those scenarios. The visual-graph API and broader content coverage are still growing.

• Select terrain to see its brush operation and stroke settings beside the Stage.
• Terrain Properties keeps the underlying data and surface layers, with fewer duplicated brush controls.
• A Vulkan resource-allocation issue affecting materials was fixed and checked.

Repeated brush strokes still needed interactive testing at this checkpoint.

• The built-in editor reads public types, signatures, and documentation through Roslyn.
• Completion replaces the intended text, including snippets for overriding behavior methods.
• The packaged language service includes the managed API’s documentation.

C# leads the code examples. Python remains supported; existing projects are not converted automatically.

• Project Settings groups keyboard, mouse, and named controller bindings, with recording and explicit Unbind controls.
• A live controller display shows buttons, axes, and their mappings. Existing bindings change only when you apply new defaults.
• Windows export tests checked scene mappings, packages without source files, moved packages, and tamper detection across renderer paths.

Controlled export tests don’t replace testing on a clean external machine or cover every project.

• C# gains behavior callbacks, entities, transforms, input, physics, UI, audio, and timers.
• Editor Play and exported games run through native simulation with a private managed runtime and game-data checks.
• Existing Python scripts stay in their own language.

C# and Python parity remains ongoing work. This records the foundation, not a guarantee for every existing script.

• Smelty’s completion checks require actual changes, saved work, and factual reports.
• Scene and package checks strengthen how content moves from the editor into exported games.
• Small projects helped identify fixes for input, script attachment, game display, and asset handling.

Published release notes above record what went out to testers. Downloads provide the current release.