Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Always while trying to save or open files that I've made that have a fair amount of form driven properties and iLogic rules.
I can close inventor, open inventor, then open the file with no problem.
Does anyone know what this error is for, why it's happening, and how I can avoid it in the future?
PS: it's not just any one file, I've received this error for several different files over the last two versions of Inventor and through all of the updates.
Perhaps you might be able to reproduce this by trying to use some of those sheet metal punches in your model and see if the error happens again. I think one of the IDE features may be corrupt.
Perhaps you might be able to reproduce this by trying to use some of those sheet metal punches in your model and see if the error happens again. I think one of the IDE features may be corrupt.
-shiva
No, they aren't corrupt. Everybody in our department uses the same .ide file, we've been using them for half a decade. 99.9% of files never get this error, it's very rare and unpredictable (almost every file has these punches). We do use a lot of multi-body, multi-level, derived work flows which does make our final models rather complicated.
The punch we use is shown in the attached image. There is a lot of bolting involved in our product.
If you see it next time, please email me (sundarsATautodeskDOTcom) with the dataset and IDE file used. I know exactly where this error is being triggered in the code and it appears to be related to ifeature file. It should be triggered the very first time you try to insert some ifeature and the ifeature seems to have some sort of corrupt information stored in it.
