Guides for game art pipelines with Perforce, Jira and Unreal

By Luca Vitiello · Updated 6 October 2026

These guides show how game art teams use Dousen with Perforce, Jira Cloud and Unreal Engine 5.7 and 5.8: checking out and locking files from Blender, Maya, 3ds Max, Houdini and Substance, keeping one changelist per Jira task, naming Unreal assets, and checking an FBX before import.

One changelist per Jira task One Perforce changelist per Jira task, with the issue moved on submit Unreal Engine asset naming conventions Prefix reference for Unreal Engine assets and how to enforce it Validate an FBX before Unreal import What to check in an FBX before Unreal imports it Perforce in Blender Check out, lock, sync and submit from the Dousen sidebar Perforce in Maya Check out, lock, sync and submit from the Dousen panel Perforce in 3ds Max Check out, lock, sync and submit from the Dousen panel Perforce in Houdini What the Dousen shelf tools do for Perforce, and what they don't Perforce in Substance Painter and Designer Check out, lock, sync and submit from the Dousen dock

Dousen is free during the studio beta, with access by request, and free forever for teams of up to 5 users. Request early access.