RE: First Softimage -> Maya transition videos posted

[Jill Ramsay (Contractor)]

Hello Morton,
Let me see if I can find a way to do that will build on the work that’s already 
gone into developing the curriculum and not get too out of hand. Stay tuned.

Thanks,
Jill

From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Morten Bartholdy
Sent: May-14-14 10:37 AM
To: softimage@listproc.autodesk.com
Subject: Re: First Softimage -> Maya transition videos posted


Thank you for these Jill. I can't help thinking since there are thousands of 
things different users would like to see covered it might be difficult for your 
team to identify and cover them all since there are almost as many ways of 
working as there are users :)



How about making a sort of list to which users can contribute and say which 
particular functionalities or workflows they would like to see in a transition 
video?



Best

Morten Bartholdy



<>

Re: First Softimage -> Maya transition videos posted

[Ognjen Vukovic]

Wasn't something like that already covered in the top 5 feature list by
Alastair?

Re: First Softimage -> Maya transition videos posted

[Morten Bartholdy]

Thank you for these Jill. I can't help thinking since there are thousands
of things different users would like to see covered it might be difficult
for your team to identify and cover them all since there are almost as many
ways of working as there are users :)

How about making a sort of list to which users can contribute and say which
particular functionalities or workflows they would like to see in a
transition video?

Best
Morten Bartholdy




Den 12. maj 2014 kl. 17:16 skrev "Jill Ramsay (Contractor)"
:

> Hello everyone,
> The first videos from our Softimage to Maya transition training
curriculum are now posted, with more to come this week and at a regular
rate thereafter. We hope to give you a thorough introduction to Maya that
draws on your existing Softimage knowledge.
>
> We thank you for your patience - we know you'd have liked to have these
sooner. On the plus side, the later release date has allowed us to validate
our curriculum with a number of customers and to use the 2015 versions of
the software.
>
> I hope you find these videos useful. You can post your feedback in the
comments section on the site.
>
> The Softimage Learning Channel can be found here:
> https://www.youtube.com/user/SoftimageHowTos
>
> With the first two videos here:
>
> https://www.youtube.com/watch?v=QokQ6r7mS1E&list=PLC4040C7FF264D722
>
> and here:
>
> https://www.youtube.com/watch?v=eWjrYBXtvPw&list=PLC4040C7FF264D722
>
>
> Best,
> Jill

RE: First Softimage -> Maya transition videos posted

[Nicholas Breslow]

If you plan on scripting in Maya I highly recommend Charcoal Editor – worth the 
investment.  See here:

http://zurbrigg.com/charcoal-editor

-Nick


From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of nick name
Sent: Wednesday, May 14, 2014 3:00 AM
To: softimage@listproc.autodesk.com
Subject: Re: First Softimage -> Maya transition videos posted

Seems like they're very well received these videos, just look at the amount of 
likes/dislikes. It might not be the best indicator, but not to be ignored 
either.

On Wed, May 14, 2014 at 7:15 AM, Jordi Bares 
mailto:jordiba...@gmail.com>> wrote:
You are a generous man…

Jordi Bares
jordiba...@gmail.com<mailto:jordiba...@gmail.com>

On 14 May 2014, at 05:04, Raffaele Fragapane 
mailto:raffsxsil...@googlemail.com>> wrote:


You're being too harsh. I reckon it feels at the very least mid 90s, if not as 
modern as a '96 or even '97 at times.

On Wed, May 14, 2014 at 1:52 PM, Jordi Bares 
mailto:jordiba...@gmail.com>> wrote:
Very much my feeling.. every time I have to use it is like going back in time 
to the early 90s…

Jordi Bares
jordiba...@gmail.com<mailto:jordiba...@gmail.com>

On 13 May 2014, at 19:41, Eric Mootz 
mailto:e...@mootzoid.com>> wrote:

> Aaaahahahah! What a workflow"!
> When I ported my plugin emPolygonizer to Maya a few months ago I obviously 
> had to use Maya for the very first time in my life.
> I was frankly shocked by what they call "the industry standard". Don't get me 
> wrong, the Maya SDK is really quite good, but the rest feels like having a 
> Linux kernel with a buggy Windows for Workgroups user interface.
> Sorry.




--
Our users will know fear and cower before our software! Ship it! Ship it and 
let them flee like the dogs they are!

Re: First Softimage -> Maya transition videos posted

[nick name]

Seems like they're very well received these videos, just look at the amount
of likes/dislikes. It might not be the best indicator, but not to be
ignored either.


On Wed, May 14, 2014 at 7:15 AM, Jordi Bares  wrote:

> You are a generous man…
>
> Jordi Bares
> jordiba...@gmail.com
>
> On 14 May 2014, at 05:04, Raffaele Fragapane 
> wrote:
>
> You're being too harsh. I reckon it feels at the very least mid 90s, if
> not as modern as a '96 or even '97 at times.
>
>
> On Wed, May 14, 2014 at 1:52 PM, Jordi Bares  wrote:
>
>> Very much my feeling.. every time I have to use it is like going back in
>> time to the early 90s…
>>
>> Jordi Bares
>> jordiba...@gmail.com
>>
>> On 13 May 2014, at 19:41, Eric Mootz  wrote:
>>
>> > Aaaahahahah! What a workflow"!
>> > When I ported my plugin emPolygonizer to Maya a few months ago I
>> obviously had to use Maya for the very first time in my life.
>> > I was frankly shocked by what they call "the industry standard". Don't
>> get me wrong, the Maya SDK is really quite good, but the rest feels like
>> having a Linux kernel with a buggy Windows for Workgroups user interface.
>> > Sorry.
>>
>>
>>
>
>
> --
> Our users will know fear and cower before our software! Ship it! Ship it
> and let them flee like the dogs they are!
>
>
>

Re: First Softimage -> Maya transition videos posted

[Jordi Bares]

You are a generous man…

Jordi Bares
jordiba...@gmail.com

On 14 May 2014, at 05:04, Raffaele Fragapane  
wrote:

> You're being too harsh. I reckon it feels at the very least mid 90s, if not 
> as modern as a '96 or even '97 at times.
> 
> 
> On Wed, May 14, 2014 at 1:52 PM, Jordi Bares  wrote:
> Very much my feeling.. every time I have to use it is like going back in time 
> to the early 90s…
> 
> Jordi Bares
> jordiba...@gmail.com
> 
> On 13 May 2014, at 19:41, Eric Mootz  wrote:
> 
> > Aaaahahahah! What a workflow"!
> > When I ported my plugin emPolygonizer to Maya a few months ago I obviously 
> > had to use Maya for the very first time in my life.
> > I was frankly shocked by what they call "the industry standard". Don't get 
> > me wrong, the Maya SDK is really quite good, but the rest feels like having 
> > a Linux kernel with a buggy Windows for Workgroups user interface.
> > Sorry.
> 
> 
> 
> 
> 
> -- 
> Our users will know fear and cower before our software! Ship it! Ship it and 
> let them flee like the dogs they are!

Re: First Softimage -> Maya transition videos posted

[Raffaele Fragapane]

You're being too harsh. I reckon it feels at the very least mid 90s, if not
as modern as a '96 or even '97 at times.


On Wed, May 14, 2014 at 1:52 PM, Jordi Bares  wrote:

> Very much my feeling.. every time I have to use it is like going back in
> time to the early 90s…
>
> Jordi Bares
> jordiba...@gmail.com
>
> On 13 May 2014, at 19:41, Eric Mootz  wrote:
>
> > Aaaahahahah! What a workflow"!
> > When I ported my plugin emPolygonizer to Maya a few months ago I
> obviously had to use Maya for the very first time in my life.
> > I was frankly shocked by what they call "the industry standard". Don't
> get me wrong, the Maya SDK is really quite good, but the rest feels like
> having a Linux kernel with a buggy Windows for Workgroups user interface.
> > Sorry.
>
>
>


-- 
Our users will know fear and cower before our software! Ship it! Ship it
and let them flee like the dogs they are!

Re: First Softimage -> Maya transition videos posted

[Jordi Bares]

Very much my feeling.. every time I have to use it is like going back in time 
to the early 90s…

Jordi Bares
jordiba...@gmail.com

On 13 May 2014, at 19:41, Eric Mootz  wrote:

> Aaaahahahah! What a workflow"!
> When I ported my plugin emPolygonizer to Maya a few months ago I obviously 
> had to use Maya for the very first time in my life.
> I was frankly shocked by what they call "the industry standard". Don't get me 
> wrong, the Maya SDK is really quite good, but the rest feels like having a 
> Linux kernel with a buggy Windows for Workgroups user interface.
> Sorry.

Re: First Softimage -> Maya transition videos posted

[Siew Yi Liang]

TBH I was never really annoyed by either script editor's behaviour...but 
I guess these days I send everything to Maya from either sublime text or 
pycharm, so I'm not bothered so much by it anymore...the only thing is 
that I can't pull up the quick help as easily as before but that's about 
it.


Yours sincerely,
Siew Yi Liang

On 5/13/2014 11:40 AM, Christopher Crouzet wrote:
I've been wondering the same for some time... you can't imagine all 
the complaints that my work colleagues had to endure when I started to 
use Maya :)

Re: First Softimage -> Maya transition videos posted

[Leendert A. Hartog]

It might be helpful (for easy access and a direct link) to point to the 
youtube playlist that contains all these videos:

https://www.youtube.com/playlist?list=PLP5KnnScX57byOldVy9rQlBRARrX6gy4b
which obviously could easily be shortened with any URL shortening service.

Greetz
Leendert

--

Leendert A. Hartog AKA Hirazi Blue
Administrator NOT the owner of si-community.com

Re: First Softimage -> Maya transition videos posted

[Eric Mootz]

Aaaahahahah! What a workflow"!
When I ported my plugin emPolygonizer to Maya a few months ago I 
obviously had to use Maya for the very first time in my life.
I was frankly shocked by what they call "the industry standard". Don't 
get me wrong, the Maya SDK is really quite good, but the rest feels like 
having a Linux kernel with a buggy Windows for Workgroups user interface.

Sorry.

Re: First Softimage -> Maya transition videos posted

[Christopher Crouzet]

I've been wondering the same for some time... you can't imagine all the
complaints that my work colleagues had to endure when I started to use Maya
:)



On 13 May 2014 14:30, Jordi Bares  wrote:

> I don't know if I want to cry or laugh…
>
> Probably both… on a loop.
>
> jb
>
>
> On 13 May 2014, at 17:52, Christopher Crouzet <
> christopher.crou...@gmail.com> wrote:
>
> The code flushing out after execution is indeed a bit annoying but you get
> used to it. The combo Ctrl+A then Ctrl+Enter quickly becomes an automatism.
>
> The two biggest annoyances for me were to code within the Script Editor (I
> guess I'm too used to Sublime Text), and more importantly the persistence
> of the variables. In my case this seemed to cause more bugs than the other
> way around. Example: when refactoring a code and deleting some variables,
> you expect the execution of the script to raise some errors if you forgot
> to remove some occurences of those variables that you've deleted. With this
> persistence thing, this will won't warn you of anything. If you're unlucky,
> this will even preserve the expected behavior of the script. Then, when you
> copy/paste the code in a library or when you reload Maya, bam.
>
> I guess the Script Editor is not made to code your super complex functions
> anyways, but to workaround those issues, I came to use a quick/hacky
> solution.
> The idea is to create a .py script file somewhere in which you define a
> main function that contains your script and that you call at the end of the
> file.
>
> def main():
> maya = 'workaround land'
> print maya
>
> main()
>
>
> Then, just create a button in the shell that calls `execfile` with the
> path of the .py file. The variables defined within the main function won't
> pollute the environment—they won't persist.
>
> There's probably ways to wrap this up more nicely but I couldn't be arsed.
>
>
>
> On 13 May 2014 12:27, Jordi Bares  wrote:
>
>> Exactly right.
>>
>>  Jordi Bares
>> jordiba...@gmail.com
>>
>> On 13 May 2014, at 17:13, Peter Agg  wrote:
>>
>> Basically I want my scripts to stay there - whether I run them or close
>> the program. I'll delete them when I'm good and ready, damnit!
>>
>>
>> On 13 May 2014 15:42, Eric Thivierge  wrote:
>>
>>> What do you mean? Close and reopen it and your scripts are still there.
>>> If you're talking about when you close Softimage, that is expected. That
>>> kind of functionality is weird to me in Maya. It's like reloading your last
>>> scene you had open before you closed the last time.
>>
>>
>>
>
>
> --
> Christopher Crouzet
> *http://christophercrouzet.com* 
>
>
>


-- 
Christopher Crouzet
*http://christophercrouzet.com* 

Re: First Softimage -> Maya transition videos posted

[Jordi Bares]

I don't know if I want to cry or laugh…

Probably both… on a loop.

jb

On 13 May 2014, at 17:52, Christopher Crouzet  
wrote:

> The code flushing out after execution is indeed a bit annoying but you get 
> used to it. The combo Ctrl+A then Ctrl+Enter quickly becomes an automatism.
> 
> The two biggest annoyances for me were to code within the Script Editor (I 
> guess I'm too used to Sublime Text), and more importantly the persistence of 
> the variables. In my case this seemed to cause more bugs than the other way 
> around. Example: when refactoring a code and deleting some variables, you 
> expect the execution of the script to raise some errors if you forgot to 
> remove some occurences of those variables that you've deleted. With this 
> persistence thing, this will won't warn you of anything. If you're unlucky, 
> this will even preserve the expected behavior of the script. Then, when you 
> copy/paste the code in a library or when you reload Maya, bam.
> 
> I guess the Script Editor is not made to code your super complex functions 
> anyways, but to workaround those issues, I came to use a quick/hacky solution.
> The idea is to create a .py script file somewhere in which you define a main 
> function that contains your script and that you call at the end of the file.
> 
> def main():
> maya = 'workaround land'
> print maya
> 
> main()
> 
> 
> Then, just create a button in the shell that calls `execfile` with the path 
> of the .py file. The variables defined within the main function won't pollute 
> the environment—they won't persist.
> 
> There's probably ways to wrap this up more nicely but I couldn't be arsed.
> 
> 
> 
> On 13 May 2014 12:27, Jordi Bares  wrote:
> Exactly right.
> 
> Jordi Bares
> jordiba...@gmail.com
> 
> On 13 May 2014, at 17:13, Peter Agg  wrote:
> 
>> Basically I want my scripts to stay there - whether I run them or close the 
>> program. I'll delete them when I'm good and ready, damnit!
>> 
>> 
>> On 13 May 2014 15:42, Eric Thivierge  wrote:
>> What do you mean? Close and reopen it and your scripts are still there. If 
>> you're talking about when you close Softimage, that is expected. That kind 
>> of functionality is weird to me in Maya. It's like reloading your last scene 
>> you had open before you closed the last time.
> 
> 
> 
> 
> -- 
> Christopher Crouzet
> http://christophercrouzet.com
> 

Re: First Softimage -> Maya transition videos posted

[Christopher Crouzet]

The code flushing out after execution is indeed a bit annoying but you get
used to it. The combo Ctrl+A then Ctrl+Enter quickly becomes an automatism.

The two biggest annoyances for me were to code within the Script Editor (I
guess I'm too used to Sublime Text), and more importantly the persistence
of the variables. In my case this seemed to cause more bugs than the other
way around. Example: when refactoring a code and deleting some variables,
you expect the execution of the script to raise some errors if you forgot
to remove some occurences of those variables that you've deleted. With this
persistence thing, this will won't warn you of anything. If you're unlucky,
this will even preserve the expected behavior of the script. Then, when you
copy/paste the code in a library or when you reload Maya, bam.

I guess the Script Editor is not made to code your super complex functions
anyways, but to workaround those issues, I came to use a quick/hacky
solution.
The idea is to create a .py script file somewhere in which you define a
main function that contains your script and that you call at the end of the
file.

def main():
maya = 'workaround land'
print maya

main()


Then, just create a button in the shell that calls `execfile` with the path
of the .py file. The variables defined within the main function won't
pollute the environment—they won't persist.

There's probably ways to wrap this up more nicely but I couldn't be arsed.



On 13 May 2014 12:27, Jordi Bares  wrote:

> Exactly right.
>
> Jordi Bares
> jordiba...@gmail.com
>
> On 13 May 2014, at 17:13, Peter Agg  wrote:
>
> Basically I want my scripts to stay there - whether I run them or close
> the program. I'll delete them when I'm good and ready, damnit!
>
>
> On 13 May 2014 15:42, Eric Thivierge  wrote:
>
>> What do you mean? Close and reopen it and your scripts are still there.
>> If you're talking about when you close Softimage, that is expected. That
>> kind of functionality is weird to me in Maya. It's like reloading your last
>> scene you had open before you closed the last time.
>
>
>


-- 
Christopher Crouzet
*http://christophercrouzet.com* 

Re: First Softimage -> Maya transition videos posted

[Jordi Bares]

Exactly right.

Jordi Bares
jordiba...@gmail.com

On 13 May 2014, at 17:13, Peter Agg  wrote:

> Basically I want my scripts to stay there - whether I run them or close the 
> program. I'll delete them when I'm good and ready, damnit!
> 
> 
> On 13 May 2014 15:42, Eric Thivierge  wrote:
> What do you mean? Close and reopen it and your scripts are still there. If 
> you're talking about when you close Softimage, that is expected. That kind of 
> functionality is weird to me in Maya. It's like reloading your last scene you 
> had open before you closed the last time.

Re: First Softimage -> Maya transition videos posted

[Peter Agg]

Basically I want my scripts to stay there - whether I run them or close the
program. I'll delete them when I'm good and ready, damnit!


On 13 May 2014 15:42, Eric Thivierge  wrote:

> What do you mean? Close and reopen it and your scripts are still there. If
> you're talking about when you close Softimage, that is expected. That kind
> of functionality is weird to me in Maya. It's like reloading your last
> scene you had open before you closed the last time.
>
>
> On Tuesday, May 13, 2014 10:39:26 AM, Peter Agg wrote:
>
>> ...and then you had the Soft script editor that clears itself out when
>> it closes. Apparently no one gets this stuff right!
>>
>>
>> On 13 May 2014 15:21, Francois Lord > > wrote:
>>
>> I remember when The Foundry asked me what I wanted in a script
>> editor. I said: make it work like the XSI one. They said:
>> everybody already said that but about the Maya one. I didn't know
>> how the Maya one worked so I assumed it would be similar.
>> When Nuke finally came with a script editor, I was shocked! I
>> never understood why would someone want that. If you want to run
>> commands and forget about them, make it a shell, not a script editor!
>> Fortunately, they added an option not to clear the script. Problem
>> solved.
>>
>> F
>>
>>
>> On 13-May-14 03:34, Andy Goehler wrote:
>>
>>>
>>> Nukes script editor behaves the same way. Down to the Selection
>>> and Ctrl-Enter to execute. For the reason Raf has mentioned.
>>>
>>> Looking into Houdini there seems to be all options: the python
>>> shell and the editor which does not delete the code :-)
>>>
>>> Andy
>>>
>>> On 13.05.2014, at 05:01, Matt Lind >> > wrote:
>>>
>>>  Honestly, I cannot think of another ‘script editor’ in any
 application that behaves in the way Maya’s does by deleting code
 upon clicking the execute button.


>>
>>
>

Re: First Softimage -> Maya transition videos posted

[Eric Thivierge]

What do you mean? Close and reopen it and your scripts are still there. 
If you're talking about when you close Softimage, that is expected. 
That kind of functionality is weird to me in Maya. It's like reloading 
your last scene you had open before you closed the last time.


On Tuesday, May 13, 2014 10:39:26 AM, Peter Agg wrote:

...and then you had the Soft script editor that clears itself out when
it closes. Apparently no one gets this stuff right!


On 13 May 2014 15:21, Francois Lord mailto:flordli...@gmail.com>> wrote:

I remember when The Foundry asked me what I wanted in a script
editor. I said: make it work like the XSI one. They said:
everybody already said that but about the Maya one. I didn't know
how the Maya one worked so I assumed it would be similar.
When Nuke finally came with a script editor, I was shocked! I
never understood why would someone want that. If you want to run
commands and forget about them, make it a shell, not a script editor!
Fortunately, they added an option not to clear the script. Problem
solved.

F


On 13-May-14 03:34, Andy Goehler wrote:


Nukes script editor behaves the same way. Down to the Selection
and Ctrl-Enter to execute. For the reason Raf has mentioned.

Looking into Houdini there seems to be all options: the python
shell and the editor which does not delete the code :-)

Andy

On 13.05.2014, at 05:01, Matt Lind mailto:ml...@carbinestudios.com>> wrote:


Honestly, I cannot think of another ‘script editor’ in any
application that behaves in the way Maya’s does by deleting code
upon clicking the execute button.

Re: First Softimage -> Maya transition videos posted

[Peter Agg]

...and then you had the Soft script editor that clears itself out when it
closes. Apparently no one gets this stuff right!


On 13 May 2014 15:21, Francois Lord  wrote:

>  I remember when The Foundry asked me what I wanted in a script editor. I
> said: make it work like the XSI one. They said: everybody already said that
> but about the Maya one. I didn't know how the Maya one worked so I assumed
> it would be similar.
> When Nuke finally came with a script editor, I was shocked! I never
> understood why would someone want that. If you want to run commands and
> forget about them, make it a shell, not a script editor!
> Fortunately, they added an option not to clear the script. Problem solved.
>
> F
>
>
> On 13-May-14 03:34, Andy Goehler wrote:
>
>
> Nukes script editor behaves the same way. Down to the Selection and
> Ctrl-Enter to execute. For the reason Raf has mentioned.
>
>  Looking into Houdini there seems to be all options: the python shell and
> the editor which does not delete the code :-)
>
>  Andy
>
> On 13.05.2014, at 05:01, Matt Lind  wrote:
>
>   Honestly, I cannot think of another ‘script editor’ in any application
> that behaves in the way Maya’s does by deleting code upon clicking the
> execute button.
>
>
>

Re: First Softimage -> Maya transition videos posted

[Francois Lord]

I remember when The Foundry asked me what I wanted in a script editor. I 
said: make it work like the XSI one. They said: everybody already said 
that but about the Maya one. I didn't know how the Maya one worked so I 
assumed it would be similar.
When Nuke finally came with a script editor, I was shocked! I never 
understood why would someone want that. If you want to run commands and 
forget about them, make it a shell, not a script editor!

Fortunately, they added an option not to clear the script. Problem solved.

F

On 13-May-14 03:34, Andy Goehler wrote:


Nukes script editor behaves the same way. Down to the Selection and 
Ctrl-Enter to execute. For the reason Raf has mentioned.


Looking into Houdini there seems to be all options: the python shell 
and the editor which does not delete the code :-)


Andy

On 13.05.2014, at 05:01, Matt Lind > wrote:


Honestly, I cannot think of another ‘script editor’ in any 
application that behaves in the way Maya’s does by deleting code upon 
clicking the execute button.

Re: First Softimage -> Maya transition videos posted

[Jordi Bares]

Indeed, really weird choice to come up with a video that showcases the really 
convoluted Maya workflows you are going to encounter… it is more off putting 
than anything else.

And what has to do Adam's CV with the transition videos?  (nothing against him 
of course… just wondering)

Jordi Bares
jordiba...@gmail.com

On 12 May 2014, at 17:31, Eric Turman  wrote:

> Thanks
> 
> I do have to say that I am a bit put off by the first choice of examples, and 
> I'm certain that I'm not alone. Any competent 3D veteran could easily figure 
> out most of this with in minutes...and probably has. The video is quite 
> frankly insulting. 
> 
> I'm not saying that transition videos aren't helpful, but it comes off as 
> condescending that we would not be able to figure out something as basic as 
> hotkeys.
> 
> More useful would be a series of videos of: here is feature A in Softimage 
> and oops! Maya doesn't have feature A, but here is the convoluted workaround 
> that you can do to kind of get the same result (like distance constraint) Or 
> even, in Softimage you'd normally work like this, but even though you can 
> work the same way in Maya, a better way would be to use this other feature or 
> methodology since trying to work like you would in Softimage will slow Maya 
> down (use expressions in Soft ==> use node networks in Maya) 
> 
> -=Eric
> -- 
> 
> 
> 
> 
> -=T=-

Re: First Softimage -> Maya transition videos posted

[Cristobal Infante]

I've found that Houdini is the answer to that question. If you think ICE is
powerful have a look at VEX, your mind will be blown away. Though I
understand not everyone can afford a multi package pipeline...

On Tuesday, 13 May 2014, Nicolas Esposito <3dv...@gmail.com> wrote:

> @Graham: They're working on the tutorial, it'll be ready to show to the
> public in 2017 :-D
>
>
> 2014-05-13 9:34 GMT+02:00 Andy Goehler 
> 
> >:
>
>>
>> Nukes script editor behaves the same way. Down to the Selection and
>> Ctrl-Enter to execute. For the reason Raf has mentioned.
>>
>> Looking into Houdini there seems to be all options: the python shell and
>> the editor which does not delete the code :-)
>>
>> Andy
>>
>> On 13.05.2014, at 05:01, Matt Lind 
>> >
>> wrote:
>>
>> Honestly, I cannot think of another ‘script editor’ in any application
>> that behaves in the way Maya’s does by deleting code upon clicking the
>> execute button.
>>
>>
>

Re: First Softimage -> Maya transition videos posted

[Nicolas Esposito]

@Graham: They're working on the tutorial, it'll be ready to show to the
public in 2017 :-D


2014-05-13 9:34 GMT+02:00 Andy Goehler :

>
> Nukes script editor behaves the same way. Down to the Selection and
> Ctrl-Enter to execute. For the reason Raf has mentioned.
>
> Looking into Houdini there seems to be all options: the python shell and
> the editor which does not delete the code :-)
>
> Andy
>
> On 13.05.2014, at 05:01, Matt Lind  wrote:
>
> Honestly, I cannot think of another ‘script editor’ in any application
> that behaves in the way Maya’s does by deleting code upon clicking the
> execute button.
>
>

Re: First Softimage -> Maya transition videos posted

[Andy Goehler]

Nukes script editor behaves the same way. Down to the Selection and Ctrl-Enter 
to execute. For the reason Raf has mentioned.

Looking into Houdini there seems to be all options: the python shell and the 
editor which does not delete the code :-)

Andy

> On 13.05.2014, at 05:01, Matt Lind  wrote:
> 
> Honestly, I cannot think of another ‘script editor’ in any application that 
> behaves in the way Maya’s does by deleting code upon clicking the execute 
> button.  

Re: First Softimage -> Maya transition videos posted

[Graham D Clark]

Is there a tutorial that shows me where ICE is in Maya?
Thanks, Graham

Graham D Clark, Head of Stereography, Deluxe 3D dba Stereo D
phone: why-I-stereo
http://www.linkedin.com/in/grahamclark

> On May 12, 2014, at 8:16 AM, "Jill Ramsay (Contractor)" 
>  wrote:
> 
> Hello everyone,
> The first videos from our Softimage to Maya transition training curriculum 
> are now posted, with more to come this week and at a regular rate thereafter. 
> We hope to give you a thorough introduction to Maya that draws on your 
> existing Softimage knowledge.
> 
> We thank you for your patience - we know you'd have liked to have these 
> sooner. On the plus side, the later release date has allowed us to validate 
> our curriculum with a number of customers and to use the 2015 versions of the 
> software.
> 
> I hope you find these videos useful. You can post your feedback in the 
> comments section on the site.
> 
> The Softimage Learning Channel can be found here:
> https://www.youtube.com/user/SoftimageHowTos
> 
> With the first two videos here:
> 
> https://www.youtube.com/watch?v=QokQ6r7mS1E&list=PLC4040C7FF264D722
> 
> and here:
> 
> https://www.youtube.com/watch?v=eWjrYBXtvPw&list=PLC4040C7FF264D722
> 
> 
> Best,
> Jill
> 

Re: First Softimage -> Maya transition videos posted

[Martin Yara]

On Tue, May 13, 2014 at 10:55 AM, Matt Lind wrote:

> deleting the code upon clicking the execute button.
>

If you click the Execute All ( >> ) button your code won't disappear. Not
having a shortcut for this, and having to put your hand out of your
keyboard, grab your mouse, move it and click is a little annoying. Press
Ctrl, then A, Enter and release Ctrl should do it though.

But since it seems you are already clicking, then just click the other
button.

Martin

RE: First Softimage -> Maya transition videos posted

[Matt Lind]

A ‘script editor’ is for developing scripted code, often from scratch, and 
testing the logic and workflow in the context of its use.  It’s a very 
iterative workflow full of trial and error as you build up the logic and 
features cumulatively while writing generically and comprehensively work with 
the application’s API.  Having your code deleted every time you click the 
execute button is the exact opposite behavior you want in such a workflow.  
That’s why it’s so stupid.  Can you imagine C++ development where your code is 
deleted each time you click the compile button?  Honestly, I cannot think of 
another ‘script editor’ in any application that behaves in the way Maya’s does 
by deleting code upon clicking the execute button.  That’s including web 
development and other industries.  I think there’s a reason for that – it’s 
counter productive.

A ‘script editor’ should have default behavior for script development.  If the 
intention is to debug with persistence, as you say, then it shouldn’t be called 
a script editor.  It should be called a debugger.  Debugging why a scene isn’t 
behaving as expected is a very different context than developing code for use 
as a tool.  In debugging mode you’re poking and prodding what things are doing 
in a specific context.  You often don’t write much code in a debug session.  
You’re more or less inspecting and tracing it to expose the problem.  The 
scenario you present about persistence is in effect, but most modern 
applications have implemented some form of JIT debugging for that purpose.  I 
can see how you only want to execute small bits of code and perhaps 
iteratively, but I still don’t see how deleting code in an editor is productive 
under any scenario.  I would tend to think it would be better to make the user 
work with selections or some other mechanism to get the same behavior.

Semantics leads to expectations.


Matt





From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Raffaele Fragapane
Sent: Monday, May 12, 2014 7:03 PM
To: softimage@listproc.autodesk.com
Subject: Re: First Softimage -> Maya transition videos posted

That feature is still present in many modern environments and a rather 
important one, it's hardly a left over, and it makes sense for backward 
compatibility as a default behaviour, and to be honest the way I use the script 
editor it makes sense in general close to half the time.
Soft lacks that feature entirely, and its debugging facilities have been 
horrible in general since day 1.

This is not some sort of maya apology, I'd like the option (though I'd like it 
as a new type of tab editor instance, NOT as a general script editor 
preference, as I want to be able to have both behaviours in different tabs), 
but it's not that big of a deal IMO, it certainly isn't show stopping or 
something you can't comfortably work around, just sort of wonky in how sudden 
it is if you're not used to it.

I feel the point is getting a bit belaboured, and it's very possible we use 
editors and contexts so differently that I simply don't understand your angle. 
That said, objectively speaking I don't think you can simply put it down to 
some archaic remnant that should be erased, because it's not. It's not "the 
editor wipes out", that'd be a bug, it's session persistence, that's a 
behaviour, and frequently enough a desirable one, so it shouldn't be removed.


On Tue, May 13, 2014 at 11:55 AM, Matt Lind 
mailto:ml...@carbinestudios.com>> wrote:
The feature was developed for a different era and is largely a holdover from 
Wavefront Advanced Visualizer, no?  Back then all that was available were 
expression languages, so it made some limited sense to have such a feature, but 
even by those standards still stupid as a default behavior.

I don’t think a new editor is necessary.  Can be solved with a user preference 
or button in the editor itself, with default value of not deleting the code 
upon clicking the execute button.  Considering there are a bazillion other user 
preferences already, I don’t see how this was ignored for so long.  It’s like 
Honda or Toyota building cars with nails embedded in the tires causing flats 
right out of the factory and refusing to fix the problem because some customers 
want to replace their tires upon taking possession of the car at the 
dealership.  While not putting nails in the tires could disrupt a few 
customers, I think it would benefit a great many more and improve the company’s 
reputation.


Matt




From: 
softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com>
 
[mailto:softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com>]
 On Behalf Of Raffaele Fragapane
Sent: Monday, May 12, 2014 6:40 PM

To: softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com&g

Re: First Softimage -> Maya transition videos posted

[Raffaele Fragapane]

That feature is still present in many modern environments and a rather
important one, it's hardly a left over, and it makes sense for backward
compatibility as a default behaviour, and to be honest the way I use the
script editor it makes sense in general close to half the time.
Soft lacks that feature entirely, and its debugging facilities have been
horrible in general since day 1.

This is not some sort of maya apology, I'd like the option (though I'd like
it as a new type of tab editor instance, NOT as a general script editor
preference, as I want to be able to have both behaviours in different
tabs), but it's not that big of a deal IMO, it certainly isn't show
stopping or something you can't comfortably work around, just sort of wonky
in how sudden it is if you're not used to it.

I feel the point is getting a bit belaboured, and it's very possible we use
editors and contexts so differently that I simply don't understand your
angle. That said, objectively speaking I don't think you can simply put it
down to some archaic remnant that should be erased, because it's not. It's
not "the editor wipes out", that'd be a bug, it's session persistence,
that's a behaviour, and frequently enough a desirable one, so it shouldn't
be removed.



On Tue, May 13, 2014 at 11:55 AM, Matt Lind wrote:

> The feature was developed for a different era and is largely a holdover
> from Wavefront Advanced Visualizer, no?  Back then all that was available
> were expression languages, so it made some limited sense to have such a
> feature, but even by those standards still stupid as a default behavior.
>
>
>
> I don’t think a new editor is necessary.  Can be solved with a user
> preference or button in the editor itself, with default value of not
> deleting the code upon clicking the execute button.  Considering there are
> a bazillion other user preferences already, I don’t see how this was
> ignored for so long.  It’s like Honda or Toyota building cars with nails
> embedded in the tires causing flats right out of the factory and refusing
> to fix the problem because some customers want to replace their tires upon
> taking possession of the car at the dealership.  While not putting nails in
> the tires could disrupt a few customers, I think it would benefit a great
> many more and improve the company’s reputation.
>
>
>
>
>
> Matt
>
>
>
>
>
>
>
>
>
> *From:* softimage-boun...@listproc.autodesk.com [mailto:
> softimage-boun...@listproc.autodesk.com] *On Behalf Of *Raffaele Fragapane
> *Sent:* Monday, May 12, 2014 6:40 PM
>
> *To:* softimage@listproc.autodesk.com
> *Subject:* Re: First Softimage -> Maya transition videos posted
>
>
>
> Well, to be honest there is a basis for it. In Maya the environment
> persists, so when you "run" something what you are doing is committing it,
> much like it'd happen in a command line python instance.
>
> E.G. type and run A = 1, run it (cleared), then run print A.
>
>
>
> That has some upsides (persistence has come in handy more than once, and
> debugging tends to be superior), but also some downsides as rot is hard to
> monitor, and it doesn't cater to any quick and dirty usage scenarios where
> you want every run to truly be run-once.
>
>
>
> If they just flat out removed it then it'd break a past quality and lose a
> feature, likely to public outrage.
>
> What they should be doing, instead of changing it in place, is offer an
> option for a new and better editor with execution mode choices.
>
>
>
> All in all for anything of a certain complexity I simply don't run things
> inside ANY script editor anyway, and I developed the select all + ctrl
> enter twitch a decade ago to cut the cost of broken mice down, but it
> surely could use more options.
>
>
>
> On Tue, May 13, 2014 at 11:33 AM, Matt Lind 
> wrote:
>
> CTRL-Z or not, that has to rank up there as one of the most stupid
> workflows in the history of 3D.  Think about it.  You have to write
> additional code to destroy that data.  Somebody actually took time to spec
> out, write, and debug the application to do that and QA didn’t catch the
> stupidity.
>
>
>
> The only thing worse is the issue hasn’t been corrected yet.  Code written
> in 1996/97 still does the same thing in the year 2014.  The only question I
> have is: did Back to the Future predict this too?
>
>
>
>
>
>
>
> Normally I’d be angling to join a beta list, but when extremely obvious
> stupidity exists front and center, it really makes a strong statement that
> efforts on a beta list would be fruitless and wasted.
>
>
>
> Houdini it is.
>
>
>
> Matt
>
>
>
>
>



-- 
Our users will know fear and cower before our software! Ship it! Ship it
and let them flee like the dogs they are!

RE: First Softimage -> Maya transition videos posted

[Matt Lind]

The feature was developed for a different era and is largely a holdover from 
Wavefront Advanced Visualizer, no?  Back then all that was available were 
expression languages, so it made some limited sense to have such a feature, but 
even by those standards still stupid as a default behavior.

I don’t think a new editor is necessary.  Can be solved with a user preference 
or button in the editor itself, with default value of not deleting the code 
upon clicking the execute button.  Considering there are a bazillion other user 
preferences already, I don’t see how this was ignored for so long.  It’s like 
Honda or Toyota building cars with nails embedded in the tires causing flats 
right out of the factory and refusing to fix the problem because some customers 
want to replace their tires upon taking possession of the car at the 
dealership.  While not putting nails in the tires could disrupt a few 
customers, I think it would benefit a great many more and improve the company’s 
reputation.


Matt




From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Raffaele Fragapane
Sent: Monday, May 12, 2014 6:40 PM
To: softimage@listproc.autodesk.com
Subject: Re: First Softimage -> Maya transition videos posted

Well, to be honest there is a basis for it. In Maya the environment persists, 
so when you "run" something what you are doing is committing it, much like it'd 
happen in a command line python instance.
E.G. type and run A = 1, run it (cleared), then run print A.

That has some upsides (persistence has come in handy more than once, and 
debugging tends to be superior), but also some downsides as rot is hard to 
monitor, and it doesn't cater to any quick and dirty usage scenarios where you 
want every run to truly be run-once.

If they just flat out removed it then it'd break a past quality and lose a 
feature, likely to public outrage.
What they should be doing, instead of changing it in place, is offer an option 
for a new and better editor with execution mode choices.

All in all for anything of a certain complexity I simply don't run things 
inside ANY script editor anyway, and I developed the select all + ctrl enter 
twitch a decade ago to cut the cost of broken mice down, but it surely could 
use more options.

On Tue, May 13, 2014 at 11:33 AM, Matt Lind 
mailto:ml...@carbinestudios.com>> wrote:
CTRL-Z or not, that has to rank up there as one of the most stupid workflows in 
the history of 3D.  Think about it.  You have to write additional code to 
destroy that data.  Somebody actually took time to spec out, write, and debug 
the application to do that and QA didn’t catch the stupidity.

The only thing worse is the issue hasn’t been corrected yet.  Code written in 
1996/97 still does the same thing in the year 2014.  The only question I have 
is: did Back to the Future predict this too?



Normally I’d be angling to join a beta list, but when extremely obvious 
stupidity exists front and center, it really makes a strong statement that 
efforts on a beta list would be fruitless and wasted.

Houdini it is.

Matt

Re: First Softimage -> Maya transition videos posted

[Raffaele Fragapane]

Well, to be honest there is a basis for it. In Maya the environment
persists, so when you "run" something what you are doing is committing it,
much like it'd happen in a command line python instance.
E.G. type and run A = 1, run it (cleared), then run print A.

That has some upsides (persistence has come in handy more than once, and
debugging tends to be superior), but also some downsides as rot is hard to
monitor, and it doesn't cater to any quick and dirty usage scenarios where
you want every run to truly be run-once.

If they just flat out removed it then it'd break a past quality and lose a
feature, likely to public outrage.
What they should be doing, instead of changing it in place, is offer an
option for a new and better editor with execution mode choices.

All in all for anything of a certain complexity I simply don't run things
inside ANY script editor anyway, and I developed the select all + ctrl
enter twitch a decade ago to cut the cost of broken mice down, but it
surely could use more options.


On Tue, May 13, 2014 at 11:33 AM, Matt Lind wrote:

> CTRL-Z or not, that has to rank up there as one of the most stupid
> workflows in the history of 3D.  Think about it.  You have to write
> additional code to destroy that data.  Somebody actually took time to spec
> out, write, and debug the application to do that and QA didn’t catch the
> stupidity.
>
>
>
> The only thing worse is the issue hasn’t been corrected yet.  Code written
> in 1996/97 still does the same thing in the year 2014.  The only question I
> have is: did Back to the Future predict this too?
>
>
>
>
>
>
>
> Normally I’d be angling to join a beta list, but when extremely obvious
> stupidity exists front and center, it really makes a strong statement that
> efforts on a beta list would be fruitless and wasted.
>
>
>
> Houdini it is.
>
>
>
> Matt
>
>
>
>
>

RE: First Softimage -> Maya transition videos posted

[Matt Lind]

CTRL-Z or not, that has to rank up there as one of the most stupid workflows in 
the history of 3D.  Think about it.  You have to write additional code to 
destroy that data.  Somebody actually took time to spec out, write, and debug 
the application to do that and QA didn’t catch the stupidity.

The only thing worse is the issue hasn’t been corrected yet.  Code written in 
1996/97 still does the same thing in the year 2014.  The only question I have 
is: did Back to the Future predict this too?



Normally I’d be angling to join a beta list, but when extremely obvious 
stupidity exists front and center, it really makes a strong statement that 
efforts on a beta list would be fruitless and wasted.

Houdini it is.

Matt





From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eric Turman
Sent: Monday, May 12, 2014 6:18 PM
To: softimage@listproc.autodesk.com
Subject: Re: First Softimage -> Maya transition videos posted

well at least they allow you to ctrl-z it now :P

On Mon, May 12, 2014 at 8:16 PM, Matt Lind 
mailto:ml...@carbinestudios.com>> wrote:
Is there a tutorial that explains how to get your script back after hitting the 
execute script button in the script editor?

17 years later and it still does this…really?


Matt



--




-=T=-

Re: First Softimage -> Maya transition videos posted

[Raffaele Fragapane]

Select all and use ctrl+enter, or edit externally and source it.
Yes, it has a legacy of retardation 16 years long that endures ;)


On Tue, May 13, 2014 at 11:16 AM, Matt Lind wrote:

> Is there a tutorial that explains how to get your script back after
> hitting the execute script button in the script editor?
>
>
>
> 17 years later and it still does this…really?
>
>
>
>
>
> Matt
>
>
>
>
>
>
>
>
>
>
>
> *From:* softimage-boun...@listproc.autodesk.com [mailto:
> softimage-boun...@listproc.autodesk.com] *On Behalf Of *Eric Turman
> *Sent:* Monday, May 12, 2014 6:09 PM
> *To:* softimage@listproc.autodesk.com
>
> *Subject:* Re: First Softimage -> Maya transition videos posted
>
>
>
> Hi Raf,
>
>
>
> They show you how to tear away the outliner...the only reason that I had
> never found that is that the capability doesn't exist with the floating
> window...you have to use the panel display one, *then* you can get the
> magic command so long as you enable "echo all commands" ... -_-
>
> This is the one useful thing that I got out of the video and I'm grateful
> that I watched it if only for this one piece of information.
>
>
>
> and the Maya devs/fanboys wonder why we look at them with a WTF!?
> expression...
>
>
>
>  Ooooh! I almost forgot! they also show you how to mel
> script a hotkey for toggling on a free tangent weight in the curve editor.
>  Something that should be on by default.
>
>
>
> There are only two things that I like better about the Maya FCurve editor
> 1) the independent pre & post infinity cycle 2) the keyframe lattice (&
> even that needs improvement.) All the rest please make work like Softimage.
> Our lead animator was a Dyed in the wool Maya user until he used Softimage
> for a few months, now he complains about the Maya FCurve editor whenever he
> has to do a Maya project.
>
>
>
> Cheers,
>
> -=Eric
>
>
>
>
>
>
>
> On Mon, May 12, 2014 at 7:54 PM, Raffaele Fragapane <
> raffsxsil...@googlemail.com> wrote:
>
> I've only glanced at the first part before my eyes glazed over.
>
> Is it actually really sixteen minutes worth of setting up hotkeys or
> there's something more interesting going on later?
>
>
>
>
>
> --
>
>
>
>
> -=T=-
>



-- 
Our users will know fear and cower before our software! Ship it! Ship it
and let them flee like the dogs they are!

Re: First Softimage -> Maya transition videos posted

[Eric Turman]

well at least they allow you to ctrl-z it now :P


On Mon, May 12, 2014 at 8:16 PM, Matt Lind  wrote:

> Is there a tutorial that explains how to get your script back after
> hitting the execute script button in the script editor?
>
>
>
> 17 years later and it still does this…really?
>
>
>
>
>
> Matt
>
>
>
>
>
-- 




-=T=-

RE: First Softimage -> Maya transition videos posted

[Matt Lind]

Is there a tutorial that explains how to get your script back after hitting the 
execute script button in the script editor?

17 years later and it still does this…really?


Matt





From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eric Turman
Sent: Monday, May 12, 2014 6:09 PM
To: softimage@listproc.autodesk.com
Subject: Re: First Softimage -> Maya transition videos posted

Hi Raf,

They show you how to tear away the outliner...the only reason that I had never 
found that is that the capability doesn't exist with the floating window...you 
have to use the panel display one, *then* you can get the magic command so long 
as you enable "echo all commands" ... -_-
This is the one useful thing that I got out of the video and I'm grateful that 
I watched it if only for this one piece of information.

and the Maya devs/fanboys wonder why we look at them with a WTF!? expression...

 Ooooh! I almost forgot! they also show you how to mel script a 
hotkey for toggling on a free tangent weight in the curve editor.  Something that should be on by default.

There are only two things that I like better about the Maya FCurve editor 1) 
the independent pre & post infinity cycle 2) the keyframe lattice (& even that 
needs improvement.) All the rest please make work like Softimage. Our lead 
animator was a Dyed in the wool Maya user until he used Softimage for a few 
months, now he complains about the Maya FCurve editor whenever he has to do a 
Maya project.

Cheers,
-=Eric



On Mon, May 12, 2014 at 7:54 PM, Raffaele Fragapane 
mailto:raffsxsil...@googlemail.com>> wrote:
I've only glanced at the first part before my eyes glazed over.
Is it actually really sixteen minutes worth of setting up hotkeys or there's 
something more interesting going on later?



--




-=T=-

Re: First Softimage -> Maya transition videos posted

[Raffaele Fragapane]

Why in a frozen bleeding hell would I want to tear away the outliner when I
can open a new (instance) one with a two lines script? :p

Alright, gonna give it a miss then.


On Tue, May 13, 2014 at 11:08 AM, Eric Turman  wrote:

> Hi Raf,
>
> They show you how to tear away the outliner...the only reason that I had
> never found that is that the capability doesn't exist with the floating
> window...you have to use the panel display one, *then* you can get the
> magic command so long as you enable "echo all commands" ... -_-
> This is the one useful thing that I got out of the video and I'm grateful
> that I watched it if only for this one piece of information.
>
> and the Maya devs/fanboys wonder why we look at them with a WTF!?
> expression...
>
>  Ooooh! I almost forgot! they also show you how to mel
> script a hotkey for toggling on a free tangent weight in the curve editor.
>  Something that should be on by default.
>
> There are only two things that I like better about the Maya FCurve editor
> 1) the independent pre & post infinity cycle 2) the keyframe lattice (&
> even that needs improvement.) All the rest please make work like Softimage.
> Our lead animator was a Dyed in the wool Maya user until he used Softimage
> for a few months, now he complains about the Maya FCurve editor whenever he
> has to do a Maya project.
>
> Cheers,
> -=Eric
>
>
>
>
> On Mon, May 12, 2014 at 7:54 PM, Raffaele Fragapane <
> raffsxsil...@googlemail.com> wrote:
>
>> I've only glanced at the first part before my eyes glazed over.
>> Is it actually really sixteen minutes worth of setting up hotkeys or
>> there's something more interesting going on later?
>>
>
>
>
> --
>
>
>
>
> -=T=-
>



-- 
Our users will know fear and cower before our software! Ship it! Ship it
and let them flee like the dogs they are!

Re: First Softimage -> Maya transition videos posted

[Eric Turman]

Hi Raf,

They show you how to tear away the outliner...the only reason that I had
never found that is that the capability doesn't exist with the floating
window...you have to use the panel display one, *then* you can get the
magic command so long as you enable "echo all commands" ... -_-
This is the one useful thing that I got out of the video and I'm grateful
that I watched it if only for this one piece of information.

and the Maya devs/fanboys wonder why we look at them with a WTF!?
expression...

 Ooooh! I almost forgot! they also show you how to mel
script a hotkey for toggling on a free tangent weight in the curve editor.
 Something that should be on by default.

There are only two things that I like better about the Maya FCurve editor
1) the independent pre & post infinity cycle 2) the keyframe lattice (&
even that needs improvement.) All the rest please make work like Softimage.
Our lead animator was a Dyed in the wool Maya user until he used Softimage
for a few months, now he complains about the Maya FCurve editor whenever he
has to do a Maya project.

Cheers,
-=Eric




On Mon, May 12, 2014 at 7:54 PM, Raffaele Fragapane <
raffsxsil...@googlemail.com> wrote:

> I've only glanced at the first part before my eyes glazed over.
> Is it actually really sixteen minutes worth of setting up hotkeys or
> there's something more interesting going on later?
>



-- 




-=T=-

Re: First Softimage -> Maya transition videos posted

[Raffaele Fragapane]

I've only glanced at the first part before my eyes glazed over.
Is it actually really sixteen minutes worth of setting up hotkeys or
there's something more interesting going on later?

RE: First Softimage -> Maya transition videos posted

[Manuel Huertas Marchena]

@Jill, cool thx!

IMDB | Portfolio | Vimeo
| Linkedin


Date: Mon, 12 May 2014 15:44:31 -0500
Subject: Re: First Softimage -> Maya transition videos posted
From: i.anima...@gmail.com
To: softimage@listproc.autodesk.com

I also was not trying to stab at you either, its just that your last sentence 
made me laugh. =)
True, it is heartening that they are making any videos to help Soft users 
transition, But, it will be more heartening if they actually carry through with 
their 2 year commitment to supporting Softimage and put developers on to 
shoring up the 2015 release of Soft before they bury Softimage 
forever... typing those last few words made me throw up in my mouth a 
little...heartbreaking. 

But yes here's to hoping for something good to come out of this tragic 
situation.
Cheers,-=Eric

On Mon, May 12, 2014 at 3:01 PM, Leendert A. Hartog  wrote:

Don't get me wrong, my post wasn't intended as a stab at you at all,

if anything it was a "general stab" (if you know what I mean)...

A while back I wouldn't have believed Autodesk to actually produce anything 
like this,

so now that they've already exceeded my expectations,

I am more than willing to give this a large amount of "benefit of a doubt".

And hopefully in the end there will be more than enough useful info to "please" 
most of us.



Greetz

Leendert



-- 



Leendert A. Hartog AKA Hirazi Blue

Administrator NOT the owner of si-community.com





-- 


 

 -=T=-
  

Re: First Softimage -> Maya transition videos posted

[Eric Turman]

I also was not trying to stab at you either, its just that your last
sentence made me laugh. =)

True, it is heartening that they are making any videos to help Soft users
transition, But, it will be more heartening if they actually carry through
with their 2 year commitment to supporting Softimage and put developers on
to shoring up the 2015 release of Soft before they bury Softimage
forever... typing those last few words made me throw up in my
mouth a little...heartbreaking.

But yes here's to hoping for something good to come out of this tragic
situation.

Cheers,
-=Eric


On Mon, May 12, 2014 at 3:01 PM, Leendert A. Hartog wrote:

> Don't get me wrong, my post wasn't intended as a stab at you at all,
> if anything it was a "general stab" (if you know what I mean)...
> A while back I wouldn't have believed Autodesk to actually produce
> anything like this,
> so now that they've already exceeded my expectations,
> I am more than willing to give this a large amount of "benefit of a doubt".
> And hopefully in the end there will be more than enough useful info to
> "please" most of us.
>
>
> Greetz
> Leendert
>
> --
>
> Leendert A. Hartog AKA Hirazi Blue
> Administrator NOT the owner of si-community.com
>
>


-- 




-=T=-

Re: First Softimage -> Maya transition videos posted

[Leendert A. Hartog]

Don't get me wrong, my post wasn't intended as a stab at you at all,
if anything it was a "general stab" (if you know what I mean)...
A while back I wouldn't have believed Autodesk to actually produce 
anything like this,

so now that they've already exceeded my expectations,
I am more than willing to give this a large amount of "benefit of a doubt".
And hopefully in the end there will be more than enough useful info to 
"please" most of us.


Greetz
Leendert

--

Leendert A. Hartog AKA Hirazi Blue
Administrator NOT the owner of si-community.com

RE: First Softimage -> Maya transition videos posted

[Jill Ramsay (Contractor)]

Hi Manu,
I'll pass that on to the team, thank you!

Jill

From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Manuel Huertas 
Marchena
Sent: May-12-14 1:52 PM
To: softimage list
Subject: RE: First Softimage -> Maya transition videos posted

Thanks Jill,

that is great news! looking forward to it.
btw if you can do some videos in regards to:

-maya pivots & snapping
-maya node editor (for shading compared to render tree) *I heard we can use 
maya's node editor to do shading instead of the ultra cumbersome hypergraph...

it'll be awesome.
Regards


-Manu


<>

Re: First Softimage -> Maya transition videos posted

[Eric Turman]

I for one welcome our Borg-bot overlords ;) (sorry Leendert...your last
sentence brought this to image to mind so vividly that I laughed out loud
and had to share...no hard feelings)

I think it is fine to show some simple stuff too, but these are "
*transition*" videos; it was not "beneath me" so much as beneath what this
video series is supposed to be. So, by all means show the
graham-crackers-and-milk information, just be sure to mix in with some
meatier concepts to keep the viewing worthwhile. There are plenty of "I'm
new to 3D and here is how I get a cube" videos.

I gave my first impression, and you only get to make a first impression
once. So, hopefully there will be more production oriented concepts such as
good referencing and asset practices marbled with the fluff concepts like
changing the shape of a node. A good example it how UV editing is different
in Maya in how you have to cut and sew islands vs. the toggle button that
it is in Softimage (I haven't checked if this is still true in Maya 2015,
but I am assuming that it is)


On Mon, May 12, 2014 at 1:43 PM, Leendert A. Hartog wrote:

> Looks like a good start
> and I personally think not just focusing on "complex workflows" but also
> on "workarounds" is a good idea
> even if that means part of the series will be beneath some... I for one
> welcome this series very much.
> ;)
>
> Greetz
> Leendert
>
> --
>
> Leendert A. Hartog AKA Hirazi Blue
> Administrator NOT the owner of si-community.com
>
>


-- 




-=T=-

Re: First Softimage -> Maya transition videos posted

[Leendert A. Hartog]

Looks like a good start
and I personally think not just focusing on "complex workflows" but also 
on "workarounds" is a good idea
even if that means part of the series will be beneath some... I for one 
welcome this series very much.

;)

Greetz
Leendert

--

Leendert A. Hartog AKA Hirazi Blue
Administrator NOT the owner of si-community.com

Re: First Softimage -> Maya transition videos posted

[Luc-Eric Rousseau]

I'm a softimage->Maya transition myself, and I liked that. .. You're
learning different things at once when trying to implement something like a
hotkey for slopes in the Animation Editor, or opening multiple Outliners.
 It's good to have someone show you that stuff.


On Mon, May 12, 2014 at 12:47 PM, Angus Davidson
wrote:

>  I do have to agree with Eric that the target audience of first two
> videos is very much at a beginner instead of a professional looking to
> transistion (Which was the original requirement)
>
>  I am hoping the series will be ramped up significantly to deal with
> workflows instead of workarounds.
>
>  So far there is also nothing that couldn’t have been done using the beta
> software months ago ;(
>
>  Also wondering why there weren’t more questions asked on the list by
> Autodesk or even Adam as to what people would want to see.
>
>
>
>
>
>
>
>   From: Eric Turman 
> Reply-To: "softimage@listproc.autodesk.com" <
> softimage@listproc.autodesk.com>
> Date: Monday 12 May 2014 at 6:31 PM
>
> To: "softimage@listproc.autodesk.com" 
> Subject: Re: First Softimage -> Maya transition videos posted
>
>   Thanks
>
>  I do have to say that I am a bit put off by the first choice of examples,
> and I'm certain that I'm not alone. Any competent 3D veteran could easily
> figure out most of this with in minutes...and probably has. The video is
> quite frankly insulting.
>
>  I'm not saying that transition videos aren't helpful, but it comes off
> as condescending that we would not be able to figure out something as basic
> as hotkeys.
>
>  More useful would be a series of videos of: here is feature A in
> Softimage and oops! Maya doesn't have feature A, but here is the convoluted
> workaround that you can do to kind of get the same result (like distance
> constraint) Or even, in Softimage you'd normally work like this, but even
> though you can work the same way in Maya, a better way would be to use this
> other feature or methodology since trying to work like you would in
> Softimage will slow Maya down (use expressions in Soft ==> use node
> networks in Maya)
>
>  -=Eric
> --
>
>
>
>
> -=T=-
>
>  This communication is intended for the addressee only. It is confidential. 
> If you have received this communication in error, please notify us 
> immediately and destroy the original message. You may not copy or disseminate 
> this communication without the permission of the University. Only authorised 
> signatories are competent to enter into agreements on behalf of the 
> University and recipients are thus advised that the content of this message 
> may not be legally binding on the University and may contain the personal 
> views and opinions of the author, which are not necessarily the views and 
> opinions of The University of the Witwatersrand, Johannesburg. All agreements 
> between the University and outsiders are subject to South African Law unless 
> the University agrees in writing to the contrary.
>
>

RE: First Softimage -> Maya transition videos posted

[Manuel Huertas Marchena]

Thanks Jill,
that is great news! looking forward to it.btw if you can do some videos in 
regards to:
-maya pivots & snapping -maya node editor (for shading compared to render tree) 
*I heard we can use maya's node editor to do shading instead of the ultra 
cumbersome hypergraph...
it'll be awesome.Regards

-Manu


IMDB | Portfolio | Vimeo
| Linkedin


From: jill.ram...@autodesk.com
To: softimage@listproc.autodesk.com
Subject: RE: First Softimage -> Maya transition videos posted
Date: Mon, 12 May 2014 17:19:36 +

There are lots, lots more to come, and the complexity level will definitely be 
ramping up so feel free to jump to whatever stage you want to.  We validated 
(and adjusted based on feedback) the curriculum with a number of our internal 
users who have made the transition themselves, and also with several users. I 
hope that as we progress you will find some things useful at any rate. Jill 
  

RE: First Softimage -> Maya transition videos posted

[Jill Ramsay (Contractor)]

There are lots, lots more to come, and the complexity level will definitely be 
ramping up so feel free to jump to whatever stage you want to.

We validated (and adjusted based on feedback) the curriculum with a number of 
our internal users who have made the transition themselves, and also with 
several users. I hope that as we progress you will find some things useful at 
any rate.

Jill


<>

Re: First Softimage -> Maya transition videos posted

[John Richard Sanchez]

Well it is a start. It is actually the same thing I did before dusting off
my old Maya skills. Use the same/ similar hot keys from XSI in maya which
others have said in other threads not to do. :) Dont use a XSI gui in maya,
dont use shelves, no xsi hot keys its not allowed. You wont learn the Maya
way. Baloney!  I did learn how to have more than one explorer / outliner
open so that was good.


On Mon, May 12, 2014 at 12:47 PM, Angus Davidson
wrote:

>  I do have to agree with Eric that the target audience of first two
> videos is very much at a beginner instead of a professional looking to
> transistion (Which was the original requirement)
>
>  I am hoping the series will be ramped up significantly to deal with
> workflows instead of workarounds.
>
>  So far there is also nothing that couldn’t have been done using the beta
> software months ago ;(
>
>  Also wondering why there weren’t more questions asked on the list by
> Autodesk or even Adam as to what people would want to see.
>
>
>
>
>
>
>
>   From: Eric Turman 
> Reply-To: "softimage@listproc.autodesk.com" <
> softimage@listproc.autodesk.com>
> Date: Monday 12 May 2014 at 6:31 PM
>
> To: "softimage@listproc.autodesk.com" 
> Subject: Re: First Softimage -> Maya transition videos posted
>
>   Thanks
>
>  I do have to say that I am a bit put off by the first choice of examples,
> and I'm certain that I'm not alone. Any competent 3D veteran could easily
> figure out most of this with in minutes...and probably has. The video is
> quite frankly insulting.
>
>  I'm not saying that transition videos aren't helpful, but it comes off
> as condescending that we would not be able to figure out something as basic
> as hotkeys.
>
>  More useful would be a series of videos of: here is feature A in
> Softimage and oops! Maya doesn't have feature A, but here is the convoluted
> workaround that you can do to kind of get the same result (like distance
> constraint) Or even, in Softimage you'd normally work like this, but even
> though you can work the same way in Maya, a better way would be to use this
> other feature or methodology since trying to work like you would in
> Softimage will slow Maya down (use expressions in Soft ==> use node
> networks in Maya)
>
>  -=Eric
> --
>
>
>
>
> -=T=-
>
>  This communication is intended for the addressee only. It is confidential. 
> If you have received this communication in error, please notify us 
> immediately and destroy the original message. You may not copy or disseminate 
> this communication without the permission of the University. Only authorised 
> signatories are competent to enter into agreements on behalf of the 
> University and recipients are thus advised that the content of this message 
> may not be legally binding on the University and may contain the personal 
> views and opinions of the author, which are not necessarily the views and 
> opinions of The University of the Witwatersrand, Johannesburg. All agreements 
> between the University and outsiders are subject to South African Law unless 
> the University agrees in writing to the contrary.
>
>


-- 
www.johnrichardsanchez.com

Re: First Softimage -> Maya transition videos posted

[Angus Davidson]

I do have to agree with Eric that the target audience of first two videos is 
very much at a beginner instead of a professional looking to transistion (Which 
was the original requirement)

I am hoping the series will be ramped up significantly to deal with workflows 
instead of workarounds.

So far there is also nothing that couldn’t have been done using the beta 
software months ago ;(

Also wondering why there weren’t more questions asked on the list by Autodesk 
or even Adam as to what people would want to see.







From: Eric Turman mailto:i.anima...@gmail.com>>
Reply-To: 
"softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com>" 
mailto:softimage@listproc.autodesk.com>>
Date: Monday 12 May 2014 at 6:31 PM
To: "softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com>" 
mailto:softimage@listproc.autodesk.com>>
Subject: Re: First Softimage -> Maya transition videos posted

Thanks

I do have to say that I am a bit put off by the first choice of examples, and 
I'm certain that I'm not alone. Any competent 3D veteran could easily figure 
out most of this with in minutes...and probably has. The video is quite frankly 
insulting.

I'm not saying that transition videos aren't helpful, but it comes off as 
condescending that we would not be able to figure out something as basic as 
hotkeys.

More useful would be a series of videos of: here is feature A in Softimage and 
oops! Maya doesn't have feature A, but here is the convoluted workaround that 
you can do to kind of get the same result (like distance constraint) Or even, 
in Softimage you'd normally work like this, but even though you can work the 
same way in Maya, a better way would be to use this other feature or 
methodology since trying to work like you would in Softimage will slow Maya 
down (use expressions in Soft ==> use node networks in Maya)

-=Eric
--




-=T=-



This communication is 
intended for the addressee only. It is confidential. If you have received this 
communication in error, please notify us immediately and destroy the original 
message. You may not copy or disseminate this communication without the 
permission of the University. Only authorised signatories are competent to 
enter into agreements on behalf of the University and recipients are thus 
advised that the content of this message may not be legally binding on the 
University and may contain the personal views and opinions of the author, which 
are not necessarily the views and opinions of The University of the 
Witwatersrand, Johannesburg. All agreements between the University and 
outsiders are subject to South African Law unless the University agrees in 
writing to the contrary. 

Re: First Softimage -> Maya transition videos posted

[Angus Davidson]

Well busy watching the videos so I will add what I pick up

  1.  The first main thing he acknowledges is that the icons on the shelf are 
not easy too figure out.
  2.  Making the shelf items text only (which is what most of us would like to 
do) just makes a mess. Really how is this not a priority UI thing to fix !
  3.  Time required before Mel is required to make something work as we want 7 
Minutes.
  4.  Amen to 8 not being bound to Paint effects in Maya 2015
  5.  I am assuming there are about another 20 or so of these before the 
softimage workflows are covered :)

Will cc to so-community as well.

Kind regards

Angus



From: Chris Marshall 
mailto:chrismarshal...@gmail.com>>
Reply-To: 
"softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com>" 
mailto:softimage@listproc.autodesk.com>>
Date: Monday 12 May 2014 at 6:00 PM
To: "softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com>" 
mailto:softimage@listproc.autodesk.com>>
Subject: Re: First Softimage -> Maya transition videos posted

I think Jill preempted the possible fall-out by including (Contractor) after 
her name. ie "Don't shoot the messenger!!"



On 12 May 2014 16:54, Eric Mootz mailto:e...@mootzoid.com>> 
wrote:
He, he, I bet my XSI license that this is going to be an interesting thread ;)





This communication is 
intended for the addressee only. It is confidential. If you have received this 
communication in error, please notify us immediately and destroy the original 
message. You may not copy or disseminate this communication without the 
permission of the University. Only authorised signatories are competent to 
enter into agreements on behalf of the University and recipients are thus 
advised that the content of this message may not be legally binding on the 
University and may contain the personal views and opinions of the author, which 
are not necessarily the views and opinions of The University of the 
Witwatersrand, Johannesburg. All agreements between the University and 
outsiders are subject to South African Law unless the University agrees in 
writing to the contrary. 

Re: First Softimage -> Maya transition videos posted

[Eric Turman]

Thanks

I do have to say that I am a bit put off by the first choice of examples,
and I'm certain that I'm not alone. Any competent 3D veteran could easily
figure out most of this with in minutes...and probably has. The video is
quite frankly insulting.

I'm not saying that transition videos aren't helpful, but it comes off as
condescending that we would not be able to figure out something as basic as
hotkeys.

More useful would be a series of videos of: here is feature A in Softimage
and oops! Maya doesn't have feature A, but here is the convoluted
workaround that you can do to kind of get the same result (like distance
constraint) Or even, in Softimage you'd normally work like this, but even
though you can work the same way in Maya, a better way would be to use this
other feature or methodology since trying to work like you would in
Softimage will slow Maya down (use expressions in Soft ==> use node
networks in Maya)

-=Eric
-- 




-=T=-

Re: First Softimage -> Maya transition videos posted

[Mirko Jankovic]

I;m not going to say anything nasty, I'm not going to say anything nasty,
I'm not going to say anything.
Good luck with transition who decide to do so.. or must :(


On Mon, May 12, 2014 at 6:00 PM, Chris Marshall
wrote:

> I think Jill preempted the possible fall-out by including (Contractor)
> after her name. ie "Don't shoot the messenger!!"
>
>
>
>
> On 12 May 2014 16:54, Eric Mootz  wrote:
>
>> He, he, I bet my XSI license that this is going to be an interesting
>> thread ;)
>>
>
>
>

Re: First Softimage -> Maya transition videos posted

[Chris Marshall]

I think Jill preempted the possible fall-out by including (Contractor)
after her name. ie "Don't shoot the messenger!!"



On 12 May 2014 16:54, Eric Mootz  wrote:

> He, he, I bet my XSI license that this is going to be an interesting
> thread ;)
>

Re: First Softimage -> Maya transition videos posted

[Eric Mootz]

He, he, I bet my XSI license that this is going to be an interesting 
thread ;)

Re: First Softimage -> Maya transition videos posted

[Chris Marshall]

What Greg meant to say was "Thank you, for helping us transition away from
our software of choice, the software we all love so much, the software that
does what we want in a clean and elegant way, the software that ticks all
our boxes, the software we have invested so much in, to a piece of
software, well, inferior software that none of us want to transition to.
But thanks anyway".

I think that's what Greg meant.
;-)

And if Greg didn't mean that, I do apologise!
Thanks from me too.



On 12 May 2014 16:22, Greg Punchatz  wrote:

>  Thank you
>  --
> *Greg Punchatz*
>  *Sr. Creative Director*
> Janimation
> 214.823.7760
> www.janimation.com
>  On 5/12/2014 10:16 AM, Jill Ramsay (Contractor) wrote:
>
>

Re: First Softimage -> Maya transition videos posted

[Greg Punchatz]

Thank you

*Greg Punchatz*
*Sr. Creative Director*
Janimation
214.823.7760
www.janimation.com 
On 5/12/2014 10:16 AM, Jill Ramsay (Contractor) wrote:

First Softimage -> Maya transition videos posted

[Jill Ramsay (Contractor)]

Hello everyone,
The first videos from our Softimage to Maya transition training curriculum are 
now posted, with more to come this week and at a regular rate thereafter. We 
hope to give you a thorough introduction to Maya that draws on your existing 
Softimage knowledge.

We thank you for your patience - we know you'd have liked to have these sooner. 
On the plus side, the later release date has allowed us to validate our 
curriculum with a number of customers and to use the 2015 versions of the 
software.

I hope you find these videos useful. You can post your feedback in the comments 
section on the site.

The Softimage Learning Channel can be found here:
https://www.youtube.com/user/SoftimageHowTos

With the first two videos here:

https://www.youtube.com/watch?v=QokQ6r7mS1E&list=PLC4040C7FF264D722

and here:

https://www.youtube.com/watch?v=eWjrYBXtvPw&list=PLC4040C7FF264D722


Best,
Jill
<>