CGPress uses technology like cookies to analyse the number of visitors to our site and how it is navigated. We DO NOT sell or profit from your data beyond displaying inconspicuous adverts relevant to CG artists. It'd really help us out if you could accept the cookies, but of course we appreciate your choice not to share data.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Why is it advocated by Autodesk to do exactly THAT to overcome broken or missing features in 3dsmax 2013?!?
I know it’s a rhetorical question, but it gives them a reason to push subscription.
‘Stay current’ is lot more palatable to marketing, than ‘Hey stick with what works, because we’ll more than likely break something in your workflow in the new release – oops.’
There a bit of technical depth in there. Sales/marketing do not necessarily understand all of this. Even if they were, they wouldn’t have much control over the whole shebang with all third-party plugins. So either case, they pretty much try to get their own part right by adding features and fixing issues in future versions. It is then business as usual and telling the user to stay current. In a way, it’s true that fixes, patched and new version are usually improvements. But that shouldn’t necessarily prompt a customer to jump on the next release – especially in the context of production pipelines.