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?
 
construction history mode

construction history mode

2004-06-09       - By Andre DeAngelis

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

Bear in mind that you can move operqtors from one mode to another pretty
easily.

I found this a life saver with say cloth sims for example.  If I applied
them in modelling mode, I could later move thm to the top opf the stack and
continue modifying the topology of my object.

AD

-- --Original Message-- --
From: owner-xsi@(protected) [mailto:owner-xsi@(protected)]On Behalf
Of Andi Farhall
Sent: Wednesday, June 09, 2004 10:18 AM
To: 'XSI@(protected)'
Subject: RE: construction history mode


i guess at the moment it's a workflow thing. The idea of multiple operator
stacks seems smart but i'm now being forced to think about what kind of
operation (out of the 4 choices) i'm trying to perform and making sure that
i'm in the right mode, which is slowing down the workflow. If there was an
element of automation to it, such as putting move component ops in the shape
modeling stack irrespective of which mode your in might speed things up.
Then again it might just lead to more confusion. I feel strangely like i did
when i was first faced with xsi after years of 3X.

-- --Original Message-- --
From: kim aldis [mailto:kim@(protected)]
Sent: 09 June 2004 14:57
To: XSI@(protected)
Subject: RE: construction history mode


Step this way, I have matches ready.

It's something you get used to. After a while it becomes second nature and
the problems it solves make it well worth the effort.

Give me an idea why you're changing it so much?

> -- --Original Message-- --
> From: owner-xsi@(protected)
> [mailto:owner-xsi@(protected)] On Behalf Of Andi Farhall
> Sent: 09 June 2004 14:44
> To: 'xsi@(protected)'
> Subject: construction history mode
>
> shoot me down in flames but the construction history is a bit
> a pain in the butt. Workflow butchered by having to think
> about which mode i'm in every 2 or 3 steps. Anyway to disable it?
>
> grumble grumble
>
> Mr F
>
> __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit
> http://www.messagelabs.com/email
> __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following
> text in body:
> unsubscribe xsi
>
>

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

__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __

__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi