Research & development
Engineering articles from Ashley Kalkowski, creator of Guassia. Explore Gaussian world authoring, asset creation, rendering quality, project preservation, and the work of delivering usable creation tools.
Each report develops a specific engineering question from Guassia’s documented work. The collection connects a creator’s goals with publicly described capabilities, observed behavior, limitations, and the tests that would support stronger conclusions.
The articles are published now as retrospective reports. Their development periods describe the earlier work; they do not backdate publication. Original research and upstream technologies are credited in the references. An application workflow or integration is a project contribution, while scientific novelty needs a separate comparison with prior work.
Guassia was created and directed by Ashley Kalkowski. Its development includes AI-assisted engineering and collaborator contributions. These reports record that work without distributing proprietary source code, unpublished algorithms, private data, or third-party assets.
The collection
Report 01 · September 17–19, 2026
Ashley Kalkowski’s documented early Guassia history: procedural music visuals, Gaussian scene integration and the first preserved development checkpoint.
4 min read · Ashley Kalkowski
Report 02 · September 19–27, 2026
An engineering account of source preservation, object editing, working copies and portable projects in Guassia, with documented scope and limits.
4 min read · Ashley Kalkowski
Report 03 · September 19–24, 2026
An engineering report on editable Guassia project archives, private playable exports and optional self-hosted voice, with explicit portability and networking limits.
4 min read · Ashley Kalkowski
Report 04 · September 20–24, 2026
Why Guassia's editor begins with open ground, keeps creative systems optional and separates authoring views from gameplay cameras.
4 min read · Ashley Kalkowski
Report 05 · September 20–24, 2026
A scoped account of progression, creator-controlled NPC behavior and bounded gameplay rules in Guassia's Gaussian world editor.
4 min read · Ashley Kalkowski
Report 06 · September 19–20, 2026
How Guassia's public sound workflow connects reactive components, spatial cues, room transitions and portable projects, with explicit testing limits.
4 min read · Ashley Kalkowski
Report 07 · September 23–27, 2026
A Guassia engineering report on authored, committed, resident and preview Gaussian counts, with bounded public observations and a proposed evaluation plan.
4 min read · Ashley Kalkowski
Report 08 · September 20–30, 2026
An engineering report on separate creation apps, visible release states, learning guidance and problem reports, distinguishing delivery from acceptance and adoption.
4 min read · Ashley Kalkowski
Report 09 · September 27–29, 2026
A Guassia engineering report distinguishing an optional static WebGPU asset preview from an ANGLE Vulkan desktop backend, including fallback and validation limits.
4 min read · Ashley Kalkowski
Report 10 · September 27–29, 2026
A creator-workflow report on parametric Gaussian parts, reversible deformation, native sculpting and World import, with finite editing and appearance limits.
4 min read · Ashley Kalkowski
Report 11 · September 27–29, 2026
A Guassia engineering report on inspecting Gaussian surfaces near the camera, equal-count synthetic comparisons and the limits of output-resolution controls.
4 min read · Ashley Kalkowski
Report 12 · September 27, 2026
A careful report on public Asset Engine unit controls, dimensions, measurements and approximate STL export, separating inspection from manufacturing validation.
4 min read · Ashley Kalkowski
Report 13 · September 24, 2026
A practical guide to Guassia's documented native GChar animation support, the static GLB import route, NPC movement, portable projects and validation limits.
6 min read · Ashley Kalkowski
The public timeline links milestones to their original release records. It keeps source checkpoints, functional checks, and public delivery distinct, so a planned capability does not become a claimed release.
Open the timeline