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?
 
pipeline development theory

pipeline development theory

2005-06-16       - By Graham D Clark

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

On 6/15/05, xsibrad@(protected) <xsibrad@(protected)> wrote:
> But every once and a while I hear some comments which make me think some
studios
> are doing a lot more than simple work force organization and data repository
> restructuring, and moving from "having a pipeline" into the realm of
> "developing a pipeline, and pipeline tools".  And its this area that I'm
> currious about.

I think it is due to the evolution of tools and creation software
where "asset tracking" and "asset creation" tools/software are merging
more and more.
In the past "pipeline tools" were often seen for management as
appending and tracking assets, and seperate from the production tools
for artists, but as a pipeline is more fully developed and
requirements for a deliverable asset is more defined to be clean,
follow conventions and be non-linear etc., "asset creation" tools fall
more into the category of "pipeline tools".

Yes reference models are still "rough around the edges" but they imply
a pipeline use with XSI and its at the core of asset types here and
was the vehicle for the pipeline at Action Synthese where Bernard and
I worked. Refs do though have a lot of limitations, the 3 slots being
an example, while other things than ref models, like above the scene
root are very difficult to share across users and shots/sequences.
Hopefully the top of the hierarchy in XSI above the scene is extended
to be project based, seems like that may have been the plan.

Regarding your question about ASCII and XSI there's an interesting
thread here discussing some of our setup that we are heavily reliant
on (especially for our area since we have hair and can't use dotxsi):
http://www.xsi-blog.com/?p=15

I have to backup Olivier about the side advantges of exporting
importing in different non-native formats as a method of creating
something clean (especially with the dirt XSI scenes collect).
REBUILDING assets is more difficult than cleaning them, but ends up
with far less corruption and more mangeable assets with tested
conventions as they move thru the pipe.

A pipeline is people, Helge stamped me with an asset ID too :)

Graham
-- ---- ---- ---- ---- ---- ---- ---- -----
http://www.grahamdclark.com
Hair|Fur Sup, Finalling Sup, Omation
TD|TA|FX|EDU

---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi