keep SI away from any meaningful upgrades, those who put let them make it even worse and get more reasons to kill it tomorrow.
I think it was clear enough. saying how SI was old impossible to implement blah blah doesn't make sense as both Maya and Max are same old crap... On Fri, May 23, 2014 at 2:36 PM, Jordi Bares <[email protected]> wrote: > Can I ask you Luc-Eric how is that the same engine was not put in XSI? the > whole HQV reinvention seems to me like I am missing something. > > If you ware allowed to discuss what was the behind that decision? I am > sure it made sense to someone but I still don't get it. > > thx > > Jordi Bares > [email protected] > > On 23 May 2014, at 12:34, Luc-Eric Rousseau <[email protected]> wrote: > > Max's Nitrous viewport and Maya's viewport 2.0 are using the same shared > viewport engine. > On May 22, 2014 9:40 PM, "Sebastien Sterling" < > [email protected]> wrote: > >> Sergio is spot on in his description. >> >> i had not heard of Scene states either. >> >> >> http://synergiscadblog.com/2013/03/22/friday-3ds-max-video-tip-how-to-use-the-scene-state-manager/ >> >> Max is a nice user friendly package, but it is being severely neglected. >> no alembic no open subdiv, no viewport 2.0 and no prospects, maya is >> slowly taking over its game industry share. modo is probably a better arch >> design package. no support from major 3rd party renderers, with the >> exception of Vray. >> >> it's sad, Sergio is right about that too. >> >> >> On 23 May 2014 01:01, Steven Caron <[email protected]> wrote: >> >>> they work, but when i was at blur we didn't use them. watch out there is >>> no way of knowing which scene state you are in. >>> >>> >>> On Thu, May 22, 2014 at 4:57 PM, Sergio Muciño >>> <[email protected]>wrote: >>> >>>> Sorry, I got mixed up. It's Scene States. >>>> Render elements are the old system. >>>> Saludos Manuel! >>>> >>>> >>>> Sergio M. >>>> >>>> Sent from my iPhone >>>> >>>> >> >
