コンテンツにスキップ

Designer r32 Release Notes

このコンテンツはまだ日本語訳がありません。

Full (Pro) build: 231132
Starter build: 231133
Released: October 22nd 2025

  • DSOF-30801 - The GX 3+ now has partial IP-VFC card support for specific output formats. You can find these formats listed here.
  • DSOF-31321 - When a Video Clip has Frame Blending enabled and a non-zero Loop-In Frame, video playback now correctly loops back to the Loop-In Frame, not the first frame of the Video Clip.
  • DSOF-31313 - RenderStream receivers no longer send redundant network messages to other receivers, greatly reducing overall network traffic over d3net when running RenderStream with many actors.
  • DSOF-31376 - Changing the Video Clip of a Sockpuppet Video Layer when Brightness is 0 no longer starts playback automatically in the background. Instead, playback now starts only when Brightness is raised above 0.
  • DSOF-31352 - When a DMX signal is lost for more than 10 seconds, DMX event transport no longer reverts to 0, which could cause unexpected behaviour e.g. jumping back to CUE 0.
    • Triggering failover via DMX is also modified to now only work when the value is first set to 0 and then set to the configured value for failover triggering. e.g. if you need to send 20 for failover you will need to set the channel to 0, then 20. If you sent it from 0 to 10 and then to 20, Failover will not trigger.
  • DSOF-31305 - Creating new tracks no longer erroneously adds broken Cues to the track list.
  • DSOF-31265 - Sockpuppeted effects layers no longer duplicate the content source texture property in their personality on project restart. This restores behaviour before r31.0.
    • For customers with projects that have already experienced this problem, you can find instructions for how to reset your personalities to their defaults here.
  • DSOF-31234 - OSC drivers (used for e.g. tracking encoders) now support parsing messages without trailing slashes again.
  • DSOF-31283 - Setting the output mode to Hold no longer flickers between two frames, but outputs the last frame properly. This restores behaviour prior to r31.2.

Full (Pro) build: 229654
Starter build: 229655
Released: October 8th 2025

  • DSOF-31299 - Opening projects with many tags and cues is no longer very slow.
  • DSOF-31263 - All user-configurations of Sockpuppet properties (like custom names etc.) now persist properly through project restarts.
  • DSOF-31257 - Notch blocks without default values set in Notch now set sensible default values in Designer instead of failing to launch properly.
    • Enum values will select the 1st enum.
    • Numerical fields will select the mid value between the min and max.
    • Colours default to black with alpha 1.
  • DSOF-30807 - The api/session/sockpuppet/patches API now correctly only returns fields patched on the layer.
  • DSOF-31275 - DSE blending now works properly in all scenarios again.
  • DSOF-31022 - When run on Windows 11 Disguise servers, the Designer installer will now disable secure-boot in Windows Task Scheduler to stop SecureBootEncodeUEFI.exe from taking focus.
  • DSOF-31318 - The Designer installer now warns if it detects UE5 and TouchDesigner running in addition to Unity and UE4.
  • DSOF-30298 - Switching Colour space from OCIO back to Gamma after setting OCIO parameters no longer results in console spam.

Full (Pro) build: 229072
Starter build: 229073
Released: September 26th 2025

r32.0.2 includes all the same features as r32.0 but now also correctly includes the fixes in r31.3.4

r32.0.1 has been removed. User r32.0.2 instead.
Section titled “r32.0.1 has been removed. User r32.0.2 instead.”

Full (Pro) build: 228975
Starter build: 228976
Released: September 25th 2025

No improvements here. This was a mistake release. Please update to r32.0.2.

Download for r32.0 has been removed. Use r32.0.1 instead.
Section titled “Download for r32.0 has been removed. Use r32.0.1 instead.”

Full (Pro) build: 228570
Starter build: 228571
Released: September 24th 2025

r32.0 supports the latest Disguise server type: the GX 3+. Full hardware specifications and further details are coming soon. You can find our initial (and eventually full) documentation here.

  • DSOF-29129 - CodeMeter Runtime included in the Designer installer has been updated to v8.40. This change supports Notch blocks exported in Notch 1.0.0.041 and newer.
  • DSOF-30897 - Under light workloads, video inputs used in video layers are now delayed by one frame to ensure smooth video playback. This functionality can be disabled by setting the option switch smoothVideoInputFramesDelay to -1. This does not affect XR workflows.
  • DSOF-30716 - Designer now supports a new API session endpoint api/session/transport/transports, which lists all the MultiTransports and normal Transports in a single response. For more details, please refer to the Developer Documentation.
  • DSOF-30718 - Users can now monitor the ongoing statuses of their Media Provisioning Tasks by subscribing to the Task Status API. For more details, please refer to the Developer Documentation.
  • DSOF-30874 - In a 2.5D layer, the boolean field “Sync To Timeline” is now renamed to “Mode”. The two available options are “Normal” and “Locked”. This makes it consistent with other layers in Designer.
  • DSOF-29074 - The default point cloud visualisation mode for Omnical is now “ProjectorReprojError” instead of “Tolerance”, as it is more useful for users.
  • DSOF-31086 - Designer now has a new Python object SequencedValue, which can be obtained through the new Python method FieldSequence.getSequencedValue(). This object contains information about the sequenced value at a given time, and its neighbouring left and right keyframes. For more details, please refer to the Developer Documentation.
  • DSOF-31180 - Designer now has new Python methods for the VideoClip class: hasAudio(), enabledVersion, proxyInfo. For more details, please refer to the Developer Documentation.
  • DSOF-26511 - The buttons in the Media Ingestion History widget now have more descriptive and useful tooltips.
  • DSOF-31055 - The Layer.module field accessible in the python API is now restricted so it cannot be accessed directly by plugin developers. This is because it doesn’t behave the way people expect and is not required for plugins.