Transform agreement
Compare position, scale, rotation and pivots against known source-scene fixtures.
← SERVICES / ENGAGEMENTS3ds Max → UnrealDiscuss a similar project ↗
WINNITUDE! / ENGAGEMENTCONTENT TRANSFER / PRODUCTION TOOLS
3ds Max → Unreal content pipelines.
A content-transfer pipeline that connects authoring in 3ds Max with production in Unreal: assets, instances, transforms and conventions carried through a repeatable process.
FOR GAME & VISUALIZATION TEAMSFOCUS / TOOLS & WORKFLOWSDELIVERY / PRODUCTION TOOLS & HANDOFF
01PREPARE
Agree on units, naming, pivot and material conventions. Inspect the source scene before export.
→02EXPORT
Separate reusable assets from their placements. Record source identity and a manifest for the next stage.
→03VALIDATE
Report missing materials, invalid transforms, naming collisions and unsupported scene content.
→04INGEST
Import assets, reconstruct placements and apply the agreed engine conventions.
→05REVIEW
Compare representative scenes and test reimport before handing the workflow to production.
Make the scene contract explicit.
A scene is more than its meshes. Units, pivots, object names, material slots, repeated instances and collision conventions all affect whether an engine import is useful. Manual export can move the geometry while leaving the production context behind.
BEFORE DATASMITH
A production need before the standard route existed.
This Max → Unreal pipeline work predated Datasmith. The task was already familiar: move a structured source scene into Unreal while retaining the transforms, reusable assets and material relationships a team needed to keep working.
OUR APPROACH
The workflow begins with agreed export conventions and a validation pass in the source scene. Exported assets and placements retain a mapping into an engine-facing manifest. Unreal ingestion applies the agreed transforms and material relationships, while exceptions stay visible for an artist or technical artist to resolve.
Make the next step
a repeatable one.
Materials & references
Check material-slot mapping, unresolved textures and object-reference failures.
Safe iteration
Review how reimport treats existing assets, authored overrides and removed source objects.
If your team needs to move content between applications, modernize an exporter or preserve production conventions across tools, we can build around the actual source data and target workflow.
A workflow the team can own.
WHAT WE CAN DELIVER
Exporter/importer tools, a documented scene contract, readable validation output, representative scenes and an operator walkthrough. Production-specific integrations and acceptance gates are agreed as part of the engagement.
Start with the work you need done.
Bring a representative scene, the applications involved and the step that keeps slowing your team down. We’ll discuss constraints, acceptance criteria and a useful first milestone.
Discuss a related pipeline ↗