Artists repeat the same setup on every asset
Automate naming, transforms, hierarchy, modifiers, materials, collections or export preparation.
Blender / Tools
Blender tools that remove repetitive content work before it reaches the engine.
Turn repeated modeling, cleanup, export, validation and content-preparation steps into focused Blender utilities that fit the existing production pipeline.
Problems we solve
DCC bottlenecks are expensive because they repeat across every asset.
The best Blender tool is usually not a giant framework. It is the smallest reliable utility that removes a recurring production cost.
Engine handoff is fragile
Standardize export data, object state and validation before content leaves Blender.
Large batches require manual cleanup
Process many assets consistently instead of repeating the same operation file by file.
A procedural workflow needs artist control
Wrap geometry or data operations in a practical UI instead of leaving them as one-off node experiments.
What we deliver
Production utilities sized to the workflow.
The scope can be a one-click script, a custom operator, a reusable add-on or a broader export/validation workflow.
Blender Python scripts
Focused operators and batch utilities for repetitive scene and asset operations.
Custom Blender add-ons
Panels, preferences, operators and project-specific tooling packaged for repeated team use.
Export & engine handoff tools
FBX or project-specific preparation, metadata, naming and validation around Unreal or Unity pipelines.
Procedural production helpers
Geometry Nodes support, rule-based content processing and controlled procedural workflows.
Technology context
Use Blender as a programmable production tool, not only a DCC.
Tooling can combine Blender Python, scene data, Geometry Nodes and engine-facing conventions without forcing the team into a separate application.
Blender Python API
Operators, panels, data access, batch processing and project-specific scene automation.
Geometry Nodes
Procedural generation and transformation workflows where node systems are the right production layer.
Unreal / Unity handoff
Export preparation, metadata and content conventions designed around the receiving realtime project.
Validation & batch processing
Checks and repeatable operations for larger asset sets before integration.
How the work runs
Automate the repeated cost, not the whole DCC.
01 Map the manual workflow
Identify the repeated actions, inputs, exceptions and expected output.
02 Define safe rules
Separate deterministic operations from cases that still need artist judgement.
03 Build the smallest useful tool
Implement the operator, panel or batch workflow around the real production task.
04 Validate the handoff
Test the output against the downstream engine or content pipeline instead of stopping at the Blender scene.
Relevant work
A Trueway-owned Blender product proves the tooling loop end to end.
SpriteOrbit is a Trueway Product: a real Blender extension with a defined user problem, documented workflow and explicit pre-release status.
SpriteOrbit — Trueway Product
Directional sprite baking, metadata, render passes and selective rebake are implemented as a maintained Blender product rather than a hypothetical tooling example.
View SpriteOrbitAuthority / parent capability
Blender tooling is one implementation layer inside Tools & Automation.
The owned product, the technical guide and custom client tooling each keep a distinct role.
Tools & Automation
The broader client-service capability for custom tools, validation, exporters and workflow automation.
Parent capabilityBlender to Unreal production pipeline
A technical guide covering transforms, pivots, data contracts, reimport and validation.
Read technical guideSpriteOrbit documentation
Exact product workflow and current format/compatibility boundaries.
Open documentationRelated services
Related content and automation services.
Tools & Automation
Broader production tooling across Unreal Engine, Unity, Blender and cross-tool workflows.
Tools & AutomationRealtime 3D / Interactive Visualization
Realtime content and environments when the problem is the interactive result rather than the tooling workflow.
Realtime 3DUnreal Engine Tools
Editor-side tooling after content reaches Unreal Engine.
Unreal Engine ToolsBlender to Unreal pipeline guide
A practical checklist for transforms, pivots, import, reimport and validation across the DCC-to-engine handoff.
Read pipeline guideFAQ
Blender tooling questions.
Can the scope be one small script?
Yes. A narrow utility is often the best solution when one repeated action is the actual bottleneck.
Can you package the tool as an add-on?
Yes. Reusable tools can be packaged with a panel, preferences and clear project-specific controls when that improves team adoption.
Can the tool prepare content for Unreal Engine?
Yes. Blender-side preparation, export metadata and validation can be designed around the Unreal project conventions that receive the content.
Start a project
Repeating the same Blender workflow across every asset?
Send the current manual steps, example input and the output the downstream pipeline expects.
Discuss a Blender tool
A short screen recording or step-by-step description is enough to identify whether a focused script or add-on is worthwhile.
Discuss this service