On OSX you may need to set DYLD_LIBRARY_PATH to 3Delights /lib directory if the renderer complains it can’t load lib3delight.dylib - whether or not this is correctly set depends on your 3delight installation and how you have launched Maya which can vary between platforms and installations. AMD Radeon ProRender is a powerful physically-based rendering engine that enables creative. If in doubt, it’s probably safe to use source pgYetiDL before rendering. If you have other custom shapes you will need to integrate the settings from our supplied l file in the one used by your studio. We provide a very generic set of Mel commands that does this for you in l - this Mel script defines the required DL_userGetGeoTypeData and DL_pgYetiMayaCanUseObjectInstance global procedures as described in the 3delight manuals, if Yeti is the only procedural shape you are using it is safe to source this file directly.
#Renderman render settings how to#
The 3Delight Maya translator also needs to be told how to interpret the custom Yeti shapes when generating rib files to be able to output the neccesary information for render Yeti caches. As of Renderman 22.x this has become much easier with the introduction of the RFMPLUGINSPATH environment variable, this should point to the Yeti bin directory where the Renderman DSO lives. If you’d prefer not to set these for some reason you can also make sure your 3Delight for Maya ( or other rib generation software ) adds the search path option to the rib files. Rendering with Renderman for Maya is straight forward, the main installation concern is to make sure you have the Yeti DSO in the Procedural search path.
The 3delight extension must be included in the procedural search path which can either be set in your rendermn.ini file or by setting the DL_PROCEDURALS_PATH environment variable. Yeti uses both a procedural DSO for rendering Yeti cache files as well as integrating into 3Delight Studio Pro.
0 kommentar(er)
