//dousen/main — for Jira + Perforce studios free studio beta
Dousen connects Jira, Perforce, your DCCs, and Unreal Engine. Artists publish from the DCC. Dousen validates the asset, imports it into Unreal, and moves the Jira ticket when the changelist is submitted.
Free during the studio beta, and free forever for teams of up to 5 users.
The log follows one asset from a Jira task to a submitted changelist. The changelist opens from the task, the checked instance is validated and exported, Unreal imports and saves it, and the Jira ticket moves when the changelist is submitted.
//dousen/features
Dousen runs when artists save, publish, or submit a changelist, and handles the changelists, validation, Unreal imports, and Jira updates around those steps.
on_save
The Dousen panel in Blender, Maya, 3ds Max, and Substance collects the publishable objects in your scene as instances. Check the ones you want and click Publish. Houdini publishes from shelf tools. In Blender, Maya, 3ds Max, and Substance Painter, turn on publish-on-save to publish the checked instances each time you save. It doesn’t run the full validation.
pre_export
Naming conventions and validators are set per project and per asset type in the web portal. A misnamed mesh or an unfrozen transform is caught in the DCC before export. In Maya and 3ds Max, Select Invalid selects the failing objects, and Repair fixes them where a validator supports it.
on_publish
The export (FBX, or textures from Substance) goes over the local bridge to the Unreal editor connected to the same project, or to a background import if no editor is open and headless import is on. Unreal imports it to the path your conventions define and saves it. Publish history in DousenDesktop shows each instance as imported, failed, or unconfirmed.
on_submit
Every changelist opens from a Jira task in DousenDesktop. File locks and checkouts show in the DCC’s Perforce tab. When you submit the changelist, Dousen runs the Jira transition configured for the project.
//dousen/product
DousenDesktop runs in the tray with your Jira tasks, changelists, and app launchers. The Dousen panel inside each DCC handles validation and publishing. Screenshots use a sample project.
//dousen/unreal
Dousen imports with Unreal’s Interchange framework. The import settings come from the project conventions and are saved with the asset, so a reimport replays them.
A profile in the project conventions sets mesh import options such as nanite,
collision, normals, tangents, import_lods, and
uniform_scale. Tag an instance with import_profile and Dousen imports it with
those settings.
On reimport, the existing members of a multi-mesh instance keep their asset paths and settings. New members aren’t imported until you approve them with Review instance topology in the Content Browser. Removed members stay in the project.
To use your conventions for manual imports too, install a project stack with the
Dousen.InstallImportStack console command. You can then select the stack in the Content
Browser import dialog. Installing a stack doesn’t change any Content Browser default.
//dousen/setup
Create the project, connect Jira and Perforce, and set the naming conventions and validators for each asset type. Run Dousen in the cloud or self-hosted.
Install DousenDesktop and run the setup wizard, then sign in. The wizard can create the Perforce workspace, find your DCCs, and check the Unreal project you select for the plugin. The DCC addons are bundled with the installer.
Publish one small instance and check that Unreal saved it. Then install DousenDesktop on the other workstations. Conventions and validators come from the server.
//dousen/docs
Instances, validation, Publish history, and retrying a failed publish.
Publishing guide → unreal / tech artImport profiles, reimport, Review instance topology, and project stacks.
Interchange guide → project adminsProject settings, conventions, validators, and deployment options.
Settings reference →//dousen/early-access
Dousen is in free beta for pilot studios, and stays free forever for teams of up to 5 users. Tell us about your team and the DCCs you run, or email [email protected], and we’ll set your studio up.