Updated Unreal publish icons and descriptions

Author: ryanmayeda

env/includes/settings/tk-multi-publish2.yml

@@ -160,7 +160,7 @@ settings.tk-multi-publish2.mari.asset_step:
 
 # asset step
 settings.tk-multi-publish2.maya.asset_step:
-  collector: "{self}/collector.py:{engine}/tk-multi-publish2/basic/collector.py"
+  collector: "{self}/collector.py:{config}/tk-multi-publish2/tk-maya/basic/collector.py"
   collector_settings:
       Work Template: maya_asset_work
   publish_plugins:
@@ -182,7 +182,7 @@ settings.tk-multi-publish2.maya.asset_step:
     settings:
         Work Template: maya_asset_fbx_export
         Publish Template: maya_asset_fbx_publish
-  - name: Render Turntable in UE4
+  - name: Publish and Submit for Review
     hook: "{self}/publish_file.py:{config}/tk-multi-publish2/tk-maya/basic/publish_turntable.py"
     settings:
         Work Template: maya_ue4_turntable_render
@@ -416,11 +416,11 @@ settings.tk-multi-publish2.unreal.project:
   - name: Publish to Shotgun
     hook: "{self}/publish_file.py:{engine}/tk-multi-publish2/basic/publish_session.py"
     settings: {}
-  - name: Publish to Shotgun
+  - name: Export FBX and Publish to Shotgun
     hook: "{self}/publish_file.py:{engine}/tk-multi-publish2/basic/publish_asset.py"
     settings:
         Publish Template: unreal_asset_publish
-  - name: Publish to Shotgun
+  - name: Render Movie and Submit for Review
     hook: "{self}/publish_file.py:{engine}/tk-multi-publish2/basic/publish_movie.py"
     settings:
         Work Template: unreal_movie_render

hooks/tk-multi-publish2/tk-maya/basic/collector.py

@@ -159,14 +159,32 @@ def collect_current_maya_session(self, settings, parent_item):
             fbx_display_name
         )
 
+        # get the icon path to display for this item
+        icon_path = os.path.join(
+            self.disk_location,
+            os.pardir,
+            "icons",
+            "fbx.png"
+        )
+
         fbx_item.set_icon_from_path(icon_path)
 
         # Add an Unreal turntable render item
         turntable_item = session_item.create_item(
             "maya.turntable",
-            "Unreal turntable render",
-            filename + " turntable"
+            "Turntable",
+            "Render Asset Turntable in Unreal"
         )
+
+        # get the icon path to display for this item
+        icon_path = os.path.join(
+            self.disk_location,
+            os.pardir,
+            "icons",
+            "unreal.png"
+        )
+
+        turntable_item.set_icon_from_path(icon_path)
 
         # discover the project root which helps in discovery of other
         # publishable items

hooks/tk-multi-publish2/tk-maya/basic/publish_fbx.py

@@ -40,50 +40,11 @@ def description(self):
         loader_url = "https://support.shotgunsoftware.com/hc/en-us/articles/219033078"
 
         return """
-        Publishes the file to Shotgun. A <b>Publish</b> entry will be
-        created in Shotgun which will include a reference to the file's current
-        path on disk. If a publish template is configured, a copy of the
-        current session will be copied to the publish template path which
-        will be the file that is published. Other users will be able to access
-        the published file via the <b><a href='%s'>Loader</a></b> so long as
-        they have access to the file's location on disk.
-
-        If the session has not been saved, validation will fail and a button
-        will be provided in the logging output to save the file.
-
-        <h3>File versioning</h3>
-        If the filename contains a version number, the process will bump the
-        file to the next version after publishing.
-
-        The <code>version</code> field of the resulting <b>Publish</b> in
-        Shotgun will also reflect the version number identified in the filename.
-        The basic worklfow recognizes the following version formats by default:
-
-        <ul>
-        <li><code>filename.v###.ext</code></li>
-        <li><code>filename_v###.ext</code></li>
-        <li><code>filename-v###.ext</code></li>
-        </ul>
-
-        After publishing, if a version number is detected in the work file, the
-        work file will automatically be saved to the next incremental version
-        number. For example, <code>filename.v001.ext</code> will be published
-        and copied to <code>filename.v002.ext</code>
-
-        If the next incremental version of the file already exists on disk, the
-        validation step will produce a warning, and a button will be provided in
-        the logging output which will allow saving the session to the next
-        available version number prior to publishing.
-
-        <br><br><i>NOTE: any amount of version number padding is supported. for
-        non-template based workflows.</i>
-
-        <h3>Overwriting an existing publish</h3>
-        In non-template workflows, a file can be published multiple times,
-        however only the most recent publish will be available to other users.
-        Warnings will be provided during validation if there are previous
-        publishes.
-        """ % (loader_url,)
+        <p>This plugin exports the Asset for the current session as an FBX file.
+        The scene will be exported to the path defined by this plugin's configured 
+        "Publish Template" setting.  The resulting FBX file can then be imported
+        into Unreal Engine via the Loader.</p>
+        """
 
     @property
     def settings(self):

hooks/tk-multi-publish2/tk-maya/basic/publish_turntable.py

@@ -55,50 +55,13 @@ def description(self):
         loader_url = "https://support.shotgunsoftware.com/hc/en-us/articles/219033078"
 
         return """
-        Publishes the file to Shotgun. A <b>Publish</b> entry will be
-        created in Shotgun which will include a reference to the file's current
-        path on disk. If a publish template is configured, a copy of the
-        current session will be copied to the publish template path which
-        will be the file that is published. Other users will be able to access
-        the published file via the <b><a href='%s'>Loader</a></b> so long as
-        they have access to the file's location on disk.
-
-        If the session has not been saved, validation will fail and a button
-        will be provided in the logging output to save the file.
-
-        <h3>File versioning</h3>
-        If the filename contains a version number, the process will bump the
-        file to the next version after publishing.
-
-        The <code>version</code> field of the resulting <b>Publish</b> in
-        Shotgun will also reflect the version number identified in the filename.
-        The basic worklfow recognizes the following version formats by default:
-
-        <ul>
-        <li><code>filename.v###.ext</code></li>
-        <li><code>filename_v###.ext</code></li>
-        <li><code>filename-v###.ext</code></li>
-        </ul>
-
-        After publishing, if a version number is detected in the work file, the
-        work file will automatically be saved to the next incremental version
-        number. For example, <code>filename.v001.ext</code> will be published
-        and copied to <code>filename.v002.ext</code>
-
-        If the next incremental version of the file already exists on disk, the
-        validation step will produce a warning, and a button will be provided in
-        the logging output which will allow saving the session to the next
-        available version number prior to publishing.
-
-        <br><br><i>NOTE: any amount of version number padding is supported. for
-        non-template based workflows.</i>
-
-        <h3>Overwriting an existing publish</h3>
-        In non-template workflows, a file can be published multiple times,
-        however only the most recent publish will be available to other users.
-        Warnings will be provided during validation if there are previous
-        publishes.
-        """ % (loader_url,)
+        <p>This plugin renders a turntable of the Asset for the current session
+        in Unreal Engine.  The Asset will be exported to FBX and imported into
+        an Unreal Project for rendering turntables.  A command line Unreal render
+        will then be initiated and output to a templated location on disk.  Then,
+        the turntable render will be published to Shotgun and submitted for review
+        as a Version.</p>
+        """
 
     @property
     def settings(self):