Changes in these updates
- added support for the Nuke WritePrism node for commandline rendering (renderfarm)
- added compression and datatype settings to the Nuke WritePrism node
- fixed a bug that import state in the State Manager were not created in some cases
- fixed a bug that setting the scene resolution in Maya to the project resolution could change the pixel aspect ratio
- fixed a bug that alembic caches, which got applied to existing objects in Maya were not updated correctly to a new version
- fixed an error when showing the versioninfo of 2d rendering in the Project Browser in some cases
- changed the default namespace in Maya for imported/referenced objects to include the sequencename
- added environment variables to use for other tools: PRISM_JOB, PRISM_JOB_LOCAL, PRISM_SEQUENCE, PRISM_SHOT, PRISM_ASSET, PRISM_ASSETPATH, PRISM_STEP, PRISM_CATEGORY, PRISM_USER, PRISM_FILE_VERSION
- improved handling of unreadable configfiles
- improved performance of the asset searchbar
- the Prism API can be accessed now from other Maya scripts using (import PrismInit;PrismInit.pcore)
- fixed a problem that the WritePrism node in Nuke was not available when rendering the Nuke script on Deadline
- fixed an error when importing a master export version when the local project folder is disabled
- fixed an error in Houdini when rightclicking in the export list of the State Manager in some cases
- fixed an issue that “$F4” could be in exports filenames, which were exported from other DCCs than Houdini
- fixed an issue that saving playblasts directly as .mp4 files didn’t work
- fixed an error when the omits.yml file had an incorrect syntax
- fixed an error when creating a WritePrism node in Nuke when no Prism project is active
Prism v126.96.36.199 was released last week and v188.8.131.52 just now. Both updates include many important bugfixes as well as a few new features.
Nuke commandline rendering
In previous Prism versions you would get errors when you try to render Nuke scripts for example on Deadline if the Nukescript contains a WritePrism node. That was because Prism wasn’t loaded in Nuke sessions without GUI. This has changed now which let’s you render the WritePrism node on renderfarms and even access the Prism API during rendertime from you custom tools
Whenever Prism is launched it will set environment variables which provide information about the current project, the current shot and more. You can use them in your custom tools to get the context of the current scenefile.
Previously this was only available in Houdini.
The variable names are:
Accessing Prism API in Maya
Accessing the current PrismCore instance from your custom tools in Maya was not easy to do. You could create a second PrismCore instance, but that would likely cause errors with the existing PrismCore instance.
Since v184.108.40.206 there is a better way now. Here is an example how you can access the Prism API in your custom Maya scripts:
import PrismInit print(PrismInit.pcore.projectName)
Prism v220.127.116.11 is available for download now from the Prism Settings window.