Irritating instance clips 2005-02-24 - By Oscar Juárez
Back
the thing is that sometimes you will want to have to clips from the same
image source
thats why it works that way, to have different options in the image clip
for the same
image source.
Oscar
Wayne Williams wrote:
>So would it be a good idea if when the user clicks {NEW} XSI doesn't
>create a new instance but just reloads the one that has already been
>presented before? I was one of the guilty as far as clicking new is
>concerned. On occasion I still find myself doing it. Seems that XSI
>should "know" it's not really a new clip and therefore not treat it as
>one? Are there any disadvantages to that?
>
>-- --Original Message-- --
>From: owner-xsi@(protected) [mailto:owner-xsi@(protected)] On Behalf
>Of Bradley R. Gabe
>Sent: Thursday, February 24, 2005 5:42 AM
>To: XSI@(protected)
>Subject: Re: Irritating instance clips
>
>
>Whenever you're presented with a parameter in XSI to select an image,
>such as for a rotoscope image or image texture node in the render tree,
>you always get the following buttons:
>
>ImageDropMenu [Clear] [Edit] [New]
>
>Before hitting the new button and opening a file browser, try clicking
>the little down arrow on the right side of the ImageDropMenu field to
>see if you've already loaded the image into a clip. Many new XSI users
>tend to click on the [New] button by reflex, which is what leads to a
>scene full of unused and repeated image sources and clips.
>
>Each time you select the [New] button, regardless of where you do it
>from (eg rotoscope, image texture, etc), XSI creates a new image source
>and clip for that image, even if it's already been loaded before. If you
>use the dropdown menu instead, you'll select from the existing list of
>clips without adding any new sources.
>
>I'm not sure how the other 3D apps are working these days with regards
>to bringing in outside image sources, but I do know that in si3D, all
>the image sources were hard wired to the input fields where they were
>set.
>
>In XSI, image sources and clips are set up in a more object oriented
>fashion, which can be very powerful for those who understand the
>structure. Meanwhile, XSI still does it's best to function even when the
>user hits the [New] button for every image.
>
>For those interested, here's how the object structure is set up:
>
>1- Each image clip has one image source object it points to. The image
>source object's job is to point to a file or sequence and bring that
>image format into XSI in a format that XSI can use for image-related
>tasks.
>
>2- Many image clips can point to the same source object.
>The image clip's job is to establish any effects to the image source, as
>well as determine the range and timing of a sequence.
>
>3- Many Objects in XSI that must rely on images (textures, rotoscopes,
>image maps, etc) can point to the same image clip.
>
>Hitting the [New] button for every instance where an image is to be
>imported into XSI creates a unique image source and image clip per
>instance... thus removing any advantages or functionality provided by an
>object oriented approach.
>
>Examples of functionality one can get from the object oriented
>structure:
>
>-Swap all image source paths between low and hi res texture folders
>-Change a single image source path or clip settings to intentionally
>affect many textures for texture versioning -Create many single frame
>clips pointing to the same image sequence source. In order of selection,
>assign one frame at a time from the sequence onto object textures.
>
>
>-Brad
>CG Soup
>---
>Unsubscribe? Mail Majordomo@(protected) with the following text in
>body: unsubscribe xsi
>
>---
>Unsubscribe? Mail Majordomo@(protected) with the following text in body:
>unsubscribe xsi
>
>
>
>
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
