Skip to content
AETHRA Game engine · Product

AETHRA Engine

A real-time engine and editor built on Godot, focused on workflow, rendering research, and safe automation.

Evidence stage
Evidence stage: Prototype
Status
Active development · Internal builds
Research domain
Simulation & Real-Time Systems

01 · Problem statement

General-purpose engines are powerful but carry a steep learning curve, and the tools around them were not designed for automated agents that edit scenes and code. Meanwhile, newer rendering techniques such as hardware ray tracing are available on consumer GPUs but are difficult to adopt inside an existing renderer without risking stability.

02 · Research motivation

A real-time engine is a demanding environment for Aporen's broader questions: every frame has a fixed computational budget, and an editor is a complex, stateful system in which both people and software agents need to make changes safely. Building on a mature open-source foundation lets the work focus on those questions rather than on re-implementing an engine.

03 · Technical direction

  1. A

    Editor workflow

    Faster scene creation, progressive disclosure in the inspector, and first-class English and Russian localization, while keeping project formats compatible with upstream Godot 4.

  2. B

    Rendering research

    Hardware ray-tracing experiments built on public engine APIs and measured against a fixed baseline scene before any engine changes are made.

  3. C

    Agent-safe tooling

    A local bridge through which external agents propose scene changes as transactions that are validated, previewed, reviewed, journaled, and reversible.

  4. D

    Polyglot development

    Language services that report real toolchain status for GDScript, C#, C++, and Lua, and a native C++ component workflow inside the editor.

04 · Current verified status

  1. 01 Hypothesis
  2. 02 Experiment
  3. 03 Prototype (current stage)
  4. 04 Validated
  5. 05 Released

Prototype: Working software exists and is tested internally. Its central claims are not yet validated.

Verified

  • AETHRA is a fork of Godot Engine 4.7.2-stable under the MIT licence, with upstream copyright notices preserved and upstream project formats kept compatible.
  • Implemented and covered by automated tests: Quick Create and lighting presets, a basic/advanced inspector, scene-management actions, EN/RU localization, AETHRA identity, Linux x86_64 packaging with its own export templates.
  • An agent bridge with journaled transactions, crash recovery, and an AI Studio panel that connects to external model providers. End-to-end tested with a local model.
  • A hardware ray-traced shadows prototype, implemented without engine changes. Its evaluation concluded that it needs further iteration before integration.
  • An internal rendering baseline shows no measurable difference from upstream Godot on one test scene and one GPU, within run-to-run variation.

Not yet done or demonstrated

  • The source code and builds are not yet publicly available.
  • Windows and macOS builds have not been produced or tested.
  • The ray-traced shadows are a prototype and not part of the default renderer.

Status source: AETHRA repository documentation (progress log, roadmap, renderer research plan). Checked .

05 · Known challenges

  • Fork maintenance

    Tracking upstream Godot releases while carrying editor and rendering changes.

  • Rendering integration

    Ray-traced visibility must be integrated into forward shading rather than applied as a post-process, which the current prototype does.

  • Platform limits

    Some techniques depend on GPU features the current rendering abstraction does not expose, such as mesh shaders and inline ray queries on Vulkan.

  • Agent safety

    Automated edits to projects must remain reviewable and reversible under failure conditions.

06 · Next milestones

  1. M1 Integrate ray-traced visibility into forward directional-light shading, with soft shadows and a native acceleration-structure manager.
  2. M2 Visual asset browser with previews and drag-and-drop scene insertion.
  3. M3 Windows build and test coverage.
  4. M4 A decision on public source availability and release channel.

Milestones are planned work, listed in intended order. They are not dated commitments.

07 · Public resources

No public resources yet. This page will link to them when they exist.

References

External work this project builds on or compares against. Listing does not imply endorsement or affiliation.