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
It would be a great idea for Autodesk Team to implement a function that can be set (with a setting) that locks the "Master/Primary" Model State for editing, as it was with the "Level Of Details" in earlier releases.
It would be nice to have the option to 'Lock' one (or more) of the ModelStates, similar (but obviously different) to our ability to Lock a DesignViewRepresentation. Locking only the first one (Master / Primary), if it was an 'option' that could be turned off, would be OK too. But there would have to be at least one other custom one, or we would not be able to change much of anything in the file. And when more than just the one original one exist in the same file, that's when the codes needed for editing it get a lot more complicated.
I'd like to add more friction when creating Model States. I find it too easy to make unintended changes to Model States.
I'd like something like iPart/iAssemblies where I have to select a feature/component/iprop and explicitly add it to the Model State table before I can make any changes.
I just came across this post and am curious as to how far Autodesk is with fixing this bug.
Due to current events, I actually think it's more of a bug than a good idea if you can manipulate all model states. We switched from IV version 2018 to IV version 2024 a few months ago and now I have encountered a problem that would not have existed with a locked main model state. I work in large assemblies with many small auxiliary assemblies (phantom), some of which in turn contain auxiliary assemblies. If for some reason these auxiliary assemblies contain suppressed components that go unnoticed, then my total number of these components in the overall parts list is not correct. To prevent this, there must be a model state that represents all components and cannot be manipulated. Just like the original main detail accuracy.
Locking/unlocking model states would also be perfectly logical. When changing assemblies with several model states, you can currently only select all or one model state. However, I only want to make changes to two out of five model states, for example, and either there is no option to select these two or I lock the model states that should not be affected by the changes.
