Skip to content
Vrynthia ecosystem
Menu

Journal

Studio notes

Releases, infrastructure changes and the occasional post-mortem. We write when there is something to say, not on a schedule.

  1. Three gateways, one edge

    External traffic now lands on three hostnames instead of one: the cloud rendering gateway, the binary build repository and this hub. All three are routed through the Amsterdam edge; documentation, endpoints and this site keep their structure. The split was planned for months — it makes the review streams and the build distribution independent of each other, so a heavy QA drop no longer competes with a producer pulling frames.

  2. Aethelgard master build v0.9.4 enters closed QA

    The first build with the rebuilt residency compiler is out to internal QA and two partner studios: 54.2 GB, Win64 and Linux, checksums published with the archive. Frame pacing on the northern citadel sequence is the main thing we are watching — the scene streams 4.1 GB of geometry into a 900 MB residency budget, and the compiler is now cutting pages by predicted camera path instead of by level chunk.

  3. Companion app beta: queue, push, offline logs

    The Android and iOS companion app is in partner beta. It shows the render queue, sends a push when a build turns green, and synchronises debug logs in the background while the device moves between Wi-Fi and mobile networks. The synchronisation is chunked and idempotent, so a capture survives a train ride through four dead zones without re-sending a single byte.

  4. Vrynthia Engine v4.2 shipped

    v4.2 is the version our productions are now built on. Deterministic simulation is enforced across the whole tick, the residency compiler moved out of the editor into a separate toolchain, and the render bridge finally shares one shading model between local frames and cloud frames. Two years of work, and the first release where a QA bug report replays identically on three machines.