Bellsey wrote:If you saw me today, then you have damn good eyesight, because I wasn't in the London office today. lol
haha or rather bad eyesite!!
Bellsey wrote:If you saw me today, then you have damn good eyesight, because I wasn't in the London office today. lol
Talking with my Max colleague and also Max customers, it took a while for many Max users to really understand what XBR actually was. And even now some that don't quite get it. When Autodesk announced it, having seen Softimage and ICE, I think many Max users thought it was going to be something along similar lines, or that it was going to be the 'new' Max, in the same way XSI was to Soft3D or Maya to PowerAnimator.Tekano wrote:ha! sorry I'm the first to admit my ignorance when it comes to Max and XBR, And although its completely non representative I've gleaned all I know about Max from that thread. so it doesnt amount to muchluceric wrote:just for completeness: 3DSMax has been actually continually delivering their progress on XBR each release, it's not like XBR is vaporware. Scalability re-writes, QuickSilver viewport rendering, MassFX, tabbed layout/new workspace, slate editor, new ribbon UI, in-viewport overlays, all of that stuff has already shipped. It's what they had talked about in 2009, and work is continuing. So XBR is actually the counter-example of non-communication of here..I thought that some user had said that it was 4 years and they still didnt have XBR. are you saying that some parts of it are already bolted onto Max and its not going to be a separate app? what was interesting to me was the high number of users who didnt want or see the point of the suites other than a corporate manoeuvre to increase profits, and the latest development on Max release strategy re-enforced this. bearing in mind the threads title and all the developments with Softimage I can associate myself with these guys quite easily!
Krakatoa is not an Autodesk product and it isn't ADKS's fault if it wasn't available for Maya.Maximus wrote:For example Maya user gets the suite with 3ds max, always did everything with maya and for one work he has to use Krakatoa, then goes to 3ds max. You force people basically to learn a whole package to just use 1 tool. Instead of taking care of those 3 packages each with updates, having them grow single, not as a suite. The suite should come after the individual software.
There is almost nothing like this. There is Send To to make ICE easier to use by other products, that's all. It's all just a wrapper for the existing FBX.Maximus wrote:This is the main reason why AD development is damn slow, because its done on the suite, with interchange data, with the "send to" in mind, with the exchange datas set. And this slow down everything. Why would i want to go to animate in maya or model in maya when i can do it in Softimage? A software that i already know? i'm productive, i'm fast, i know already everything, why should i litterally waste my time learning another complex/deep/new software to do 1 task?
Two of these suites already exists. The only difference with the Premium or Ultimate suite is that more apps are included in the box, that's zero development cost, it's just licensing.Maximus wrote:To me the suites gonna be whats gonna sink Autodesk. They put together things that should be separate and have their own path/updates/development.
Have just 3 suites max+motionbuilder+mudbox+toxic | Maya+motionbuilder+mudbox+toxic | Softimage+motionbuilder+mudbox+toxic, and work on the interchange between them.
I know it wont happen, but the suites really made the freelance/small studios life really hard.
I don't know why they would do that and in what way Autodesk's suite would be responsible for that. It's more likely the lighters were a Maya pipeline; this business is about people first and foremost. That's how we got kicked out of ILM; the TDs taking the decisions liked Maya, even though the animators loved Softimage.Maximus wrote:Also you say that people ask for multiple softwares to do tasks, this is the consequence of no-development from AD, not because people like to jump to other softwares.
Many behind the scenes we saw lately, they did everything in softimage then went to render in maya with arnold or mental ray, why? dont you have mental ray or arnold in Softimage?
Doesnt make sense. Or vice-versa.
Max's Project Geppetto has been in development for years, by the creator of Character Studio. It's vastly superior at producing high quality crowds for filling environments, however it's not directly programmable. It's not a TD tool or an FX tool, it's for meant for visualization at this point. It's on Autodesk Labs for customer validation, as an "open beta" of sorts. It's part of an openness initiative.Maximus wrote:AD is all about suites now, and in the end the development is and will be really slow. Was checking autodesk Lab and guess what i found? The monolitic project Geppetto. Which is nothing more than guess? A crowd system that was gonna be implemented in max. Probably it failed or they didnt make it happen, and they had Softimage devs create a crowd FX which was never asked from SI community at all. That tool was not really needed compared to many other features/updates people are asking since a lot of time. And this is frustrating when you see that the software you use is being projected and updated having in mind a "suite" and not the real benefit of the software itself, and your work.
The bigger the company, the lesser the need to adapt; greater the opportunity to dictate.Bellsey wrote:My comment on a big company was simply saying that Autodesk has lots of products, lots of people and procedures, etc. And the bigger the company, the less flexible and slower it appears to be. I often make the anology of Autodesk being like an oil tanker - its big, slow moving and can't turn on a sixpence. But it does do its job and can turn in the right direction, just not as fast as people would like it to.
Companies like SideFx, and Luxology, only sell one product. And being smaller, they can adapt more quickly and be more flexible in their pricing and business model. Softimage (pre-Autodesk) was very much the same.
And how should this happen when you are not allowed to share information? Its perfectly understandable why you cant, its just nonsense to suggest things will get clearer at some point. I mean, no one will come out in few months and say "Yeah, we tried to impose the two-tier system to max users because of such-and-such and decided to do so-and-so." Doesn't happen.Bellsey wrote:I've stolen a quote from Ken Pimentel yesterday that best sums it up for me:
"Because you all don't have the complete facts/future of what is going on. You have limited information, the rest we're not allowed to talk to you about publicly. I can understand why you might ask these questions, but it doesn't mean we don't have answers, just that we can't talk about them publicly. I'm just trying to suggest there might be a reason and it might be clearer when you get the rest of the information we're holding back."
I know that krakatoa isnt an AD products, my point is the slow development, you could clearly develop a krakatoa render. Isnt in AD possibilities? So people dont have to jump to max and buy another 1k+ render engine? Thats what development is for.luceric wrote:Krakatoa is not an Autodesk product and it isn't ADKS's fault if it wasn't available for Maya.
Why if there is nothing like this then you ship 2 softwares or even three in the same suite that do the same thing? Again Why havin maya and softimage make sense? They almost do the same if not for ICE, actually Maya can just do the same with its particles and scripting. Develop ICE for Maya, update the single package instead of moving through suites. Thats my point.luceric wrote:There is almost nothing like this. There is Send To to make ICE easier to use by other products, that's all. It's all just a wrapper for the existing FBX.
The only "big work" was for motion builder<->Maya for mocap workflows.
I'm speaking in general here, not Softimage only. AD is indeed forcing people to switch to Suites, when you dont develop and dont update softwares sections because the other software does it better its kinda "forcing" user to jump to the other software for that precise task. Instead of keep updating the software at 360° like always been and like every software house does.luceric wrote:Autodesk is absolutely not trying to force to have two or three "360" apps, that's a complete fantasy. It bundle Softimage to try to give ICE a change to capture more audience. The rest of what you say is a complete fabrication: if people use multiple apps, it's their decisions to do so, the suite isn't the cause of that. Also the Premium suites are a good way to give people a deal to keep they multiple apps they already use up-to-date. Because it's difficult to get them back in after they've fallen behind.
You have a perfect example here on how things work. People didnt see the need of switching application to do something they can do just fine in Maya, so they have no use of Softimage.luceric wrote:I don't know why they would do that and in what way Autodesk's suite would be responsible for that. It's more likely the lighters were a Maya pipeline; this business is about people first and foremost. That's how we got kicked out of ILM; the TDs taking the decisions liked Maya, even though the animators loved Softimage.
I don't think, when people suggest ICE for maya, that they literally mean an exact clone of Softimage's version.luceric wrote:It isn't possible to add ICE to Maya, it's too tied to Softimage's architecture. So the only thing that can be done is a bundle.
Any source on this?Bullit wrote:DCC is about 10-15% of Autodesk revenue.
Maximus' idea is idealistic and impossible. To develop 3 applications as if they were totally independent, self-centered, competitive projects... Hummm... No sane person would intentionally backstab him self over and over again, so neither would business.Bullit wrote:I also think the bundles/suites are great to allow people from different knowledge of softwares. At present it is very good specially to put Softimage in many studios.
Now that will be bad if it would mean that Maya/Max/Softimage loose their broad capability and start to be focused in some area.
Skymatter actually outsourced the development to the Hungarian guys. The idea was originally theirs, and Skymatter jumped on it. A colleague of mine was close friend to one of the programmers, and I had the luck to talk to that guy.My understanding was that Andrew Camenisch, Dave Cardwell, and Tibor Madjar were creators of Mudbox and subsequently Skymatter. Dave and Tibor have moved on but Andrew still heads up Mudbox though. You still see Dave doing some stuff though, like tutorials.
Are you saw Coral integration? It can receive floats, integers, angles, matrices and vectors from maya via dg nodes and output data backPooby wrote:I can't see why the concept behind ICE. Ie a visual programming environment for manipulating scene data could not be developed for Maya.
Why is that not possible?
Well said. Don't renew your subscription, so AD will understoodI think the only way you can make your frustrations be heard is to speak in Moneyeze.
I quote McNistor here, but it is meant as a general observation:McNistor wrote:Why do you keep arguing with "Autodesk people"? They're happy to keep responding to your frustrations (often generating even more of it) until they grow old and retire with a fat monthly pension.