Autodesk Inventor

[#1]

It's times like these I regret ever switching - give me back my Solidworks anyday...

Regards.

[#2]

Let's give them a moment: Chris wrote that today the update will come. Then we'll see

[#3]

We discovered a couple of install/uninstall issues with this specific update; we now hope to release it by the end of this week, subject to further testing, etc.

Thanks,
Chris

[#4]

As I said  - give me back my Solidworks anyday...

[#5]

Chris, the end of the week came.

The service pack did not.

It's two months that we are going ahead with this joke now.

Since the announcement that in inv2013 the piping module would be available in all Premium packages we have invested a lot of resources in creating our piping library (more or less 250.000 components) in order to be able to use the piping module on each workstation. This was not possible, and we suffered a relevant damage from that.

We would like to have the payment for our subscriptions 2013 to be considerd for the 2014 release, since it was not possible to use the 2013.

[#6]

By any chance will this update include a cure for the famous "I'm going to make 47 copies of this material all with a generic appearance and a .n after the name" bug?

[#7]

Massimo,

I'm sorry, but you are correct - the Update is not going to be released today; I mention below that we hoped to release it subject to outcome of testing. However, we encountered some issues in testing it internally, this week, so it'll be a while longer yet. I'll provide an update when it's available.

Regarding your final statement, that's something well out of my control/influence & is something that you can only really discuss with your local Autodesk Sales contact or Reseller.

Mike,

No, that infamous issue is not included in the update that is mentioned here, but it is something that is currently being working on.

Thanks,
Chris

[#8]

Chris, this story is getting unserious: one more week, nothing happened, no news.

[#9]

Dear Autodesk Customers,

I want to thank you for your patience while waiting for this product update to be released.  We continue to review and refine our process to ensure we deliver quality updates as quickly as possible.  Please feel free to provide any feedback on this Update and the process in general.

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=21028655&linkID=9242019

Best regards,

David

[#10]

Dear Chris,

dear David,

I'm sorry: it's not over.

After installing SP1.1u2 inventor became usable.

Nevertheless not all issues related to the new (absurd) material library are working fine.

We are quite highly specialized company, therefore our material library is so extended and customized. Our standard parts are available in several materials (from 4 to 12 materials each family). In total our content center counts a quarter of a million components (ok, about 105.000 are piping elbows, but still a relevant amount), and about 25000 have been created as files (everything working perfectly with 2012).

All our *.idcl files have been migrated from Inv2012SP2 to Inv2013SP1.1u2. No error messages came (our standard parts have multiple materials inside the same family to speed up the workflow when a component must be substituted with another one).

All materials in our library and apperances worked fine. All xml styles were properly set, and no errors came.

All standard parts have been properly migrated (0 failures!!) with the inventor task scheduler after setting up the new environment.
Again: no errors, no warnings at all.

When using on the field the content center, only 2 materials per each family survived. The other 2 to 10 materials are lost. The column MATERIAL of the family table is empty, and all materials must be set once again. I still have not found a pattern to understand why certain materials disappeared and certain remained. I will try to find this pattern in the next days.

Now, as I said, our content center counts almost a quarter of a million parts, so the job is not that easy. Nevertheless it is not possible any more to revert back to 2012, because most of workspace files have been migrated.

And now?