How to use ARMORY /
A practical path through ARMORY, from the first input to a saved, reviewable result.
A mineral-green asset workbench pairs a large interactive 3D stage with an object inspector and collection shelf. Three original GLBs can be inspected and downloaded from the public interface.
Before you begin
Explore the public interface with example records first. Its preview interactions stay in the current view; use the workspace link to open the account-backed product described below.
Create an account in ARMORY and work in its own private workspace. Accounts and records from another Lumia product are separate. Small 3D studios, independent artists and production teams managing reusable, self-contained models and version-specific deliveries.
Follow the workflow below to understand the application. Contact Lumia for a guided walkthrough; account access is private. An exported file reflects the record at the time of export.
Register the asset and its rights
Upload a self-contained GLB with a descriptive title, useful tags and a rights statement you can support. Confirm that you hold permission to upload and share it. ARMORY records this declaration with the asset; it does not decide a licence for you. Begin with a model whose dependencies are embedded.
Inspect before committing to reuse
Open the actual model in the viewport. Use wireframe to understand the mesh and the exploded view to distinguish named parts. Read the reported mesh, material, node and file-size counts. These observations help an artist decide whether the asset fits the next scene before downloading or including it in a delivery.
Keep revisions without changing old handovers
Upload a revision as another version of the asset. The library can point to the newer version while an existing delivery continues to reference the earlier one. Name collections around an actual handover or review milestone so their purpose remains clear when several versions coexist in the same workspace.
Deliver files with an inspectable manifest
Select the exact asset versions for a collection and download its ZIP. The bundle includes the original GLB bytes and a manifest identifying each file, version, rights statement and checksum. Inspect the manifest when handing work to another tool or person. Search by tags when returning to the library for a later job.
Operating the product
Start with the public interface to explore the design using example records. These interactions stay in the current view. Open the private workspace from the interface to use the existing account, storage and product workflows.
Resolve missing or external dependencies in the authoring tool and export a self-contained model before uploading.
Create a new version for a revised file instead of expecting an older delivery to follow the latest asset.
Split a collection if its combined model bytes exceed the delivery cap.
If an integrity check fails, retain the failed record for investigation and recover the intended original file before retrying.
Keep the bundle manifest with the models so recipients can identify versions and verify checksums.
A similar problem in your business?
Bring a real workflow, representative inputs and the result that needs to be reliable.
Shape a project brief