What changed in Guassia, what we tested, and what still needs work.
Last updated · Dates use America/Denver.
How to read release dates and status
Dates use America/Denver. Source checkpoints, local tests, historical delivery and newly verified delivery are recorded separately. Older entries were reconstructed from dated source and QA records; no earlier public release date is inferred from a commit alone.
“Included with this site release” describes the features shipped alongside this page. “Verified public release” records a separate public-destination check. Reconstructed historical entries keep their original source and delivery evidence; we do not backdate new work.
Included with this site release
Private hosted onboarding compatibility
Added support for an additional hosted onboarding address returned by the payment provider.
Source checkpoint 8d9bbc9f73b1dc9e0aa4214ca7d656675f6fed81Source availability and destination verification are separate.
What changed
The private seller flow recognizes the provider’s additional secure onboarding route.
Recipient identity, expiry, URL structure and sandbox-only restrictions remain verified.
What was checked
Local checks cover both supported routes and reject substituted accounts, altered hosts and malformed addresses.
Known limits and unfinished work
Public purchases and live seller payouts remain disabled.
A working onboarding link does not establish seller eligibility or a bank payment.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Groups fresh authorization and accounting queries and corrects the private onboarding request without changing financial eligibility or storage ceilings.
Local compiled guard checks · seller-contract.json
Local synthetic checks, not payment or payout qualification.
Private payment-provider compatibility
Included with this site release
Private payment-provider compatibility
Corrected two compatibility issues found while testing the private seller flow.
Source checkpoint 32f8e9b78f1b3b1927ebbbf627aaf47543c203bbSource availability and destination verification are separate.
What changed
Synthetic test recipients now include clearly marked test contact information.
Account reads use the payment provider’s documented query format.
Existing account-creation references, purchase records and download limits are preserved.
What was checked
Local integration tests cover the corrected request, strict response checks and safe retries. Actual provider results remain separate from local tests.
Known limits and unfinished work
Public purchases and live seller payouts remain disabled.
These changes do not verify a real seller’s identity or establish that money reached a bank.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Corrects synthetic recipient contact and indexed account-read parameters while preserving the existing creation reference.
Local compiled guard checks · seller-contract.json
Local synthetic checks, not payment or payout qualification.
Private seller and download testing
Included with this site release
Private seller and download testing
Improved private marketplace testing while public purchases remain unavailable.
Source checkpoint e1b740692fdca5d629f02b795c672fa7ce32c0c4Source availability and destination verification are separate.
What changed
Added a clearly labeled synthetic seller test that preserves the original asset and its license.
Improved handling of country codes returned during payment-provider testing.
Added a controlled, one-time allowance for private download qualification; earlier usage is retained.
What was checked
Local tests check account boundaries, download limits and seller accounting. These checks do not establish live payment or bank-payout readiness.
Known limits and unfinished work
Public sales and live seller payouts remain disabled.
A private test allowance requires a separate recorded approval; installing this update does not activate it.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Private seller and delivery testing · e1b740692fdca5d629f02b795c672fa7ce32c0c4
Preserves original purchases and isolates synthetic seller qualification.
Local compiled guard checks · seller-contract.json
Local synthetic checks, not payment or payout qualification.
Guassia — private fixture accounting correction
Included with this site release
Guassia — private fixture accounting correction
Private marketplace tests now require an explicit financial designation for the operator's own test asset.
Source checkpoint 1be667b919e1563afee78e8dfde7c42b6ab83cdbSource availability and destination verification are separate.
Clear ownership and accounting
Administrator access alone does not determine who earns sale proceeds. The private test requires an explicit designation and blocks a mismatched classification before delivery.
A narrowly scoped correction preserves the original test listing and its history. It cannot rewrite a purchase or seller payout.
What was checked
Local compiled checks cover the owner boundary, classification guards, existing account access and commercial holds. These checks use synthetic data.
Known limits and unfinished work
Public purchases and seller payouts remain disabled. This correction does not establish a successful payment or payout. Existing installers, update feeds and asset storage limits are unchanged.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Requires explicit financial designation and preserves the original test record.
Local compiled guard checks · classification-contract.json
Local synthetic checks, not payment or payout qualification.
Guassia — private setup diagnostics
Included with this site release
Guassia — private setup diagnostics
Owner-only checks now show which sandbox configuration prerequisite needs attention.
Source checkpoint d89ad0884c58ce95596b86c3664f63c415fa6f17Source availability and destination verification are separate.
Clearer private testing
The operator can identify a missing configuration or database prerequisite without revealing credentials or account details. Later checks may remain unverified when an earlier check fails.
What was checked
70 local regression tests passed, including authorization, all prerequisite checks and existing test purchase and delivery flows. Separate compiled-server checks preserve the access restrictions.
Known limits and unfinished work
This diagnostic does not confirm a successful payment or payout. Public paid commerce remains disabled. Existing installers and update feeds are unchanged.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Shares operational readiness checks without exposing configuration values.
Local authorization and readiness regressions · CHANGELOG-SANDBOX-READINESS-20261028.md
Local synthetic tests only; payment and payout outcomes remain unverified.
Guassia — isolated marketplace validation update
Included with this site release
Guassia — isolated marketplace validation update
Private sandbox checks now connect test purchases, approved assets and signed delivery while public paid commerce remains unavailable.
Source checkpoint da70dcb73f25482206337bb2a78965d433e77d31Source availability and destination verification are separate.
Private marketplace testing
The owner-only test workflow connects an isolated purchase to a reviewed private asset, explicit installation terms and signed delivery before seller settlement can be considered.
Sandbox checkout, funding, refunds and disputes verify the configured merchant and test mode before changing financial records. Incorrect or incomplete test configuration is rejected.
What was checked
309 local regression tests passed. Separate compiled-worker and migration checks preserve existing tools and hold live commerce. These are simulated checks, not live sales or confirmed bank payouts.
Known limits and unfinished work
Public purchases, public asset uploads and seller payouts remain disabled. Sign-in, free tool access, existing app installers and update feeds are unchanged. This is a server-only update; no new desktop installer is required.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
A server correction lets the current desktop app add reviewed free test assets to its Library.
Source checkpoint 9770b7de0fb6902fba234b11f2b31dd49b938bb1Source availability and destination verification are separate.
What changed
The private test service accepts the desktop app’s explicit zero-price request. Changed prices, malformed values and unknown fields remain rejected.
What was checked
19 local helper and route tests passed, including the desktop request format, repeat claims, original installation terms and signed delivery. These are local fixtures; production installation is checked separately.
Known limits and unfinished work
This correction does not enable public uploads, purchases or seller payouts. The desktop installer, engine versions, private access rules and storage limits are unchanged.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Accepts the existing desktop zero-price request while preserving private qualification rules.
Local compatibility checks · private-claim-compat-public-note.md
19 local helper and route tests passed. Native installation and production deployment are checked separately.
Guassia 0.5.34 — private asset testing and clearer review
Included with this site release
Guassia 0.5.34 — private asset testing and clearer review
Isolated private asset qualification, clearer desktop review states, and stronger transaction-accounting foundations. Public uploads, purchases and seller payouts remain unavailable.
Source checkpoint c513886aa6bd4ec2730b4146f1bafdc43d9736ceSource availability and destination verification are separate.
Private asset tests stay private
Internal test assets now have a separate release and library lifecycle. Completing a private qualification does not publish an item to the public store or create a sale.
Original asset terms still require explicit acceptance. Turning the test service off preserves normal library history and does not falsely mark a remembered offline license as revoked.
Clearer creator review
The desktop review flow distinguishes private qualification from public publication. Creators can see the submission result and current review state without a success message implying that an item is on sale.
Existing free creator tools and legitimate library items remain separate from the restricted test. Frozen accounts and exhausted test allowances cannot obtain new private access.
Commerce groundwork
Local accounting now tracks delivery evidence separately from purchases and installation acknowledgements. Seller settlement requires the relevant delivery records; an unfinished transfer does not become proof of installation.
Tests cover once-only credit refunds and reversal of the original platform and creator allocation. A credit refund is not a bank refund; refund-to-repurchase support and live processor integration still need further work.
What was checked
Focused local tests cover private upload, review, ownership, original terms, signed descriptors, full and partial package reads, and preservation of ordinary library history. They also check unauthorized access, revocation and held services.
Separate local accounting fixtures exercise delivery records, funding holds, duplicate requests, refunds and settlement eligibility. These are synthetic tests, not evidence of an actual Stripe sandbox payment, cash refund, seller transfer or bank payout.
Known limits and unfinished work
Public uploads, asset purchases, credit top-ups, seller payouts and game publishing are not enabled by this update. Existing small test limits and lifetime usage reservations remain in force.
Actual private provider delivery, desktop installation, normal updater operation and public deployment are verified separately. ASHVEIL Engine 0.5.31 and Asset Engine 0.1.14 remain unchanged.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Private asset lifecycle and accounting checkpoint · c513886aa6bd4ec2730b4146f1bafdc43d9736ce
Private test isolation, explicit review states and local delivery-accounting groundwork.
88 focused local regression tests passed. Accounting fixtures and actual public delivery remain separate evidence.
Guassia 0.5.33 — account readiness and clearer marketplace controls
Included with this site release
Guassia 0.5.33 — account readiness and clearer marketplace controls
Account-aware service checks, clearer upload and seller states, and easier-to-find update controls. This checkpoint prepares restricted asset testing; it does not open public uploads or purchases.
Source checkpoint 893bfc21bcb966346e6cde08f49029a7f92306e6Source availability and destination verification are separate.
Readiness follows your account
Signed-in service checks, catalog reads and asset preflights use the current account. Responses from an earlier account are discarded when the account changes.
Guest browsing and bundled local previews remain available. A failed asset-service check does not remove remembered offline libraries or make account access depend on storage capacity.
Understand what is available
Creator and seller panels distinguish checking, available and unavailable services. Upload controls explain current limits before opening a file picker; unavailable uploads stop before file selection or decoding.
Settings place update controls ahead of unavailable seeding options. The launcher keeps the existing desktop game engine and Asset Engine versions.
Prepare controlled asset testing
Restricted qualification controls keep unfinished asset workflows unavailable to other accounts during an explicitly enabled internal test. Public asset intake, hosted asset delivery, purchases and payouts remain disabled in this release configuration.
The asset submission path now reaches its existing validation checks correctly. Qualification keeps the small existing test limits and does not increase storage allowances. Account, draft and free-tool access retain their separate checks.
What was checked
331 local regression tests passed across launcher account handling, creator workflows and backend routes. Fixtures exercise account changes, held service states, submission validation and package delivery checks.
These are source tests with synthetic data. They do not establish a live purchase, public asset publication, production hosted installation or installation of this new launcher on another computer.
Known limits and unfinished work
Local tests do not verify a public download or installation. Release delivery and normal updater checks are recorded separately; a working configuration does not guarantee capacity or access for another account.
Public uploads, asset purchases, credit top-ups, seller payouts and game publishing are not enabled by this update. ASHVEIL Engine 0.5.31 and Asset Engine 0.1.14 remain unchanged.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Account and marketplace workflow checkpoint · 893bfc21bcb966346e6cde08f49029a7f92306e6
Current-account readiness, clearer creator controls and restricted internal qualification support.
Launcher and platform validation notes · CHANGELOG-OWNER-QUALIFICATION-20261026.md
331 combined local regression tests passed. Source tests and actual public delivery remain separate.
Guassia 0.5.32: a clearer path from asset draft to review
Verified public release
Guassia 0.5.32: a clearer path from asset draft to review
Creator drafts connect directly to private upload review. Current limits are shown before file selection, and content verification is prepared without opening paid checkout.
Open Guassia, sign in, then choose Publish & earn and set Listing type to Gaussian asset.
Save creator draft selects the saved asset in the upload step. Save on this device keeps a local draft only.
A saved draft or private upload is not a public listing. Submission does not charge a publishing fee or guarantee approval.
Use the actual upload limits
The bounded qualification profile allows 64 KiB and 1,024 Gaussians per review file. The app checks current limits before file selection and rejects oversized files before decoding them. Local Asset Engine capacity is unchanged.
Keep access and delivery separate
Verified accounts, free creation tools and available free browser games do not require paid checkout. Asset storage limits do not become a sign-in or free-tool download requirement.
Production content verification is prepared with a trusted release identity. Installation still requires a verified package and the account's valid entitlement; readiness alone is not delivery.
What was checked
112 local launcher, uploader and service tests passed. They cover exact draft selection, account isolation, changing upload limits, bounded parsing and the existing library workflows.
90 focused platform tests passed across readiness, draft, upload, browser-game and free-tool paths. These fixture results do not prove live purchases, seller payouts or successful production delivery.
Production readback on October 26, 2026 verified 25 public files on guassia.com, including the website files and all six parts of the complete Guassia 0.5.32 installer. The launcher feed and native catalog signatures were verified. No installer was executed. HTML comparison allowed only the recorded 214-byte Cloudflare analytics insertion.
Known limits and unfinished work
Asset uploads are being tested. Public submissions, purchases and seller payouts are not available yet.
Guassia 0.5.32 was installed and reopened through the normal updater on the release-test PC. That check does not verify other computers or fresh sign-in; the Windows build remains unsigned. The desktop game and asset engines retain their existing versions. Translations are machine-authored and await fluent human review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Creator workflow and storage accounting checkpoint · af778287c072c230f97b95649f521b259a01aff9
Source implementation, local fixture tests and deployment verification remain separate.
Local launcher and uploader checks · CHANGELOG-CREATOR-FLOW-20261026.md
112 focused source tests passed; these do not establish an installed update or a live purchase.
90 focused platform tests preserve account and free-tool access independently of artifact capacity. Production delivery still needs its own verification.
Website guidance and build integration · 41489e1e258e8a14eebd2b62221711a00e46678a
Website copy and durable build integration, separate from the launcher implementation checkpoint.
Production website and launcher distribution readback · public-verification-production-01.json
Deployment 6beb780f.guassia.pages.dev was checked at guassia.com. Exact public files and the complete launcher installer were verified; native installation, public asset intake and paid transactions were not verified.
Responsive camera movement with a settled final image
Included with this site release
Responsive camera movement with a settled final image
Orbit, pan and zoom use interactive rendering in authoring views; the image refines when input stops. Desktop and browser world editing share the same scheduling policy.
Source checkpoint 15c844e79745b971e90443a163853e880583a9e1Source availability and destination verification are separate.
Move first, refine when still
Camera requests are combined into bounded work instead of queuing every input. Releasing or canceling a drag, or pausing input for 120 milliseconds, requests an exact final render.
Keep source edits and capture exact
Source changes, graphics changes, resizing and capture retain exact rendering. Replacing or closing a view cancels obsolete requests and drains active work before releasing resources. Gameplay and animated studies keep their existing rendering contracts.
What was checked
A private real-WebGL comparison used 30 camera changes on one 12,000-Gaussian block at 859 by 424 pixels, Balanced quality, on an RTX 3050 Ti. Median awaited render time was 23.30 ms in exact mode and 2.25 ms in interactive mode. The final exact image matched all 1,456,864 RGBA channels of the reference.
Known limits and unfinished work
These are awaited CPU wall times, not GPU time, FPS or input-to-display latency. Exact mode ran first; this is one small scene on one GPU. Startup was measured separately. Image equality applies to this test, not every asset.
This change adds no source detail, photorealism guarantee, paid commerce or online Asset Engine. Translation still needs fluent human review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Source changes and bounded tests are documented separately from packaged application checks, installation and public delivery.
Clearer editor controls and less repeated rendering work
Verified public release
Clearer editor controls and less repeated rendering work
Choose view quality by task, edit supported game components through labeled controls, and find the browser preview and desktop tools through clearer product pages.
Shared graphics controls offer Balanced, Fine edges and Close inspection. Advanced options, lighting inspection and diagnostics start collapsed. Higher sampling explains its pixel cost; it does not add detail to source models. Existing custom preferences are preserved, and failed changes recover safely.
Edit supported game components directly
The native world inspector provides labeled controls for player movement and health, collectibles, practice targets and ground-plane collision. Apply and Discard make edits explicit; validation, undo and saved projects preserve unrelated custom component data. Expert JSON remains available separately.
Reduce repeated preview work
Renderer queries reuse camera state and expose lightweight graphics metrics. Bounded asset streams avoid redundant whole-buffer copies. Native editing redraws when the scene changes; playback and capture retain continuous rendering. These changes reduce unnecessary work without changing the saved model.
Know where each tool runs
The product chooser separates the online ASHVEIL ENGINE Preview, desktop creation tools and stores. Browser scene import and placement remain available. Asset Engine information stays on the website; standalone modeling and sculpting open in the installed Asset Engine. Repeated preview-start clicks no longer reload an active draft.
What was checked
Graphics controls passed 12 source tests and 28 isolated Electron checks: 16 behavior checks and 12 layouts across six languages. The fixture uses a deterministic renderer adapter, not a GPU performance benchmark.
Native component controls and related runtime regressions passed 30 source tests. A separate browser fixture exercised editing, undo, validation and save/reopen, with 12 desktop/mobile layout observations across six languages.
Product and preview flows passed 26 source tests. A separate browser audit recorded 28 observations covering desktop/mobile layouts, language coverage, lazy preview loading and the separation of online and installed tools. These checks do not establish public delivery or a successful installed update.
Known limits and unfinished work
No GPU frame-rate or end-to-end latency gain is claimed from these isolated checks. Higher sampling is not additional model detail, photorealism validation or Unreal/Blender feature parity.
The typed game controls cover the current ground-plane runtime, not general physics, navigation or every imported mission format. Packaged native integration and public delivery require their own verification.
This update does not activate paid purchases, public seeding or new paid assets. The six-language text is machine-authored and still needs fluent human review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
The checkpoint records implemented source changes. Isolated tests, installed application checks and public delivery are separate evidence.
Public delivery checked · ad2635fb
The October 22 deployment passed public byte verification for 77 files and all three installers. Both updated tools were installed through the normal Guassia library and opened as independent native applications.
One online preview, clearly separate desktop tools
Included with this site release
One online preview, clearly separate desktop tools
Try ASHVEIL Engine Preview in the browser, find the desktop Asset Engine, and inspect six Gaussian detail studies before installing Guassia.
Source checkpoint 45bfed08b2a71fe3e1b7ba1a60bbfe3603deea9dSource availability and destination verification are separate.
Choose the right creation tool
The Asset Engine product page now explains the desktop application and its install path. Legacy browser asset-workspace links redirect there before recovering or saving a draft. The online ASHVEIL Engine Preview retains scene imports, placement, transforms and collision controls; standalone modeling, sculpting, cleanup and individual asset exports belong to the desktop Asset Engine.
Browse on the website; manage assets in Guassia
Product navigation, store pages and creator guidance distinguish browser previews from desktop installation and the asset library. Paid purchases are explicitly unavailable. Existing free teaching downloads and functional mechanism demonstrations keep their own clearly described access.
Six original Gaussian detail studies
Door, crate, terracotta pot, bench, column and lantern studies have whole and close views from actual 3840 × 2160 renders captured on September 24, 2026. Compact thumbnails load on demand, and full-size images open separately. The original native models remain local while their quality and delivery are reviewed.
What was checked
44 focused route, scene editing, import, draft and product-flow tests passed. Five separate asset checks passed for exact hashes, native decode and round-trip integrity, finite attributes, positive scales and bounded preview files.
The public image set contains 24 WebP files totaling 1,019,840 bytes. Source originals and the separate desktop application packages are preserved. Public delivery is verified separately from these source checks.
Known limits and unfinished work
4K describes the preview image dimensions, not a photorealism rating or a texture-resolution guarantee. These original AI-assisted procedural surfaces retain baked appearance, soft close detail and other disclosed visual limitations.
This website update does not activate paid purchases, public seeding, new store entitlements or native model downloads. The interface translations are machine-authored and await fluent human review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
This checkpoint includes the source changes. Public delivery and installed application verification remain separate.
Guassia 0.5.31: sharing preferences and complete store packaging
Included with this site release
Guassia 0.5.31: sharing preferences and complete store packaging
Save optional sharing limits in Settings and reach them from My Library. Public peer transfers remain unavailable; this update does not activate sharing or commerce.
Source checkpoint f29a79bcca9c605938a74f497d1b41136b558f1eSource availability and destination verification are separate.
Local sharing controls
Account-specific preferences save upload rate, session payload budget and a one-connection limit. Pause preserves permissions; Stop revokes them. Signing out or changing accounts cancels pending sharing work without deleting owned files.
Permissions bind the original publisher, listing, exact version and package hash. Verified installation and explicit publisher authorization are required. Buying, installing, signing in or opening an editor never opts a user in, and saving preferences never starts a transfer.
Store package repair
The launcher package now includes the Guassian display helper imported by the store, along with the sharing controls and their six-language text. One Guassian remains US$0.01; credit purchasing stays disabled.
What was checked
63 focused and related regression tests passed for account isolation, exact identity, bounded settings, IPC, renderer behavior, translations, navigation, updates and packaging.
A matching static package review and isolated packaged startup smoke are required before this candidate can be staged. They do not establish installation or performance on another computer.
Known limits and unfinished work
Public peer discovery, publisher sharing authorization and buyer-to-buyer delivery are not connected. Saved caps describe payload preferences, not a guarantee about network overhead or billing.
The proposed hosting policy is 10,000 Guassians (US$100) to publish a hosted game, with up to 100 GB per game; assets would use seeding by default, with optional hosting at 1,000 Guassians (US$10) and up to 1 GB per asset. These are gated proposals, not active checkout, paid storage promises or increased live quotas.
Paid commerce remains closed. This launcher update does not replace the ASHVEIL Engine or Asset Engine releases. Windows Authenticode signing is still absent.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Source and test records · f29a79bcca9c605938a74f497d1b41136b558f1e
Source checkpoint and native sharing regression receipt. Public delivery is checked separately.
Verification · source-readiness.json
63 focused and related regression tests passed for account isolation, exact identity, bounded settings, IPC, renderer behavior, translations, navigation, updates and packaging.
Whole Guassians, clear dollar values
Delivery verification pending
Whole Guassians, clear dollar values
Desktop source now displays one Guassian as one US cent, preserves existing monetary records, and previews custom credit amounts without enabling payments.
Source checkpoint 5402d83d6866f716d63c1bfae2917a0de9f3fca1Source availability and destination verification are separate.
Prices and credit estimates
Catalog prices, purchase confirmations and balances show whole Guassians with their US-dollar equivalent. Creator draft prices keep the same stored cents and dollar value when saved or reopened.
The credit amount field accepts 500 to 100,000 whole Guassians, corresponding to US$5 to US$1,000 before any tax. Its preview is not a tax calculation or checkout quote. Custom credit purchases remain disabled, including against the older fixed-pack service.
Sharing stays a separate choice
Library, item details and Settings provide an informational seeding guide through a fixed help route. These links do not start sharing, accept terms, buy an item or download content. ASHVEIL ENGINE Help and Asset Engine Account menus open the explanation in Guassia without changing the active project. Older Guassia builds fall back to Library.
What was checked
76 focused desktop source tests passed, including unchanged draft value, exact currency display, amount boundaries, disabled legacy checkout, account isolation and existing library actions. 45 engine-menu and launcher checks passed, including bounded destinations and compatibility fallback.
59 focused website tests passed after adding the consumer-rights clarification. The canonical creator-policy text and hash are unchanged; incomplete merchant information still prevents legal readiness.
Known limits and unfinished work
These are source changes awaiting a newly built and verified desktop release. No installed update, live payment, tax assessment, seller payout or public peer transfer is established by these tests.
Paid commerce remains closed. The custom checkout service, complete merchant disclosures and payment-provider review are still required. Interface translations are machine-authored and await fluent human review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
This checkpoint includes the source changes. Public delivery and installed application verification remain separate.
Optional seeding explained, without automatic sharing
Delivery verification pending
Optional seeding explained, without automatic sharing
A new download guide explains proposed peer-assisted delivery, separate permissions and planned controls. It does not enable public seeding or purchases.
Source checkpoint 5402d83d6866f716d63c1bfae2917a0de9f3fca1Source availability and destination verification are separate.
Understand the proposed download flow
The guide separates purchase and license review, downloading a complete verified file, and a later voluntary seeding choice. It explains publisher permission, network visibility, resource use, pause and stop limits, and the boundaries of the private experiment. The proposed store hides items with no verified seed from new shoppers while preserving existing libraries. It reserves coins, begins downloading immediately, waits for verified delivery before seller settlement and releases or returns coins after failed delivery. Seeding would be offered only after verified installation; these rules are not live.
Downloads, the desktop library guide, both store previews, the changelog and legal navigation link to the explanation. Proposed native locations are My Library item controls and Settings for download limits. No desktop transfer controls are installed by this website change. The informational terms notice distinguishes mandatory remedies for undelivered, faulty or misdescribed digital content from change-of-mind cancellation; the separately accepted creator policy is unchanged.
What was checked
59 focused source checks passed across the informational page, product routes, legal navigation and localization. The isolated website build completed; this is not a public deployment receipt.
The generated page was inspected in Chrome at a desktop width and a 390-pixel emulated mobile width. All six core languages switched successfully with no horizontal overflow in the mobile checks. This is not physical-device testing.
Known limits and unfinished work
Public peer delivery, purchase acceptance and paid commerce remain unavailable. The page adds no payment, tracking, file sharing or consent collection, and does not alter the canonical commercial agreement.
Private same-computer transfer tests do not establish internet reachability, large-bundle delivery or production security. Translations are machine-authored and await fluent human review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
This checkpoint includes the source changes. Public delivery and installed application verification remain separate.
0.5.30 installer delivery correction
Verified public release
0.5.30 installer delivery correction
Public checks now confirm complete 0.5.30 installer delivery after earlier empty responses. Every signed part and the combined installer match their expected size and SHA-256.
The same six-part installer is retrievable again. Empty, incomplete or mismatched downloads are still rejected; updater size and checksum guards were not relaxed.
What was checked
All six local parts passed size and checksum checks. Subsequent public checks received HTTP 200 but zero body bytes for each part.
The earlier 24-check public receipt covered pages, metadata and service status. It did not download the installer bodies and therefore did not establish installer delivery.
On October 18 at 19:43:47 UTC, all six public parts passed complete-body checks. The combined 125,509,117-byte Windows installer matched the signed SHA-256 and MZ prefix. No installer was executed by this byte audit.
A separate pinned-key catalog audit verified all 13 current engine parts: ASHVEIL ENGINE 0.5.29, 125,941,067 bytes; Asset Engine 0.1.12, 113,170,213 bytes. Both complete files matched their signed hashes and MZ prefixes. Historical installers were not checked.
The normal Windows updater completed Check, Download, Apply, current-user installation and relaunch from Guassia 0.5.28 to 0.5.30 on the tested PC. A further update check reported up to date. Five installed-file and release-identity checks passed; this is not testing on another computer.
Known limits and unfinished work
These checks establish public byte delivery, not application runtime behavior or a newly built engine version. Native installation and relaunch remain separate observations. Paid commerce and public peer delivery remain closed.
Windows installers remain Authenticode-unsigned. These translations await fluent human review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
This dated correction accompanies delivery repair; it does not change updater validation.
Earlier bounded public check · public-verification-04.json
The successful receipt excludes installer body verification; it is not evidence that the updater could retrieve the installer.
Complete public installer check · installer-public-03.json
The signed feed, six response bodies, total size, combined SHA-256 and MZ prefix passed. Earlier empty-response observations are retained.
Current standalone installer bodies · standalone-delivery-01.json
All current parts were streamed through bounded integrity checks without saving or executing the installers.
Normal installed update and relaunch · normal-update-ui-01.json
The native updater receipt records the normal workflow. The separate installed-launcher-01.json receipt records matching executable, app archive, release cache, pinned key and version checks. Authenticode is still unsigned.
Your first game, editable free assets and reviewed game listings
Included with this site release
Your first game, editable free assets and reviewed game listings
Start creating or playing from the homepage. Follow an optional first-game guide, edit the bundled free utilities, and request a reviewed listing for a game you host yourself.
Source checkpoint 8760c9413a66a2ca1d955d615f8593c8291fdb92Source availability and destination verification are separate.
A clearer first project
The learning page and browser editor guide you through the existing Beacon Run example: collect, unlock, restart, edit and save. New worlds remain empty. The guide never replaces a draft or saves work automatically.
Free assets that reach the editor
Guassia 0.5.30 repairs the bundled utility asset handoff and clarifies Install and Open actions. An exact installed-version check clears completed installer notices. The existing ASHVEIL ENGINE 0.5.29 and Asset Engine 0.1.12 remain compatible.
Reviewed self-hosted discovery
Browser-game requests have a separate readiness switch, verified-account and CAPTCHA checks. The private owner inbox shows readable listing details and counts for the loaded view. Requests do not automatically publish games; the creator hosts the game files.
What was checked
Local checks cover the five original utility assets through installation, editor handoff, working-copy save, world-file roundtrip, removal and reinstallation. Account, native dialog and launch actions in these checks use fixtures. Interface additions have six-language coverage.
Known limits and unfinished work
Browser .guassia.zip and desktop .gworld formats are distinct. Export permissions and third-party asset rights still apply. Paid marketplace sales and public hosted-asset delivery remain disabled.
A fresh non-owner signup and complete real installed-user journey still need separate acceptance. Inbox counts are not audience analytics. Translations await fluent human review, and Windows installers remain Authenticode-unsigned.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Source and local tests are separate from installed and public delivery.
Connected mechanics and clearer creator journeys
Included with this site release
Connected mechanics and clearer creator journeys
This update connects the website, Guassia library and native creation tools with clearer next steps. The browser product is now named Online ASHVEIL ENGINE Preview. New mechanics and print-preparation tools are teaching prototypes with explicit validation limits.
Source checkpoint b91c0f6df992042d6827c07d7a0fa29ea459831aSource availability and destination verification are separate.
Get from discovery to creation
The homepage and product pages provide direct paths to the online preview, account, desktop download, assets and release preparation. Responsive toolbars, a visible Studies row and an in-app Guide make native controls easier to find. Product pages now use fewer repeated navigation links and quieter expandable help. Account, download and library pages put the main action before troubleshooting. Optional shortcuts no longer look like required numbered steps. The website download and desktop update feed are now checked against the same launcher version and installer hashes.
Edit a personal asset directly
My local assets now offers Edit in Asset Engine. The launcher checks the installed receiver version, verifies the source bytes and waits for a confirmed editor handoff. Editing preserves the original file and does not create a store entitlement.
Explore connected mechanical motion
The supported gear-drive study adds force-driven motion with torque, inertia, gravity, damping and slider load under ideal joint constraints. Public machine previews start when visible and pause off-screen; reduced-motion preferences are respected.
Prepare a small assembly
A separate crank-slider prototype includes printable parts, a clearance coupon, specified hardware and piece-by-piece instructions. The tutorial distinguishes Gaussian appearance, numerical checks, manufacturing surfaces and actual physical fit.
What was checked
Focused lifecycle, account-isolation, source-integrity, mechanics and responsive-interface checks are recorded separately. Final packaged, installed and public delivery checks remain pending at this source checkpoint.
Known limits and unfinished work
The mechanism is a reduced-coordinate teaching model, not a general contact or structural solver. The print kit has not been physically printed, fitted or durability tested.
Marketplace drafts remain available, but paid purchases, public marketplace publishing and creator payouts are not enabled. A locally tested payment-observation inbox does not establish live financial readiness.
Translations are machine-authored and require fluent human review. Windows packages remain unsigned under Authenticode.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Personal library handoff checkpoint · b91c0f6df992042d6827c07d7a0fa29ea459831a
This source checkpoint verifies local asset editing; the other update components have separate working-source and test records.
Scoped implementation and verification · release-note-evidence.json
Source, local tests, packaged applications and public delivery are distinct checkpoints.
Browser studies, free utility assets and clearer tool updates
Delivery verification pending
Browser studies, free utility assets and clearer tool updates
This release candidate brings together ASHVEIL ENGINE 0.5.28, Guassia Asset Engine 0.1.11 and Guassia 0.5.27. It adds connected browser demonstrations and a small original asset collection with an explicit local-library workflow. The changes focus on understandable navigation, editable files and honest capability limits. Final installed and public delivery checks remain separate from source preparation.
Source checkpoint 8379205901ffc39e927b48c580748bc7f2567afbSource availability and destination verification are separate.
Explore a fixed browser landscape
Alpine valley opens only after choosing Start. Its authored 5 × 5 km map loads saved resources at Balanced detail, with detailed areas around five named landmarks and a coarser travel surface spaced at 19.53 m. Moving the camera does not generate a new landscape. Walking, flight, landmark travel and local view sessions share one entry point. Closing cancels the active load; the optional wildlife movement pack is not loaded in this browser study.
Inspect supported mechanical motion
The gear-and-slider study now uses one prescribed input with connected rigid-body frames, shaft rotations, a connecting rod with joint openings and a guided slider. The planetary study remains separately selectable. These are kinematic studies with approximate Gaussian teeth: they do not solve contact forces, torque, wear or manufacturing tolerances, and neither is a print-qualified moving mechanism.
Choose, install and edit five free utilities
The original collection contains a parts tray, divided tray, card/photo stand, cable comb and shallow dish. Adding an item records the accepted asset terms in this account’s local library without downloading or installing it. Install creates a verified local copy; Edit opens Asset Engine and Use opens ASHVEIL ENGINE. Remove deletes the installed copy while retaining the library entry for reinstalling from the bundled collection. This is a local free-content record, not a paid purchase, cloud-synced entitlement or credit transaction.
Keep appearance and print surfaces separate
Print preparation exports a separate finite-envelope surface without replacing the Gaussian source. The utility proxies have bounded topology and dimension checks; changing their illustrative surface colors does not change the tested proxy geometry. The supplied preview diagrams show that separate surface, not a Gaussian screenshot. A closed surface is not evidence of physical printability, fit, strength or safety.
Understand account and update state
The existing account service was resumed after a service pause. Browser sign-in and the installed account refresh were observed working; this does not establish checkout or payout readiness. Tool cards distinguish an available update from an update requiring sign-in. Account, agreement and package checks remain in place. Remembered offline access is not treated as a newly authenticated online session.
See why a world save is waiting
World Save and Save As now show preparation and blocked-operation feedback. Toolbar availability matches the native menu during play. A failed or cancelled save keeps the authored world open, and an older document’s receipt cannot clear a newer document’s unsaved state. Native menu account-connection failures explain the next step. Encoding still runs before the desktop picker; this is not an asynchronous serialization rewrite. Focused CPU checks passed; installed interaction verification is pending.
What was checked
At their recorded checkpoints, the broad CPU regression passed 1,287 tests with zero failures and one optional skip across 138 files; the focused save checks passed 26, and the final integrated mechanism checks passed 45. These overlapping scopes are not a combined unique-test total. Independent connection checks sampled 1,441 times and 241 rendered-transform poses over a 15-second cycle. They check modeled joint relationships and attachment transforms, not physical contact, printer tolerances or manufacturing accuracy.
Chrome checks covered the final connected drive’s animation, 4× speed, pause, reset and detail views without reported JavaScript errors. Earlier candidate checks covered switching to the planetary study. All five Alpine destinations loaded; cancellation/reopening, pause/flight, local session save/reopen and image export worked. At a 390-pixel responsive viewport, both study pages had no horizontal overflow; a physical mobile device was not tested. The five utilities passed native visual review. Final new-version installation, save-feedback interaction and public downloads remain pending.
Known limits and unfinished work
The landscape is Swiss-inspired original scenery, not a surveyed reconstruction. Its detailed coverage is limited, and neither the scenery nor the utility assets are certified photorealistic. No general browser frame-rate or memory improvement is claimed.
Physical printing, fit, material strength and manufacturing tolerances are not validated. The utility colors are authored readability aids. The mechanical studies use prescribed animation rather than engineering dynamics.
The five bundled assets are free under the existing creation policy. This update does not enable browser checkout, paid marketplace transactions, creator payouts or cloud download hosting. Existing commercial restrictions and separately accepted creator terms remain in place.
Windows packages remain unsigned under Authenticode. Update-catalog signatures establish recorded package integrity, not a trusted Windows publisher. Six-language interface and release-note coverage is machine-authored; fluent human review remains pending, and canonical legal terms remain English.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
The immutable source revision identifies the bundled changes. A source checkpoint does not by itself establish public delivery.
Scoped verification records · release-note-evidence.json
Local tests, actual browser/native observations and package delivery checks are recorded separately, with their limits retained. Pending checks are not counted as passes.
Photorealism Update: surface controls and moving mechanisms
Included with this site release
Photorealism Update: surface controls and moving mechanisms
ASHVEIL ENGINE 0.5.27 and Guassia Asset Engine 0.1.10 bring more deliberate Gaussian surface editing, shared lighting controls, clearer model-import feedback and a moving mechanical study. The update name describes the direction of development; it does not certify photographic realism. Public delivery and installed-app verification are recorded separately.
Source checkpoint 4137695c4022ff8476447ddb317a6e0eb6ed0888Source availability and destination verification are separate.
Shape and inspect local surfaces
Asset Engine adds Scrape and Fill brushes, an adjustable plane offset and stroke-plane locking. Undo, cancellation and local save/reopen preserve the editable Gaussian data. Shared sun and sky controls let creators inspect static surfaces under directional light and ambient fill without baking those preview settings into source colors.
Reduce repeated editing work
Compatible small geometry changes use sparse retained Undo records and partial source updates. Shared sorting and depth-readback paths reuse selected buffers, and unchanged LOD selections avoid redundant commits. Full-array reconstruction and other rendering work still occur in some operations; these changes do not establish a general frame-rate, RAM or VRAM improvement.
Control the conversion footprint
Model imports expose a surface-footprint factor from 0.5 to 1.5, with the existing 1.0 coverage as the default. The factor changes the tangent extent of each sampled Gaussian while keeping its thin-axis thickness. Smaller footprints can reveal texture variation but may reduce coverage or expose gaps; they do not add texture pixels, geometry samples or captured detail.
See what the importer preserves
A bounded material report distinguishes sampled base and emissive color from omitted normal maps, roughness, metallic response and other unsupported material channels. The report is provenance and compatibility information, not a new PBR material system. Saving a converted native asset retains its sampled appearance and import metadata.
Inspect a moving mechanism
A four-gear mechanical study provides coordinated, repeatable Gaussian motion for inspecting a more complex assembled model. Its motion is prescribed kinematics, not contact, torque, load, wear or engineering simulation. It is an authoring and rendering example, not manufacturing-ready CAD.
Explore the Alpine sandbox
The Alpine explorer adds local view-and-settings sessions, pause and return-to-trail controls, adjustable look sensitivity and invert-Y. Authored vegetation includes mixed growth stages, adjustable wind and temporary contact bending underfoot. Optional insects, animated lake water and fish, and opt-in synthesized spatial nature cues add environmental motion and sound. These are visual and audio approximations, not validated Swiss ecology or fluid physics. Session files do not contain movement packs or a complete saved world.
What was checked
The current source regression recorded 1160 passing tests, zero failures and one optional skip across 129 test files. Isolated native checks passed 50 World assertions, 33 Asset import assertions and 25 mechanical-study assertions on one Windows RTX 3050 Ti/ANGLE D3D11 machine. Native fixtures exercised the bundled UI and local file workflows; they are not regular-Chrome, mobile, multi-device or whole-engine certification.
Final versioned-package checks, public downloads, updater delivery and installed launches require separate release evidence. This entry initially keeps delivery verification pending. These functional checks do not establish a frame-rate improvement or photographic realism.
Known limits and unfinished work
Close-range coverage, vegetation, terrain materials, water and movement still need improvement. Four-kilopixel source images, more Gaussians or a 4K output setting alone do not establish realistic detail or a smooth browser frame rate.
Normal-map and PBR-material preservation, calibrated physics, a manufacturing CAD kernel and unlimited physical memory are not supplied by these changes. Narrow footprints and dense models need device-specific inspection.
Windows installers remain unsigned under Authenticode. Signed update catalogs verify their recorded bytes but do not establish a trusted Windows publisher. Existing accounts, marketplace availability and commercial requirements are unchanged.
These notes include English, Spanish, Simplified Chinese, German, French and Dutch text. The translations are machine-authored; fluent human review remains pending.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
The exact release source revision is recorded here. Source availability does not establish installation or public delivery.
Current source and native checks · regression-04.json
The source regression and separately recorded native World, Asset import and mechanical checks establish the scoped results above. Packaging, installed delivery and public deployment require separate validation.
A movement workshop and an original alpine world
Delivery verification pending
A movement workshop and an original alpine world
The ASHVEIL ENGINE 0.5.26 and Guassia Asset Engine 0.1.9 source checkpoint adds a shared local movement workshop. A prepared community collection, an optional alpine explorer and Gaussian club effects extend character and world creation. Public delivery and installed-app verification remain separate.
Source checkpoint c0633882ec91bb4938175b0aa84af41e478da2caSource availability and destination verification are separate.
Preview and keep individual movements
Open a native .gchar character and install selected .gmotion files locally. Search, filter, scrub, change speed, and inspect source travel or in-place movement. Exact rest-rig signatures prevent incompatible playback. Source keyframes are preserved by default; saving an animated character creates a separate copy. Each editor keeps its own local installed library.
A prepared collection of 500 clips and 16 characters
The revised selection contains 342 Rocketbox motions and one CMU crawl passage for the supplied female rig, three separately retargeted male-rig motions, and 154 animal/bird clips. It still totals 500 clips and 16 characters. The community page searches metadata first and downloads only a chosen file, with cancellation, length bounds and SHA-256 verification. Matching species does not establish rig compatibility.
Microsoft Rocketbox assets retain MIT notices; Quaternius assets retain CC0 rights. The original Guassia bird uses MIT with Guassia copyright retained. The CMU Graphics Lab crawl retains separate terms permitting free use and product inclusion but prohibiting direct resale of the data, even converted. It is not MIT or CC0. Full source and adaptation notices accompany the collection. Asset rights remain separate from the engine license and grant no rights to ASHVEIL recordings.
Explore an original 5 km by 5 km alpine landscape
The optional explorer adds Gaussian terrain, lake and mountain landmarks, vegetation and authored wind. Balanced is the default, with visible budgets of 300,000 terrain and 100,000 plant Gaussians; High raises these to 1,200,000 and 260,000. Residency has separate limits. Opening the movement pack enables a sparse nearby population, bounded to six resident actors and 500,000 actor Gaussians. Walk, fly-camera and landmark controls support inspection; the blank world template remains available.
Move Gaussian club fields without rewriting the source
The shared GPU field adds deterministic wave and scatter motion to selected club visualizers. Conservative bounds and covariance transforms accompany the displacement. Seekable phases, reduced-motion handling and an effect toggle support controlled previews. The effect changes existing splats; it does not add captured surface detail.
What was checked
Focused tests cover rig and file validation, local storage, source-key playback, cancellation, bounded scene selection and lifecycle cleanup. Native fixtures rendered animal/bird and male-rig motions; source arrays stayed unchanged. These checks do not establish an artistic review of all 500 clips.
Matched 1080p club fixtures checked effect identity, changed phases, exact seek repetition and unchanged source-upload counts. Static-download tests check corruption, truncation, cancellation and unsafe paths. These are scoped regression checks, not process-RAM, physical-VRAM or real-time frame-rate measurements.
Known limits and unfinished work
The 500 entries include related behaviors and travel variants, not 500 unrelated inventions. The CMU crawl is a four-second one-shot with preserved root travel, constrained wrist poses and rest fingers. It is not a seamless loop or validated physical-contact solution. Characters and vegetation are stylized or adapted game assets; the original alpine scenery is Swiss-inspired, not a geographic survey or photoreal capture.
Realistic visual quality remains unfinished: terrain can look soft and plants repeat. Character feet are not guaranteed to follow uneven terrain, and root-motion removal does not match stride length to gameplay speed. Sparse residency and an offline 1080p export do not establish a dense world or real-time playability. Measured moving and animated views remain too slow to support a 30-fps playability claim. The visible loop waits for exact rendering; the experimental asynchronous sorting path is not enabled.
The new movement and alpine panels are English-only. These release-note companions cover English, Spanish, Simplified Chinese, German, French and Dutch; translations are machine-authored and fluent human review is pending. Compatible desktop releases, public file delivery and installation require their own verification.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Movement and alpine functional source checkpoint · c0633882ec91bb4938175b0aa84af41e478da2ca
Exact functional source for the shared workshop, motion storage, original alpine world, community download page and club field effects. A source commit and private staging build are not proof of public release or successful installation.
Reviewed community collection revision · community-library-500-v2-receipt.json
After the initial foundation checkpoint, one Rocketbox idle variation was replaced by the reviewed four-second CMU 111/03 crawl. The original pack was retained, the other 499 motions and all 16 character bytes were preserved, and CMU source terms and adaptation limits accompany the revision. This is private preparation, not public-delivery proof.
Initial movement and alpine foundation · aa7365ba7e15fcf46c0ab8ad39a4d9354c69ec34
Earlier source checkpoint for the shared workshop, exact-rig motion playback, initial alpine scene and club effects. The final checkpoint adds bounded detail choices, verified payload credits and reviewed rendering changes.
Deeper asset creation and safer world editing
Included with this site release
Deeper asset creation and safer world editing
Guassia 0.5.26, ASHVEIL ENGINE 0.5.25 and Guassia Asset Engine 0.1.8 improve the path from local modeling to reusable world assets. Protection masks, appearance layers, reviewed source revisions and bounded quality inspection give creators more control while preserving the original Gaussian data.
Source checkpoint 458975e494a9304b5ec20498bb495cd2e5288949Source availability and destination verification are separate.
Protect detail and edit appearance in layers
Asset Engine adds protected regions for sculpting and painting. Creators can mark areas to preserve, inspect the protection overlay and remove protection deliberately. Protection is stored with the local asset rather than silently changing the source geometry.
Named color and opacity layers keep appearance edits separate from the source. Layer controls, Undo and local save/reopen make experiments reversible. These controls do not add captured texture detail or certify CAD precision.
Review a new source before updating a world
World creators can review a revised asset and choose the selected object or all references to its old source. Object position, rotation, scale and components are preserved. Changed bounds, existing source edits and component fit require explicit review; source-index edits are not copied onto a different dataset. Previous sources remain available for Undo.
Outliner search and visibility filters help locate objects. Locks protect object edits, and shared-source changes refuse to proceed while a locked object still uses that source. A revision cannot quietly overwrite object or source changes made after its review.
Inspect possible artifacts without deleting the source
Both editors offer bounded source-quality inspection for invalid sampled attributes, extreme scale ratios, very close centres and possible isolated or weakly supported thin splats. Findings are clearly labelled as checks or heuristics. A sample cannot establish missing neighbours across the full source, and incomplete neighbour work does not certify surface coverage.
Asset Engine can select reported candidates for close inspection. Both editors can hide reviewed candidates through an edit layer, with Undo to restore them. Actions reject stale source revisions. No automatic deletion or realism score is applied.
Load one exact collection chunk near the camera
Inspect near camera selects one verified source chunk of at most 250,000 Gaussians. The view states resident and committed-on-disk counts separately. The source stays read-only until the creator chooses an independent editable chunk copy. Cancellation and stale collection changes must not adopt a late result.
The 256 MiB source-buffer envelope accounts conservatively for reported current source and retained history plus incoming copies. GPU buffers, framebuffers, driver memory and object overhead are additional. This is camera-guided inspection of one chunk, not continuous streaming, a larger editable-document limit or proof that every nearby detail is resident.
Clearer language and library status
Native World menus add language options. New Asset Engine creation and inspection controls include English, Spanish, Simplified Chinese, German, French and Dutch phrases. The launcher distinguishes a library still loading from a completed failure instead of prematurely reporting it unavailable.
What was checked
Targeted source tests cover local save/reopen, undo, cancellation, stale source rejection, shared references, locked objects and bounded collection reads. Source tests, native UI checks, package inspection, installed-app behavior and public delivery remain distinct verification stages; passing one does not establish the others.
Known limits and unfinished work
This update does not establish complete Blender or CAD equivalence, photographic realism, a rendering-performance improvement, unlimited resident Gaussians or continuous open-world streaming. Quality findings are supportable heuristics and attribute checks; creators must inspect the result before changing an asset.
New interface and release-note translations are machine-authored; fluent human review is pending. Authored names and project data remain literal. Windows publisher signing and unfinished marketplace purchases, publication and creator settlement remain separate release limitations.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Source checkpoint for asset authoring, world revisions, quality inspection and bounded collection viewing. Packaging, installation and destination verification are recorded separately.
Clearer navigation and a direct way to report problems
Verified public release
Clearer navigation and a direct way to report problems
Guassia 0.5.25, ASHVEIL ENGINE 0.5.24 and Guassia Asset Engine 0.1.7 add direct Report a problem actions and clearer routes between playing, creating, downloads and feedback. Website changes distinguish available tools from unfinished commerce.
Larger home actions make the two installed creation tools easier to find. Hosted games use /games/ instead of sending players into the old showcase world. Store screens explain their current availability rather than implying that purchases or publishing are ready.
Each application can open the feedback page from its own interface. Product and version context helps identify the affected application; users can describe the problem before submitting it.
Contribute time and keep feedback traceable
The investor page now invites people to invest their time: use the engine, test a workflow and report errors or useful ideas. It links directly to creation and feedback rather than requesting a financial commitment.
A local feedback draft is clearly labelled not submitted. A server receipt appears only after persistence succeeds. Retrying unchanged content with the same request ID avoids duplicate reports. Signed-in, email-verified accounts, same-origin checks, request limits and a server-verified CAPTCHA protect submissions.
The owner review screen retains request IDs and notes, filters active or completed statuses, and loads additional pages. Exact verified owner identity controls access. Stale-status conflicts prompt a reload instead of silently overwriting another status change; original submitted text remains intact.
Readable controls and current guidance
Save controls and editor guidance receive readability fixes. About and Learn explain the current browser and installed workflows. Existing Ashley Kalkowski profile and creator-note pages remain available. No Gaussian renderer, asset density or graphics-quality algorithm changes in this release.
What was checked
The client, native menu and locale suites passed 529 checks; native save, import, navigation and launcher checks passed 48; packaging, signing and release-closure checks passed 31. Platform and Pages-adapter checks passed 213, and focused website checks passed 42. These scoped tests are separate from real installation, public delivery and a persisted feedback receipt.
Known limits and unfinished work
Windows installers still lack Authenticode publisher signing. Paid purchases, game publication, creator settlement and other unfinished commerce remain held. This usability release does not establish complete professional-engine parity, universal reliability or improved rendering performance.
World native menus remain English. The website and release-note companions cover the six core languages where implemented, but machine-authored translations have not received fluent human review. A saved draft is not a submitted report, and submission is not a promise of implementation.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Professional navigation and feedback source · 2b16bd72b1f54bcb5a5d7c04ef313311b141ac87
Functional source checkpoint for this audit release. Installer and live-service verification remain separate records; earlier profile and update-release evidence stays intact.
Public release verification · guassia-professional-publication-success-20261001.json
Public pages, feedback availability and signed downloads match the reviewed release. Account actions and installation have separate checks.
A clearer introduction to Guassia’s creator
Delivery verification pending
A clearer introduction to Guassia’s creator
Ashley Kalkowski is clearly credited as creator of Guassia’s Gaussian game engine. The profile, creator note and engine landing explain free browser creation and private playtesting, with separate public and commercial permissions.
Source checkpoint f9a96e79700505b8986a54a3414bdd0ac272e018Source availability and destination verification are separate.
Creator identity and a direct path to the engine
The profile and first-party creator note connect Ashley Kalkowski with Guassia’s Gaussian game engine in their titles, descriptions and visible introduction. A concise credit on the engine landing uses the same Person identity. Direct engine, playtest, creator-note and legal links explain the available next steps.
What was checked
The required existing source suite passed 596 checks. Canonical URLs, the stable creator identity, permission links, one visible H1 per page, and existing language controls passed scoped rendering checks.
Desktop and mobile browser review, native publication and public HTTPS readback are separate gates; this prepared source record does not claim they have completed.
Known limits and unfinished work
This website wording update changes no editor runtime, accounts, installers, update feeds, worlds or legal terms. It makes no first-engine, novel-algorithm, Google indexing or ranking claim.
The five full companion translations are machine-authored and await fluent human review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Profile and creator-note wording, direct engine link, restrained product credit and stable Person schema; source checkpoint includes the preceding content update.
Meet the creator of Guassia
Historical public delivery verified
Meet the creator of Guassia
Ashley Kalkowski has a dedicated creator profile, an approved portrait, and a practical note about Guassia’s Gaussian game engine. Both pages link to the browser engine preview and feedback.
The profile connects Ashley’s confirmed work on Guassia with her official Instagram and Black Natrixx profile. A separate creator note explains the current workflow and limitations without claiming to be independent reporting. Existing software, accounts, downloads, worlds and legal pages retain their current behavior.
What was checked
The required existing source suite passed 596 checks; targeted profile, route, language and article integration checks passed after the portrait and creator note were added. Public browser review and deployment verification are separate.
Known limits and unfinished work
This is a prepared website update. It does not establish a Google ranking, independent press coverage, or the earliest Gaussian game engine. The five companion translations are machine-authored and await fluent review.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Creator profile and article source · 9ff21f149a91fa2f2ecbd0e8f01863aa5206512a
Dedicated profile, approved original photograph, creator note, shared links and generated sitemap routes.
Public profile and article verification · guassia-ashley-publication-success-20260930.json
Native production success and public HTTPS checks confirm both pages, the approved portrait, schema, discovery links and sitemap. Existing update-feed bytes and 18 latest installer HEAD responses were checked; installer bodies were not rehashed.
Find application updates from any computer
Included with this site release
Find application updates from any computer
Guassia 0.5.24 replaces the customer-facing local update folder with signed online update discovery. My Library can discover new releases of the separate ASHVEIL ENGINE and Guassia Asset Engine applications without a new launcher for each tool release.
Source checkpoint 2554eac1d5b4b9e05bbff81aaa9c1941e81f4c02Source availability and destination verification are separate.
One initial upgrade, then clear update controls
If the old app says No signed local release is staged, install Guassia 0.5.24 once from the Downloads page. Then use Settings → Updates for Guassia and My Library → Install or Update for the two separate creation tools. Existing projects and downloaded libraries stay in their current locations.
Automatic update checks remain optional and are off by default. Enabling them checks and downloads verified Guassia updates; installing still needs confirmation. A newer tool catalog does not install creation tools automatically.
Verified downloads and preserved release history
The launcher checks publisher-signed metadata, exact product identities, expiry, every download chunk and the complete installer hash. The tool catalog retains older verified releases so installed tools can be recognized. Altered signatures, expired metadata and conflicting hashes for the same version are refused; offline access keeps the existing trusted local records.
What was checked
Release-signing tests verify reviewed installer and chunk hashes, refuse changed files and wrong keys, preserve earlier output, and cover catalogs containing both current and older tool releases. Live deployment and installation are checked separately.
Known limits and unfinished work
This repair changes the Guassia launcher; ASHVEIL ENGINE 0.5.23 and Guassia Asset Engine 0.1.6 remain separate existing releases. Windows x64 only. Update signatures are not Windows Authenticode publisher signatures, so Windows may still display an unsigned-publisher warning. Older local-channel launchers require the one-time manual upgrade.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Reviewed source checkpoint for the launcher update and signed standalone catalog. Source availability does not establish live delivery.
Sculpt native Gaussian assets and create clearer surfaces
Source checkpoint only
Sculpt native Gaussian assets and create clearer surfaces
Prepared for Guassia and ASHVEIL ENGINE 0.5.23 with Guassia Asset Engine 0.1.6: sculpt source assets in Asset Engine, then import their native files into World for game assembly. Both creation pipelines use the improved ten-shape surface generator.
Source checkpoint 202060feb6b0bce099926fae35a273c0bbbf45bcSource availability and destination verification are separate.
Brushes that edit the saved source
Draw, Inflate, Flatten, Pinch, Grab, Crease and Smooth provide radius, strength, falloff, axis symmetry and an optional existing selection. Dragging previews geometry continuously through sparse GPU updates; releasing commits one undo step. Escape cancels. Save finishes an active stroke before writing the native file.
Sculpt lighting is a preview aid; saved colors remain unchanged. Alt-drag or right-drag orbits, middle-drag pans, Shift smooths and Ctrl reverses the brush. Controls and native menus support all six core languages.
Shared surface quality without extra source points
All ten parametric shapes use improved surface spacing, edge coverage and oriented Gaussian covariance at the requested count. New quick primitives save their actual generated arrays. Existing saved assets, imported sources and legacy primitive recipes keep their original meaning.
Guest quick shapes now remain usable as temporary drafts in the current tab; an authorized project save preserves their exact source arrays. Closing the tab before saving discards those drafts.
What was checked
The prepared native application passed 23 checks covering live pointer preview, exact undo/redo, cancellation, save during a stroke, six languages and native reopen. The saved sculpt imported through the actual World interface and survived World saving with identical geometry and appearance.
Actual Gaussian GPU comparisons covered all ten shapes at equal counts of 2,048 and 12,000 points in three fixed views (60 pairs), with fewer silhouette errors and no recorded WebGL errors. Separate sculpt GPU checks confirmed visible geometry updates, exact cancellation and no source reupload during a stroke.
Known limits and unfinished work
The current editable chunk limit is one million Gaussians; interactive sculpt testing used 12,000. Directional spherical harmonics above degree zero remain blocked for geometry edits. Surface directions are inferred from Gaussian shape. These tools reshape existing detail; fixed synthetic GPU tests do not establish photographic detail, universal sharpness or frame-rate gains.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Native sculpt and shared surface source · 202060feb6b0bce099926fae35a273c0bbbf45bc
Committed functional source checkpoint. Final installer, installed startup and public delivery are verified separately.
A direct route from Guassia to your installed engines
Source checkpoint only
A direct route from Guassia to your installed engines
Guassia 0.5.22 simplifies opening the two creation applications. Home, the sidebar and the software library use one activation flow with visible progress and errors.
Source checkpoint 7fd5586ca91cad4f85a84fbdb22c388aff20cb13Source availability and destination verification are separate.
Open the tool you chose
Clicking an engine waits for its installation status before acting. An installed application opens directly from the current screen; the tools page is used when installation is needed. Repeated clicks during the same request do not launch duplicate copies.
Open remains the primary action for installed software, even when an update is available. Update is a separate action. Labels and first-run guidance distinguish opening an installed application from installing one. The six core languages include the changed interface text.
A focused browser Play menu
The browser Play menu now keeps keyboard focus inside its controls and prevents interaction with the editor behind it. Resume returns focus to the world; closing restores the editor. The menu uses a simpler solid panel with clearer keyboard focus.
What was checked
Targeted navigation checks cover delayed availability, repeated clicks, installed and missing tools, failed opening, and visible errors. Native rendering, project saving and installer checks are recorded in the separate graphics and Vulkan entries.
All 39 browser playtest tests passed, including focus containment, previous inert-state restoration, startup cancellation, Escape, restart and disposal. These controlled tests do not establish a full browser visual audit.
Known limits and unfinished work
The launcher still requires sign-in and installation terms for protected downloads. ASHVEIL ENGINE and Asset Engine remain separate local applications with their own project files. This routing change does not grant paid content or activate checkout, publishing or payouts.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Direct engine activation and navigation source · 7fd5586ca91cad4f85a84fbdb22c388aff20cb13
Source behavior is separate from final installer and public download verification.
Optional Vulkan rendering in both desktop engines
Source checkpoint only
Optional Vulkan rendering in both desktop engines
ASHVEIL ENGINE 0.5.22 and Guassia Asset Engine 0.1.5 add a shared native rendering-backend preference. Automatic stays the default; Vulkan is an experimental option for supported Windows and Linux builds.
Source checkpoint f3e5e15cd916dfa68bfeb5bfb5e8f6bc73f0b376Source availability and destination verification are separate.
One native backend setting
Open Graphics and choose Automatic or Vulkan. The preference applies when each engine next launches; changing it never closes an editor or discards work. The panel reports the current renderer separately from the requested backend and shows when a restart is pending.
The setting is validated and stored atomically in an application-owned location. Missing or corrupt preferences fall back to Automatic. Starting an engine with --guassia-gpu=auto temporarily restores Chromium’s automatic selection without deleting the saved choice.
Responsive settings and honest capability reporting
The native query for graphics information has a time limit, so an empty editor can still load and save settings before a GPU context is available. Asynchronous status refreshes cannot overwrite a newer selection.
Vulkan is supplied by ANGLE beneath the existing WebGL2 Gaussian renderer. This retains the same splat data, shaders, editing and image-quality controls. It is not a new direct Vulkan rasterizer, does not change browser graphics settings, and does not enable hardware ray tracing.
What was checked
Isolated native fixtures rendered actual Gaussian pixels at native and 2x internal resolution using the reported NVIDIA Vulkan backend, with zero recorded WebGL errors or GPU process crashes. Separate Automatic and recovery runs reported D3D11. Preferences were isolated from the owner’s installed applications.
Backend preference, recovery, IPC, package and asynchronous interface checks passed. The release also preserves the separate native Library and Asset Store routes and editable local asset copies. Installer integrity, installed startup and public update delivery are verified separately.
Known limits and unfinished work
On the tested NVIDIA Windows configuration, Vulkan used WebGL readback and software page compositing; Automatic retained GPU compositing. Vulkan can therefore be slower, and no performance improvement is claimed. Keep Automatic unless you are deliberately evaluating another backend.
This release packages Windows x64 previews. Linux capability in the preference code is not a tested Linux distribution; macOS exposes Automatic only. Windows executables remain unsigned. This change does not activate marketplace payments or seller payouts.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Native Vulkan integration and shared controls · f3e5e15cd916dfa68bfeb5bfb5e8f6bc73f0b376
Functional source checkpoint; packaging and destination verification are separate.
Sharper Gaussian blocks and shared graphics controls
Source checkpoint only
Sharper Gaussian blocks and shared graphics controls
ASHVEIL ENGINE 0.5.22 and Guassia Asset Engine 0.1.5 share new image-quality controls and improved block surfaces. The browser workshop, scene view and playtest use the same renderer settings. Existing native Library and editable-copy fixes are retained.
Source checkpoint c254ef75219accaca363878fb609d22fc76ee6ecSource availability and destination verification are separate.
More deliberate surface placement
New blocks concentrate smaller surface splats near edges and use overlapping interior footprints. The source count stays exact. The browser quick Block keeps its 1,350-splat budget and stores its new native source; existing saved primitive references still load through their original recipe. Other modeled shapes and existing files are not regenerated.
One Graphics panel across the editors
Gaussian antialiasing offers Off, Balanced and Smooth. Bounded 1x, 1.5x and 2x supersampling renders additional internal pixels and averages them into the original output. The panel shows effective dimensions and pixel cost, saves local preferences, and provides Reset. All six core interface languages are included.
The extra color target is capped at 16 megapixels and the device dimensions. A failed allocation returns to native resolution and reports the effective fallback. Source records, saved projects, picking coordinates and authored colors stay unchanged. The cap is not a measurement of total GPU memory.
Reliable appearance edits
Partial appearance uploads now split at texture-row boundaries. This repairs invalid WebGL unpack ranges that could prevent recoloring from reaching the GPU. The shared fix serves both installed engines and browser views.
What was checked
The required source suite passed 589 tests. The separate 53-check real WebGL2 block comparison tested equal counts at 1,350, 2,048 and 12,000 splats from multiple views. At 12,000, measured silhouette-mask error fell by 55–69% across those synthetic views; this is not a general realism or performance score.
Separate actual GPU quality and control fixtures verified source preservation, color consistency, output and picking dimensions, six-language switching, stored preferences, reset, fractional supersampling and allocation fallback. The native sparse-upload regression completed with no WebGL errors. Package, installation and public delivery are separate checks.
Known limits and unfinished work
Higher output resolution and supersampling cannot invent missing source detail. Smooth filtering is a visual tradeoff, not always the sharpest option. RTX ray tracing, ambient occlusion, reconstructed PBR materials and dynamic shadows are not implemented by these controls. Finite Gaussian surfaces are not exact CAD solids.
This remains an unsigned Windows preview. Existing local editing and source budgets remain in force. Paid commerce and public owned-download delivery have not been activated by this graphics update.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Shared graphics and surface source · c254ef75219accaca363878fb609d22fc76ee6ec
Functional checkpoint, separate from subsequent packages and destination verification.
Find and remember your Guassia application
Source checkpoint only
Find and remember your Guassia application
ASHVEIL ENGINE 0.5.21 and Guassia Asset Engine 0.1.4 repair the route back to the Guassia launcher when its executable is not in the previously assumed folder. A shared discovery routine and an explicit location chooser replace that fixed-path assumption.
Source checkpoint 8a87ced941d4c71efe51259278a6d72c67986045Source availability and destination verification are separate.
Choose a launcher location
Choose Guassia location opens a native file chooser for Guassia.exe. The selected location is remembered by the application. Cancelling keeps the previous setting; choosing a file does not launch it, sign in or accept an agreement. The control is available beside Asset Engine’s Library action and in the account connection screens.
Library and publishing actions use the remembered executable or supported installed-location discovery. Native process errors are handled and reported; a missing file or failed spawn is not reported as a successful opening. The destination arguments remain limited to the existing Guassia routes.
Library, Asset Store and editable copies
Guassia library opens owned downloads; the separate Asset Store action opens discovery. The prepared Edit in Asset Engine flow sends a verified, downloaded asset as a working copy with its source and license provenance. It never gives the editor an overwrite handle to the purchased original. An empty editor may accept the copy directly; an occupied or busy workspace exposes an explicit pending action and confirmation before replacement. Save As writes the local working copy.
A September 27 follow-up keeps the Store’s visible view and navigation history in sync, so returning to Asset Store repeatedly opens the correct section.
What was checked
Separate suites passed 44 native, 27 interface-source and 116 client checks. The prepared Asset Engine passed 20 actual application-fixture checks with zero recorded errors, covering visible routes, cancellation, launch failures and protected incoming copies. That fixture uses synthetic navigation and owned-asset responses, not a real purchase or entitlement grant. Native installers are built; launcher packaging, public delivery and installed-user acceptance remain pending. The earlier 0.5.20 upload is not assumed complete.
The follow-up Store flow passed a separate 20-check actual Electron interface fixture with zero recorded errors, including repeated Asset Store navigation. This is distinct from the 20 Asset Engine checks above; it does not establish installed or public delivery.
Known limits and unfinished work
Local Asset editing remains available without login; World’s account requirement is unchanged. Selecting a location does not install or update Guassia. The new native packages retain the previous surface-modeling and perspective-floor corrections, including the known extreme near-floor approximation limit. These remain unsigned Windows previews, with no new commerce or internet-wide automatic update service.
The current live catalog returned HTTP 200 with an empty items list, and the content-key registry is empty. Paid owned downloads are therefore unavailable in the current service. The 40 bundled local previews remain private evaluation content, separate from purchases and entitlement grants. Preparing an editing route does not create a purchase, activate commerce or grant redistribution rights.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
This separate client checkpoint records the Library and Asset Store destinations and protected asset-copy handoff; it is not proof of public availability or a successful paid download.
Near-eye floor projection correction
Source checkpoint only
Near-eye floor projection correction
Guassia and ASHVEIL ENGINE 0.5.20 accompany Guassia Asset Engine 0.1.3. This targeted patch addresses a visual regression found in the actual installed 0.5.19 World editor: floor Gaussians could form rings across the floor and sky. The successful 0.5.19 delivery and installation remain recorded separately from that quality failure.
Source checkpoint 96236820f72af3a706b6d4d8c61d7e5cfd397e2bSource availability and destination verification are separate.
Bound the perspective footprint approximation
The renderers now constrain the angular slope used to calculate perspective covariance for Gaussian centres far outside the view and close to the eye. This stabilizes the projected ellipse without moving its projected centre or changing the stored position, scale, rotation, colour or count. The shared WebGL bridge and optional WebGPU preview use the same bounded principle; the orthographic projection is unchanged.
Preserve the source and existing workflow
The patch retains the close-up support correction, imported surface footprints, modeling tools and local file formats from the prior release. Current and previous standalone application identities remain pinned so Guassia can offer Update for a verified older installation. Existing files and download URLs are preserved. This patch does not enable commerce or a new automatic update service.
What was checked
The actual 14,641-Gaussian blank-world floor was tested at matched 960 × 640 output in WebGL2 and WebGPU. Standing, crouched and oblique views passed 33 targeted checks, including unchanged canonical arrays and visible floor coverage. In the default-view diagnostic, contaminated sky pixels fell from 88,100 of 147,456 sampled pixels to zero. The prior 22 raster and 62 source-precision checks also passed. These are scoped synthetic checks, not final installed-app acceptance or a frame-rate benchmark.
Known limits and unfinished work
An extreme camera position about 20 cm above the floor still showed artifacts in a retained exploratory test. The covariance projection remains an approximation, and this patch does not promise every near-surface angle is artifact-free. Editable/resident/disk budgets, source fidelity and unsigned Windows-preview status remain unchanged. Installation, public delivery and actual owner visual acceptance require their own evidence.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
The reviewed functional checkpoint is recorded separately from the preserved 0.5.19 failure evidence and later binary, deployment and installed-app checks.
Clearer imported surfaces and practical Gaussian modeling
Verified public release
Clearer imported surfaces and practical Gaussian modeling
Guassia and ASHVEIL ENGINE 0.5.19 accompany Guassia Asset Engine 0.1.2. This update improves imported surface footprints and texture sampling, corrects close-up rendering artifacts, and adds shared parametric shapes plus local asset assembly and deformation tools.
GLB samples now use the shape of their local surface cell instead of one circular footprint for the whole model. Requested counts, sample positions and ordering remain unchanged. Material-aware bilinear sampling works in linear RGB, preserves explicitly nearest-filtered textures and prevents invisible texel colours from leaking across alpha edges. Embedded data resources are decoded through temporary local Blob URLs under the existing security policy.
Animated node, skin and morph evaluation keeps stable output arrays and repeatable rewinds. The CPU memory estimate includes the extra 24 bytes per sample used to retain local cell shape. Original GLB files are not modified; the result remains a sampled Gaussian surface, not a trained photographic reconstruction or a complete PBR material conversion.
Close-up projection and filtering
Large projected Gaussians retain their visible support near the camera and viewport edges instead of being incorrectly clipped or compressed by a fixed pixel-radius limit. The legacy renderer compensates opacity when filtering subpixel splats. These are projection and filtering corrections; they do not enlarge the stored source or apply global sharpening.
Build and reshape Gaussian parts
Ten shared parametric shapes are available in the browser workshop and native Asset Engine. Choose a shape and an explicit source count, then set dimensions, colour and the applicable bevel or thickness controls. The same generation code supplies both editors, while their placement and local-save workflows remain explicit.
In the local Asset Engine, add generated parts to the open asset and use stretch, taper or twist on the supported source. Deformations update Gaussian ellipsoid shape and orientation as well as position, with Undo/Redo and native local Save. Directional spherical-harmonic appearance is not supported by these deformation operations and is rejected rather than silently changed.
Shift-drag or right-drag pans the native Asset camera; Fit restores the framing. The output selector includes an explicit 3840 × 2160 inspection mode. Camera movement and output size do not change the saved Gaussian count or create additional source detail.
Clearer bounded disk overviews
Complete procedural collections use an independently derived, bounded surface overview to avoid regular index-sampling rings and spokes. Partial collections still select only already committed source indices. Exact chunk data and the existing generator-version checks remain unchanged. The billion-target comparison uses 50,000 resident preview Gaussians; it does not generate, load or render a billion stored records.
What was checked
Matched synthetic fixtures compare identical sample counts, source positions, cameras and output dimensions. They measure thin-surface spill, texture-gradient error, transparent-edge colour and close-up projection, alongside animation rewind and memory-preflight regressions. These checks provide bounded functional and image evidence; installation and public delivery are verified separately.
September 27 delivery follow-up: the public site passed 143 exact-file HTTPS comparisons and all three installers matched their complete hashes. Guassia 0.5.19, ASHVEIL ENGINE 0.5.19 and Asset Engine 0.1.2 were installed on the owner computer. Native executable, ASAR, version and shortcut checks passed; the 24,000-Gaussian arch opened in Asset Engine and imported, saved and played in World. These successful operations do not override the visual issue documented below.
Known limits and unfinished work
The editable asset limit remains one million source Gaussians. Billion-record disk collections remain separate from resident preview and editable assets; entering a large target does not allocate or render that many Gaussians. A 4K output setting specifies image dimensions, not captured detail, photorealism or a smooth-frame-rate guarantee. Parametric and GLB-sampled surfaces remain distinct from trained captured assets.
These remain unsigned Windows previews. Reviewed installer pins and the configured Guassia update source still govern native installation and updates. This release does not enable payments, remove account requirements from ASHVEIL ENGINE, or claim feature parity with Blender, Unreal or CAD tools.
September 27 installed-app finding: the default World floor produced unwanted rings across the floor and sky near the camera. Final visual-quality acceptance of 0.5.19 was held despite verified installation and delivery. The separate 0.5.20 correction records its own source and acceptance evidence; the original failure screenshots remain preserved.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Surface quality and modeling source · 432f499c3fc80ef9d6a13ed15f5e42dfc01b04da
The functional source checkpoint is recorded separately from packaged, installed and publicly delivered evidence.
Verified 0.5.19 public delivery · guassia-0519-authoring-live-20260927.json
The HTTPS readback records actual public file delivery; installed use and visual quality remain separate checks.
Installed acceptance and recorded visual failure · GUASSIA-QUALITY-RELEASE-20260927.json
The release record retains exact installed identities, successful native file operations and the floor-ring failure rather than treating delivery as clean visual acceptance.
Local Asset Engine access, working native menus and browser game discovery
Source checkpoint only
Local Asset Engine access, working native menus and browser game discovery
Guassia and ASHVEIL ENGINE 0.5.18 accompany Guassia Asset Engine 0.1.1. Installed Asset Engine opens into a local workspace without signing in. Both native editors gain menus connected to their existing tools, while the website leads with the hosted Doom showcase and a clear route to browse or request a free self-hosted browser-game listing.
Source checkpoint 99366f6b498eb6a636acdface67b4ac7f806e567Source availability and destination verification are separate.
Local editing with an optional account connection
Open a verified installed Guassia Asset Engine from its desktop shortcut or Guassia while signed out. Native files, disk collections and Save/Save As remain local. Connecting a Guassia account is optional for publishing integration; changing that account or choosing local mode disconnects publishing without discarding the open local work. Downloading or updating tools and using ASHVEIL ENGINE retain their account and agreement requirements, as do paid-content permissions.
The large disk workspace accepts a typed procedural source count, including one billion, within its 65,536-chunk format capacity and available storage. Each chunk holds at most 250,000 actual records; cancellation preserves committed chunks for verified resume. Requested, committed and preview counts stay separate. The resident overview is approximate, and a selected exact chunk can be copied into a one-million-record editable asset. This is not whole-collection editing, arbitrary scan conversion or proof of billion-record rendering performance.
Menus that operate the native workspace
World exposes File, Edit, View, Play, Tools, Workspaces and Help. Menu actions dispatch the existing new/open/save, object history, framing, playtest and workspace controls. Text-field undo and clipboard commands retain text focus rather than changing scene objects. Unsaved-work checks protect close and workspace changes, and Keep Editing cancels either transition.
Asset Engine provides File, Edit, View, Account and Help menus for local files, collection creation/open/recovery, selection, history, camera views and STL proxy export. Unavailable actions are disabled. The local guide explains shortcuts, and menu labels follow the six-language chooser. These menus expose implemented tools; they do not imply Blender, Unreal or CAD feature parity.
Browser games first
The homepage leads with Doom hosted by Chris. Browse the reviewed catalog at /games/ with title/creator search and a category filter; separate Guassia examples remain labeled. Games and leaderboard frames load only after an explicit choice. The Guassia page displays Anonymous for a guest or a verified username for a signed-in player, without exposing email addresses or sending that identity to the external game or leaderboard.
An explicit, free self-hosted listing request
At /games/submit/, provide a public HTTPS game link, title and description, then explicitly confirm free play, listing permission and content rights. Online submission requires a verified account, working CAPTCHA and enabled service configuration. Requests stay private for review; idempotent retries do not create duplicate requests. The fallback JSON download is only a local copy. A free browser listing does not change the $100 initial desktop game-publishing policy or the paid-sale 70/30 split.
What was checked
Source and isolated Electron checks cover native menu dispatch, visible controls, guest Asset opening, World access refusal, exact installed-file checks, account changes, unsaved-work protection, responsive browser routes and all six core interface dictionaries. These checks use local fixtures where applicable; installed-owner acceptance and public deployment retain separate receipts.
Known limits and unfinished work
Native applications remain unsigned Windows x64 previews. Exact hashes identify reviewed bytes, not an Authenticode publisher signature. Application updates remain tied to reviewed Guassia release pins and the configured launcher update source; this is not a promise that every installation updates itself over the internet. Existing asset, disk, memory and rendering limits remain in force.
Online browser-game submissions remain unavailable until the live form and CAPTCHA configuration are connected. A listing request is not approval, file hosting, game publication or payment. The external Doom game and leaderboard retain their own language, identity, availability and rules. Six-language interface coverage is not a claim of fluent human review or translation of external game content.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Native navigation and browser discovery source · 99366f6b498eb6a636acdface67b4ac7f806e567
The functional source checkpoint records this change independently of later package, installation and public-delivery evidence.
A separate Asset Engine, native editing and creator update requests
Source checkpoint only
A separate Asset Engine, native editing and creator update requests
Guassia 0.5.17 adds Guassia Asset Engine 0.1.0 as its own installed Windows application alongside ASHVEIL ENGINE. Guassia manages each application’s Install, Update and Open state independently. The asset workspace edits local Gaussian files, and creators can prepare versioned update requests for their existing published games and assets.
Source checkpoint 14c53ca03c4fbe240e192baefa5d25febf999c44Source availability and destination verification are separate.
Two independent native applications
Each application has its own product identity, installation directory, executable and ASAR verification. A legacy creator-tools package cannot establish either native installation or silently open the browser studio. Remembered accounts can open verified installed applications offline; installing or updating still requires the current account and recorded creator agreement.
Local assets and precise editing controls
Open and save native .gasset files, import supported GLB, PLY or image sources, or start with a Gaussian primitive. Display measurements in millimetres, centimetres, metres, inches or feet while stored coordinates remain metres. Region selection, numeric translation, rotation, uniform scaling, centring, dimensions and centre-to-centre measurement operate on explicit local copies. Undo and redo have a bounded history; colour, opacity and visibility edits remain reversible layers.
The editor checks the 128 MiB native asset-file limit before expensive copying or encoding and keeps the current work open after refusal. Reopened files receive unique edit-layer IDs. The six core languages cover the asset workspace controls and fixed guidance; authored names, numerical diagnostics and error details are preserved, with English fallback where no translation exists.
Gaussian appearance and an optional print surface
The native World renderer can display assets with more than 256 active appearance overrides through a dense RGBA fallback, while retaining the sparse fast path for smaller edits. Authoritative Gaussian positions and saved layers remain intact, and opacity-only edits preserve directional SH colour. This does not increase the 256-point interactive brush selection. STL export explicitly derives a bounded voxel surface for printing; the original visible asset remains Gaussian. The proxy needs slicer inspection and has no watertightness, tolerance or manufacturing-quality guarantee.
Update an existing published item
Publish now provides a private update-request path for a game or asset the signed-in creator already owns and has published. Save a version and release notes against the existing listing; request IDs and the base artifact reference are immutable, and metadata can be viewed or copied as JSON. Readiness remains blocked until actual artifact upload and review are available. An update does not create a second publishing fee or replace player licenses. The initial $100 game-publishing policy is unchanged; this work does not enable purchases, payouts or public artifact promotion.
Large source collections stay on disk
Type a total count for a procedural source collection, including billion-scale requests when disk capacity permits. Immutable .gasset chunks hold at most 250,000 actual Gaussians each; a checksummed manifest records their contiguous ranges, sizes and bounds. The directory is bounded to 65,536 chunks, rather than unlimited metadata. Disk space is checked before creation and each append. Atomic checkpoints retain the last committed count after cancellation or a failed write; reopening for resume verifies all saved chunks and binds the exact generator version, seed, dimensions, colour and requested total.
Requested, committed and preview counts are separate. A reduced procedural overview or selected source chunk is a bounded preview, not proof that the whole requested collection exists or fits in GPU memory. A source chunk can be exported as an editable copy; the immutable collection is not silently loaded as one giant .gasset. Higher sampling of an analytic shape does not create new captured detail. This release does not claim that a billion-record collection was generated, rendered simultaneously or benchmarked smoothly.
Owned games on a fresh installation
Guassia now includes a fixed first-party game player with per-file hash checks and offline language files and notices. Opening an owned declarative game no longer depends on an old .gtools editor installation. The player keeps its isolated sandbox and does not run JavaScript supplied by a game package.
What was checked
Targeted source checks cover both native product boundaries, account and agreement changes, exact file identities, rejected downloads, offline installed Open, asset-file preflight, edit history and six-language controls. Separate application, GPU and installed-owner checks retain their own receipts. Source tests alone are not evidence that this version has been publicly delivered or accepted on another computer.
Known limits and unfinished work
This is a Windows x64 preview, not unlimited geometry or a certified CAD replacement. A single editable asset supports up to 1,000,000 source Gaussians; individual native files are limited to 128 MiB, and cleanup and print proxies have lower explicit budgets. More output pixels do not create source detail, captured lighting is not automatically relit, and directional SH rotation remains blocked. Both applications remain unsigned; approved application pins arrive through Guassia releases, not an unrestricted internet-wide automatic updater.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Separate asset application and creator workflow source · 14c53ca03c4fbe240e192baefa5d25febf999c44
The functional source checkpoint is recorded independently of later binary, public-delivery and owner-acceptance receipts.
Native engine account handoff and first-launch repair
Verified public release
Native engine account handoff and first-launch repair
Version 0.5.16 addresses two failures observed after installing 0.5.15 on the owner’s computer: the separate engine could not decrypt Guassia’s account record, and its first window could stay hidden. This correction keeps the standalone application and replaces the account handoff, makes startup visible and recognizes the prior installation for Update.
A local account handoff without service credentials
Guassia handles its own protected account session. The engine receives a bounded local identity handoff instead of trying to decrypt another application’s session storage. Passwords, service access tokens and refresh tokens are not handed to the engine. Remembered offline identity is stored in the engine’s own application context and remains tied to the same account; it does not grant paid-content ownership or permission to download new content.
Visible startup and a recognized upgrade
The packaged application explicitly shows its first ready window, and launching it again restores and focuses the existing window. Guassia retains the approved 0.5.15 installed-file identities so a matching older installation is offered Update. The new version still requires exact executable and ASAR verification; an opened installer alone is not recorded as a completed upgrade.
What was checked
September 27 acceptance: the public Guassia and ASHVEIL ENGINE 0.5.16 installers were read back over HTTPS and their complete hashes matched the approved artifacts. The owner’s actual installed Ash account then entered the visible native World editor, and the desktop shortcut reopened that editor. Installed executable and ASAR hashes matched the frozen native build. These are separate from the earlier synthetic-account tests; this owner smoke check did not simulate a disconnected network or a full game playthrough.
Known limits and unfinished work
This repair does not add graphics features, enable commerce or create a global automatic updater. The applications remain unsigned Windows previews. Local identity is not a payment entitlement, and its remembered offline state does not prove uninterrupted access on another device.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Native account and startup correction · df17b60606e8abbec397d7b113696c443caf3d04
A later source correction following actual 0.5.15 owner-installation failures; earlier deployment receipts do not verify the repair.
Verified 0.5.16 public installers · guassia-0516-live-installers-20260927.json
Anonymous HTTPS descriptor, part and complete-installer hashes matched both pinned releases. This is delivery evidence; owner access is recorded separately.
Actual owner World-entry and shortcut acceptance · guassia-0516-actual-owner-acceptance-20260927.json
The operator observed the remembered Ash account in the installed native World editor and reopened it through the desktop shortcut. This additive receipt binds exact installed-file hashes and inspected screenshots without reading credentials.
ASHVEIL ENGINE becomes a separate desktop application
Historical public delivery verified
ASHVEIL ENGINE becomes a separate desktop application
Version 0.5.15 separates the native ASHVEIL ENGINE application from Guassia. Install in My Library uses a dedicated Windows installer; Open launches the verified engine executable. The application has its own desktop shortcut and retains the World, Music and Film workspaces. Guassia continues to manage accounts, creator consent and installation.
A browser Studio or .gtools package no longer counts as an installed game engine. The engine card checks the separate executable and app.asar against approved sizes and SHA-256 hashes. Opening an installer is reported separately from a confirmed installation. The asset creator keeps its existing .gtools route, so installing or updating it does not replace the native engine.
Local creation workspaces
The standalone package retains the current world editor and mission runtime, music arrangement tools, film workspace and native project-file operations. World opens to the blank outdoor starting scene. Existing Gaussian authoring modules and vendored rendering dependencies are packaged locally. Local Blob texture reads and full Float32 source positions are enabled for the native engine origin; saved source arrays are preserved. This is the current editor preview, not a claim of feature parity with other engines.
Account checks continue across installation
Download requires a freshly checked signed-in account and its current creator-policy receipt. Sign-out, account changes, expired access or an active editor stop a pending installation path. Installation and creation remain free. The separate application uses the local account handoff; opening a public installer file alone does not grant creator access. Existing account-bound offline access remains distinct from permission to download new software.
Reviewed release pins and bounded downloads
The Guassia release contains approved engine installer and installed-file identities. Downloads use ordered, content-addressed parts with per-part and full-file integrity checks. The release helper validates the Windows executable headers and ASAR application identity before creating its descriptor. New trusted engine versions currently arrive in reviewed Guassia releases; this does not create an internet-wide automatic update feed. The existing Guassia app updater and the separate asset-creator update route keep their own scope.
What was checked
Focused source tests check installer-part reconstruction, application identity, separate tool state, account and consent changes, cancellation, duplicate requests and honest installer-opened status. New launcher guidance and this entry have six core translations. Packaged runtime checks, public delivery and actual installation are separate release evidence; source tests alone do not establish them.
Known limits and unfinished work
This release remains a Windows x64 preview and is unsigned. SHA-256 verification is integrity checking, not an Authenticode publisher certificate, so Windows warnings can remain. Native applications and project formats are not made interchangeable with browser Studio merely by sharing the brand. No unlimited scene size, photographic quality, frame-rate improvement, paid-commerce activation or complete replacement of other engines is claimed.
September 27 delivery follow-up: 0.5.15 was publicly delivered and installed, but the owner’s actual native launch exposed a cross-application account decryption failure and a first window that could stay hidden. Isolated startup checks had not established owner access. These failures are the reason for the separate 0.5.16 repair; successful delivery of 0.5.15 is not proof of a working account handoff.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Standalone source and packaging contract · e3778f9b440b9df8809fa0818aa2fc986769206b
The release separates the executable, creator account boundary and legacy asset package. Delivery is verified independently.
Local fixtures reconstruct every part and reject stale application identity, missing runtime entries and invalid size or executable headers.
Verified 0.5.15 public delivery · guassia-authoring-live-verification-0515-20260927.json
Public HTTPS readback verified the website delivery. The dated limitation records the separate native owner-access failures; this receipt does not validate the later repair.
Hosted DOOM showcase and shared leaderboard
Included with this site release
Hosted DOOM showcase and shared leaderboard
The public Games preview now links to an optional, unofficial hosted DOOM showcase at /play/doom/. Visitors choose when to load the external game or its shared leaderboard. This website integration is separate from the installed ASHVEIL ENGINE and its project files.
Source checkpoint 4ca7f78d0eae0f2991de57cabc9924d4c46048f7Source availability and destination verification are separate.
Load only when requested
Load game and Load leaderboard create their separate embedded views only after a deliberate choice. The page does not connect to the game host before a load action or direct-link visit. Public access needs no Guassia account, and the Games page remains a preview rather than browser checkout.
Unload removes the selected frame, cancels its loading timer and leaves any fullscreen view owned by that frame. Leaving the page also removes active frames. Returning through browser history restores working load controls without automatically restarting the external content. Direct links remain available when embedding is unavailable.
September 27 follow-up: a successful fullscreen retry clears an earlier unavailable message. Late fullscreen results from an unloaded or replaced frame are ignored, so they cannot overwrite the current panel status. This correction has separate source and regression evidence below.
An explicit external-host boundary
Only play.chriskalkowski.com is added to the parent frame policy; the parent connection policy stays unchanged. Both frames suppress referrer data. The game sandbox permits scripts, its own origin and requested pointer capture, with a fullscreen permission; the leaderboard permits scripts and its own origin only. These permissions are not evidence that every browser interaction has succeeded.
The hosted experience keeps its existing service and leaderboard. Guassia does not forward account credentials or messages, proxy score submissions, or create a second score database. The page identifies the external host and explains that the showcase is not a native ASHVEIL project or an installed store package.
What was checked
Source checks cover route discovery, restrictive frame policy, deliberate loading, unloading, timeout cleanup and browser-history lifecycle. All new interface guidance and this release entry have six core translations. The separate public-header intake found both hosted destinations reachable and Guassia origins allowed for embedding; those header checks did not play the game or submit a score.
Known limits and unfinished work
Native game adaptation remains separate. No third-party maps, models or game assets are copied into the Guassia site, installer or asset library by this integration. Host availability, full-campaign completion, pointer capture, fullscreen behavior and accepted leaderboard submissions need their own live evidence. The Windows 0.5.14 repair package and its existing account, consent and payment boundaries remain unchanged.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
September 27 fullscreen-status follow-up source · 429dab199fd28bcc33751c704216d76b3f8fc47f
A later website-only correction; earlier deployment observations do not verify this change.
Route and lifecycle regression checks · guassia-hosted-showcase-shared-tests-20260927-02.log
Source-level controls, cleanup and translation checks; actual hosted browser acceptance is recorded separately.
Current installer and clearer creator agreement
Verified public release
Current installer and clearer creator agreement
Version 0.5.14 corrects the stale Windows download, keeps agreement controls visible, and records installation terms separately for each owned game or asset. Agreement is an explicit choice tied to the signed-in account; unchanged terms do not prompt again on reinstall.
Review creator terms provides a clear entry point. The responsive dialog keeps the agreement actions visible while the exact policy text scrolls separately. Loading, retry, recording and account-accepted states explain what is happening. Not now closes the review without recording agreement.
Nothing is accepted automatically. The existing creator-policy checkbox remains explicit. Install uses Accept and install; reviewing the creator policy without installing keeps Agree and continue. Installation continues only after the service confirms the current account and exact policy version/hash. Sign-in alone is not consent, and the creator-policy text is unchanged.
One current download route
The Windows download metadata moves from the stale 0.5.1 launcher to 0.5.14. The site packager rejects a download page or manifest with an app-version mismatch and verifies every hosted chunk and the reconstructed installer against their sizes and SHA-256 hashes. These release checks prevent a stale pointer from passing packaging; they do not prove installation on another computer or sign an unsigned installer.
Separate agreement for each owned item
Install opens the terms for the selected owned game or asset when this account has not accepted that exact item and terms version. Accept and install saves the account-bound receipt before downloading; declining starts no download. Reinstalling under unchanged terms reuses the receipt. Item installation agreement is separate from creator-policy acceptance and creates no purchase, publishing fee or new ownership entitlement.
What was checked
The new review, loading, retry and acceptance guidance is present in all six core runtime dictionaries. Translation checks preserve the existing agreement checkbox and continue action and verify the unchanged policy text against its stored hash. Delivery status stays separate from these source checks.
Known limits and unfinished work
The free creation tools still require a verified account and explicit creator-policy acceptance. This repair does not enable purchases, token spending or seller payouts, change commercial fees, or establish legal compliance in every country. The Windows installer remains Authenticode unsigned; Windows may still show an unknown-publisher warning.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Installer and consent source checkpoint · 33b93b9239dc8da745f93f4c2a14dd005ed1f6a1
Source identity; public and installed verification remain separate.
Six core languages, explicit agreement labels and unchanged policy hash.
Verified public delivery · guassia-0514-first-production-20260927.json
HTTPS readback matches the published release. Mocked agreement tests remain separate from actual user acceptance.
Optional WebGPU close-up inspection
Historical public delivery verified
Optional WebGPU close-up inspection
Guassia 0.5.13 adds an explicit WebGPU asset preview beside the existing inspector. It uses GPU projection and sorting for one static RGB source without replacing the standard editor or Play renderer. Public website delivery, installation and the authenticated creator-tool update are verified separately from graphics tests.
Open GPU preview creates a dedicated canvas only on request. It preserves the source arrays, account and save rules, and supported RGB/opacity edits. A replacement must finish its first frame before it replaces the last successful preview. Closing or changing selection cancels stale work and releases its resources.
Orbit, zoom, eye-height and close-up cameras are separate from the standard inspector. Fit whole asset includes a conservative three-sigma splat envelope and the output aspect ratio. Panel, 1080p and 4K describe output pixels; they do not add captured detail. New controls and status messages have all six core translations.
Finite, visible resource budgets
Auto allows up to 1,000,000 source and placed Gaussians for one preview instance. Advanced accepts an explicit count up to the sorter ceiling of 2,097,152, subject to the negotiated device limits. Requested, effective and supported limits are shown separately; lower device limits require an explicit adjustment choice. Asset detail is never silently discarded to fit.
GPU and combined working-memory estimates include the current and replacement preview together. They cover known source, sorting and render buffers, with additional driver and JavaScript overhead. They are not measurements of free memory or a hardware guarantee. Unsupported devices and SH, animated, deforming, diffuse-lit, fog or LOD content keep their standard rendering path.
What was checked
The supplied integration snapshot passed all 79 package and 52 source-file hash checks. Independent synthetic GPU tests passed 50 exact sorter comparisons and 18 adapter checks. The editor lifecycle, budget and camera regression suite passed 31 focused checks. These counts describe separate test scopes and are not a speedup benchmark.
The exact packaged editor passed 14 real interface checks: open, orbit, 4K output, rejected-budget retention, close/cancel/reopen, unchanged project and embedded asset bytes after Save, and ordinary Play and return. Post-run source binding matched all 100 decoded package files to the reviewed 0.5.13 package and frozen source. This is functional evidence, not a general frame-rate or speedup claim.
Public release verification passed 135 HTTPS artifact comparisons. On the observed Windows device, Guassia 0.5.13 retained the existing sign-in; the app files matched the reviewed build and a local update check reported up to date. My library then installed the authenticated 0.5.13 creator-tool update with matching package bytes. These are distinct launcher and creator-tool delivery checks.
Known limits and unfinished work
This is an optional one-source RGB preview, not a migration of the entire engine to WebGPU. It does not raise project import limits or promise unlimited Gaussians, photorealism, CAD accuracy or faster gameplay. No private maps, manufacturer assets or rejected fixture art are included. Existing authentication, commerce restrictions and the separate launcher/tool update paths remain unchanged.
Installed acceptance covers one Windows device and account. The installer remains Authenticode unsigned. Automatic launcher updates were off, and the observed launcher update used the local release feed; an internet-wide launcher rollout is not established. Hosted creator-tool updates remain separately authenticated. No new offline test or enabled purchase, token or seller-payout flow is claimed.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Fourteen interface checks with post-run source and package binding.
Public and installed release evidence · guassia-installed-gpu-0513-20260927.json
Separate HTTPS readback, installed app and authenticated creator-tool update receipts.
Clearer tools, controlled detail and current public pages
Historical public delivery verified
Clearer tools, controlled detail and current public pages
Guassia 0.5.12 is released with controlled model-detail imports, consistent native save limits and a direct return from installed Studio to My library. Public pages and account notices now match the current tools. Website delivery and an actual installed app and creator-tool update are verified separately from graphics benchmarks.
Model conversion distributes samples through deterministic equal-area surface cells instead of independently random points. It preserves the selected sample count and area allocation. This changes Gaussian placement without modifying or rendering the imported triangle source as visible world geometry.
Model import offers 100,000 and 250,000 high-detail choices, an advanced 1,000,000-sample option and an exact custom count within that ceiling. The ordinary default stays at 16,000. The panel shows attribute bytes and planned CPU working memory before conversion, with source geometry and file copies checked separately. Native Gaussian assets keep their authored detail within storage limits.
The import panel can select High Gaussian detail for the next playtest: up to 1,500,000 resident source splats and 1,000,000 active object samples, while devices reporting 4 GB RAM or less keep the lower budget. Starting quality sets this source budget; Auto quality changes during play affect render size only. Frame time is elapsed wall time, not a GPU timer. Local Blob textures are permitted in the creator context without opening store privileges or new external hosts.
Only the installed Guassia creator origin enables extended source-position storage in the native editor, Studio inspector, scene view and Play. It preserves canonical Float32 positions during upload; browser and file previews keep the packed mode. Extended source slots use 32 bytes instead of 16 per padded slot. Other attributes remain encoded, other GPU resources are additional, and this is not certified CAD accuracy. The native profiler exposes the selected position mode.
Clear routes and an empty starting point
The historical /desktop-store/ entry redirects to the current informational /store/ page. Its static fallback uses that same page, with routes to downloads and product previews. It no longer exposes the old browser sign-in mock. No browser checkout or purchase is added.
Home, Studio and learning instructions now describe an open white floor and sky. Walls, imported objects, music and objectives remain optional. The new instructions have complete English, Spanish, Simplified Chinese, German, French and Dutch text.
The existing ASHVEIL world receives a screen-reader heading through its shared page shell without rebuilding its world data, audio or renderer. The founder Easter egg keeps its original introduction and receives an explicit noindex directive.
Account and storage disclosures
Browser notices now describe the available verified accounts, username and email handling, sessions, server-side creator listing drafts and policy records, and device-local project and media storage. Archiving a draft is distinguished from erasing an account. The agreed creator policy, age rules, seller requirements and payment gates are unchanged.
Consistent native files and a clear return path
The native editor applies the same 256 MiB world-file and 128 MiB asset-file limits when saving and reopening. A metadata-only preflight rejects oversized work before source snapshots and large encoding, and the final encoded size is checked again. Rejection leaves the current project open. Cancelled saves and browser download requests no longer claim a confirmed disk save.
Installed Studio shows an Installed creator tools bar with Back to My Library. The return link opens the exact local Guassia library route; the editor receives no store privileges. Ordinary browser Studio is unchanged. The new labels are available in the six core languages.
Software cards use a wider layout in My library so installed versions and Install, Update or Open actions are easier to scan.
What was checked
Read-only HTTPS and HTML inspection covered 31 public pages, 38 same-site paths and 858 internal links. Static language mounts and service-gated forms were checked. JavaScript-created Studio anchors and Cloudflare email placeholders were distinguished from confirmed broken links; this inspection alone does not prove every interactive flow.
The public-page and language regression suite passed 24 tests. The separate account/storage disclosure, authentication and policy suite passed 33 tests. These source checks preserve the existing commerce restrictions and do not constitute legal review or a live deployment receipt.
Model-import changes passed 49 focused source tests; native file capacity passed 32. The final Float32 desktop build passed 12 million-sample import/preview/save/reopen/play checks with unchanged source and attribute hashes. At 1440 × 1000 after a ten-second settle, 30 CPU-plus-awaited-renderer moving-average observations had a median of 90.9 ms and a 95th percentile of 116.2 ms on this PC. They are not raw frame or GPU timings. This is functional acceptance, not smooth-performance proof; the earlier packed-mode measurement is historical and not directly comparable.
The explicit position-precision option passed 33 unit tests and 62 actual WebGL2 checks on a synthetic fixture, including two source centers that the packed representation merged but the extended representation kept distinct. This local graphics evidence is separate from an installed release and does not measure full-scene CAD accuracy.
Public 0.5.12 delivery passed 131 exact HTTPS file comparisons. On the observed Windows device, the installed app matched the reviewed build, retained the existing sign-in, and My library updated both shared creator tools from 0.5.11 to 0.5.12. Open launched installed Studio with the library return bar and million-sample control. The live catalog serves 0.5.12 to compatible clients and preserves 0.5.9 for legacy clients; unauthenticated package access remains denied. Back to My Library returned successfully, and a subsequent local launcher check reported up to date.
Known limits and unfinished work
Installed acceptance covers one Windows device and account, not every user. The Windows installer remains Authenticode unsigned. The launcher update used a local release feed and installer; a shared internet-wide launcher rollout is not verified. Creator-tool updates are separately available through authenticated online delivery. The import ceiling and memory estimates are finite safeguards, not a guarantee of smooth million-splat rendering. Purchases, token spending and seller payouts remain unavailable; no new offline acceptance is claimed.
A 3840 × 2160 render specifies output pixels, not the fidelity of a captured or converted asset. The demonstrated fixture is synthetic; it does not establish photorealistic characters, relightable captures, unlimited world capacity or smooth million-splat performance on other hardware. Captured colours can retain baked lighting.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Targeted page, translation, redirect and accessible-shell checks.
Million-sample import and round-trip acceptance · guassia-one-million-final-0.5.12-qa-20260927-01.json
The final frozen Float32 build passed twelve fixture checks and records the current moving-average timing. The earlier packed-mode receipt is retained separately and is not a like-for-like comparison.
Native save and reopen capacity checks · guassia-native-capacity-consistency-tests-20260927.log
Thirty-two focused source checks; no larger GPU or source-count limit is inferred.
Sixty-two real WebGL2 checks; the earlier harness-only failed run is retained separately.
Verified 0.5.12 delivery and installed update · guassia-installed-quality-0512-20260927.json
Records the production deployment, 131-file readback, matching installed app and active tool hashes, retained sign-in and actual installed Studio launch.
Free creation tools in your library
Historical public delivery verified
Free creation tools in your library
Guassia 0.5.11 adds ASHVEIL ENGINE and ASHVEIL ASSET CREATOR to the signed-in library with Install, Update and Open actions. The compatible hosted release is live, and an actual installed client updated both tools from 0.5.10 to 0.5.11 through My library. Older clients retain their compatible package.
My library includes both free tools under Everything and Software, even when there are no purchased games or assets. Installing either tool installs their shared package. It requires verified sign-in and the current creator agreement, but no purchase, credits or publishing fee. Installation starts only when requested.
The cards distinguish installed and available versions. Check tool updates refreshes availability; Update appears only for a newer compatible release. Offline or failed checks preserve Open for installed tools and show that update status is unknown. Games and Assets filters keep their existing ownership and download behavior.
Keep updates compatible and account-controlled
The live hosted release keeps the reviewed 0.5.9 package for clients without a valid version header or below 0.5.10. Compatible clients receive 0.5.11. The version header selects compatibility only; verified account, creator-agreement and native-download checks still apply. At most two verified packages are cached per edge binding.
Package activation rejects downgrades and different bytes using the same installed version. Exact size, SHA-256 and allowed file paths are checked before activation. Account changes and open editors block unsafe replacement; a failed download keeps the previous installation. Updating creator tools is separate from updating the Guassia launcher.
Move projects between browser and desktop Studio
Open project validates an editable .guassia.zip and its Gaussian, character and audio sources before confirmation or storage. Camera and spawn, optional story/NPC/script settings, source and instance edits, appearance coefficients and original media survive the shared Studio round trip. Unknown or unsupported fields are rejected with an explanation. The native world editor uses the separate .gworld format.
Learn from an optional complete small game
Beacon Run is an original optional courtyard example with an editable spawn, a patrol NPC, a required collectible, a locked exit and an ending. Its nine instances reuse four procedural Gaussian sources. Load it explicitly to explore the objective controls, play, save and reopen it. New world still starts empty, with no required story or music.
What was checked
Hosted delivery passed 38 targeted Node tests and six isolated upload-packager tests. They cover version compatibility, unchanged account and policy gates, exact package identity, bounded cache reuse and rejected duplicate or unreviewed deployment files. These are source and synthetic-package checks; they do not establish live installation or production capacity.
Project interchange passed 62 focused source tests. Beacon Run passed 15 targeted source/lifecycle tests and 21 isolated Electron checks using the built Studio, actual controls, gameplay and save/reimport. These suites overlap other checks and are not an installed-account or live-deployment receipt.
The broader regression runs passed 356 client/package tests, 491 editor/runtime tests and 155 platform tests, with no failures or skipped tests. These groups overlap the focused checks and must not be added together as a unique test count. The live and installed evidence is recorded below.
Public release verification passed 130 exact HTTPS file comparisons. On the observed Windows device, the installed 0.5.11 client retained the existing account, and My library → Update replaced the shared creation tools from 0.5.10 with the reviewed 0.5.11 bytes. Both cards then showed Open and Up to date. Live catalog checks returned 0.5.9 for the legacy route and 0.5.11 for the compatible route.
Known limits and unfinished work
Actual update acceptance covers one Windows device and account, not every user. The Windows installer remains Authenticode unsigned. Automatic launcher updates were disabled on this device; the observed flow used the in-app update controls and installer. Updating hosted creation tools is separate from updating the Guassia app, and this receipt does not establish a new offline test.
The tools remain free previews with supported formats and finite hardware budgets. No game or asset purchase, paid publishing, token spending or creator payout is enabled. New worlds remain a blank open floor; examples and story objectives are optional.
Project imports are additive across separate local media stores. Cancellation, superseded work or an intervening draft edit preserves the active project; a failed storage commit can leave unused imported media. Device-local storage identifiers intentionally change. The example is procedural and does not establish photorealism, unlimited detail or multiplayer acceptance.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Library and compatible update source · dd10f1e96c46e14ffc72095c4f51dabf25c12c57
The source checkpoint records the launcher, package and compatibility implementation; deployment is separately verified.
The built-Studio receipt records 21 real-control and rendering checks. It is separate from public delivery and native account acceptance.
Live release and installed library update · guassia-library-update-delivery-20260927.json
Records the 130-file public readback, deployment identity, actual installed version and matching shared-tool activation. No credentials are included.
Native world editor and reversible playtests
Historical public delivery verified
Native world editor and reversible playtests
The locally installed Guassia 0.5.10 preview now includes a separate native world editor. Its real account-controlled launch rendered an open Gaussian floor and sky. The existing studio remains the default creation tool, while hosted creator-tool downloads intentionally remain on compatible version 0.5.9.
After sign-in and installation of the current free creation-tools package, choose Open native world editor from the engine card or application menu. The editor has a route back to the launcher. Its separate entry does not replace the studio or asset workshop, and introduces no purchase or publishing fee.
Open a project, play, then return to editing
The native editor keeps the blank open-world start and optional camera modes. Open project accepts supported .gworld files. Save and Save As export a portable project through the local download flow when a direct file picker is unavailable; imported mission metadata is retained.
Play selects the compatible controller for the project. Imported missions own their first-person camera and input instead of competing with the editor camera. Stop removes temporary gameplay objects, controls and HUD, then restores the exact authored world and camera. Ordinary top-down projects retain their existing controller.
Preserve input and account boundaries
Pointer capture is restricted to the signed-in main editor document, with drag-to-look as a fallback. The native page keeps external-only styles and receives no new account, store or filesystem bridge. Sign-out and application updates remain protected while an editor is open.
Imported mission collision remains separate from the Gaussian appearance. Supported appearance, spawn and actor edits are checked against the collision contract; structural changes that break it cannot silently start with stale collision. Asynchronous startup failures and world replacement dispose the active play session cleanly.
Recover cleanly from browser playtest changes
Closing a browser playtest cancels late initialization, rendering and recovery. Restart waits for room collision data before resuming; pausing while a room loads keeps the game paused. Late mouse-capture results respect drag mode and pause. Invalid inherited resolution names fall back to Auto.
What was checked
Twenty-four targeted source tests passed for creator routes, account continuity, pointer permissions, editor protection and package restrictions. The packaging fixture also checks combined mission styles and rejects private map inputs. Its stub bundler does not establish a finished installer.
Twenty-one checks passed in isolated Electron using the real Gaussian renderer and three private mission fixtures. Movement, pause, exact Stop restoration, HUD cleanup and a real portable-project download were verified without runtime or CSP errors. This is source-rendering evidence, not installed-account or multiplayer acceptance.
The wider shared regression run passed 469 tests, and the native/account/packaging run passed 297 tests. These suites overlap and must not be added as unique tests. The actual packaged native bundle also passed 27 isolated rendering checks, including level framing and wheel scale. Installed-user acceptance remains a separate release step.
The actual Windows update flow completed Check, Copy and Apply, followed by the normal per-user installer. The installed executable and application archive matched the frozen 9b8a035 source release. The existing account remained signed in. Installing the local 0.5.10 creator package made both tools show Installed, and Open native world editor rendered the blank white Gaussian floor and blue sky.
Thirteen further isolated checks passed against the frozen studio package: asset rendering, real project Save/Open controls, source-preserving round trips through cleared storage, and top-down/in-scene camera views. These are separate from the real installed-account launch; they are not a complete manual game playthrough or an offline test.
The browser release passed all 130 live HTTPS comparisons against the reviewed build. This verifies delivery of the browser playtest fixes and existing site files, with documented hosting transformations accounted for. The native 0.5.10 installation remains local; the authenticated hosted creator download still serves compatible 0.5.9.
After installation, Check for updates reported that the local release channel was current; automatic updates remained off. The actual installed editor also opened a private Hangar fixture: Play displayed the mission HUD, Pause displayed its overlay, and Stop restored authoring controls and removed the HUD. This bounded check does not establish firing, a completed campaign or a full manual playthrough.
Known limits and unfinished work
The mission compatibility preview opens one selected project at a time. Automatic mission sequencing, arbitrary collision reconstruction and authoritative multiplayer are not included. Copyrighted reference map data is not shipped with Guassia.
Version 0.5.10 is verified as a local Windows installation and is still unsigned. Hosted tools stay at 0.5.9 because older clients cannot load the new native package path. Browser changes passed public HTTPS verification. Internet-wide automatic client updates and paid marketplace operations remain inactive.
The new launcher entry is translated into the six core languages. Existing native-editor labels still need a complete language review. Source checks do not establish performance on every GPU, unlimited scene detail or a complete replacement for Blender or Unreal Engine.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Native and browser playtest source · 1ab36d830655131d51602c0bb6b25d60f490364a
This checkpoint includes the reviewed controller integration, browser lifecycle fixes and authenticated native package route. Build and deployment remain separate records.
Native route and package tests · guassia-native-route-package-tests-20260926.log
The source suite covers isolated creator access and reviewed package entries. It does not distribute reference maps.
All 27 checks passed against the actual packaged bundle in an isolated host. This is not an installed-account, public deployment or multiplayer receipt.
Installed Windows update and native editor · guassia-installed-0510-20260926.json
The receipt verifies the actual local 0.5.10 installation, matching executable/archive hashes, retained account, local tool-package installation and rendered native route. The publisher signature remains absent.
Frozen studio package verification · guassia-handoff-studio-release-qa-20260927-versioned.json
Thirteen isolated checks verify actual save/open and rendering behavior against the frozen creator package. They do not establish public deployment or offline acceptance.
All 130 live HTTPS comparisons passed for deployment 9fe1418d-5886-477e-ba3b-21e659115368. The receipt records actual browser delivery; the local native installation and hosted 0.5.9 package remain distinct.
Free creation tools inside Guassia
Historical public delivery verified
Free creation tools inside Guassia
On September 26, free in-app delivery of ASHVEIL ENGINE and ASHVEIL ASSET CREATOR became available to verified Guassia accounts. The installed Windows client completed a real requested download and installed both tools. The reviewed 0.5.9 package prepared on September 24 is unchanged.
Sign in with a verified Guassia account, accept the current creator agreement, and request installation from Free creation tools. One package installs both ASHVEIL ENGINE and the ASHVEIL ASSET CREATOR. Installation is optional and does not begin merely because an account was created.
The reviewed 0.5.9 creator package contains 12,388,615 bytes. The client checks the exact release size and SHA-256 plus the package’s allowed paths and individual file hashes before installation. After verified sign-in and installation, the remembered account can use installed tools offline. This does not enable offline downloads.
Protect the download boundary
The prepared delivery path uses an encrypted artifact on the existing site and a server-only decryption key. Plain creator-package bytes are returned only after verified account and creator-agreement checks. This path avoids activating a new R2 storage subscription; it does not make downloaded software impossible to copy.
Understand the current editor preview
ASHVEIL ENGINE supports Gaussian world authoring, imported assets, optional cameras and interactions, playtesting and local project files. The asset tool imports, inspects and edits supported Gaussian assets. These are the current editor previews, with bounded rendering and supported import formats; they are not a complete replacement for Unreal Engine or Blender.
What was checked
165 automated source tests passed. Thirteen additional checks ran against the exact encrypted package in the local workerd edge runtime, covering verified sign-in, accepted policy, frozen accounts, tampered data, repeated downloads and exact package hashes. These local fixtures do not establish production CPU or memory capacity.
Production verification passed all 130 HTTPS file checks and 13 public delivery checks. Both tools report free availability; unauthenticated requests and browser-context downloads are denied. Checked public responses did not expose the server key, server module or plain creator package. Paid commerce remains disabled.
A real signed-in Windows 0.5.9 client downloaded and installed the canonical package after the user requested Free creation tools. Both tools showed Installed, version 0.5.9, and the activated package matched the reviewed SHA-256. The downloaded ASHVEIL ENGINE opened in its local studio, and ASHVEIL ASSET CREATOR opened the asset workshop. Offline operation was not retested during this live download check.
Known limits and unfinished work
Free tool installation does not purchase games or assets, spend tokens, publish a game, grant general redistribution rights or activate creator payouts. Paid checkout and the remaining marketplace lifecycle are still unavailable.
This release activates hosted creator-tool delivery without replacing the desktop installer: it remains version 0.5.9 and is still unsigned for Windows publisher verification. The existing local-package updater is separate from internet-wide automatic client updates. This download check does not establish performance on every machine or complete editor functionality.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
The source checkpoint records the protected delivery implementation and its validation. It does not contain the server-only key or change the frozen desktop package.
Production HTTPS verification · guassia-free-tools-production-20260926.json
All 130 checked site files matched the reviewed release, allowing for documented hosting transformations. This is delivery evidence, not a full editor acceptance test.
Public delivery boundary verification · guassia-tools-live-public-verification-20260926.json
Thirteen live public checks cover free availability, denied unauthenticated access, encrypted artifact identity and absence of plain package or server-source exposure on the checked routes.
Installed Windows client acceptance · guassia-free-tools-live-acceptance-20260926.json
The native-client record separates an actual signed-in requested download, installed package identity and observed tool launches from untested offline or cross-device behavior. No credentials are part of the public record.
Shared account verification and unique usernames
Source checkpoint only
Shared account verification and unique usernames
Browser and desktop sign-in now validate the canonical username against the same verified account profile. This patch also strengthens suspended-account checks and corrects signup verification and existing-account email access.
Source checkpoint 75bc24397e986d4e0ae9fc0dbd2bdb7d3e44b3bdSource availability and destination verification are separate.
One canonical username per account
Usernames remain lowercase ASCII identifiers with a database primary key and a separate unique account constraint. Case variants resolve to one name; concurrent claims cannot create duplicate aliases. Public world publishing and its slug allocation remain separate unfinished work.
The reserved owner name is accepted only for its explicitly configured verified account ID, both when claiming the name and when signing in. A display name never grants administrator or owner-testing privileges.
The profile response derives /u/name/ directly from the unique username; it does not create a public profile page. Administrator access requires both operator settings to match the same single verified owner ID. A list or a different ID fails closed.
Check authorization at the shared service boundary
Suspended accounts cannot access profiles, downloads, creator actions or administrator data; read-only library history preserves suspended records. Username insertion rechecks suspension atomically. Invalid email-confirmation timestamps are rejected, and provider outages are distinguished from rejected credentials.
Provider requests preserve the host fetch context. Failures expose only fixed diagnostic codes for the failed stage; passwords, tokens, account data and raw provider replies are excluded. The diagnostics support investigation and do not establish a successful live login.
The edge runtime rejects the fetch redirect mode previously used for authentication. Provider calls now use supported manual redirect handling and explicitly reject redirect responses without following them. This keeps credentials on the fixed provider route while allowing the request to run in the deployed runtime.
Validate the account before accepting a session
Browser and desktop password login require the fresh server profile to match the requested canonical username and verified account ID. A mismatched profile cannot replace the current session. Expired or revoked browser sessions are cleared while a new sign-in remains available.
Make signup and email access consistent
Browser signup normalizes email and username, uses the same email-code verification type as desktop, and expires pending signup after one hour. If a name is already taken, the verified account can choose another name. Desktop email-code access to an existing account does not create a new passwordless account.
Clearer sign-in and registration forms
The browser account panel uses the Guassia palm, dark plum surfaces, light text and a clear lime primary action. Selected modes, field guidance and narrow-screen spacing are easier to follow. Keyboard focus, autofill and announced loading, error and success states are explicit; all four forms are disabled while a request is running.
September 24 browser-only follow-up: the studio replaces its initial guest-save reminder after a stored session is freshly verified or sign-in succeeds. It does not auto-save or overwrite unrelated operation results; sign-out changes only the account reminder. All 30 focused tests passed. The reviewed 0.5.9 desktop installer and creator package are unchanged.
What was checked
Source regression checks cover case-variant and competing username claims, owner-name binding, suspended accounts, malformed provider replies, mismatched profiles, signup verification and session cancellation. These checks use controlled identities and responses; they do not create a real owner account.
143 platform tests and 357 client/browser tests passed, with no failed, skipped or canceled tests in either run. These counts describe separate source suites, not completed live account acceptance.
The form polish passed 24 focused interface, authentication and locale tests, including four new interaction checks. These fixtures do not establish browser screenshot review or public deployment.
Known limits and unfinished work
Live account creation, verification-email delivery, owner permissions and browser-to-desktop sign-in require separate destination checks. No password, account identifier or credential is included in these notes.
Password reset, verified email changes, account-wide session revocation, administrator MFA enforcement and public slug allocation still need complete product workflows. Commerce, creator payouts and hosted private downloads are not enabled by this account patch.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
The source checkpoint contains the account-boundary and client-verification changes with regression tests. Public delivery and real-account acceptance are recorded separately.
Guassia 0.5.8: refresh cached game players
Source checkpoint only
Guassia 0.5.8: refresh cached game players
A returning browser could keep an older First Quest runtime after a deployment and stop at the first frame. This patch versions both startup imports so a refreshed page requests the matching player code.
Source checkpoint 14f27e489f48e1e6fcadba08e3f0aa2f3ccc1dbaSource availability and destination verification are separate.
Invalidate both cached module links
Portable exports now derive the runtime URL from its SHA-256, then derive the startup-script URL from the rewritten script. The HTML, startup script and renderer therefore advance together. These hashes identify cache versions; they do not grant distribution rights or replace package signatures.
Refreshing First Quest updates only index.html, web-player.mjs and playtest-runtime.js in the hosted world and both existing ZIPs. Authored project data, Gaussian assets, audio and license files remain byte-identical. Signed education exports require a regenerated receipt and are refused by this refresh command.
When the runtime entries are already current, refresh preserves the original ZIP container without rewriting it. Existing timestamps, compression and archive hashes remain unchanged; an actual runtime change still refreshes both archives.
Resume without negative simulation time
The playtest now uses one animation-frame clock and resets its anchor when resuming. A queued frame older than the Resume click cannot produce a negative delta. The first resumed frame advances no simulation time; long active frames retain the 0.2-second cap. Story validation still rejects invalid inputs.
Show the selected local asset in its details
Private bundled asset details show the validated local preview image with its whole silhouette visible and a missing-image fallback. Their availability message describes local preview use in ASHVEIL ENGINE. Ordinary marketplace checkout remains disabled; the preview is not a published product.
What was checked
32 focused source tests passed, including a returning-browser cache fixture, repeated refresh, preserved export entries, signed education receipts and all four camera modes. The browser export also compiled successfully. The release verifier now checks the startup script as well as the renderer.
26 clock, story and camera tests passed, including pause, a long background interval, resume, collect interaction and restart with the real story runtime. 17 detail-panel tests passed, covering validated image paths, stale image errors and preview-only messaging.
Known limits and unfinished work
A page already open with the old runtime must be reloaded. Source and isolated filesystem tests do not establish completed native installation or a successful live game session; those checks are recorded separately.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Portable player cache patch source · 14f27e489f48e1e6fcadba08e3f0aa2f3ccc1dba
The recorded source includes cache-versioned imports and export-preservation regression tests.
Local updates, creator packages and account-isolated drafts
Source checkpoint only
Local updates, creator packages and account-isolated drafts
The Guassia 0.5.7 source adds signed updates from a local release folder, an explicit local creator-package installer, and account-isolated listing drafts. These changes do not establish a completed native installation.
Source checkpoint 9040c394ca8ea6f08e1062a1bb6617185c03dba6Source availability and destination verification are separate.
A local update channel with explicit installation
Update checks read a signed release folder on this computer. The client verifies the pinned signing key, version, expiry, artifact size and SHA-256 before staging an update. The Settings panel says when a check is local and uses Copy local update. No internet update feed is activated.
Automatic checks and copying are optional and off by default. Installation always needs a separate visible Apply action and confirmation, with the existing editor and running-game guard. Version 0.5.7 must first be installed manually to gain this channel; older builds cannot be assumed to discover it.
Install the reviewed local creator package
Tools offers Install local creator package. After verified sign-in and acceptance of the current creator terms, a native picker accepts only the approved .gtools package for this app release. Both free tools are installed together after integrity checks. This is separate from remote downloads or publishing, and already installed tools remain usable by a remembered account offline.
Keep listing drafts with the verified account
Local listing drafts are now stored in the main process under the verified account subject. Signing out or changing accounts clears the visible form; delayed reads and save replies cannot restore another account’s draft. Atomic file replacement preserves the previous draft if a write fails. The old unowned browser-storage draft is preserved but never automatically read or attributed to the next account.
Report public link opening accurately
The native public-link action now returns the exact opened receipt expected by Play First Quest. This prevents an already opened browser link from being reported as an unconfirmed operation. The receipt confirms the link action only, not successful rendering, gameplay or a multiplayer connection.
What was checked
Source fixtures cover account separation, delayed draft responses, failed file replacement, exact link receipts, local update labels and explicit creator-package actions. These are source and isolated filesystem tests, not a completed native installation or public delivery check.
Known limits and unfinished work
The first local tool installation still requires verified online sign-in and a real acceptance record for the current creator terms. Store purchases, final publication and creator payouts are separate unfinished journeys; this update does not activate them.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Local desktop source checkpoint · 9040c394ca8ea6f08e1062a1bb6617185c03dba6
Private source and fixture evidence; installation and service activation are recorded separately.
Username sign-in and account creation in the desktop app
Source checkpoint only
Username sign-in and account creation in the desktop app
Guassia 0.5.7 adds a username and password sign-in form with Create an account underneath, while preserving local access and remembered sessions.
Source checkpoint 38f389cecd5f4bbe05afc3a60828d490a40328d7Source availability and destination verification are separate.
A familiar account flow
New accounts enter a username, email and password, then verify their email. Usernames are private login aliases linked to the verified provider account. They never grant administrator privileges or replace ownership checks. Existing accounts can still use the secondary email-code route.
Passwords are cleared from the interface after submission and are not saved in local account files. The client preserves encrypted remembered sessions. The server validates email and account identity, limits attempts and keeps username-to-email lookup private.
One consistent local installer
The release handoff verifies the reviewed version, source commit and artifact hashes before updating the Desktop installer shortcut. Older release folders remain available. Staging an installer does not install it or activate automatic updates.
Open the engine with fewer steps
Home now centers on Open ASHVEIL ENGINE. It reports whether the installed engine is ready, the creator tools need downloading, or account/download services are unavailable. The asset creator and Updates & settings are secondary actions. Sidebar labels and consistent stroke icons retain the existing colors and typography.
Desktop creation tools, libraries, creator publishing, hosting and owner reports require a signed-in account; a remembered account can still use installed tools and local files offline. Public store browsing and community game links remain available to guests. First Quest has a direct browser-play action, and guest display is labeled Anonymous without claiming control over a community host’s player names.
40 bundled construction previews
The desktop asset catalog can show the 40 actual construction assets with local Gaussian-rendered preview images when the remote catalog is unavailable. Their cards explicitly say Local preview · not published. They are private review material, not invented marketplace listings, completed purchases or verified store entitlements.
Use in ASHVEIL ENGINE is an explicit signed-in action. The renderer accepts only the matching local preview path and passes an asset ID and language to the trusted desktop bridge. It checks an exact open receipt, displays failures, and does not claim ownership or start a purchase. Existing projects are not silently overwritten.
One account across browser and desktop
The browser account interface uses the same verified username and password service as the desktop app. Guest editing remains a preview; browser save, export and local-library actions require verified sign-in. The browser keeps a verified session in the current tab for at most one hour and never saves the password. Account creation alone does not accept creator terms, activate checkout or grant publication rights.
First Quest camera correction
The playtest camera now uses the position returned by bridge.setCamera(). The previous first-frame path read bridge.camera.position even though camera was not exposed there. Four camera-mode and source fixtures pass. These source results do not establish that the public game deployment or a new native installer has been run successfully.
Clear store units and fees
Paid prices are displayed in Guassians: 1 Guassian equals US$1, including fractional prices such as 0.99. The underlying integer-cent accounting is unchanged. Game publication has a one-time US$100 fee per title, asset uploads are free, creators may set a zero price, and paid sales retain the stated 30% platform share. Displaying these amounts does not enable token purchases, checkout, payouts or a live paid catalog.
What was checked
Client, server and interface fixtures cover disabled services, identity checks, interrupted sign-in and account changes. Package checks compare shipped source and locale files. These checks do not establish a successful production registration.
Known limits and unfinished work
The production account provider, verified email delivery and private username migration must be connected before username sign-in or account creation is enabled. The online updater remains unconfigured; this update does not activate payments or content delivery.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Private implementation, tests and local release tooling; public service activation is separate.
Downloaded games can be removed and reinstalled
Source checkpoint only
Downloaded games can be removed and reinstalled
The private Guassia 0.5.6 update extends the explicit Download, Remove from device and Reinstall workflow from assets to games while retaining account ownership.
Source checkpoint 21b629e239b395d72f06b56ba95c5ab76eeb5072Source availability and destination verification are separate.
Choose downloads without losing ownership
Library refresh and ownership records do not start automatic downloads. A game is downloaded only through its explicit action. Remove from device asks for confirmation and retains the signed ownership record; it does not issue a refund, revoke the license or create another purchase.
Removal targets the managed game download, preserving exported copies and saved editor projects. Shared cached packages remain when another installation needs them or safe cleanup is uncertain. The removed account entry stays uninstalled even when shared bytes remain. Reinstall requires an internet connection and verified access to the game.
Close running games and cancel stale work
A running instance of the selected game must close before removal. The client reports this requirement instead of forcibly closing the game. Locked-file cleanup remains visible and can be retried.
Starting removal invalidates pending loads and downloads for that account and item, and blocks new conflicting operations while the installer queue completes. A delayed download cannot silently reinstall the removed game, and switching accounts cannot redirect the operation to another account.
What was checked
The combined client, removal, localization and policy run passed 229 tests with no failures, skips or cancellations. Game lifecycle checks cover explicit reinstall, retained ownership, shared packages, running-game rejection, pending-operation cancellation and account changes. Overlapping focused groups are not counted again.
The localization and changelog suite passed 46 tests. The five game-specific phrases and four shared service messages are covered in English, Spanish, Simplified Chinese, German, French and Dutch, including separate first-download and reinstall labels.
Known limits and unfinished work
This is a private source update for the next desktop package. These checks do not establish native installation, live store activation, payment processing or verified delivery of a purchased game.
This change does not add persistent gameplay saves or progress synchronization. Preserving saved editor projects is separate from retaining a running game session.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Game library source checkpoint · 21b629e239b395d72f06b56ba95c5ab76eeb5072
Explicit game removal and reinstall, running-game protection and six-language controls.
Game removal regression checks · guassia-056-source-tests-final-20260924.log
Source and isolated fixtures; native installation and live store delivery remain unverified.
Guassia desktop: download control and optional updates
Source checkpoint only
Guassia desktop: download control and optional updates
Remove downloaded assets while keeping account ownership, reinstall on demand, and choose optional verified update downloads from Settings.
Source checkpoint 0298b62c2f0cf532e08d15df7274dd06166cd8bbSource availability and destination verification are separate.
Keep licenses, choose downloads
Asset ownership already stayed in the account without automatic downloads. The library now adds Remove from device, an explicit confirmation and Reinstall asset. Removal preserves the signed ownership record, exported copies and saved projects. Shared cached bytes are retained when needed or when another local installation cannot be ruled out; locked-file cleanup remains retryable.
Per-item guards cancel older downloads and loads when removal starts, prevent new conflicting operations, and require an active asset export to finish or be canceled first. Account changes cannot redirect removal to another account.
Updates stay under your control
Settings adds a default-off preference for background checks and verified installer downloads, with manual check, download and apply actions. The automatic path checks at startup and every six hours while enabled. It never installs an update automatically.
The main process validates signed update metadata, the allowed HTTPS destination, installer size and SHA-256 before staging. Apply verifies the cached file again and asks for confirmation with the editor and games closed. It opens the installer; it does not prove installation finished or promise an automatic restart.
Guassia app identity
The desktop app and installer use the Guassia name. ASHVEIL ENGINE and ASHVEIL ASSET CREATOR retain their tool names. Browser checkout and store entitlements are unchanged.
What was checked
Eleven downloaded-asset removal tests and thirteen update-settings interface tests passed. They cover shared copies, account and download races, locked-file retry, explicit confirmation, settings availability and operation states.
The combined automated suite passed 809 tests with no failures or skips. Checks include current controls in six priority languages, update signature and download verification, cancellation, explicit apply and chunked Windows installer packaging. These results do not establish native installation.
Known limits and unfinished work
The signed update channel still requires its trusted production configuration. A missing pinned public key prevents both manual and automatic update requests; enabling the preference does not connect an unavailable channel.
These checks did not launch a native installer or verify clean-machine installation or live automatic update delivery. Removal currently covers active owned assets; games and revoked or expired asset-cache cleanup are outside this interface.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Desktop download and update source checkpoint · 0298b62c2f0cf532e08d15df7274dd06166cd8bb
Local removal, optional verified update staging, Settings and Guassia app naming.
Managed-file, shared-copy and account-isolation fixtures; native installation remains unverified.
Desktop library integrity and offline game languages
Source checkpoint only
Desktop library integrity and offline game languages
Personal-asset exports protect managed library files, while owned games obtain interface languages from trusted installed creation tools instead of uploaded game content.
Source checkpoint 11da636e20be34364ef5eccffcab70eafa3ab1b5Source availability and destination verification are separate.
Protect other assets during export
Copy export refuses destinations inside the managed personal asset library, including directory-junction aliases. Exporting asset A cannot overwrite asset B. Selecting the exact source file remains a no-op that leaves it unchanged.
Trusted offline interface languages
Owned games load interface scripts and language files from verified installed creation tools. Missing trusted language resources request a tools update before opening the game. Uploaded games cannot replace these scripts or dictionaries; creator-authored text remains intact.
What was checked
17 local-library tests and six owned-game language tests passed, including managed-path aliases, trusted-resource loading, account changes during loading and isolated-origin restrictions.
The combined automated suite passed 753 tests with zero failures or skips. The source checkpoint also adds the previously local model-texture-policy module and its two tests to version control; this does not describe a new rendering behavior. Test groups overlap.
Known limits and unfinished work
The updated native game window and installer were not launched during this check. These source and fixture results do not establish native execution or a clean-machine installation.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Managed-file export protection, trusted offline localization and tracked texture-policy sources.
Offline language regression checks · owned-game-language.test.cjs
Trusted controller and protocol fixtures; native game launch remains unverified.
Detailed Gaussian authoring, product previews and an explicit creator agreement
Included with this site release
Detailed Gaussian authoring, product previews and an explicit creator agreement
Preserve more source appearance, edit shared assets through sparse layers, browse larger local libraries, author visual game rules and recover local projects. New creator-tool downloads require a versioned commercial-distribution agreement.
Source checkpoint ecd4d865480988ec62c471672788d50336e07b0bSource availability and destination verification are separate.
Source appearance and selective detail
GLB color-texture sampling now offers original resolution or an explicit 1024, 2048 or 4096 pixel limit, with decoded-image and sampling-memory checks. High resolution is no longer silently reduced to 1024 pixels. Source resolution and a 4K output image remain different measurements.
Supported PLY spherical harmonics through degree 3 are retained in native files and evaluated with view direction. Invalid or incomplete coefficient sets are rejected. Orthographic views use parallel viewing rays. Unsupported SH transform baking is rejected rather than silently losing appearance.
Derived spatial hierarchies select source-index candidates with a bounded traversal budget. Whole source assets load asynchronously by active area and use a resident-memory cache. Source IDs remain stable through LOD selection and sparse edits; original data stays unchanged.
Sparse editing and a usable local library
Object edit layers support region-selected recoloring, opacity and hiding without replacing the shared source. Layers can be reordered, duplicated and toggled, with up to 32 layers and 1024 edited source IDs per object. Oversized selections fail atomically.
The local asset definition ceiling rises from 16 to 256 while Gaussian, instance and package budgets remain separate. Search, categories, usage filters, paginated outliner groups and on-demand thumbnails avoid loading the full library merely to browse it.
Portable Save project includes Gaussian sources, settings and selected audio. Local recovery separately keeps up to eight checksum-verified project snapshots, saves the current state before restoring, and reports unavailable storage. Recovery references local assets and is not a substitute for a portable backup.
Gameplay tools and optional lighting
Visual event, condition and ordered-action cards compile into the same bounded game-script format. Supported controls include doors, transforms, tint, opacity, visibility, named signals, spatial sound, journal entries, achievements, endings and area teleportation. Advanced nested logic stays available in the existing script editor.
Running script diagnostics retain a bounded rule trace. NPCs can use obstacle-aware ground-plane paths against mathematical collision boxes, with bounded search and periodic replanning. Existing behavior, detection and reset controls remain optional.
Creators may opt authored Gaussian objects into diffuse relighting with ambient light and up to eight point or cone lights, including a camera flashlight. Captured radiance stays unlit by default. This path uses oriented Gaussian surface normals and does not reconstruct PBR materials or produce shadows.
Native animated Gaussian characters
Import a native .gchar source, choose its animation clip, speed and playback state, then place it in the editor or use it with existing NPC movement. The visible actor uses Gaussian skin bindings; no visible mesh fallback is introduced.
Character bytes and clips remain intact in editable and playable project archives. A room admits up to four animated instances and 500,000 total character Gaussians, with a 64 MiB file limit. Animated actors bypass static LOD; motion envelopes are conservative and collision uses separately authored boxes.
Characters retain their native sampled material and skin-lighting path. Static sparse layers, diffuse-light controls and unsupported appearance edits are rejected for these actors rather than silently changing them. GLB import is still a static path; use native .gchar for continuing animation.
Clear previews and international navigation
A product overview connects to separate engine, asset-editor, Games Store and Asset Store previews. The actual editor loads on demand; store pages show truthful empty or unavailable states, clear desktop-only routes and no browser checkout.
Account and download journeys report service readiness instead of pretending that a completed form created an account or entitlement. Creator-authored names and content are protected from interface translation.
Changelog localization uses entry fingerprints and separate locale files, preserving canonical English and disclosing partial translations. A translated overview is not presented as a complete technical translation.
Guassia-only commercial distribution
The owner-selected license condition reserves commercial distribution and monetization of games or assets created or materially modified with newly accepted creation tools to the official Guassia stores. The browser preview grants private creation and testing permission, not commercial distribution permission. Original creator ownership, earlier independent grants, third-party licenses and mandatory rights remain separate.
A desktop user must explicitly accept the exact policy text and version before new creator-tool downloads or future publishing submissions. The server records the verified account, policy version, SHA-256, request reference and time. Browsing, general signup, an old download or a locally saved checkbox is not treated as acceptance.
A one-time US$100 game-publishing fee, free asset listings, optional zero-priced content and a 30% share of paid third-party sales remain the planned store model. There is no Enterprise subscription. Accepting the policy does not charge, publish, create a purchase or activate commerce.
What was checked
Focused regression suites cover SH preservation, bounded LOD, source identity, sparse instance isolation, source-cache cancellation, portable project validation, visual-rule execution, NPC obstacle routing, lighting reference calculations and recovery corruption. Exact run receipts distinguish these CPU and data checks from real GPU execution.
Independent review fixed a missing installer policy file and stale account/dialog responses. Tests exercise the actual desktop policy verifier against the actual service with a database fixture, explicit acceptance, version mismatch, account isolation and idempotent retries.
Known limits and unfinished work
Current source integration is a bounded browser-engine preview, not Blender or Unreal feature parity. Character clip selection does not provide retargeting, an animation state-machine editor or cross-area NPC patrols. Full hierarchical file-chunk streaming remains separate work.
LOD currently pages whole assets, not individual storage clusters; transitions are not blended. Sparse region selection is cooperative CPU work, not a GPU brush. Full-detail inspection is bounded at one million source Gaussians.
Relighting has no dynamic shadows and may be inappropriate for radiance-only captures. CPU tests and selection benchmarks do not establish GPU frame rate or universal 4K quality.
Authentication, private cloud downloads and paid transactions remain unconnected. No new live account, purchase, entitlement or acceptance record is fabricated. Existing installed content and prior license rights are preserved.
Notices and agreement records are not tamper-proof DRM and do not guarantee enforcement in every jurisdiction. Native installer execution and clean-machine testing remain unverified.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Immutable policy checkpoint. The editor and localization follow-up described here is bundled with this release; its final source and public delivery are recorded separately.
Acceptance and commercial-use boundaries · POLICY-ACCEPTANCE.md
Versioned explicit acceptance, preserved earlier rights and inactive commerce.
Detail selection and residency · LOD-AND-ROOM-RESIDENCY.md
Derived candidate indices, resource limits and whole-asset paging boundaries.
Source appearance fidelity · ASSET-FIDELITY.md
Texture sampling, SH preservation and inspection constraints.
Desktop libraries grow on disk
Source checkpoint only
Desktop libraries grow on disk
The personal desktop asset library now keeps its catalog in SQLite and loads one metadata page at a time. Browsing a larger collection does not require loading every Gaussian payload.
Source checkpoint b08f68bed7af246f576f48506c35040b140d0997Source availability and destination verification are separate.
A growing personal library
Removed the default 256-file and 2 GiB total quotas from the local personal library. SQLite stores disk metadata; the interface shows 48 rows per page, with at most 100 per request and Unicode substring search. Listing pages does not decode asset payloads.
Original files remain unchanged. A one-time migration preserves the earlier JSON catalog, and transaction rollback allows failed imports to be retried.
Reliable copy export
Exports resolve the exact selected asset beyond the first page. A sibling temporary file and atomic replacement preserve an existing destination if writing or renaming fails.
What was checked
15 local-library tests passed, including 260 real native asset imports and a 5,000-record metadata fixture traversed across 105 interface pages without loading payloads.
Injected disk-full and rename failures preserved destination files. Transaction rollback, migration and retry checks also passed.
Known limits and unfinished work
Individual native .gasset files remain limited to 128 MiB. Disk, filesystem and database limits still apply; this change does not increase active-world or GPU budgets or add arbitrary file formats.
Substring search currently runs synchronously over metadata. Larger collections need profiling before deciding whether to move that work to a worker.
This is a source checkpoint. The updated native installer was not run; no clean-machine installation or unlimited-capacity guarantee is claimed.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Personal-library storage, pagination, migration and export changes; active rendering limits remain separate.
Local library regressions · local-asset-library.test.cjs
Real native imports, bounded metadata pages and injected write failures; not a native-installer or hardware-fleet test.
Signed offline library and owner testing controls - private 0.5.3 candidate
Source checkpoint only
Signed offline library and owner testing controls - private 0.5.3 candidate
The desktop candidate can validate account-bound content, install declarative game or Gaussian asset packages, and enforce learned license denials. A separate owner testing action is controlled by the server.
Source checkpoint c74cdfc7b46406a32089ec4ac168dcdc24275f8bSource availability and destination verification are separate.
Owned content with an offline path
The main process verifies pinned Ed25519 account grants, exact package size and SHA-256 before atomic installation. Every opening rechecks identity, receipt and file integrity. Cached library metadata alone grants nothing.
Games use validated data-only project archives and a trusted installed player. Each game has an isolated origin and session with no Node integration, preload bridge, external navigation or network access. Gaussian assets can be exported as verified native bytes.
Logout closes owned games and preserves downloaded files. Learned suspension or revocation immediately blocks new and pending operations, including while a disk write is queued. Temporary outages retain previously verified offline grants.
Separate owner testing
A hidden catalog detail action appears only after fresh server authorization. Each claim rechecks the account and verifies its signed descriptor. It is labeled testing access and does not create a purchase or creator revenue.
Stale replies after logout, newer operations, dialog closure or authority removal cannot restore access. Testing denial also cancels pending test-content operations and persists known revocations.
The new controls include English, Spanish, Mandarin, German, French and Dutch phrases.
What was checked
120 client tests passed, including signed content, real data decoding, account isolation, unsafe package rejection, interrupted installs, stale responses and revocation persistence. Five changelog checks also passed in the final combined run.
Independent review reproduced the queued suspension race and the owner capability-denial race, then confirmed the fixes. Native window security checks remain fixture-based.
Known limits and unfinished work
This is a private Windows candidate. Its new native game launch was not verified, and no clean-machine or Mac/Linux installation result is claimed.
Production auth, signing keys and approved private delivery are not configured. No live owner account or test grant was created, and paid commerce stays off.
Perpetual offline grants cannot learn remote revocation until reconnecting. This is not tamper-proof DRM.
Downloads retry whole packages. Current installation and library counts remain bounded; multi-asset pack installation, large-library pagination, streaming and synchronized multiplayer remain separate work.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Source and fixture verification, not public desktop delivery.
Package, sandbox and offline boundaries · OWNED-CONTENT.md
Records supported data and remaining native verification.
Platform API and isolated owner testing foundation
Included with this site release
Platform API and isolated owner testing foundation
A dedicated API adapter, signed account-bound content descriptors and separate owner testing records are implemented. Authentication, private cloud delivery and paid commerce remain separate integrations.
Source checkpoint b876f2392406474c3074b1a4e1a88e56b5302088Source availability and destination verification are separate.
One owner testing identity
Testing authority accepts one server-configured verified provider UUID. Display names, email, client metadata and administrator lists cannot grant it. No owner subject or account is fabricated by the implementation.
Explicit testing claims use separate grant and audit tables. They do not create purchases, consume credits, change prices or publishing fees, or create creator earnings. Published future listings can use the same verified claim path.
Every descriptor and download checks current authority, account state and immutable package identity. Changes to the owner configuration, a frozen account, withdrawn listing or changed artifact produce an explicit online denial.
Signed data and deployment boundaries
Owned game archives and single Gaussian assets use account-bound Ed25519 descriptors, content-addressed files, checksums and bounded download ranges. Uploaded executable code is outside this format.
An opt-in Pages adapter routes only /api/platform/* to the service and leaves ordinary static requests with Pages. The normal static build remains separate; the release overlay is explicit.
An optional Sentry diagnostic adapter has a closed event schema and consent/configuration gates. Its configuration remains disabled, no SDK is connected and no external error event was sent.
What was checked
125 platform, Pages adapter and optional telemetry tests passed. The platform and adapter subset contains 110 tests; these counts overlap.
Owner testing tests include ordinary-user and metadata spoofing rejection, exact-account signatures, idempotent claims, future listings, ledger isolation, changed authority, frozen accounts and changed/withdrawn artifacts.
Known limits and unfinished work
The real authentication project is still awaiting completion. No live owner testing account is activated by this release.
R2 was declined and remains off. Private hosted content, signing keys, tool downloads and testing downloads are not configured; local files remain local.
Perpetual signed offline grants learn revocation only when a device reconnects. They are not tamper-proof DRM.
Catalog and combined library results remain bounded; full large-library pagination and owned multi-asset pack installation are not implemented.
Paid commerce remains disabled pending the remaining seller, settlement, refund/dispute and publishing lifecycle.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Platform and optional monitoring checkpoint · b876f2392406474c3074b1a4e1a88e56b5302088
Implementation and local tests; live activation is recorded separately.
Testing authority and deployment boundaries · OWNER-TESTING.md
Documents isolated ledgers, exact provider identity and offline limitations.
Region editing, source exports and camera-aware Gaussian rendering
Included with this site release
Region editing, source exports and camera-aware Gaussian rendering
Select a source region, inspect and bake targeted changes to a new asset, or export the stored source unchanged. The renderer skips conservatively off-camera instances before accumulation.
Source checkpoint 15b73a730af1d129947f4b3b63b6a0b8646416a9Source availability and destination verification are separate.
Editable Gaussian assets
Source-coordinate XYZ box selection offers inverted selection, exact selected counts and a lime/gray preview. Keep, remove, multiply color and set opacity operations prepare an explicit baked copy; selected-region cleanup preserves outside attributes and counts neighbors beyond the boundary.
Saving replaces only the chosen object asset reference. Other instances retain their original source, and undo/redo restores the previous reference. Cancellation and project-change checks prevent stale work from attaching to another project. Collision recipes remain separate and need review after geometry removal.
Download stored source returns exact validated stored native bytes. Download baked object separately applies the instance appearance and transform. Import may assign a new ID/name, so stored-source export is not a promise of the original uploaded-file hash.
A center-height close inspection view helps examine small props. Fifty-eight new workshop phrases have English, Spanish, Mandarin, German, French and Dutch versions, including the copy-baking limits and source/baked distinction.
Less off-camera work
The renderer computes conservative bounds from packed Gaussian means and covariance scale, caches transformed instance bounds, and excludes fully off-camera instances before generator allocation and accumulation. Transparent source splats remain included in bounds so later opacity edits can reveal them safely.
Projection, nonuniform transforms, shear and pixel blur margins are considered. Near-plane and unknown depth-of-field cases fail open. Moving an object continues to update its transform rather than rewriting the source positions.
What was checked
305 engine/builder integration tests passed before the locale-only additions; 26 focused localization/cache checks passed afterward. Test groups overlap with separately reported focused tests.
A native workshop fixture passed 12 checks with actual IndexedDB and Gaussian rendering, including byte-exact stored export, selected-copy edits, undo/redo and stale-save cancellation.
Four paired 3840 by 2160 comparisons had zero changed pixels with culling enabled or disabled. In a separate 1280 by 720 synthetic offscreen-heavy scene, candidates dropped from 800,000 to 20,000 and paired median synchronized wall times changed from 24.1–24.7 ms to 8.3 ms on one RTX 3050 Ti laptop.
Known limits and unfinished work
Region operations are full-copy CPU baking with a 250,000-source limit, not sparse GPU editing. Ordinary object appearance and transform edits keep the existing parameter/reference path.
The culling benchmark is specific to that synthetic scene and hardware. It is synchronized wall time, not GPU timestamps. No general speedup, 4K performance guarantee or Blender/Unreal comparison is established.
This is per-instance camera culling, not source streaming, hierarchical Gaussian LOD or VRAM eviction. Authored and rendering count limits are unchanged.
New workshop translations are machine-authored and await human review; technical documentation and some existing interface content remain English.
Production account services, paid marketplace fulfillment and private hosted downloads are separate work. R2 activation was declined and remains off.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Gaussian workshop and visibility checkpoint · 15b73a730af1d129947f4b3b63b6a0b8646416a9
Browser/source changes and tests; delivery must be verified separately.
Source editing scope · ASSET-REGION-WORKFLOW.md
Documents explicit copy baking and retained originals.
Records hardware, timings, pixel comparisons and unsupported claims.
Remembered accounts and offline library context — private 0.5.2 candidate
Source checkpoint only
Remembered accounts and offline library context — private 0.5.2 candidate
The next private desktop candidate restores a previously verified account before waiting for the network, labels saved library information, and offers device sign-out without deleting local work. Production authentication and paid-content installation remain unavailable.
Source checkpoint e1b35556cf4eee7ff7865600dc18a41fa7072069Source availability and destination verification are separate.
Restore an account without inventing one
After verified sign-in, the candidate stores remembered account data with operating-system-backed Electron safeStorage. There is no plaintext credential fallback. When protected storage is unavailable, the account remains limited to the current app run and a warning explains the limitation.
The launcher restores local account state before waiting for the service. Access and refresh tokens remain in the main process; online renewal and protected requests still depend on actual provider verification and server authorization. A remembered identity is not an offline grant of ownership.
Useful offline status and deliberate sign-out
An earlier successful library response can be retained as a timestamped metadata snapshot. Offline cards say Saved library record. Connect to check ownership changes or download new content; a snapshot is not current license authority or a wallet balance.
The account dialog adds Sign out on this device. Successful sign-out clears remembered credentials and the library snapshot, returns to Home/sign-in and preserves projects, installed tools and downloaded files. A failure to remove the protected record remains an explicit error rather than a false success.
Previously installed creator tools and local .gasset assets remain usable on the device. Six new offline-account, mode, sign-out and saved-library phrases have English, Spanish, Mandarin, German, French and Dutch wording. Other technical help may still use English fallback.
Free construction pilot and catalog planning
A private pilot contains 40 distinct original procedural Gaussian construction components: 459,779 source Gaussians, 40 actual 1024 by 768 previews, full native decode/hash checks and an independently reopened review ZIP. These are visual-review candidates, not photorealistic or production-approved inventory.
The catalog reserves 5,000 planned free slots separately from actual artifacts. Proposed paid inventory is 100 one-asset listings at US$0.99, one 100-character bundle at US$19.99 and one 100-landscape bundle at US$19.99. No listing, payment or paid license was activated.
What was checked
Private source checkpoint tested with 72 client tests, including 15 offline-account cases; the combined client, changelog and catalog run passed 95 checks. Synthetic accounts establish regression behavior, not real customer authentication.
An isolated hidden Electron run passed 23 checks, including actual Windows safeStorage encryption/recovery, retained downloaded files, offline Home, cached library and sign-out/reload. Native packaged startup is verified separately.
Known limits and unfinished work
The real authentication backend is not connected in this preview. Only a genuine verified response can establish a remembered account; fixtures remain tests.
Paid game and asset installation and launch remain unfinished. Cached metadata does not enable purchases, grant ownership or authorize new downloads.
Protected account storage depends on the operating system and device. The app does not offer plaintext persistence when it is unavailable, and a copied account file is not promised to work on another computer.
Device sign-out does not claim to revoke all remote sessions or remove another device's account. Candidate packaging, native behavior verification and public delivery require separate receipts.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Offline account and construction-pilot implementation checkpoint · e1b35556cf4eee7ff7865600dc18a41fa7072069
Includes account storage, online/offline separation, renderer flow, regressions and private asset catalog tooling. Public delivery remains separate.
Desktop candidate scope and limits · README.md
The desktop README describes protected persistence, dated library context, local-file preservation and currently unavailable paid-content services.
Portable projects, open ground and ASHVEIL ENGINE by Guassia
Included with this site release
Portable projects, open ground and ASHVEIL ENGINE by Guassia
Save and reopen complete local projects, start outdoors on white Gaussian ground, and choose how the game camera follows the player. Dedicated engine pages explain the free creation workflow.
Source checkpoint 97a7350Source availability and destination verification are separate.
Files you can keep and reopen
The browser editor adds Save project, Save As and Open project, including Ctrl+S, Ctrl+Shift+S and Ctrl+O. An editable .guassia.zip contains referenced Gaussian assets and chosen original soundtrack/spatial-audio bytes. The data archive contains no executable player; the separate website export remains available for private playtesting.
Supported browser file pickers reuse the chosen file for Save. Other browsers request a download and say to check Downloads; a request is not reported as confirmed disk completion. Cancellation and failed writes preserve the current document and previous file handle. Browser recovery remains a separate convenience.
The native Windows editor adds actual .gworld Open/Save/Save As through a restricted IPC interface. Checksums and bounds are validated, writes use a sibling temporary file and replacement, and renderer-side opaque tokens refer only to user-selected files. No general filesystem bridge was added.
New/Open now invalidates in-flight document saves so a late picker or write cannot reattach the previous project file. Late status messages are discarded. Portable project JSON is compact and checked against the same import envelope, fixing large narrative projects that previously saved but could not reopen. Restricted browser pickers use a clearly reported download fallback; cancel stays cancel.
A blank world and optional game cameras
New projects start with white Gaussian ground, open sky, no walls or ceiling and no required music, NPCs, collectibles or story. Existing saved room interiors retain their prior enclosing surfaces. Iron Nave and music examples require an explicit action.
First-person, third-person, fixed and top-down gameplay camera settings are serialized. Third-person arms shorten against independent box colliders; authoring navigation remains separate from gameplay. The controller is still a bounded ground-plane prototype, not a general character/physics system.
Identity, discovery and usable controls
The product is named ASHVEIL ENGINE by Guassia. /engine/, /free-game-engine/ and /gaussian-asset-editor/ provide distinct, crawlable workflow descriptions, canonical URLs, useful internal links and factual metadata. A dedicated social card replaces the music-world card on engine pages. SoftwareApplication data contains no fabricated reviews or ratings.
New file controls and open-ground guidance are translated for English, Spanish, Mandarin, German, French and Dutch. The other language choices use an explicit English fallback for new copy. Added mobile wrapping keeps Save project visible and fixes the expanded Save control contrast.
A dated capability atlas compares 144 workflows across 18 Blender/Unreal domains using 31 official references. It identifies scope and gaps; it is not an exhaustive operator census or a claim of engine parity.
Desktop Home and personal assets
The Guassia 0.5.1 launcher opens with a sign-in prompt and a Home screen for Join a game, Host a game, ASHVEIL ENGINE and ASHVEIL ASSET CREATOR. An unconnected account provider is shown as unavailable; no local profile pretends to be a verified account. Previously installed tools may still open offline.
A separate local asset library imports validated native .gasset copies, deduplicates by content hash, exports a copy and reveals its folder. Originals remain unchanged. Local assets are independent of account purchase entitlements. Start making money opens an asset listing draft; it cannot publish or charge money.
Join/Host explains the current browser-hosted ten-person presence and voice preview. It does not claim authoritative synchronized game simulation or a deployed public server directory.
Owner reports expose private administrator ledger pages and a native CSV save dialog. Signed-out, denied and disconnected states remain explicit. Session changes discard in-flight responses, report sizes are bounded and CSV text cells are protected from spreadsheet formula execution. Live report data requires the backend service.
Private Gaussian surface review
Ten original procedural Gaussian assets were authored for owner review: oak tree, moss granite, brick arch, oak-and-iron door, limestone column, bronze lantern, shipping crate, park bench, fern and terracotta pot. The sources total 1,425,198 Gaussians, with full and close 3840 by 2160 rendered previews.
A private .gworld arranges the ten assets on open white Gaussian ground. Its eleven source assets, including the ground, fully decode and each embedded review source matches its original hash. This review collection is not published as a free download or activated as a paid pack. The assets remain visibly procedural; 4K describes capture dimensions, not photographic quality or texture resolution.
Broken logging pipe fix
A background capture test could keep writing after its parent output pipe closed, producing repeated EPIPE error dialogs. The affected agent test was stopped. Main-process logging now handles broken stdout/stderr pipes without repeatedly throwing; unrelated application errors remain errors. The capture harness uses file-based progress instead of console output.
Prepared marketplace records — not a live checkout
The prepared platform service adds administrator-only purchase, earnings, checkout and wallet history with bounded pagination, filters and CSV export. Reports do not expose serials, storage keys or payment-provider secrets. These are ledger extracts, not complete tax filings or net-profit accounting.
Operator-configured first-party sellers allocate all item revenue to Guassia before costs, taxes and refunds. Other sellers retain the existing 30%/70% allocation. New purchases snapshot policy and item identity atomically so retries or later catalog changes cannot rewrite prior receipts.
The additive database migration has not been applied to production. Production account/status service returned 404 in this review. Paid activation remains disabled until the account, seller, payment, refund/dispute, payout and private-download lifecycle is completed and verified.
What was checked
297 authoring/export/project regression tests passed in the final integrated run. A separate 23-test focused review passed across project saves, portable archives, native files, process logging and engine SEO. Groups overlap and must not be added as a unique total.
The logging regression launches a real child process, closes its stdout pipe from the parent and confirms continued execution and normal exit.
A 390-pixel browser check verified Spanish Save project controls, retained Open input and fully visible mobile actions. Desktop engine landing page and branding were visually inspected.
Platform service tests passed 73/73, covering authorization, allocation, immutable receipts, transactions, migration, pagination and CSV protection. Local fixtures do not prove real payments or production database behavior.
Native Electron checks verified blank startup, restricted preload, validated file writes, repeated Ctrl+S without another dialog, Save As, native Open, canceled Open, camera persistence and recovery after navigation. Dialog destination choices were supplied by the test harness.
Eight new review regressions cover document changes during picker/build/write, stale UI completion, native token adoption, restricted picker fallback/cancellation and near-limit narrative archives.
Five asset/import tests passed; all twenty native 4K captures completed with zero WebGL errors and zero renderer console errors. The private review world contains 1,439,839 source Gaussians including its ground.
The final launcher service suite passed 57/57 tests, including a real local HTTP transport fixture for sign-in, report JSON/CSV headers and denied/redirect/stalled responses. Thirteen hidden launcher UI checks passed. Synthetic account fixtures do not establish live sign-in or purchases.
Known limits and unfinished work
Browser and native world formats remain separate workflows; .guassia.zip and .gworld are not interchangeable file extensions.
Finite source and preview budgets remain. True streamed hierarchical LOD, dynamic relighting and articulated character authoring are still substantial work. No unlimited-Gaussian or universal 4K-performance claim is made.
The SEO release establishes content and technical discovery signals; ranking, indexing and audience growth require subsequent search evidence.
The native Windows build is unsigned. Clean-machine installation and macOS/Linux packages require separate verification.
Long newly added desktop help and the developer changelog still use English fallback. Six-language action and new camera labels do not establish a fully translated product.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Portable projects and engine discovery source checkpoint · 97a7350
Open ground, game cameras, local files, localization, logging and prepared commerce records.
Real main/preload IPC and filesystem writes with dialog destination choices stubbed; not a clean-machine installation.
Save-race correction and private Gaussian detail review · 8a11508
Follow-up source checkpoint, including data-only portable archive round-trip regressions.
In-scene creation, larger Gaussian projects and desktop stores
Included with this site release
In-scene creation, larger Gaussian projects and desktop stores
Build inside your scene, use bounded gameplay scripts, and retain larger Gaussian sources. The installed client now separates Games, Assets, Library and Creator tools; the browser remains a free editor without purchases.
Source checkpoint 983efc3Source availability and destination verification are separate.
September 23 follow-up: returning-browser language controls
A public browser retained an older unversioned locale module while loading the new language entry script, causing a missing-export error and hiding the language selector. This follow-up versions raw module dependencies by their content hash before calculating the page entry URL. A dependency-only change now refreshes the importing entry too.
Locale JSON requests revalidate HTTP caches while retaining the controller’s in-session cache. Portable exports remove the known build-time module query from their copied entry, so their matching local files work on the strict self-host server. Desktop installation packages are not rebuilt by this web-only cache fix.
Larger sources with bounded previews
The authored budget increases to 5,000,000 instantiated Gaussians, with up to 1,000,000 per source and 5,000,000 across the source library. Shared instances retain one immutable source. Independent limits remain 2,048 objects, 16 asset definitions, 16 NPCs and 24 rooms.
Preview tiers cap resident source samples and active-room samples separately. Balanced allows 750,000 resident and 350,000 active; High allows 1.5 million and 1 million. Source storage and exports retain original detail. This is deterministic preview sampling, not full streaming or hierarchical LOD.
GAssets allow 64 MiB, and portable ZIP imports allow 512 MiB compressed/expanded data under strict bounds. Exports reserve package overhead. Larger authoring limits do not guarantee smooth rendering.
Navigate inside your scene
The asset workshop adds Top-down and In-scene viewport modes, drag looking, WASD/Q/E navigation, camera speed and touch movement controls.
Frame room and Frame selection bring work into view. Shift-click places the selected instance while preserving source arrays and owned NPC route offsets.
Authoring pauses gameplay, scripts and music. The viewport currently shows the selected room, with conservative object picking rather than exact translucent-splat selection.
Optional game scripting
Game tools includes Script v1, a bounded JSON gameplay language with events, variables, arithmetic, conditions, repeat blocks and object/gameplay commands. Examples cover journals, collectibles, interactions, doors and room transitions.
Scripts can alter Gaussian instance transforms, tint, opacity and visibility; add journal entries; award objectives; trigger supported sounds; and use gated progression. Story remains optional and new worlds stay empty.
Check validates before Apply. Per-frame instruction, event and command limits pause faulty scripts. Scripts cannot execute JavaScript, access the DOM, run programs or make network requests. This is not unrestricted professional scripting or a visual node editor.
Desktop distribution
The public Windows installer contains the Guassia launcher, stores and six interface dictionaries. Game Engine and Asset Builder are separate free downloads inside the app after verified sign-in; once installed, they work offline. The public installer contains no creator runtime. macOS and Linux packaging targets still need native builds and verification.
The installed app opens Guassia Games Store and Guassia Asset Store, with search/filtering, listing details, an account dialog, Library, Creator dashboard and Free creation tools. Empty or disconnected services are shown honestly. Licenses and installed files are separate; game installation and paid fulfillment remain unfinished.
Creator downloads use a private content-addressed container, whole-package and per-file hashes, bounded size, atomic installation and interrupted-write recovery. Creator pages use a separate origin without the store bridge. Verified sign-in and actual private-storage configuration are required; there is no paid entitlement for these tools.
Update checks authenticate signed manifest metadata and bound actual response bytes, including chunked responses. A signing key and release channel must be configured. The client does not yet download, verify and automatically install updates.
Authored environments and self-hosting
Rooms can disable generated surfaces while retaining collision and world boundaries. Authored areas support up to 256 by 256 by 128 metres; generated shells retain their smaller budgets. The safe-spawn search has bounded work so a large map cannot trigger a full-volume scan.
Museum Night Shift and Neon Rain contributions were adapted privately to the current trusted runtime. Original asset bytes and credits were preserved; contributed programs were not executed. Museum redistribution rights remain unconfirmed. Neon retains 132 objects and 950,496 placed source Gaussians.
The self-host starter runs on an owner's computer or VPS, with ten-person invitation rooms, project identity checks and opt-in WebRTC voice. Push-to-talk, mute, deafen and leave controls release the microphone. It is inspired by familiar voice-chat controls; it does not implement the Mumble protocol or record audio.
The first self-hosted room service coordinates presence and voice, not authoritative shared NPCs, inventory, physics or progression. Local tests are separate from internet hosting: TLS, approved origins and optional relay configuration are operator responsibilities. No rented server or automatic router/firewall changes are created.
The self-host starter includes a bounded static host for a complete trusted website export and an optional in-game Voice overlay. The host retains the original export files and injects its own external interface module only into the served entry page. Node.js 24 or newer is required; the server ZIP does not include Node.
Partnerships, requests and store foundations
The Let's map the world partnership page explains the long-term Gaussian mapping objective and includes company, contact, interest and proposal fields.
The request form has idea, bug, accessibility and translation categories. The prepared service requires verified-email sign-in, server-verified CAPTCHA and private administrator review. Weekly review is scheduled; unconnected forms remain disabled.
The owner-selected model is a free engine, a one-time $100 publishing fee per game including free games, free asset uploads, optional zero-priced listings and a 30% share of paid game/asset sales. There is no Enterprise subscription.
Backend foundations include atomic purchases, credit ledgers, serial entitlements, free claims and protected downloads. The store remains a preview. Creator uploads, publishing, payouts, refunds, disputes, taxes and live payment delivery are unfinished; paid checkout stays disabled.
The existing Stripe merchant contains a separate one-time $100 Guassia product. Product creation is not a charge, completed merchant verification or store activation.
Browser store and library pages are informational and contain no checkout, credit top-up or purchase controls. Backend store actions require the native channel plus verified account and ownership checks; a client header alone is not authentication.
Creator metadata drafts support bounded prices, explicit license notes, retry-safe IDs, revision checks and private account ownership. Saving a draft cannot charge a fee, publish a listing or issue a license.
New engine/runtime exports include a personal-preview notice for learning, private testing and backup. Original creator ownership, separately licensed components and earlier license grants are preserved. Public distribution requires separate permission; a provenance marker is not tamper-proof DRM.
Language coverage and developer guidance
English, Spanish, Simplified Chinese, German, French and Dutch receive an expanded first-party interface catalog for editor, assets, scene, gameplay, accounts and platform controls. The globe selector persists the language and handles dynamic panels.
Authored names, notes, scripts and uploaded content are preserved. Historical changelog paragraphs, some long documentation and lower-level errors remain English; full human language review is not claimed.
The Gaussian toolset comparison adds measured next milestones for batching, close-range appearance, streaming/LOD, articulated movement, geographic coordinates and reliable creator services.
What was checked
Chrome rendered a 1-million-source asset referenced five times. Balanced preview used 70,000 shared samples and 350,000 active samples while preserving all 5 million authored Gaussians and the source SHA-256.
The isolated 1214 x 758 test measured 84.2 ms CPU plus awaited-renderer work. It was not smooth 60 FPS, measured GPU time or evidence of drawing five million full-detail visible splats.
Browser checks exercised camera projection, movement, instance placement and a 390-pixel layout without horizontal overflow or page errors.
Automated test and native packaging receipts remain separate from public delivery proof. Local checks do not establish real payment fulfillment or clean-machine compatibility.
Desktop storefront fixture checks cover disconnected services, local draft persistence, untrusted text, catalog filtering, library state, creator draft receipts and narrow layouts. Fixtures do not establish live service readiness.
The final combined editor, native download/update, platform and self-host suite passed 374 automated tests. In-game voice was checked between two isolated Chrome contexts using synthetic microphones and actual audio RTP; opt-in, push-to-talk, focus loss, deafen and microphone shutdown passed.
Native Windows developer-app startup checks verified a working launcher and separately installed creator editor with no renderer Node access and no creator store bridge. Final installer delivery and clean-machine installation remain separate evidence.
A Chrome 153 regression warmed an actual one-hour HTTP cache, reproduced the missing initializePageLocale export, then loaded the fixed entry in the same context without clearing cache. The selector and Spanish/English switching worked with zero subsequent page errors. Twenty-seven focused module-cache, localization and portable-export tests passed.
Known limits and unfinished work
No unlimited-memory, photorealism, world-scale mapping, Blender/Unreal parity, universal 4K/8K performance or 100x improvement claim is made.
Windows signing, clean-machine installation, automatic update installation and native macOS/Linux verification remain release requirements.
Accounts, authenticated submissions and financial services need configured providers and destination verification. Serial identifiers do not transfer creator copyrights.
The September 23 cache follow-up is source-tested here; the repaired public page still requires a new deployment and verification in the affected browser cache. Prior fresh-context localization checks did not exercise this returning-browser failure.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Actual Chrome HTTP cache reproduced the old missing-export failure and verified the content-versioned replacement without clearing cache; this is a local fixture, not public deployment proof.
Deeper NPC authoring, precise selection tools and 2,048 object slots
Historical public delivery verified
Deeper NPC authoring, precise selection tools and 2,048 object slots
Create patrols, companions and look-away figures, edit several shared Gaussian instances together, and build larger layouts. The learning page now has readable cards and illustrated lessons for the new controls.
Source checkpoint 9d7db313Public delivery checked
NPCs with editable attention and routes
Game tools → NPC movement offers stationary, patrol, patrol-and-pursue, look-away, follow and flee behavior. Four behavior presets fill a draft; Apply saves the chosen settings. No NPC is inserted into a new world.
Draw a route on the room map, drag its numbered points, or edit and reorder the XYZ list. Routes support up to 24 points, looping, back-and-forth or one-shot travel, with optional waypoint pauses.
Advanced controls expose separate route and active speeds, turning speed, home boundary, following/fleeing distance, field of view, detection distance, optional line of sight, last-seen memory, contact cooldown and reset conditions.
Sight memory follows only the last observed position. Fleeing stops at the chosen safety distance. Restart clears behavior state; leaving a room can return its NPCs home. Optional diagnostics show behavior state, route index, sight and blocked movement.
Typed route coordinates are collected and validated directly when Apply is pressed, preventing loss when a blur event has not fired. Invalid route edits cannot partially change the saved world.
Precise editing of shared Gaussian instances
Selection & transform tools can select one or more objects in the current room, move them, snap origins to a grid, rotate or uniformly scale around the selection center, align origins, distribute at least three origins evenly, and apply tint/opacity overrides.
Yaw composes with the existing object rotation. Owned NPC route points follow their object transforms. Separate proximity zones, transition areas and sound emitters keep their own positions.
Each selection operation validates before committing and creates one object-undo step. Shared source Gaussian arrays are not rewritten by these placement or appearance edits. Alignment uses object origins, not surface-to-surface spacing.
Object undo history is cleared when later game-authoring changes would make restoring an older snapshot unsafe. Blocked deletion reports its explanation, and individual position edits or duplication carry the owning NPC route along.
Larger layouts with explicit budgets
The placed-object limit increases from 128 to 2,048, a 16-fold increase in authoring slots. Source assets can be reused without duplicating their Gaussian data.
Object count and rendering detail remain separate budgets: 300,000 instantiated object Gaussians, 50,000 per imported asset, 16 NPCs, 16 asset definitions and 24 rooms. A scene may reach its detail budget before its object-slot limit. The workshop shows both object and Gaussian usage.
The bounded draft description limit increases from 256 KiB to 2 MiB so large valid layouts can be saved, exported and reimported. The player reserves separate instance slots for room shells and optional music visuals.
Runtime lookups use object IDs and room-local lists to avoid repeatedly scanning unrelated rooms. This improves CPU bookkeeping; it does not establish full asset streaming, hierarchical LOD or a frame-rate guarantee.
Readable tutorials and architecture reference
Fixed the pale cards under Optional paths through your world: headings and body text now use dark, readable colors. NPC panels and route coordinate fields receive matching contrast and responsive layout fixes.
Added illustrated, hands-on lessons for selection transforms and NPC patrol/sight/memory, with direct links to the relevant builder panels.
A downloadable Gaussian toolset audit maps 30 Blender/Unreal workflow domains to current Guassia features, existing lower-level foundations and proposed work. It links to official documentation and sets dependency and validation gates; it is not an exhaustive operator list or a feature-parity claim.
Every subsequent engine or site update must include changelog notes, including fixes. Release instructions now state that missing notes mean the update is incomplete.
Release packaging removes obsolete generated, hashed JavaScript chunks from the fixed hub output directory, keeping unused older runtimes out of new uploads. World assets and unrelated files are preserved.
Compatibility and upgrade notes
Existing version-1 drafts retain their behavior defaults. New worlds remain empty, with music, NPCs, story and objectives optional.
Re-export downloaded games to obtain the new runtime and limits. Existing offline ZIPs do not update automatically. Keep the complete ZIP for asset/audio backup; a project JSON is not an asset archive.
Current developer lessons and release notes are English. The existing globe language picker remains available; partial interface dictionaries do not imply that all new technical copy is translated.
What was checked
Regression checks cover NPC behavior, collision and last-seen memory, route persistence, validation, source immutability, multi-object transforms and export boundaries.
Browser checks exercised the actual preset, visual-route dragging, numeric edit and Apply workflow, multi-object Move and Undo, NPC pursuit/contact reset, optional diagnostics, readable lesson cards and a 390-pixel layout.
A private 2,048-object world imported and rendered in Chrome using two rooms and one shared 100-Gaussian source (204,800 object Gaussians). The active 1,024-object room at 1181 × 780 produced isolated running frame-work readings of 162.8 and 248.1 ms on this host, so this dense scene was not smooth. These are CPU-plus-awaited-render measurements, not GPU timestamps or percentiles.
CPU bookkeeping is measured separately: the synthetic Node fixture validated in a median 5.37 ms, dispatched a single transform edit in a median 0.014 ms with a counting bridge, and sent no updates for unchanged static frames. This excludes actual GPU rendering. Exact test totals and destination checks are saved in the release receipt.
Known limits and unfinished work
NPCs are rigid Gaussian groups with ground-plane steering and mathematical collision/sight proxies. They do not yet have skeletal walking animation, navigation meshes, automatic obstacle routing or a behavior-tree editor.
The 2,048-object authoring ceiling is not a promise that every 2,048-object scene renders smoothly. Gaussian count, transparency, active simulation and device capability still matter.
Full relighting, dynamic shadows, articulated characters, arbitrary visual scripting and hierarchical streamed worlds remain separate engineering work. No Blender/Unreal parity, universal 4K/8K frame rate or 100x improvement is claimed.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Editor and runtime source checkpoint · 9d7db313
Immutable source checkpoint for this update; public delivery is checked separately.
Existing Cloudflare production delivery · 9ae4ee64-609f-412d-85c6-73628df00837
Fresh native production ID and 68 exact HTTPS file checks verified September 23; the original deployment completion time was not inferred.
Scope and limits · BUILD-STATUS.md
Implemented authoring features and remaining engineering work.
Actual UI observations; does not establish a hardware fleet benchmark.
A blank engine with optional gameplay, better controls and language choices
Historical public delivery verified
A blank engine with optional gameplay, better controls and language choices
The builder starts with an empty room. Creators can add assets, story progression, movement, spatial sound and visual effects only when their project needs them.
Source checkpoint de15e0dPublic delivery checked
Starting a project and building a game
New projects contain one empty room. The music example, soundtrack, effects and gameplay systems are optional; no club or quest is inserted automatically.
Creators can require specific collectible objects, lock an exit, write an ending and restart with the original world state restored.
Optional achievements, room gates and transition zones support progression between authored spaces. Destination gates are checked, and the starting room cannot be locked behind a progression requirement.
Readable notes, a journal, proximity events, reveal/hide actions and opening doors turn a layout into a sequence of interactions.
Input, movement and sound
Mouse capture has a click-and-drag fallback for embedded browsers, with sensitivity and invert-Y settings. Desktop movement and mobile controls remain available.
NPC controls expose basic patrol, pursuit and move-only-when-unseen behavior, with bounded detection and reset settings. Figures move as rigid Gaussian objects; this is not skeletal character import.
Spatial emitters, one-shot cues and room soundscape fades are authorable. Active audio uses a bounded 128 MB decoded cache and a 16-voice limit.
Optional diagnostics report input mode, room, loading errors and CPU/awaited-render timing. Those timings are not measurements of GPU execution time.
Gaussian assets and close inspection
The workshop imports static GLB surface samples, anisotropic Gaussian PLY, native GAsset files and flat image art. A photograph does not become a reconstructed 3D scene.
Explicit adaptive import reduction retains spatial coverage and prioritizes local color variation and smaller source splats. Preserve mode refuses an excessive PLY count instead of silently discarding points.
Cleanup can preview low-opacity, oversized and isolated-splat removal, then save a separate copy. Floater removal starts off to preserve thin authored features, and the original asset remains available.
The 3D inspection view starts only when opened. Full-asset, player-eye and arm-length views help inspect signs, doors, thin edges and overlapping surfaces at actual object scale.
Appearance, collision and budgets
Visible assets remain Gaussian source data. Object transforms, tint, opacity and dissolve overrides operate on instances rather than rewriting source positions.
Compound mathematical collision boxes are separate from appearance, so an opening can remain walkable. Groups preserve shared source assets and individual behaviors; grouping does not bypass budgets.
The current authoring limits are 128 objects, 16 NPCs, 24 rooms, 16 asset definitions and 300,000 instantiated Gaussians. Individual imported assets remain capped at 50,000 Gaussians.
Distance fog and silhouette dissolve are optional. Auto, 1080p and 4K render choices are accompanied by explicit advanced 8K eligibility checks. A larger framebuffer does not add missing asset detail or guarantee frame rate.
Saving, exporting and rebuilding
Website ZIP export and reimport preserve Gaussian assets, authored relationships and selected original audio bytes. Sound manifests and chunks are checked before imported sources are saved.
Missing or corrupted sources are reported instead of producing a silent or incomplete success. Oversized authored project descriptions are rejected before an unimportable package is generated.
Local Save stores data on the current device. Downloading a draft or website ZIP does not publish a world. Website packages need HTTPS hosting; they are distinct from compiled Windows applications.
Language access and learning
A visible globe-marked language control at the top of site pages offers 21 locale choices representing 20 distinct languages, including Simplified and Traditional Chinese. Language selection is also available in portable and paused players. Arabic and Urdu support right-to-left layout.
The dictionaries cover 93 navigation, builder, accessibility, gameplay and help strings. Only the selected first-party locale loads; English remains the fallback and the selected language can persist on the device.
Translations are machine-authored and await fluent human review. Coverage is partial: creator content is unchanged, some interface and tutorial material remains English, and legal terms remain in their original English.
Guides explain empty projects, importing and inspecting assets, optional objectives and story events, movement and sound, testing, and the difference between a local draft and a published website.
Compatibility and upgrade notes
Existing version-1 drafts remain supported. Starting a new world creates an empty room; loading an older draft preserves that draft's authored rooms and content.
Re-export an existing game from the current builder to include the new runtime, bundled languages and authoring behavior. Previously downloaded ZIPs keep their original code and do not update automatically.
Keep the whole website package together, including models, audio, i18n and license folders. Import the complete ZIP to restore its assets; project JSON alone is not an asset backup.
The language control changes the supported interface labels. Creator-written dialogue and titles stay intact, and current developer release notes and legal copy remain in English.
Education and platform services
An optional signed education-entitlement verifier and export notice/branding hooks are a development foundation only.
Public education onboarding, entitlement issuance, hosted accounts and payment or protected-build delivery are not activated by this update.
The build-status record reports browser checks for an empty world, ZIP import, a 3840 × 2160 framebuffer, collection, an ending and restart, achievement journal, close asset inspection, room-gate authoring and a 390-pixel Arabic layout.
Included with this site release identifies the source features bundled with this changelog. A public deployment receipt is recorded separately after matching destination readback; the source checkpoint alone does not prove live delivery.
Known limits and unfinished work
Captured PLY appearance still uses baked/DC color. Full view-dependent SH preservation, relightable PBR materials, dynamic shadows and articulated/skinned Gaussian characters remain substantial work.
Current room visibility and audio caching are not full asset streaming or hierarchical Gaussian LOD. GPU memory/time adaptation, fleet performance and universal 4K/8K performance are not established.
This is not feature parity with Blender or Unreal, and it does not establish a 100× editing advantage.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Source checkpoint · de15e0d
Commit dated September 20, 2026 at 21:34 America/Denver; a source checkpoint is not a live-delivery receipt.
Authoring build status · BUILD-STATUS.md
Implemented scope, browser verification boundaries and unfinished engineering work.
Localization validation · i18n.test.mjs
Dictionary completeness, text-only insertion, RTL, fallback, persistence and visible language-control behavior; not linguistic certification.
Previous production release · guassia-authoring-release-receipt.json
The prior deployment and HTTPS readback verified the preceding authoring and language release. This does not cover the new NPC and capacity work.
Gaussian asset workshop, export clarification and club lighting
Historical public delivery verified
Gaussian asset workshop, export clarification and club lighting
The builder gained reusable imported objects and a guided asset workflow. Website packages were labeled more clearly, while separate Windows prototypes were built and inspected as packages.
Source checkpoint 6e22b68Public delivery checked
Creation and reuse
Added GLB, Gaussian PLY, GAsset and PNG/JPEG import, native Gaussian shapes, shared-source instances, object transforms and appearance controls.
Added duplicate/combine operations, undo/redo, simple spin/bob/collect behaviors, collision boxes, six illustrated tutorial steps and the editable First Quest example.
Music-world update
The club added 100 authored lighting combinations with 15-second changes and crossfades, moving Gaussian fixtures, dancers and walkers.
ASHVEIL walking and DJ choreography remained authored animation. Lighting timing was not represented as detected musical-drop timing, and assets remained stylized.
Export and Windows clarification
The browser entry changed to web-player.mjs and website ZIP instructions explained the HTTPS-hosting requirement. Opening browser JavaScript with Windows Script Host was identified separately from an EXE failure.
Separate unsigned First Quest and club Windows prototypes were built. Package contents, executable structure and recorded hashes were inspected; native startup, rendering and audio were not verified.
What was checked
The historical release receipt records Cloudflare success, 95 uploaded files and matching HTTPS file comparisons.
The receipt reports 128 engine/builder checks and eight desktop-packager checks. A later 12-check rerun overlaps those tests and must not be added as unique coverage.
Browser observations covered conversion, rendering, export, collection/pause and touch-emulated layout; this was not a physical-device benchmark.
Known limits and unfinished work
This historical version had a 48-object limit, which the newer authoring update changes. Public account, publishing and payment services were not completed by this release.
A successful Windows build and package inspection did not establish successful native execution.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Source checkpoint · 6e22b68
Asset workshop, club lighting and desktop export source changes.
Deployment e3e41408; source, HTTPS checks and build receipts recorded separately.
Club and First Quest prototype receipts · build-receipt.json
Both receipts explicitly record nativeLaunchPerformed as false.
Music-reactive plugins and portable original audio
Historical public delivery verified
Music-reactive plugins and portable original audio
Optional sound-driven components connected the simple world builder to a soundtrack, while the public ASHVEIL world gained authored performer choreography.
Source checkpoint b06ba81Public delivery checked
Audio and authoring
Added pulse lights, an eight-band spectrum wall and an interactive sound orb, plus demo/local soundtrack selection, per-room response and selected-room playtesting.
Portable website ZIPs included the selected original audio in verified parts. The recorded test export matched the original soundtrack bytes without transcoding.
Club and usability
Added deterministic walking, grounded stance and DJ-rig animation, with responsive visualizer bars and rings.
Browser checks identified and corrected stale scripts, hidden spectrum bars, selected-room preview behavior, small-room interaction priority and overlapping new-room placement.
What was checked
The historical receipt records production deployment success, ten matching HTTPS file comparisons and 81 integrated automated checks.
The recorded three-room browser export contained the exact original 57,600,044 soundtrack bytes and a runtime matching that release.
A 390-pixel touch-emulated builder layout was checked. Independent hosting of that exported ZIP and physical-device performance were not verified.
Known limits and unfinished work
Public accounts, creator publishing and integrated multiplayer servers remained incomplete. The experience was a stylized Gaussian world, not a claim of photorealism or a complete general-purpose engine.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Source checkpoint · b06ba81
Reactive plugins and authored club choreography.
Historical release and export receipt · GUASSIA-MUSIC-CLUB-QA.json
Deployment 2832b404; checked September 19 at 22:21 America/Denver.
First public Guassia hub and portable room prototype
Historical public delivery verified
First public Guassia hub and portable room prototype
The palm-branded browser hub connected a learning guide, local room editor, creator/world routes and the ASHVEIL listening-world experience.
Source checkpoint 3628911Public delivery checked
Browser foundation
Introduced the public hub, learning pages and /u/name/ and /w/world-name/ route structure, with a coordinated palm-and-fruit brand mark.
The room-layout editor could open a bounded Gaussian solo playtest, save a local draft and download a website ZIP. Source audio and performer data used checked byte parts for static hosting.
What was separate
A ten-player invitation-room service foundation was committed separately as 2755f9d with automated tests. It was disabled, not integrated into the public frontend and not deployed as working friend servers.
The world editor did not create public accounts or publish creator worlds merely by saving a draft.
What was checked
The initial release record contains public route/body checks, successful custom-domain HTTPS comparisons and an actual browser-created nine-file prototype export.
Browser QA checked two-room editing and persistence, Gaussian rendering, play/pause/return controls, JSON import/export and a touch-emulated joystick.
The historical receipt timestamp is preserved here; it is not a claim that the earliest commit time was the public launch time.
Known limits and unfinished work
The initial ZIP was inspected, but its standalone execution on a separate host was not verified. Sustained physical-device input/performance and full multiplayer delivery remained future work.
Source records and delivery evidence
Record names identify the development evidence behind this entry. A source commit or successful build alone is not proof of a public release.
Hub source checkpoint · 3628911
Palm-branded learning hub, local editor and portable Gaussian-world foundation.
Initial public launch evidence · GUASSIA-LIVE-LAUNCH-QA-2026-09-19.json
Deployment e698c3a8; public-domain and export evidence recorded September 19, America/Denver.
Separate service foundation · 2755f9d
Source/tests only; no public multiplayer deployment is asserted.
