any news about Softimage 2014 ???

[EricTRocks]

I don't think anyone does...

But you initially asked about Crowds in 2013. I chimed in about that. Then you took a left turn onto M&E profits, then a sharp right onto the layoffs.

*Just as a note, no one from the Softimage dev team got let go.

[Hirazi Blue]

Indirect quote from Cory Mogk (Sep-19-2012):

We'll be opening the Softimage beta soon and I invite people who haven't
participated before to sign up at https://beta.autodesk.com You can see
what we're doing, try it out and we can discuss things that you would like
to see in the future with the team.

(Quoted by Daniel H in this Mailing List post)

[Rork]

As Beta's fall under the NDA, you will not hearing a lot about 2014 until it's about to be released.
Or get yourself into the beta, so you can see what's happening.

And it's like Fightclub, first rule is not to talk about 2014.....

rob

[EricTRocks]

I'd also emphasize that getting on the beta doesn't mean you get to talk about it or post about it or post pictures or videos from it unless you're authorized to do so which is most often times not at all.

[iamVFX]

For all signed beta testers, please test the new features. Otherwise we'll get 2013 again. Thanks.

[Bellsey]

It's also worth pointing out, that we expect some decent participation in Beta programs, we don't want people being signed up just so they can find out what's coming. We want and need people to use and test the features and builds.

Also for the first time, and now going forward, Softimage will be using the Autodesk Feedback Community for its Beta program. I believe this is a far better format then using previous mailing lists, as it's forum based like this site. However, as much as we don't mind feedback, criticism and healthy discussion we don't want snipers and trolls on the beta forum, though I'm sure that people will act professionally. If things follow the way of the other product betas, than it should be good.

[EricTRocks]

@iamVFX: Implying that testers didn't for 2013? Keep in mind that beta testers are real people with real full time jobs and social lives. The time they put into testing is taking away from those other aspects of their lives.

Also, 2013 didn't have any killer bugs introduced that I know about. Was a pretty solid release IMO. We're not going to get into it again of whether you like the feature set or not cause that isn't what I'm referencing.

[iamVFX]

EricTRocks, read Bellsey message carefully. If you a guy with full time job and social live and you trying to find other reasons to not doing your job well, in this case to test the features and builds well - you better don't sign on. We all know the consequences of 2013 M&E releases, let's try to do something better.

[Bellsey]

actually, my bad. lol.
I just saw what I had put, that will teach me for typing too quickly.

[EricTRocks]

@iamVFX: You have no idea what you're talking about. You clearly think that those who tested 2013 didn't do what they were supposed to. Have you ever participated in a beta before? Beta testers aren't responsible for the features put into the new releases. They are responsible for testing the features that were put there. Find bugs, report, comment on workflows, make suggestions.

I'm well aware at what responsibilities beta testing includes and the time it takes. I've actually had a good amount of time on various betas and also had to run one for Species while developing it.

I didn't say that time was taken away from our regular duties. If you read carefully (maybe slowly and repeatedly) you'll hopefully be able to comprehend that what I said is that you should not judge the testers or imply they didn't do what they were asked to do and show them some respect because on top of (not in place of) their normal responsibilities they are giving up additional time to help out with the beta.

Lastly, clearly you didn't like the features from 2013 but that isn't up to the testers.

[iamVFX]

EricTRocks, PM me a river, don't flame here.

[EricTRocks]

[bottleofram]

I dont remember any showstoppers with 2013 but there was a famous 10 seconds mental ray delay in 2012. Doesn't necessarily mean beta testers missed it, though. With AD's fixed schedule its no secret all sorts of bugs make it to the official release. As long as it doesnt come to 2 sp's and 4 hotfixes to make it barely useable, we should be happy.

[iamVFX]

Doesn't necessarily mean beta testers missed it, though. With AD's fixed schedule its no secret all sorts of bugs make it to the official release.

Yea, that's a fair point. I don't know what stops the developers from implementing online update system. It would be even simpler for testers to test builds without reinstallations, not to mention the developers themselves who can fix stuff and deploy it faster.

[Letterbox]

Doesn't necessarily mean beta testers missed it, though. With AD's fixed schedule its no secret all sorts of bugs make it to the official release.

Yea, that's a fair point. I don't know what stops the developers from implementing online update system. It would be even simpler for testers to test builds without reinstallations, not to mention the developers themselves who can fix stuff and deploy it faster.

While its certainly possible to build an updater, or use windows update itself, the problem comes with making sure that people don't update what could be a production machine, otherwise you've got to have a roll back feature, which just adds more work. Then you'd need a separate updater for linux as well. Then you have to manage and support those programs. Also you have to be careful and not allow 'selective' updates, otherwise fix's that you thought were there aren't. And as for an iso image, that can be installed into whatever directory you want, that might give registry entries issues, if you install it with another version in place, which could be the cause of the errors, not the actual program itself.

So a complete installer (just for softimage, not the ancillary programs), which you 'must' use on a seperate machine, that checks if softimage is install and removes it first, would be a better and cleaner solution all round, specially when tracking and eradicating bugs, because your ensuring that the machine is in a clean a state as possible - before users start looking for them.

[iamVFX]

Doesn't necessarily mean beta testers missed it, though. With AD's fixed schedule its no secret all sorts of bugs make it to the official release.

Yea, that's a fair point. I don't know what stops the developers from implementing online update system. It would be even simpler for testers to test builds without reinstallations, not to mention the developers themselves who can fix stuff and deploy it faster.

While its certainly possible to build an updater, or use windows update itself, the problem comes with making sure that people don't update what could be a production machine, otherwise you've got to have a roll back feature, which just adds more work. Then you'd need a separate updater for linux as well. Then you have to manage and support those programs. Also you have to be careful and not allow 'selective' updates, otherwise fix's that you thought were there aren't. And as for an iso image, that can be installed into whatever directory you want, that might give registry entries issues, if you install it with another version in place, which could be the cause of the errors, not the actual program itself.

Imagine Steam or Firefox or other software which is used on a daily basis have manual installation process for every update as it is for AD products now - would they be so popular for such a wide audience? I get your point, Chris, it's a lot of work to make it flawless, but online updates already approved themselves by larger companies, such as Adobe, and if Autodesk want to join the "big club" I think it's a way in the right direction. I feel I have to note here: cloud the entire application is not gonna help users, IMO, since they will be limited by the fact that their application won't work without internet connection or in case of server downs.