I think you are absolutely correct on this.
On Fri, Mar 21, 2014 at 7:21 PM, Mirko Jankovic <mirkoj.anima...@gmail.com>wrote: > In the one side it is understandable that there are limits for revealing > what future hole > But also that limit makes bifrost like cat in the bag. > People will loose ICE, for some vague promises of what bifrost will be. > Sorry but vaporware... > > Imagine some other more known company announce that they are creating > application to rule them all top of the to will do all this and that.. and > promises... just you wait and see.. come pay subscription and you will see > it will be great!!! > > SO you will flockand buy what? bag of promisses? > DO you even see and understand what AD is doing? Selling promise of > something that will work, not really like ICE but something... and don;t > wanna reveal anything and people need to base their future plans and > investments in promises? > Honestly only smart thing woul dbe to stick to what is working now, yes > ICE! and see after couple years of what bifrost is shaping into.. or i it > will be around after couple years at all.. > Bifrost future is bright.. click!? > > > On Fri, Mar 21, 2014 at 6:53 PM, John Richard Sanchez < > youngupstar...@gmail.com> wrote: > >> Is that the Softimage Beta or Maya Beta? :) >> >> >> On Fri, Mar 21, 2014 at 1:45 PM, Sebastian Kowalski <l...@sekow.com>wrote: >> >>> I (we) understand, it is just that we want to be heard. Finally. >>> Everything sounds promising and exciting, just do not take too long. >>> >>> >>> Am 21.03.2014 um 18:41 schrieb Adrian Graham <adrian.gra...@autodesk.com >>> >: >>> >>> Look, I can't comment exactly on where we're going with Bifrost, this is >>> where I run into all sorts of SEC limitations and stuff. I could defer to >>> ChrisV to answer those questions in a more official manner. >>> >>> Rest assured we're aware that ICE is more than just FX, more than >>> particles and simulation, that it's a complete procedural workflow >>> involving all kinds of data, throughout the package. >>> >>> Adrian >>> >>> From: softimage-boun...@listproc.autodesk.com [ >>> mailto:softimage-boun...@listproc.autodesk.com<softimage-boun...@listproc.autodesk.com>] >>> On Behalf Of Sebastian Kowalski >>> Sent: Friday, March 21, 2014 10:38 AM >>> To: softimage@listproc.autodesk.com >>> Subject: Re: ICE - When will we have todays functionality in Maya? >>> >>> thats is my concern too. as much as I embrace a decoupling from maya, >>> its how ICE is capable to talk to different scene elements that makes it so >>> powerful. >>> managing data until the very least work process at render time. and we >>> are in full control. >>> as beautiful big ass fluid sims look, its not what we day for day. >>> please have a look on the 'what uses is ICE?' thread ( >>> https://groups.google.com/forum/#!topic/xsi_list/7aGyes8lBQE) >>> >>> thanks >>> >>> Am 21.03.2014 um 18:29 schrieb Alastair Hearsum < >>> hear...@glassworks.co.uk<mailto:hear...@glassworks.co.uk<hear...@glassworks.co.uk> >>> >>: >>> >>> >>> Hi Adrian >>> >>> I'm no egg head so forgive the simplicity of my question. Would this >>> platform agnostic scenario actively prevent any of the procedures and >>> scenarios that we currently use ICE for? Is ICE so functional because its >>> embedded in Softimage? Can we have the same functionality with a non >>> embedded engine? >>> >>> Alastair >>> Alastair Hearsum >>> Head of 3d >>> [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 >>> <http://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 21/03/2014 16:53, Adrian Graham wrote: >>> >>> Ah, but may I respectfully point out that this was one of the problems >>> with ICE, in that its complete and total integration into Softimage makes >>> it difficult to engineer and manage, from a software and, unfortunately, a >>> marketing point of view. >>> >>> >>> >>> Most modern software libraries are platform-agnostic, and this is what >>> we're aiming for with Bifrost. The problem with ICE is that you had to use >>> Softimage in order to gain access to it. Nothing against Softimage, just >>> that you're limiting ICE's exposure to the industry at large. >>> >>> >>> >>> Would a renderer be more or less popular if it only worked with Maya, >>> and not with Max or Houdini? No, it should be available on all >>> applications, on all OSs if you want it to be successful. >>> >>> >>> >>> Adrian >>> >>> >>> >>> <winmail.dat> >>> >>> >>> >> >> >> -- >> www.johnrichardsanchez.com >> > >
