The new deployment 'Custom install'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
When introduced last year, the new deployment 'feature' didn't make me happy. Fortunately, it was only for 3DS Max at that time. With the promise this would be the way to go for future releases of most software. Oh boy. So I did some suggestions for improvement. Didn't have much hope for implementation and indeed, they're not.
The most silly omission being the deployment configurations NOT being saved. So every time a change to a deployment is needed, you need to fill out all data again. Now for most programs, this is not such a big thing - most of them don't offer much configuration options anyway. But some programs do, like Revit. So as a work-around, just before clicking the 'Create deployment' button, one just saves the configuration settings to a PDF. Only to find out just the visible part of the webpage is saved. Sigh.
I wonder. What was wrong with the 'old' deployment mechanism? Surely there was room for improvement. The key word being 'improvement'. Was Autodesk overwhelmed with suggestions to fix this thing? Or was there someone at Autodesk who obviously never rolled out a bunch of programs on the office computers who thought this new deployment method was the most fantastic thing ever made?