Mailing List
Home
Forum Home
Softimage
Carrara
trueSpace
Dir3d-l
Maya - a powerful 3D animation and visual effects software
Macromedia Flash Development
Subjects
Cameras
scaleDown command
black out solved
Aircraft Tutorial
Mathematical XYZ ?
Its done This vs That
Its done first week
recommendations for screen video captures?
3DExplorer "Oddity "
New Director
ProTeam renewals
Fuel 's new websites (X post)
Blue peter create a make toy
targeting groups question
XPost: Shockwave 3D game ( sort of )
RES: RES: RES: Fish Modeling
Emitting particles from object intersection
Fuel 's new websites (X post)
Texturing
Big Break Contest Videos
New Plugins
Models and Texture on my updated site
Error Installing Patch tS6 6
Plasma?
Looking for Inspiration
Weird EMail Q
It 's done first week ?
Cherry not cranberry
New game
Camera Animation Problem
Particle plugins?
 
shader wizard question on .mi file to spdl

shader wizard question on .mi file to spdl

2005-03-21       - By Schoenberger

 Back
Reply:     1     2     3     4     5     6     7     8     9     10     >>  


My problem is:
I update a shader with the same GUID and I have added some more
parameters into the spdl.
I install them into the workgroup. XSIbatch (only checked batch
rendering, no XSI standalone) checks for the shader GUID and finds the
shader, then it starts rendering and does not find the new parameter
GUID and aborts.

Holger Schönberger
technical director
The day has 24 hours, if that does not suffice, I will take the night



-- --Original Message-- --
From: owner-xsi@(protected) [mailto:owner-xsi@(protected)] On Behalf
Of Jim Rothrock
Sent: Monday, March 21, 2005 11:59 PM
To: XSI@(protected)
Subject: Re: shader wizard question on .mi file to spdl


Schoenberger wrote:


One thing that really sucks is that you are not able to extent a shader.
E.g. I have installed a spdl into my workgroup path. All other machines
register the shader GUID and all parameter GUIDs.
Now I add an parameter in the spdl, I reinstall the shader. Works on my
machine, but all other machines disable the shader because they can't
find the new GUID. The shader is installed, the new parameter not. That
sucks!


I do this all the time, and it works for me.  I occasionally have
machines "forget" about shaders in their registries, but not often.

--

Jim Rothrock | Stan Winston Digital | jimr@(protected)
--- Unsubscribe? Mail Majordomo@(protected) with the following text in
body: unsubscribe xsi


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1">
<TITLE>Nachricht</TITLE>

<META content="MSHTML 6.00.2900.2604" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><SPAN class=015341700-22032005><FONT face=Arial color=#000080
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=015341700-22032005><FONT face=Arial color=#000080 size=2>My
problem is:</FONT></SPAN></DIV>
<DIV><SPAN class=015341700-22032005><FONT face=Arial color=#000080 size=2>I
update a shader with the same GUID and I have added some more parameters into
the spdl. </FONT></SPAN></DIV>
<DIV><SPAN class=015341700-22032005><FONT face=Arial color=#000080 size=2>I
install them into the workgroup. XSIbatch (only checked batch rendering, no XSI
standalone) checks for the shader GUID and finds the shader, then it starts
rendering and does not find the new parameter GUID and
aborts.</FONT></SPAN></DIV>
<DIV><SPAN class=015341700-22032005><FONT face=Arial color=#000080
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=015341700-22032005>
<P align=left><FONT face=Arial size=2>Holger Schönberger</FONT> <BR><FONT
face=Arial size=1>technical director</FONT><BR><FONT face=Arial size=1>The day
has 24 hours, if that does not suffice, I will take the night
</FONT></P></SPAN></DIV>
<DIV><SPAN class=015341700-22032005></SPAN><SPAN class=015341700-22032005><FONT
face=Arial color=#000080 size=2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000080 2px solid;
MARGIN-RIGHT: 0px">
 <DIV></DIV>
 <DIV class=OutlookMessageHeader lang=de dir=ltr align=left><FONT face=Tahoma
 size=2>-- --Original Message-- --<BR><B>From:</B> owner-xsi@(protected)
 [mailto:owner-xsi@(protected)] <B>On Behalf Of </B>Jim
 Rothrock<BR><B>Sent:</B> Monday, March 21, 2005 11:59 PM<BR><B>To:</B>
 XSI@(protected)<BR><B>Subject:</B> Re: shader wizard question on .mi file
to
 spdl<BR><BR></FONT></DIV>Schoenberger wrote:
 <BLOCKQUOTE cite=mid000001c52e65$ef8088c0$3700a8c0@(protected) type="cite">
   <META content="MSHTML 6.00.2900.2604" name=GENERATOR>
   <DIV><SPAN class=875514019-21032005></SPAN>&nbsp;</DIV>
   <DIV><SPAN class=875514019-21032005><FONT face=Arial color=#000080
   size=2>One thing that really sucks is that you are not able to extent a
   shader.</FONT></SPAN></DIV>
   <DIV><SPAN class=875514019-21032005><FONT face=Arial color=#000080
   size=2>E.g. I have installed a spdl into my workgroup path. All other
   machines register the shader GUID and all parameter
   GUIDs.</FONT></SPAN></DIV>
   <DIV><SPAN class=875514019-21032005><FONT face=Arial color=#000080
   size=2>Now I add an parameter in the spdl, I reinstall the shader. Works on
   my machine, but all other machines disable the shader because they can't
   find the new GUID. The shader is installed, the new parameter not. That
   sucks!</FONT></SPAN></DIV>
   <DIV><SPAN class=875514019-21032005></SPAN></DIV></BLOCKQUOTE>I do this all
 the time, and it works for me.&nbsp; I occasionally have machines "forget"
 about shaders in their registries, but not often.<BR><PRE class=moz-signature
cols="72">--
Jim Rothrock | Stan Winston Digital | <A class=moz-txt-link-abbreviated href=
"mailto:jimr@(protected)">jimr@(protected)</A>
</PRE>--- Unsubscribe? Mail Majordomo@(protected) with the following text in
 body: unsubscribe xsi</BLOCKQUOTE></BODY></HTML>