Oh right I see what you mean... yeah, I don't know if you can change those
values either. Your method seems like the right solution in that case. You
could have created a new spdl in a workgroup as well but your method will
ensure that all scenes that use this shader will have it configured that way
without actually having to change anything in your scenes. Creating a new
spdl would have given you both choices but in your case, I guess you've done
the right thing.
-----Original Message-----
From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM]On Behalf
Of takita
Sent: Thursday, September 28, 2006 2:40 PM
To: XSI(at)Softimage.COM
Subject: Re: replacing spdl files
Mathieu Leclaire wrote:
> Then you just give it a new name... but of course you create a new shader
> and you have to use that one from now on but you'll get your settings by
> default. If you have old scenes that you want to update to the new setting
I
> guess you have no choice but to do a script to do it. It all depends on
what
> you want to do. You basically just want to turn some switches on. If you
> want them to be on by default from now on, I see a few possibilities:
>
> First one is to do Matt's method and change all the spdls on all the
> machines. Quite long and painful depending on how many machines you have.
>
It worked out okay that way, not too bad since our systems person could
copy it en masse.
Kind of like a qfe of sorts.
> The second one is coping the spdl in your workgroup, rename it, change the
> guids and the default settings of the switch you want to change.
>
> Or for a third option, you could simply create a script that'll import the
> default shader and activate the switches at the same time and use this
> script/button/where ever you want to call it from, and use that to get the
> shader in the rendertree with the proper settings.
>
Yeah, except the "switches" weren't really exposed in the default
interface as buttons. I'm not sure if you can set parameter values that
are not exposed in the UI by script can you? Wouldn't the spdl
setttings of override that?
> There might be a fourth option if you can set-up an event for when you get
> this shader so that it'll change the settings of that new shader instance
> when that event is triggered. If it is possible then you wouldn't even
have
> to worry about creating a button or what ever but I don't know if that
event
> exists. I haven't played around a lot with events lately.
>
> Hum... just got another idea... I guess you could add a script to your
> workgroup that would be triggered by an event (XSI turns-on for example)
> that would go and update the local spdl of that shader so now anyone who
> adds that shader will have the new updated spdl.
>
>
> You have plenty of possibilities here. And like I said, if you want to
> change old scenes, you're gonna have to script it or your gonna have to do
> the changes manually. So I guess the only real question here is: how good
> are your scripting skills?
>
> I hope that helped you out in one way or another. Let me know if you want
> more details.
>
>
> Mathieu Leclaire
> R&D Programmer
> Hybride Technologies
>
Yeah, I
---
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
