Using a workgroup (never ever use several!) is worth only if your slaves
have to become a master, so if they have to run xsi(batch).
If they will remain slaves for the rest of their life, then the only thing
they need is a good way to address the libraries.
So, you can probably just put all the dll's somewhere, and use the
MI_RAY_SUBSTITUTE variable in the slaves' .xsi file, so that the path to the
master's libraries (workgroup/Application/bin....) matches the "somewhere"
directory.
Stefano
----- Original Message -----
From: "Tim Leydecker" <BauerOink(at)gmx.de>
To: <XSI(at)Softimage.COM>
Sent: Monday, June 19, 2006 11:23 AM
Subject: installing custom shaders without a workgroup)
Hi guys,
I´m looking for information and details about the
various ways of making custom shaders render
correctly on renderslave/satellite setups.
The docs suggest a workgroup but I don´t get
the expected results, at least not when using either
BA_Shader_Collection_14.0.1 or T2S_MentalRay
shaders together with Satellite rendering on XSI 5.1?
Is there a way to install shaders (.addon/spdll) locally
to the install_dir of XSI instead?
I only have 3 machines total to manage, two pretty
identical satellites (in terms of fileorganizations) and
would welcome if I could have all neccesary files
in one directory instead of having to track the user
directory, workgroup and install_dir on each for
any problems. Also, having the workgroup with a
driveletter mapped on each machine (w2k) and a
root/admin account required to make it work is a
potential security risk for our mixed priviledges network here.
Cheers
tim
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
