What's New: 2022
If you use model states where there are cross-part relationships, changes to the source geometry can cause unexpected results. In these cases, there can be multiple solutions, when one solution is expected. Model States are not recommended in the following cases:
Projected Loop
A model state contains a projected loop from another part where a model state controls the feature size. The loop geometry changes when you edit the size in the source part. This behavior can unexpectedly change the size of features that consume the projected loop.
Frame Generator
In the following image, the model states in SimpleFrame_MS (1) consume the sketch dimensions specified in the active model state of SimpleFrame (2).
The system-generated frame assembly Frame (3) controls the current layout. It contains a copy of the sketch geometry in SimpleFrame. Because model states are not allowed in the frame file, there is no way to synchronize the Frame sketch with the model states in SimpleFrame. The Frame skeleton sketch always reflects the dimensions specified in the currently active model state of SimpleFrame:1.
Because Frame has no awareness of model states, there are multiple solutions when one is expected. This results in unexpected changes in the assembly and drawings created from the assembly.
