Inventor 2022 disables adaptive components in assemblies

[KOKAK]

When opening assemblies from previous versions such as 2021 in the new Inventor 2022, all adaptive components appear deactivated, and the option also being impossible to activate their adaptivity. The only solution I have found is to make a copy of each one and replace them with the copy. So if it allows to activate adaptive, but you have to restrict them again.

[designing.windcam]

I already tried with Inventor 2023. The situation is the same. Is there any chance in the future that Inventor will support adaptability for parts with multiple model state , or will the level of detail return?

[johnsonshiue]

Hi! It would be great if Model State fully supports Adaptivity. We are aware of the request but we don't have a good solution yet at the moment.

In terms of reviving LOD, there is no such plan. LOD is a memory management tool. It does not change any design data or model geometry. Although an adaptive component remains adaptive in different LODs, it is because the geometry does not change per LOD. If you migrate existing assembly with LODs to Model States, the geometry should not be different than what it was. If there is a difference, please share the files and workflows. It will be a bug to look into.

The only thing that may cause confusion is that in the past you could activate a non-Master LOD and change parameters (applied to all LODs regardless) and enable adaptive solve. This workflow needs to be changed a bit with Model States. Now, at the top-level, the adaptive component can be adaptive in only one Model State. If you want to keep adaptive relationship alive, you need to activate the Model State where the component is adaptive, make it unadaptive, activate another Model State, and make the component adaptive again.

If the adaptive subassembly itself used to have LODs but now have Model States, the adaptivity is turned off as we discussed earlier. You will need to remove all non-Master (Primary) Model States so that the subassembly can become adaptive again.

Many thanks!

[designing.windcam]

So, can you clearly explain what is the advantage of model state over level of detail?

[CCarreiras]

With model states you can have a behavior similar to an iPart or iAssembly and you can vary the family member into the main files (without creating one different file for each family member). Model states is a newer technology, it will improve in the next updates and versions.... i hope.

[johnsonshiue]

Hi! LOD was a memory management tool for 32-bit Windows. Without changing the design intent, it helps reduce the memory footprint a given assembly. It was never meant to be used as a configuration tool. It merely makes a given component suppressed (unloaded) or unsuppressed (loaded).

Model State helps manage feature, parameters, and properties. All the variations are captured on a table. Each Model State can live independently from another. Each can be documented independently from another. The biggest difference between Model State and iPart/iAssembly is in two fronts. 1) All Model States are within the same file (ipt or iam), as opposed to individual member ipt/iam files. 2) When annotating each Model States, the annotations can be reused much more often than annotating iPart/iAssembly members.

Many thanks!

[djen]

So then those of us who where using Level of Detail to create multiple states of the assembly must now use Model States.  Though this change to Model States in Inventor 2022 does not have some of the features that LOD had.

For me I assemblies which work in Inventor 2020 and prior, yet have broken features in 2022.  This includes iCopy parts which are no longer associative.  I have worked the assemblies in 2022 to the point the iCopy and Assembly will function, though not all changes are correct in other Model States.  For example, I have an iCopy feature that when the width parameter in the assembly changes will adjust the iCopy features length.  The iCopy appears correctly in the Model State that has the feature as adaptive, though in the other Model States the feature is not updated and displayed correctly.

I see the user can select "Toggle Edit Scope" to turn on/off edit all model states, yet there are aspects that should change in all model states, like my adaptive parts, though if I want to suppress a part in one state and not another, if the "Toggle Edit Scope" is turned on this changes all model states.

[johnsonshiue]

Hi! LOD does not alter geometry, which is why adaptive is available in all LODs. Model State does change geometry. As a result, it only supports adaptive for a given component in one Model State, not multiple Model States.

To preserve the LOD-like behavior in 2022 and later, you may want to copy the migrated Model States to Design View Reps. And, the adaptive component will remain adaptive regardless of Design Views.

Many thanks!

[djen]

Hi,

I have added the representations in the assembly to show the components I want to see in each representation.  This has worked ok.  Yet, where I previously could suppress items, it seems in representations if I suppress a part, that part is suppressed in all views, not just the one representation I want to suppress the part in.  Though, I am able to control the visibility for parts in each representation.    

In previous versions, I would use LOD to suppress items I do not altered by some iLogic I have which adds custom iProperties.   When I run the iLogic with the part not visible, the Ilogic custom iProperty is still added to the part. 

Also, I have found that the adaptive components I bring in from previous versions are not adaptive until the iCopy component is opened and additional model states removed from the part.  Only then will the component be adaptive in newer versions of inventor.

[johnsonshiue]

Hi! As discussed earlier, LOD was a memory management tool helping unload documents to boost capacity. It does not alter the design or change the geometry. Adaptive works in all LODs for the exact reason.

On migrating to 2022, LODs have become Model States. In general, there should not be any impact. However, if you want to preserve LOD-like behaviors (particularly in adaptive workflows) in 2022 and later, you may want to copy the Model States to Design Views (or LODs to Design Views). This is because Model State does not fully support Adaptive. In an assembly, a component can only be adaptive in one Model State (unadaptive in others). Also, when the component itself has Model States, its adaptivity will be blocked. This has been discussed in various threads on the forum.

Many thanks!

[davesmith00]

Hi johnson,

Is there an easy way to see if a part is used in another assembly, and has had an adaptive relationship created? a search tool of some sort? I have a part with adaptivity ticked but IS grayed out, and cannot be changed. dispite this, sketch projections within the part from mating parts also apear to not update when changes are made to the mating parts.

[johnsonshiue]

Hi Dave,

The part itself does not know where it is used. It only knows that it is indeed adaptively used somewhere. Only the hosting assembly knows the adaptive part is adaptive. The flag to track such adaptivity in the part is in Tools -> Doc Settings -> Modeling -> "Adaptively used in an assembly." When this option is checked and the hosting assembly does not have a preexisting adaptive relationship with the part, the Adaptive option will be grayed out.

Many thanks!

[davesmith00]

Hi john,

Still havent quite got my head around how this is meant to completely function, im sure your sick of explaining it and ive most likely miss understood something you've already explained...  An example of a typical model workflow for us is we design part in a completed state (Obviously), but then need those parts in 1, 2 or somthimes 3 model states for differant manufacturing stages. and expamle would be a part that need profile cutting with exess stock, then would be followed up buy a milling op then a turning op. my issue is, how can i keep a part adaptive to the model in a completed state and suppress or modify features to accomadate differant stages of manufacture? Many thanks, Dave

[johnsonshiue]

Hi Dave,

The short answer to your question is that there is no workflow to do that using Model State. The geometric change between Model State has to be triggered by parameter change within the document. And, such change needs to  be captured on the table.

For adaptive solve, the parameter change comes from another component or the hosting assembly. Such change cannot be captured on the Model State table. As a result, there is no workflow.

The only solution in this case is to replicate the assembly and the part three times independently. So that each adaptive part is a standalone ipt file.

Many thanks!

[Frank.HallWQLC5]

Hi All,

I'd like to float the idea of having a new option to reset "Adaptively Used In Assembly" after each use. The new option shown below "Always off" would grey out the existing option "Adaptively Used In Assembly" since at it's simplest implementation, it would immediately untick "Adaptively Used In Assembly" after it would normally become ticked.

The effect of this option would be the 'apparent' adaptivity across multiple Model States and should give the end users the experience that they are after.

Cheers,

Frank.

Proposed new option for Adaptivity

Edit: @johnsonshiue, this would effectively automate your earlier comment "If you want to keep adaptive relationship alive, you need to activate the Model State where the component is adaptive, make it unadaptive, activate another Model State, and make the component adaptive again."

[johnsonshiue]

Hi! Many thanks for sharing the thought! At the moment, Model States and Adaptivity have significant limitations. At the assembly level, an adaptive part only allows to be adaptive in one Model State per hosting assembly. Also, if when the adaptive part itself contains a non-Primary Model State, the adaptivity will be disabled.

Thanks again!