FILE / /Users/forgebot/.hermes/artifacts/studio-workloads/index.html
ForgeFX / Production Capacity Brief / 01 Oct 2026

A Production Workhorse,
Not Just a Bigger Chatbot.

The biggest gain is room to keep real scenes, source assets and production tools working together—and to run heavier local jobs while the Mini handles conversations.

16 → 256 GB16× unified-memory capacity
M4 → M5 Ultra10 → 30 CPU cores · 10 → 64 GPU cores
4 TB SSDOrdered storage for projects, caches and renders
Verified baseline: forgebot-mini is an M4, 16 GB machine. Adam’s order image specifies M5 Ultra, 30-core CPU, 64-core GPU, 256 GB memory and 4 TB storage. These are capacity/spec comparisons—not measured speedups. Most workflows below already exist; their practical scale changes.
Internal / Opportunities Grounded in Current Work

Where Departments Benefit

01 / ART & ENVIRONMENTS

More complete Unity scenes

Newly practical

Coal Valley / John Deere studies already run on the Mini. The Studio gives terrain, vegetation, textures, Editor and capture tools far more room together. Queue three controlled lighting/planting alternatives, render fixed cameras, then publish the actual Unity WebGL review.

More iterations without stripping the scene down just to work. Preserve original scenes; keep target-device texture and frame-time budgets. [1]

02 / TECHNICAL ART

CAD → simulator-ready assets

Newly practical

The Elite baseline contains 17.58M triangles and 24,180 objects. Hold larger source and derived assemblies in Blender; batch LOD generation, UV/texture repacking, normal-map bakes and multi-angle inspection. Halliburton specifically discussed repacking shared 4K atlases for reused DME parts.

More local batch preparation—not automatic retopology, rigging or correct valves. The raw CAD already imported; memory was not proven to be its only bottleneck. [3] [4]

03 / ENGINEERING & R&D

Unreal environment work beside Unity

Newly practical

ForgeIsland is already a proving ground for training-ground visuals and asset reuse. A larger machine makes native Unreal scene assembly, shader compilation, local cooking and short cinematic renders more practical while reference tools remain open.

Transfer meshes and textures, then rebuild engine-specific materials, wind and LOD behavior. Windows builds, plugins and headset validation still need their target environment. [2] [9]

04 / QA & PRODUCTION

Repeatable review batches

Newly practical

For Halliburton lesson/model changes and Kubota tablet work: import a candidate, run supported automated tests, capture fixed views and collect logs/frame times. Keep separate project copies and retain before/after evidence for human review.

Queue GPU-heavy work rather than promising unlimited parallel jobs. Mac smoke tests do not certify Windows, Android or headset performance. [4] [7]

05 / SALES & MARKETING

Real demo footage and larger edits

Newly practical

Build on the Light Rail 2030 creative work: assemble genuine simulator captures into 4K reels, render Blender turntables, add captions/voice tracks and export presentation/social variants with FFmpeg or licensed editing tools.

More room for footage, textures and render buffers; codec/media engines also matter. Cloud-generated video and Tripo jobs do not become faster merely because our Mac improves. [6] [8]

06 / CONTENT & LOCAL AI

A much larger local AI workspace

New capacity

Evaluate quantized 70B-class models for approved lesson drafts, technical-document comparison and code assistance; run local transcription or supported image tools. These models exceed the Mini’s practical memory budget but can fit comfortably in 256 GB with appropriate settings.

Model quality, context size and speed still need tests. Keep the existing cloud assistant; local execution is an optional tool, not an automatic replacement or a guarantee of privacy. [8]

External / Platform Reality

More Memory ≠ Every Feature

Unified memory is one fast pool shared by CPU and GPU. It is not 256 GB of exclusively reserved VRAM. My earlier “192 GB usable” figure was a rough default-limit estimate, not a verified M5 limit; measure the actual Metal working set on arrival.

Blender supports Apple GPU rendering through Metal. Epic’s UE 5.8 page lists Mac Nanite as beta and hardware Lumen/MegaLights as experimental. Validate our exact engine and plugins. Keep Windows for 3ds Max, Windows-specific builds and device integration. [9] [10]

Recommended First Use

Prove Three Production Wins

1. Repeat one Coal Valley scene import, fixed-camera capture and WebGL build on both machines.

2. Run the same CAD/texture preparation batch; compare peak memory, elapsed time and visual fidelity.

3. Export the same real 4K demo reel; compare time and responsiveness.

Reserve SSD space for caches and recovery. This Mini had only about 5 GB free when checked. Keep its messaging service separate; route bounded heavy jobs to the Studio. Same inputs and settings, saved outputs, human review.

Evidence, original order and research scope

Targeted research: live Slack project searches; two full Fireflies transcripts; ForgeCAD/Brandon project notes; Unity and Unreal production runbooks; local hardware inspection; Apple, Epic and Blender documentation. Recommendations are forecasts, not Studio benchmark results. No new image-generation jobs were needed. No commercial terms or raw transcripts are published here.

Internal

  1. Coal Valley: requested real-runtime studies
  2. ForgeIsland: Unreal → Unity training-ground reuse
  3. Elite CAD baseline: 17.58M triangles / 24,180 objects
  4. Halliburton production, Sep 29: full transcript; rigging ~11:32, atlas reuse ~16:22–17:36, QA ~7:08
  5. Dozer-engine reduction and original comparison
  6. Creative precedent: Light Rail 2030 artwork + motion clip
  7. Kubota WorkSmart production alignment: tablet delivery / branch consolidation

External

  1. Apple: M5 Studio specifications and media capabilities
  2. Epic: UE 5.8 macOS requirements / feature status
  3. Blender: Metal GPU rendering
Adam's supplied Mac Studio M5 Ultra order configuration

Original order image: Slack attachment. Live Mini check: system_profiler, October 1, 2026. Clock-dependent workload speeds remain unmeasured.