3ds Max - Integrated Submitter Workflow - Phoenix FD Simulation

Phoenix FD Simulation Workflow Overview

../_images/max_workflow_phoenixfd.png

The Phoenix FD Simulation workflow lets you submit one or more Phoenix FD grids for simulation on Deadline.

Accessing The Workflow

  • This workflow will only be accessible in SMTD if the Chaos Group Phoenix FD plugin has been installed on the workstation.

  • To use the workflow, select the Submit PHOENIX FD SIMULATIONS To Deadline entry from the Workflow: drop-down list on top of the SMTD UI.

User Interface

  • The Phoenix FD Simulation workflow adds a Phoenix FD Job tab

    • It contains a custom Phoenix FD Simulations rollout

    • It features a custom Phoenix FD Job Options rollout with a reduced number of controls compared to the standard Job Options rollout.

    • It also features the standard Job Failure Detection rollout with no changes.

  • The standard Assets, Render, Options and Limits tabs will also be available with most of their default content.

    • The Render tab only features the relevant Scene Tweaks and 3ds Max Startup rollouts.

Submit Button Behavior

  • The SUBMIT button of SMTD will be disabled if

    • No Phoenix FD objects have been found in the scene

    • Phoenix FD objects have been found, but none of them has been checked in the list.

    • At least one of the Phoenix FD simulators has a path rooted at C:\ and the Use Cache Output Directory Override checkbox is unchecked.

Custom User Interface Controls

Check All button

  • Pressing this button will check all Phoenix FD simulators on the list.

Invert button

  • Pressing this button will check the unchecked and uncheck the checked Phoenix FD simulators on the list.

Update FumeFX Objects From The Scene… button

  • Pressing this button will refresh the content of the list.

Phoenix FD Object listView

  • Shows a list of all Phoenix FD simulators in the current scene.

  • Each object will have a corresponding checkbox to control whether it will be included in the submission or not.

  • The second column will show the simulation type of the object, which also controls the color coding of the list

    • FireSmokeSim - red color

    • LiquidSim - blue color

    • PHXSimulator - green color

  • A third column shows the Output path of each Phoenix FD simulator

Simulation Cache Output Directory Override text field and button

  • The text field provides an optional cache path override.

  • Press the […] button to the right of the field to open a directory browser.

  • You can also paste or type and enter a valid path directly into the text field.

Use Cache Output Directory Override

  • Default is unchecked.

  • When checked, and if the override path is valid, the simulation paths of all Phoenix FD simulators will be repathed to the override path folder.

  • This is useful when the original paths are pointing at a local storage not accessible to the Deadline Workers.

Make Directory Override Changes Permanent

  • Default is unchecked.

  • When checked, and only if Use Cache Output Directory Override is checked and a job is submitted, the simulation paths will not be restored after submission.

    • This would allow the current 3ds Max scene to access the simulation data from the location where Deadline will write it to.

Simulation Details

  • The 3ds Max scene will always be saved and submitted with the job, regardless of the relevant SMTD control.

  • Each Task in the Phoenix FD Simulation job will process one Phoenix FD simulator.

  • In other words, the number of Tasks will be equal to the number of Phoenix FD objects checked for submission on the list.

Workflow Script Files

This workflow consists of two script files:

  • SMTDWorkflow_PhoenixFD.ms - the workflow definition

  • MAXScriptJob_SimulatePhoenixFD.ms - the MAXScript Job file to be run by the Workers to perform the actual simulation.