//dousen/main — built for Jira + Perforce studios

The automation framework
for game assets.

Dousen sits between Jira, Perforce, and every DCC in your studio. Changelists open themselves, tickets transition themselves, and assets land in Unreal with the right name, in the right folder.

pipeline.log live
09:41:07blenderfile.saveSM_Crate_01.blend
09:41:07dousenvalidatenaming   scale   materials
09:41:08dousenexportSM_Crate_01.fbx → //depot/props/
09:41:08perforcechangelistCL 28471 opened against DOU-142
09:41:08jiratransitionDOU-142  To Do → In Progress
09:41:11unrealreimport/Game/Props/SM_Crate_01

One save. The artist never left Blender.

ships with addons for
blender maya houdini 3ds_max substance_painter substance_designer unreal_engine_5

Four hooks. The whole pipeline.

Dousen listens to the events your artists already produce — saves, exports, submits — and does the bookkeeping nobody wants to do by hand.

on_save

Every DCC, one bridge

Blender, Maya, Houdini, 3ds Max, Substance Painter, Substance Designer, and Unreal all talk to a local relay on the artist's machine. An export in one app is an event in every other — no watch folders, no "did you reimport?" messages.

blender → bridge:8766 → unreal  3s later

pre_export

Validation before it ships

Naming conventions and validators are defined once, in YAML, per project and per asset type. A misnamed mesh or a wrong-scale export gets caught inside the DCC — not three days later in review.

SM_{asset}_{variant} → SM_Crate_01

on_submit

Perforce and Jira, in lockstep

Every changelist is opened against a ticket. Submit the CL and the ticket transitions itself. File locks, checkouts, and stream info show up right inside the DCC, so nobody stomps anyone's work.

CL 28471 ↔ DOU-142 → In Progress

on_publish

Assets land in Unreal

Published meshes, textures, and animations reimport automatically into the correct content browser path. Right-click any asset in Unreal to open its source file in the DCC that made it.

SM_Crate_01.fbx → /Game/Props/SM_Crate_01

Set up once. Ship forever.

01

Connect your tools

Point Dousen at your Jira project and Perforce server. Install the desktop app and DCC addons. A setup wizard walks you through — done in under 15 minutes.

02

Artists work as normal

Nobody learns a new tool. Dousen runs in the tray — routing events between DCCs, syncing changelists with Jira, and showing file lock status where artists are already looking.

03

Review and ship

Full traceability from Jira ticket to Perforce CL to Unreal asset. Validation history, asset versioning, and a web portal for project admins.

blender
maya
houdini
3ds max
substance
dousen bridge

local relay :8766 — validation · routing · publish

perforce
jira
unreal

CL open/submit · ticket sync · auto-reimport

Put it in front of your artists.

Dousen is in free beta for pilot studios. Tell us about your team and which DCCs you run — or email [email protected] directly — and we'll have your studio set up this week.