GO3D processing
Cloud when you need it.
Dragon Fire when it is connected.
The cloud coordinates the work. Your MSI Titan 18 HX can run a separate local worker for supported jobs, then return versioned results to the project. The existing Dragonfire worker is reused; connection and workload checks come first.
Dragonfire worker v0.3.0 supports mesh.inspect.v1: CPU-based STL/OBJ mesh inspection. The MSI is not verified as paired with this Builder. GPU reconstruction, HDR processing and automatic Drive mirroring are not active capabilities here.
MSI Titan 18 HX · Norse Myth · 6 TB storage is the owner-reported machine configuration. GPU model, free space, engine versions and measured throughput still require an on-device check.
Worker package: 34,532 bytes · SHA-256 a571d55cd6f7ad99cb42e83877069e71ae459f8e2d408eff7f0902afa89b8b22. The console requires GO3D operator access; this is not a public job-submission link.
Connect the existing worker
- Open GO3D’s existing Dragonfire setup on the MSI and use its current worker package and pairing flow.
- Verify the reported machine, allowed workspace folder and worker version.
- Run the small supported mesh-inspection test first. Compare the exact input and returned report hashes.
- Enable additional scan or HDR engines only after their installation, licensing, workload and output checks are complete.
Pairing does not move ChatGPT or its models onto the laptop. It connects a separate processing worker to the cloud workflow.
Return results without losing the source
- Keep the original scan, images and CAD in the established Drive project.
- Identify each job by source checksum, settings, branch and revision.
- Return the result, processing log and checksums as a new versioned package.
- Verify the upload by reading it back before marking a Drive mirror complete.
The Builder does not yet perform this local-worker-to-Drive route automatically. A saved route request is a draft, not evidence that a job ran or a backup completed.
On the MSI
Extract the package and open a terminal in its folder. Python 3.10 or later is required.
python -m dragonfire_worker doctor python -m dragonfire_worker status
The first command checks basic readiness. The second checks an existing registration without starting work. For initial pairing, copy the command and enter the private one-time code shown by the signed-in console.
python -m dragonfire_worker run --once
Run only after the intended source job is explicitly authorized in the console. No service or startup task is installed.
Inspect a local file first
python -m dragonfire_worker inspect model.stl --output new-inspection.json
This supported offline operation streams the source without editing it. Use a new output filename. It produces counts, coordinate bounds and a source hash; topology and engineering accuracy are not evaluated.
Hosted pilot inputs are limited to 32 MiB. Offline inspection defaults to a 4 GiB byte limit. Neither mode accelerates arbitrary CAD or HDR applications.
Choose a route or compare actual runs
Open Processing inside Bill Builder to save a request tied to the active source and design branch. A route request is a plan for the existing operator workflow; the worker cannot execute it as a job file. The comparison below can record timings you obtained from the same input and settings.