Absolutley. The Foundry has been doing things the way it should be.
A 3d dedicated app was the only missing link in their film/vfx chain. And with Modo, they closed the round trip. I can see Nuke displaying a Modo scene interactively doing all the lighiting, rendering and compositing, beeing send to Hiero to be dispalyed with the rest of the feature. Something that Softimage started a long time ago when DS was capable of reading a Softimage scene... and 15 years later, finally The Foundry discovered the black thread. Something that Autodesk and had in his hands. With all that technology and amazing dev teams. Instead of after acquiring Softimage and say "Hey lets create something new that will have the best of both worlds", they simply took a pristine and talented dev team who understood the artists, and plugged them into The Matrix. 2014-02-14 11:57 GMT-06:00 Angus Davidson <angus.david...@wits.ac.za>: > Hi Ben > > The big difference is Modo is also successfully cross platform, and in > active development. When the time comes to move on they will be in a > position to do so. > > Something Softimage currently lacks. Which is something Autodesk will > regret down the line. > > > ------------------------------ > *From:* Ben Rogall [xsi_l...@shaders.moederogall.com] > *Sent:* 14 February 2014 07:45 PM > > *To:* softimage@listproc.autodesk.com > *Subject:* Re: Survey - how would you do this? > > As a matter of fact, Modo is COM based. When programming with its SDK, > the COM roots are more visible than with Softimage. However most everything > is nicely wrapped in C++ classes so you don't usually have to deal with the > low level nuts and bolts of COM. > > Ben > > On 2/14/2014 7:42 AM, Angus Davidson wrote: > > Unfortunately it will be Softimages achilles heel if they don't find a > way off of it (which is unlikely given the very small dev team) COM doesn't > scale the way new 3d apps require. To many bottlenecks. > > Jumping into Modo for my first attempt at particles. Managed to get the > following after my allotted 5 minutes > > pic.twitter.com/EDOKamNkkn > > Just used a plain cube as a poly source. Need to update that with a more > random rock ;) > > > > > > From: Guillaume Laforge <guillaume.laforge...@gmail.com> > Reply-To: "softimage@listproc.autodesk.com" < > softimage@listproc.autodesk.com> > Date: Friday 14 February 2014 at 2:06 PM > To: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com> > Subject: Re: Survey - how would you do this? > > Softimage code in Linux is pretty much the same as on Windows and so is > using COM too. How it works on Linux has been explain on this list many > time (almost as often as people asking how to > install Softimage successfully on Linux). > > I have nothing against COM in theory, except that it is hard to find > good programmers mastering this interface those days. It is an old tech and > Softimage is built on it. Easy to get the picture no ? > > > > On Fri, Feb 14, 2014 at 12:04 AM, Angus Davidson < > angus.david...@wits.ac.za> wrote: > >> How does the linux version get around all of the MFC / Com+ dependencies >> ? Would be great if we could get the linux version to be used as the >> compile base. In theory then a more open windows version and even a mac >> version would be possible ;) >> >> On the plus side at least you have moved to a decent laptop now ;) >> >> My only experience in this was from a long time back. FBX , was buggy and >> Alembic wasnt yet an option. We came up with an exporter that allowed a >> decent to and fro between 3D app and Games engine. >> >> Similar to how the obj exporter worked it was text based and had a >> separate include file for geometry, materials,bones animation etc. This >> allowed it to be be easy to use for version control , and also allowed us >> to reuse animations etc across more then one model. Admittedly things were >> a lot simpler then . >> >> Havent looked at Modo for creating the asteroid belt. will try have a >> look this weekend. >> >> ________________________________________ >> From: Luc-Eric Rousseau [luceri...@gmail.com] >> Sent: 14 February 2014 04:26 AM >> To: softimage@listproc.autodesk.com >> Subject: Re: Survey - how would you do this? >> >> imagine if we made such jokes every time the Fabric came to pimp their >> stuff here. ;) >> >> If there is going to be a discussion about creating custom tools for >> artists, sweeping statements about DCCs, and name dropping like Pixar, >> it's in everyone's interest to be informed about the maya side of the >> story. On my side, as Maya UI team lead, pyside (python+qt) is part >> of the day-to-day. Something I could have never imagine on Softimage. >> I'd always have to write everything in C++/MFC to do anything. I've >> also dumped my PC for a Macbook Pro. >> >> >> On Thu, Feb 13, 2014 at 8:56 PM, Guillaume Laforge >> <guillaume.laforge...@gmail.com> wrote: >> > Don't forget to print the threads/coupons Steven ! >> > >> > >> > On Thu, Feb 13, 2014 at 8:37 PM, Steven Caron <car...@gmail.com> wrote: >> >> >> >> ya, i get that feeling too ;) >> >> >> >> its magical >> >> >> >> >> >> On Thu, Feb 13, 2014 at 5:32 PM, Guillaume Laforge >> >> <guillaume.laforge...@gmail.com> wrote: >> >>> >> >>> I've got the feeling that someone is trying to sell us some Autodesk >> >>> products here. >> >>> Can I have a special discount if I print this thread and bring it to >> my >> >>> reseller ? >> >>> >> > >> = >> <table width="100%" border="0" cellspacing="0" cellpadding="0" >> style="width:100%;"> >> <tr> >> <td align="left" style="text-align:justify;"><font >> face="arial,sans-serif" size="1" color="#999999"><span >> style="font-size:11px;">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. </span></font></td> >> </tr> >> </table> >> >> >> > 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. > > > 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. > >
