Playback & media servers · software
disguise Designer troubleshooting
The disguise Designer problems live-event techs bring to Ask Roadie most (also called d3, d3 Designer, disguise, gx). Pick your symptom, or describe your own in plain words, and get the likeliest fix first, with the manual page when there is one.
Common disguise Designer errors & problems
What techs run into most, and what's usually behind it. The step-by-step fix for your exact software is in Ask Roadie.
- Step-by-step fixGet the fix →
Ghost render processes left running after stopping a workload
Likely cause: Fixed in current Designer builds; clean shutdown of child render processes.
- Step-by-step fixGet the fix →
Spurious audio-device notifications fire on startup for installed ASIO/Dante drivers even with no hardware connected
Likely cause: The startup enumeration was treating installed-but-idle ASIO/Dante drivers as active devices; r33.1 only notifies on an actual mid-session disconnect of a device that was in use.
- Step-by-step fixGet the fix →
Experimental HDR output causes unexpected/incorrect display behaviour
Likely cause: The HDR options were never a supported feature and produced undefined display results; removing them in r33 prevents accidental use of the broken path.
- Step-by-step fixGet the fix →
RenderStream workload shows an INVALID scene and fails to load remote parameters when first detected
Likely cause: The first-detection race that left the scene marked INVALID and skipped remote-parameter load was fixed in r33, so parameters populate correctly on initial detection.
- Step-by-step fixGet the fix →
Projection masks do not update until you open display settings first
Likely cause: Mask geometry was only being re-evaluated when the display-settings view was opened; r33 updates masks on edit regardless of which view is active.
- Step-by-step fixGet the fix →
After upgrading a project to r33.1+, layers that were muted are unexpectedly Disabled
Likely cause: r33.1 narrowed the mute-to-Disabled conversion so it only applies to Locked-to-Director mutes, matching author intent and avoiding wrongly disabling Independent-mode mutes.
- Step-by-step fixGet the fix →
A Python API script that raises an exception leaves partial/half-applied changes in the project
Likely cause: r33 wraps script execution in a transaction-style rollback: any exception reverts the changes the script made, preventing partial mutations from persisting.
- Step-by-step fixGet the fix →
Understudy/failover not taking over when Director or Actor fails
Likely cause: Failover only works if roles are assigned and the project is distributed to the standby.
- Step-by-step fixGet the fix →
What does disguise Designer need to run (license/OS)?
Likely cause: DX11 dependency is why virtualised GPU environments fail.
- Step-by-step fixGet the fix →
Which media codec/settings for reliable playback on disguise?
Likely cause: GPU-decoded HAP scales for playback; Notch blocks stay real-time and parametric.
- Step-by-step fixGet the fix →
HDMI/SDI capture input shows a black screen
Likely cause: Colour-range handling and stable capture topology fixed the common black-capture cases.
- Step-by-step fixGet the fix →
How is DMX/timeline control distributed across networked machines?
Likely cause: d3Net is the sync backbone, so control need only reach the Director.
Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.
How Ask Roadie helps with the disguise Designer
- 1. Pick the disguise Designer. It's already in the list.
- 2. Describe what you're seeing. In your own words, or the error code off the screen.
- 3. Get the likeliest fix first. Steps in order, the manual page when there is one, and a note when other techs have confirmed it.
- 4. Still broken? Tap 👎 and it keeps going from where you left off.
Free trial
Get your disguise Designer back up before doors.
Try it free. No card required.
Start free trial →