None of these products are for newbies; we spent years learning Softimage. Sounds like you wanted to edit a history node, doing a procedural modification. You'd open the node editor or try the input section of the channel box. This is a first days stuff. We would probably not have had a render tree in XSI if we had focused on simplicity over power. And certainly not Ice. God you have to guess node name and search for them, are you kidding me. Even with classic simulation it's not always obvious to know what to select and when to call menu. There is all sort of stuff we just learn - the measure of usability is how well you can do more complex stuff once you know the basics On Mar 19, 2014 9:55 AM, "Alastair Hearsum" <hear...@glassworks.co.uk> wrote:
> Graham > > Sorry , I just can't accept that. We have very experienced people here who > have used Maya a lot in production. I trust them implicitly. They produce > some of our best work. They are not raving newbies and have shown > repeatedly their willingness and ability to embrace new technology and > workflows. Its not only from my lack of experience that I have formed my > opinions. I'll say it again, Maya's interface and general workflow leaves a > lot to be desired. If you want to listen and you have a genuine desire to > improve Maya, this what we are saying. > > Alastair > > > Alastair Hearsum > Head of 3d > [image: GLASSWORKS] > 33/34 Great Pulteney Street > London > W1F 9NP > +44 (0)20 7434 1182 > glassworks.co.uk <http://www.glassworks.co.uk/> > Glassworks Terms and Conditions of Sale can be found at glassworks.co.uk > (Company registered in England with number 04759979. Registered office 25 > Harley Street, London, W1G 9BR. VAT registration number: 867290000) > Please consider the environment before you print this email. > DISCLAIMER: This e-mail and attachments are strictly privileged, private > and confidential and are intended solely for the stated recipient(s). Any > views or opinions presented are solely those of the author and do not > necessarily represent those of the Company. If you are not the intended > recipient, be advised that you have received this e-mail in error and that > any use, dissemination, forwarding, printing, or copying of this e-mail is > strictly prohibited. If this transmission is received in error please > kindly return it to the sender and delete this message from your system. > On 19/03/2014 13:25, Graham Bell wrote: > > I'm not being disingenuous at all, only that this is a common problem when > people jump from one software to another. I've seen this many times from > users where they start in another package and try to do the exact same > workflow, only to then become frustrated. > > You can't jump to something else and expect it to work in the same way, you > simply can't. It's a recipe for disaster. And it's all too easy to label > something as being bad. > I'm not saying that Maya's workflow is superior either. There are things I > like and hate about Maya, but you could also say the same about Softimage and > any software package to be fair. > I think it was Luc-Eric who said in a previous post that apps have their set > of compromises, which we essentially accept. > > Chris has mention on work starting to improve Maya's UI and I welcome that. > And if there some Softimage goodness in there, then I welcome that too. > > > From: softimage-boun...@listproc.autodesk.com > [mailto:softimage-boun...@listproc.autodesk.com > <softimage-boun...@listproc.autodesk.com>] On Behalf Of Alastair Hearsum > Sent: 19 March 2014 12:45 > To: softimage@listproc.autodesk.com > Subject: Re: A confession > > Graham > > I think its disingenuous to ascribe the difficulties people have in doing > things in Maya only to the workflow being different. It was simple example I > gave and I would have hoped that it would have highlighted the Maya workflow > as being, dare I say, bad. I hope you don't mind the analogy here but the > first step to an alcoholics recovery is admitting the problem. Marc Stevens > went as far as he could in the webinar in conceding that there may be > qualitative differences in the Maya/Softimage interface workflow scenario and > that it is something that you are looking at > > So yes, different, but lets not shy away from calling a spade a spade. > > Alastair > > Alastair Hearsum > Head of 3d > [GLASSWORKS] > 33/34 Great Pulteney Street > London > W1F 9NP+44 (0)20 7434 1182glassworks.co.uk<http://www.glassworks.co.uk/> > <http://www.glassworks.co.uk/> > Glassworks Terms and Conditions of Sale can be found at glassworks.co.uk > (Company registered in England with number 04759979. Registered office 25 > Harley Street, London, W1G 9BR. VAT registration number: 867290000) > Please consider the environment before you print this email. > DISCLAIMER: This e-mail and attachments are strictly privileged, private and > confidential and are intended solely for the stated recipient(s). Any views > or opinions presented are solely those of the author and do not necessarily > represent those of the Company. If you are not the intended recipient, be > advised that you have received this e-mail in error and that any use, > dissemination, forwarding, printing, or copying of this e-mail is strictly > prohibited. If this transmission is received in error please kindly return it > to the sender and delete this message from your system. > On 19/03/2014 11:31, Graham Bell wrote: > > I've use both Maya and Softimage (XSI) for years, and the problem (imo) that > many will make is that they're two different applications. You simply can't > go into one and expect it to work in the same way to something else. This is > no different to when jumping to Modo, Houdini, or Max. > > > > > > From: > softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com> > <softimage-boun...@listproc.autodesk.com> > [mailto:softimage-boun...@listproc.autodesk.com > <softimage-boun...@listproc.autodesk.com>] On Behalf Of Martin Yara > > Sent: 19 March 2014 11:19 > > To: softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com> > <softimage@listproc.autodesk.com> > > Subject: Re: A confession > > > > You shouldn't rely too much on the outliners, they are nowhere near what SI > Explorer is. But if you must, and want to open multiple outliners ala > Softimage, you can do it with something like this: > > > > // MEL > > //------------------------------------- > > window -t "Outliner" -wh 200 500; > > frameLayout -labelVisible false; > > string $panel = `outlinerPanel`; > > showWindow; > > //------------------------------------- > > > > Yeah, you have to script a lot in Maya. Even for stupid things like this. > > > > Knowing basic scripting in SI is very useful, but in Maya, not knowing basic > scripting may be critical. > > > > Martin > > > > > > On Wed, Mar 19, 2014 at 6:51 PM, Ivan Vasiljevic > <klebed...@gmail.com<mailto:klebed...@gmail.com> > <klebed...@gmail.com><mailto:klebed...@gmail.com> > <klebed...@gmail.com><mailto:klebed...@gmail.com> <klebed...@gmail.com>> > wrote: > > You should go with something more simpler for start: > > Try opening few outliners as you would often have few explorer opened in SI. > > > > > >
