solidworks-to-blender-pipeline

Use when converting SolidWorks .sldprt/.sldasm geometry to Blender for rendering, animation, or visualization, including questions about STEP export settings, FreeCAD as a bridge, or which mesh format (STL/OBJ/GLTF) to choose.

5 stars

Best use case

solidworks-to-blender-pipeline is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when converting SolidWorks .sldprt/.sldasm geometry to Blender for rendering, animation, or visualization, including questions about STEP export settings, FreeCAD as a bridge, or which mesh format (STL/OBJ/GLTF) to choose.

Teams using solidworks-to-blender-pipeline should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/solidworks-to-blender-pipeline/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.claude/skills/engineering/cad/solidworks-to-blender-pipeline/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/solidworks-to-blender-pipeline/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How solidworks-to-blender-pipeline Compares

Feature / Agentsolidworks-to-blender-pipelineStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when converting SolidWorks .sldprt/.sldasm geometry to Blender for rendering, animation, or visualization, including questions about STEP export settings, FreeCAD as a bridge, or which mesh format (STL/OBJ/GLTF) to choose.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# SolidWorks → Blender Pipeline

## Overview

No FOSS tool natively parses `.sldprt` / `.sldasm` — Dassault keeps the format proprietary. The reliable pipeline goes through an interchange format (**STEP** preferred, IGES fallback) and optionally **FreeCAD** as a cleanup bridge before Blender.

Core principle: **STEP is the contract.** Treat the SolidWorks-side STEP export as the only durable surface — everything downstream re-derives from it.

## When to Use

- Importing mechanical CAD into Blender for rendering, animation, or marketing visuals
- Choosing between STL / OBJ / GLTF for a Blender-bound asset
- Deciding whether to add FreeCAD as an intermediate (yes, if geometry needs cleanup or assemblies need to be preserved)
- Picking SolidWorks STEP export flags
- Evaluating direct `.sldprt` readers (short answer: only commercial/partial — Fusion personal, MoI3D, CAD Exchanger, Okino PolyTrans)

Don't use when:
- You only need a print-ready mesh → go straight to STL (no Blender)
- You're staying inside the FreeCAD ecosystem → see `../freecad-automation/SKILL.md`
- You're rendering pre-existing Blender scenes → see `../blender/SKILL.md`

## Decision matrix — pipeline by use case

| Use case | Pipeline | Why |
|---|---|---|
| Rendering / animation | `SW → STEP → FreeCAD → GLTF → Blender` | GLTF preserves hierarchy + materials |
| 3D printing | `SW → STL` | Mesh-only, no need for Blender |
| Game assets | `SW → STEP → Blender (retopo)` | Quads needed, original solids discarded |
| Fully FOSS workflow | `FreeCAD + Blender` (no SW step) | Avoid the proprietary format entirely |
| Quick geometry check / repair | `SW → STEP → CAD Assistant` | Lightweight viewer, exports STL/OBJ |

## Recommended export settings (SolidWorks side)

Export as **STEP AP242 Binary** with the following enabled:
- Curves
- Assembly structure
- Colors

Rationale: AP242 is the modern PMI-bearing flavor; binary halves file size vs ASCII; the three flags above are commonly off by default and silently drop information Blender can otherwise show.

## FreeCAD bridge (when to use it)

Add FreeCAD between SolidWorks and Blender when any of:
- Assembly hierarchy must survive (FreeCAD preserves it better than Blender's STEP importer)
- Topology needs cleaning before tessellation
- You want fine control over mesh density per body
- You need a Python automation step (FreeCAD's `Part` + `Mesh` modules)

Inside FreeCAD: `Mesh → Mesh from shape → Fine tessellation → Export GLTF`.

GLTF beats STL for Blender because it preserves hierarchy, materials, and is smaller. STL still wins when the next consumer is a 3D printer or analysis mesher.

## Tool inventory

**Open-source (recommended):**
- **FreeCAD** — bridge of choice; cross-link `../freecad-automation/SKILL.md`
- **Blender + add-ons** — STEPper, CAD Sketcher, BlenderBIM, OCC/STEP importers. Note: imported solids become polygon meshes; assemblies may flatten; constraints/features/history are lost
- **CAD Assistant** — lightweight STEP viewer + STL/OBJ exporter (not a full editor)

**Commercial-ish (the only paths that read `.sldprt` more directly):**
- Autodesk Fusion personal edition
- MoI3D
- CAD Exchanger
- Okino PolyTrans

**The open-source reality:** even the FOSS tools above rely on STEP / Parasolid export from a SolidWorks seat. There is no robust direct-read path; if you don't have a SolidWorks license to export from, you need someone who does.

## Common mistakes

| Mistake | Fix |
|---|---|
| Exporting STEP AP203 by default | Switch to AP242 — AP203 drops colors and PMI |
| Choosing STL for a Blender render | Use GLTF; STL is mesh-only and strips materials |
| Skipping FreeCAD when assembly hierarchy matters | Run STEP through FreeCAD first — Blender flattens assemblies more aggressively |
| Tessellating coarsely | FreeCAD's "fine" tessellation is the floor for renders; bump deviation lower for hero shots |
| Treating direct `.sldprt` readers as drop-in | All are partial — geometry yes, features/history no |

## Related skills

- [blender](../blender/SKILL.md) — once geometry is in Blender, the bpy/CLI side
- [freecad-automation](../freecad-automation/SKILL.md) — scripting the FreeCAD intermediate step
- [gmsh-meshing](../gmsh-meshing/SKILL.md) — when the destination is FEM/CFD, not render
- [pyvista-3d](../pyvista-3d/SKILL.md) — alternative visualization path without Blender

## References

- FreeCAD: https://www.freecad.org/
- Blender: https://www.blender.org/
- STEP AP242 overview: https://www.iso.org/standard/66654.html

## Version history

- **1.0.0** (2026-05-10): Initial reference. Source: external ChatGPT consult on SolidWorks→Blender FOSS workflow; cross-referenced against existing `blender` and `freecad-automation` skills.

Related Skills

teams-meeting-pipeline

5
from vamseeachanta/workspace-hub

Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.

blender-worktree-test-hardening

5
from vamseeachanta/workspace-hub

Recover and harden digitalmodel Blender automation work in isolated worktrees when uv/editable dependency paths break and local machines lack a Blender executable.

multi-role-agent-contract-review-pipeline

5
from vamseeachanta/workspace-hub

Execute a 4-role agent team (Planner/Architect/Reviewer/Integrator) pipeline for self-reviewing knowledge artifacts before delivery

gtm-prospect-pipeline-phased-execution

5
from vamseeachanta/workspace-hub

Phased execution pattern for

nextflow-pipelines

5
from vamseeachanta/workspace-hub

Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data for gene expression, variant calling, and chromatin accessibility analyses.

blender-interface

5
from vamseeachanta/workspace-hub

AI interface skill for Blender 3D — headless CLI execution, Python bpy API, mesh import/export, rendering, and integration with engineering analysis workflows.

data-pipeline-processor

5
from vamseeachanta/workspace-hub

Process data files through transformation pipelines with validation, cleaning, and export. Use for CSV/Excel/JSON data processing, encoding handling, batch operations, and data transformation workflows.

knowledge-pipeline

5
from vamseeachanta/workspace-hub

Workflow for maintaining workspace-hub knowledge and learning pipelines across scripts/knowledge, scripts/learning, and docs/superpowers, including indexing, archive synthesis, issue updates, and pipeline troubleshooting.

document-rag-pipeline

5
from vamseeachanta/workspace-hub

Build complete document knowledge bases with PDF text extraction, OCR for scanned documents, vector embeddings, and semantic search. Use this for creating searchable document libraries from folders of PDFs, technical standards, or any document collection.

document-index-pipeline

5
from vamseeachanta/workspace-hub

Orchestrate the 7-phase document indexing pipeline (A→G) for the 1M+ document corpus. Use when running batch extraction, classification, or gap analysis on og_standards, ace_standards, or workspace_spec sources.

continuous-planning-pipeline

5
from vamseeachanta/workspace-hub

Maintain a standing day/night GitHub issue pipeline so agents always have planned, reviewed, user-approved work for overnight execution and next-day QA/approval.

nextflow-pipelines-workflow-checklist

5
from vamseeachanta/workspace-hub

Sub-skill of nextflow-pipelines: Workflow Checklist.