This script allows to Attach/Detach/Set multiple Liquid attributes for selected objects.
liquidAttrubuteManager.mel replaces a lot of menu items from Liquid main menu.
The code is located in liquidmaya mesh branch on SF:
http://liquidmaya.svn.sourceforge.net/viewvc/liquidmaya/branches/mesh/
Friday, January 21, 2011
Thursday, January 20, 2011
Custom slim.ini
With every new version of Slim, Pixar changes the method of organization their standard templates. And adding custom templates to default hierarchy each time became a bit tricky.
With RMS 1.0 I was forced to be rejected of my previous methods and started to learn, how to use very smart palette conception.
Tuesday, January 18, 2011
Custom TOR.ini
Instead of editing original TOR.ini (located in $RATTREE/etc), its better to keep custom
version of this file in location, defined in RAT_SCRIPT_PATHS environment variable. Here you can override MTOR default values and add your own options and extensions.
Monday, September 6, 2010
Fedora 13 troubles
Don't know, why I've decided to install new Fedora 13, after being almost satisfied with my previous Fedora 11 desktop... I already became accustomed to disable SELinux and firewall for decreasing headache while installing specific software. But in F13 it isn't so easy now.
Any way, googling may help and in this case, though...
Any way, googling may help and in this case, though...
Thursday, September 2, 2010
Monday, August 16, 2010
meBakeRadiosity.slim
This Slim template implements bake_radiosity surface shader that was described in Pixar's RenderMan Application Notes - Point-Based Approximate Ambient Occlusion and Color Bleeding - 3.1 Baking a point cloud with area and radiosity data.
meBake.slim
meBakeAreas.slim
This Slim template implements bake_areas surface shader that was described in Pixar's RenderMan Application Notes - Point-Based Approximate Ambient Occlusion and Color Bleeding - 2.1 Baking a point cloud with area data.
Theresn't any separate standart template (at least in Slim 7.1 from RMS 1.0.1) for baking areas pointclouds using in Point-Based shading. Only if you are using shading components in conjunction with Environment light where this functionality is hidden under the hood.
See DiffuseEffects->ObjectCalculation->Approximated...
But this is more complicated method as for me...
meBake.slim
Theresn't any separate standart template (at least in Slim 7.1 from RMS 1.0.1) for baking areas pointclouds using in Point-Based shading. Only if you are using shading components in conjunction with Environment light where this functionality is hidden under the hood.
See DiffuseEffects->ObjectCalculation->Approximated...
But this is more complicated method as for me...
Thursday, August 12, 2010
meBake3D.slim + meTexture3D.slim vs Bakeable
The Bakeable template in Slim looks very powerful. And most part of its power is hidden under the hood. Depending of CONTEXT, defined in Bake generator, it can write pointclouds by bake3d function call or reuse baked data by texture3d. BakeStyle parameter controls a special post job for Alfred that converts pointclouds to brickmaps or texturemaps. But there are not controls to adjust some useful parameters (e.g. MaxError) for brickmake. The Bakeable is general purpose template, it needs DisplayChannels _float and _color for storing corresponding values to pointcloud file. And again, both bake3d and texture3d functions have optional parameters that are absent in original template...
Tuesday, August 10, 2010
FlatShader.tcl
This script flattens Slim shading network to subfolder inside current project but preserves the original shader name. You can modify parameters and nodes in original shading network and perform FlatShader again. Original Slim "Flatten" command fails to override existing shader with changed parameters list.
About how to setup user commands in Slim, see previous post Slim user commands
Slim user commands
For adding a custom user commands to Slim menu, you need to modify your custom slim.ini and TOR.ini. Also you have to write custom Slim template with your cmdui definition.
Tip:
To customize RAT environment, it is a good practice to keep your custom slim.ini and TOR.ini files in the directory defined in system environment variable RAT_SCRIPT_PATHS. You can define space-separated list of directories in this variable for connecting templates and settings from different location inside studio.
E.g.: SET RAT_SCRIPT_PATHS=d:/slim //server/studio/slim
Subscribe to:
Posts (Atom)


