GO3D · Local-first capacity plan

Dragonfire
Build in stages.

Start with the MSI you have. Add capacity when real work calls for it.

A short local language-model test is confirmed. Scan-processing speed is not. This guide separates what we measured from what is still a planning estimate.

See the upgrade path Open the public resource guide

Prototype · No public scan upload or processing offer

The simple answer

Keep the MSI.
Upgrade in steps.

No scan data has been supplied, so the next machine should not be chosen from a made-up return number.

NOW · NO PURCHASE

Use the MSI.

It has a confirmed local language-model test. The test was text, not scan processing. Keep it as the prototype machine while the workflow is being built.

IF FIELD WORK NEEDS IT

Start with one workstation.

Quote one FieldCart system first. The current worksheet lists a pair, not a one-unit price. Add a second only for another independent job.

LATER · WHEN WORK PROVES IT

Build the shared engine.

Compare the 512 GB rack first when jobs or the queue outgrow one workstation. Hold 1 TB / 96 GB until measurements show why it is needed.

SIMULATION, NOT ROI

Current records do not include valid prices, scan-processing times, or job volume. This page shows capacity choices; it does not claim savings, payback, or measured scan speed.

What we know so far

The MSI is enough to keep learning.

These are measured computer specs and simple memory estimates. No scan job or candidate upgrade was tested.

MSI processor: 24 logical CPU cores
System memory: 63.4 GiB RAM
Graphics memory: 15.9 GiB VRAM
Local model test: 7B text prompt only

When does a GPU matter?

File inspection mainly reads files and checks their contents. Point-cloud processing depends on the chosen method; some methods can use a GPU. High-resolution display work can also use more graphics memory. A 3D file alone does not tell us which computer is needed.

Planning example: a 30B local language model with a very long 256K context leaves about 0.5 GiB of raw graphics memory on a 32 GB card, before Windows and runtime use. That is a capacity estimate, not a tested speed result or a GO3D requirement.

Open the full prototype, workflow, and resource notes

Dragonfire / Local processing guide

MSI first.
Parallel by design.

Build and enhance apps using the power you already own. Match each task to the right tools, resources and review.

GO3D Dragonfire MSI-first concept illustration. A short local text prompt has been tested on the MSI; scan-processing performance has not. — Concept illustration with the original approved GO3D logo. The four buttons open official setup and usage guides. The same links are available beside the image.

Use local capacity for compatible work.

Run app builds, tests, local previews, CAD and mesh preparation, rendering, media processing and repeatable scripts on the MSI when the required software and resources are available.

Split the work with care.

Run independent tasks in separate worktrees or job directories. Size concurrency to measured CPU, memory and VRAM capacity. Reuse scripts and cached results, avoid duplicate jobs and conflicting writes, and validate outputs.

Keep processing costs visible.

Local tools use workstation hardware. Cloud model calls still consume allowance or credits, and more cloud agents can increase usage. On-device processing requires a separately configured compatible local model.

Download the clickable PDF Open the full-size image

MSI check · 1 Nov 2026. One short local 7B text prompt ran on CPU and GPU. No scan-processing benchmark has been run.

Watch the 29-second overview

Silent overview with on-screen text. Concept illustration; original approved GO3D logo preserved.

DRACARYS / HARDWARE DIRECTION

One field workstation first. Shared rack later.

The equipment list is for planning. Exact parts, one-unit pricing, power, cooling, cart design, and compatibility still need confirmation.

The community rack engine is a future goal; it is not currently accepting processing jobs.

Dragonfire / Report & resources

Less desk time.
More work delivered.

Explore the performance opportunity report, both comparison graphics, and the local processing guide in one place.

NO SCAN-TIME CLAIM

There is no measured GO3D scan-processing time or time-saved figure yet. The local text-generation test and hardware-capacity simulation do not predict scan performance.

Open the Dragonfire resource hub

01 / Shape the request

Choose the work.
Define the result.

Select a workload to explore the service and build a short brief for project scoping.

What are you working on?

This brief stays on your device. Nothing has been submitted.

Your processing briefLocal planner

A lighter model for review.

Requested output: A separate review mesh with an agreed balance of detail, file size and viewing performance.
Bring to scoping: The source scan or mesh, units, intended viewer and the details that must remain visible.
GO3D reviews: Source condition, detail priorities, target format and a practical reduction approach.

See public workflow resources

This planner creates a local brief only. It does not upload files or start a processing job.

02 / The planned approach

Keep each result
easy to check.

Compute is one part of the work. The input, chosen method, and review criteria matter too.

01 / SCOPE

Match the work.

Confirm the files, required output and review criteria. GO3D scopes the software and compute needed for that job.

02 / PRESERVE

Keep your source.

Plan processing as a new revision. Preserve the original files and record the settings used to produce the result.

03 / REVIEW

Make results usable.

Agree how the output will be checked, reviewed and delivered for its intended use.

FUTURE COMMUNITY ENGINE

The goal is a shared GO3D engine that can serve community work. It is not live for processing today. The local prototype and the future shared service are separate stages.

03 / A few useful answers

Before you
start a test.

Dragonfire / Dracarys is a GO3D prototype.

What can I do here today?

Review the upgrade path and public resources. This page does not accept scan uploads or start processing jobs. A small STL/OBJ inspection worker is available separately; it reports basic file details and has not been validated as a full scan-processing workflow.

Does turning on my MSI laptop speed up ChatGPT?

Turning on the laptop or opening the same chat does not assign cloud computation to it. Its hardware can help when a supported processing job actually runs on that computer through an explicit connection. GO3D would need to configure and verify that connection first.

Can every scan become editable CAD?

The right output depends on the source and design intent. GO3D reviews the required regions, surface detail, target software and file format before agreeing a conversion approach. A mesh, a fitted surface and an editable CAD part serve different purposes.

What happens to my original files?

The service is scoped around preserving source files and delivering separately identified revisions. Repository access, output locations and retention are agreed for each project. This page does not read or upload your project files.

How does it fit my other GO3D tools?

Dragonfire / Dracarys is intended to support future GO3D workflows. Each connection must be built and checked before we say it works.

Dragonfire / Dracarys

Measure first.
Scale with the work.

Use the system you have. Add another only when a real job shows the limit.

Review the three steps