murphy wrote:
> Hello,
>
> we have some strange problems rendering maya scene with realflow mesh
> inside.
>
> we have a network installation of different maya versions and different
> platforms. As a central point for preferences, plugins and modules we
> use MAYA_APP_DIR environment variable pointing to a network disk.
>
> during rush render maya cries it can not find Reaflowmesh.mll plugin.
> But when I run rushrender$$$.bat used by rush to render my frames and
> execute it manually from cmd line it works perfectly and all plugins are
> successfully loaded.
Are you running that in a DOS window that's logged in as the
same user the Rushd service is running as?
Sometimes permissions on eg. dll files or the directories they're
in are restrictive enough that only certain users can access them.
> I suspect there is a huge difference running the
> bat file manually and running the same file from rushd. It seems to me
> system environments are not visible to mayarender when invoked from rush.
> We have modified our submit to include set MAYA_APP_DIR just before
> render is executed in our bat file but it did not helped.
Actually, rush under windows does inherit the combined
System Environment and User Environment (for the user the
rushd service is running as), so assuming you've rebooted
the rendering box since installing the plugin, rush should
pick up all those environment variables.
Check to see if the script is changing them around in
ways where it might loose the values. eg:
$ENV{MAYA_PLUG_IN_PATH} = "/some/path";
..would overwrite the value of that variable if it were
correctly in the system environment, whereas:
$ENV{MAYA_PLUG_IN_PATH} = "/some/path;$ENV{MAYA_PLUG_IN_PATH}";
..would *augment* the path, without stomping on it.
> Now I really do not know what else could be wrong . . . .
If you think it's an environment issue, try running the
following from your working DOS window:
set > dos-env.txt
..and then load that file up, and compare it to the environment
variable dump in the rush log which you can enable by either changing
the 'Print Environment:' pulldown from 'No' to 'yes' (In the submit
form, click on the 'Rush' tab, and scroll down to the bottom to find
that setting)
Or, if you've written your own script for submitting, just stick in
a command just before the render that prints out the environment,
eg. in the script just before it invokes the renderer, add:
if ( $G::iswindows ) { print "--- ENVIRONMENT IS:\n"; system("set"); }
..and that will dump out the environment in the log, so you can compare
it to the dos-env.txt (above).
|