When working with content in Dreem, you can build complete Outfits by combining primary and secondary products from your Creative Force catalog. In this article, we will walk through how to get started and deep dive into the functionality.
Feature Overview
The Dreem Connector supports flexible Outfit creation— whether you build Outfits in Creative Force before the Dreem step, modify them within Dreem, or create them from scratch using Dreem's product browser.
📘 Prerequisites: This article assumes you have already enabled the Dreem Connector and added Dreem to a Generative Workflow. For general setup and functionality information, please see the main Dreem Connector article.
All Outfit data automatically syncs between Creative Force and Dreem, ensuring your production records stay accurate and up-to-date.
Use-Case Scenarios
The Dreem Connector currently supports three outfit-building scenarios:
Scenario | Workflow | Description |
Pre-Built Outfits | CF → Dreem | Build complete outfits in Creative Force that are sent to Dreem as is. |
Pre-Built with Modifications | CF ↔ Dreem | Build outfits in Creative Force, then modify them in Dreem with changes syncing back automatically. |
Build from Scratch (Coming soon) | Dreem → CF | Create new outfits entirely in Dreem using your Creative Force product catalog, then sync back to Creative Force. |
Outfits in Creative Force
Before your task reaches Dreem via the Cloud Automation step in your Workflow, you can pre-build outfits in Creative Force.
For an in-depth look at creating Outfits in Creative Force, please see our dedicated article on the subject by following the link below.
Sync Outfits in Dreem
When a task with a pre-built Outfit reaches the Cloud Automation step associated with Dreem, Creative Force automatically sends and displays associated secondary products in the Styling panel of the Virtual Model Dreem Session.
Editing Outfits
If an Outfit was created in Creative Force, you can modify it within Dreem. Select the Outfit Builder pop-out option to enter a full-screen view where you can change out styling pieces as desired.
Removing Products
Remove any secondary product from the Outfit composition by hovering over it and selecting the trash icon.
🔄 Sync Behavior: Products removed in Dreem are removed from the Outfit in Creative Force.
Dreem Wardrobe Items
In addition to the Creative Force Product Catalog, you will have the option to select styling items from the Dreem Wardrobe to generate your content.
🔄 Sync Behavior: Dreem wardrobe items are Dreem-only and do not sync back to Outfit data in Creative Force.
Adding Products + Product Catalog (Coming Soon)
In a future update, studios will be able to search the Creative Force Product Catalog for existing secondary products and add them freely to Outfits created in Dreem.
Troubleshooting
In this section, we will cover a few potential pain points when interacting with Outfits between Creative Force and Dreem. If you are experiencing issues, please review the recommended troubleshooting below.
Potential Issues
Issue | Solution |
Can't find a Product when searching in Dreem. | Please ensure that the associated Product:
|
Images aren't showing for a Secondary Product in Dreem | Check that the Secondary Product has:
|
Outfit edits in Dreem didn't sync back to Creative Force | Please verify that:
|
Expected Behavior
Behavior | Logic |
An item in the output was replaced with an earlier/later added secondary product. | This is expected behavior. If a CF Outfit is modified between the time it was first pushed to Dreem and the time Dreem syncs back, Dreem's version overwrites the CF outfit.
Users may occasionally see CF Outfit data "replaced" when this occurs. |
Multiple Outfits merged unexpectedly in Creative Force | This is expected behavior. For more information on how this works, please see the section on Multi-Outfit Handling. |
The Styling Display Image for a Product in Dreem is different from what was expected. | This is expected behavior. For more information on how this works, please see the section on Styling Assets Resolution Rule. |
If your issue persists after reviewing the recommended troubleshooting, please reach out to the Creative Force Support Team directly.
Technical Logic
In the section below, we will detail more complex logic related to Outfits in Dreem.
Multi-Outfit Handling
When multiple Outfit variations are created in Dreem across different images, they merge into one consolidated Outfit in Creative Force.
In Dreem, different images within the same session may use different Outfit combinations (e.g., Image 1 uses Outfit A, Image 2 uses Outfit B).
In Creative Force, when the Session completes, all Outfits are merged into a single consolidated Outfit on the Creative Force side.
The merged Outfit contains all unique Product IDs used across all Dreem Outfits.
Example:
Dreem Image 1: Primary Product + Secondary Products A, B, C
Dreem Image 2: Primary Product + Secondary Products B, C, D
CF Outfit after sync: Primary Product + Secondary Products A, B, C, D
Asset Resolution Rule
When Creative Force sends Secondary Product images to Dreem, it follows a specific resolution rule to determine which images to provide. First, it decides on a Work Unit (Production), then it selects assets from specific Photography Positions.
Work Unit Priority
For each Secondary Product, Creative Force selects images from work units based on a fixed priority logic related to the Production Type Category. In the table below, 1 is the highest priority, and 4 is the lowest.
Priority | Production Type Category |
1 | Mannequin |
2 | Flat |
3 | Any other non-On Model |
4 | On Model |
For cases with competing priorities, images will be retrieved from the last completed task in the selected work unit.
Asset Selection
Within that work unit, Dreem attempts to pull two images: one each from photo positions named "Front" and "Back" if they exist.
If there are no photo positions containing these names, they will default to pulling from the first two available positions.
If "Front" and "Back" positions exist: First 2 normal assets from each position.
If "Front" and "Back" positions don't exist: First 2 normal assets from any available positions
Fallback: If no output assets are available, the product cover image is sent