Migrating existing Motion Design projects

Outline:

1. Main level:

   1. Replace ControlPxMotionDesign with ControlMotionDesign

   2. Type Channel_1 in Details > Control > Playback channel

   3. Add all levels that were streamed into MD_Collection into the Details > Levels array in the ControlMotionDesign actor

2. MD_Collection can be removed from the project

3. Make sure the right Rendering Mode is selected. It is possible that the 2D Mode will provide better rendering results to the existing project

4. Template Builder is not available anymore.

   1. Each level will be one template.

   2. The name of the template will be the name of the level.

   3. The “Mark as template” option in the Motion Design Outliner does not exist anymore. A level will be a template imported in Erizos if it is added in the step 1. c. above.

5. In each of the templates (levels), the Remote Control window will present the exposed properties with the same IDs as they were set in Template Builder.

   1. Erizos Studio still supports this workflow where only properties are exposed, without Controllers, and the values for the properties are set directly from the rundown.

   2. However, the Controller workflow is also available and the user is free to use this instead. Please note that once you add at least one Controller to the scene, Erizos Studio will switch to Controller-driven templates and only import Controllers, not exposed properties.

6. From 25.3, Motion Design levels will NOT spawn a PixotopeTrackedCamera by default. If this was used as the main camera, a new AvaCineCameraActor must be added instead. You can easily do this by pressing the Create Defaults button on the bar on top of the viewport and only checking the Cine Camera option.

   

   1. Once the actor is added, make sure it has the right Horizontal FOV by setting the correct Focal length values in the Details panel