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.

[CCarreiras]

Hi!

Have you tried to check "Adaptatively Used in Assembly" in tools->Documents  Settings?

[johnsonshiue]

Hi! A few possibilities to see this behavior.

1. There were non-master LODs, migrated to Model States on 2022. In the past, a component can remain adaptive in all LODs, since LOD was for memory management, irrelevant to design. But, on 2022, a component can only be adaptive in one Model State.

2. Go to Tools -> App Options -> Assembly -> In-Place Features -> Cross Part Projection -> make sure both boxes are checked.

3. The adaptive components are already adaptive in other assemblies.

Many thanks!

[Anonymous]

Hi,

So this

"1. There were non-master LODs, migrated to Model States on 2022. In the past, a component can remain adaptive in all LODs, since LOD was for memory management, irrelevant to design. But, on 2022, a component can only be adaptive in one Model State"

explains why all projections between assemblies have broken but is there a way of fixing this and enabling all projects again in the master state? 

Thanks

Gary

[johnsonshiue]

Hi Gary,

Inventor 2022 migrates any pre-existing LODs to Model States. In Model States, an adaptive component can only be adaptive in one Model State, not all Model States.

Think of LODs as an assembly in different file loading states. So, the assembly is just one assembly and adaptive works in all LODs since LODs do not change how geometry is computed.

Assembly Model States on the other hand means each Model State can exist independent of others. It does feel like there are multiple assemblies within one iam file.

Do you mind elaborating the workflow that you need to have adaptive works in multiple LODs?

Many thanks!

[Manuelcamposcosta]

@johnsonshiue Are you sure we can have one model state as adaptive? I'm not being able to turn on a single one not even the master.

Inventor 2022.3

[johnsonshiue]

Hi Manuel,

Yes, a component can be adaptive only in one Model State. Also, it can only be adaptive within one iam file. It sounds like the component (part or subassembly) you want to turn on adaptivity is already adaptive in another iam file. Also, if the component itself already has a non-Master (Primary) Model State, adaptive option is removed. This is because the component has to be totally driven by the table, not by anything outside of the file.

Many thanks!

[Manuelcamposcosta]

@johnsonshiue Have a try with the files attached they are from 2022, I'm not being able to make adaptive things in an upper level than the part is.

You are able to make adaptive features on the part 7 from part 10 but not from part 9 I think it's because 10 is on the same level as 7 but 9 is on an upper level

[johnsonshiue]

Hi Manuel,

I must not have followed the instruction correctly. Par9 can be made adaptive without an issue. Did I miss something here?

Many thanks!

[Manuelcamposcosta]

@johnsonshiue 

try to understand what I'm saying from the video, in your image you made  part 9 adaptive, that's another thing that I'm not talking about.

Try to project the hole of part 9 in part 7, you won't be able, because the assembly where the part 7 is has a model state.

Also in my video I show that if you have only one assembly with two parts inside, and one of them has model states you aren't able to make that one adaptive.

https://screencast.autodesk.com/Embed/Timeline/d74602b4-8cf1-4e67-9b9c-ee309daa783a

[johnsonshiue]

Hi Manu,

The reason why when you edit Part7:1, the edge projected from Part9:1 are grounded is because Assembly1:1 cannot be made adaptive. It has a non-Primary Model State. Once the editing part or its hosting subassembly has a non-Primary Model State, Adaptive is disabled.

This is why I keep saying there are many limitations in Adaptive when working with non-Primary Model State. Model State needs to be driven by the table. Any attempt to establish or drive cross-part relationship will hit the wall eventually.

Many thanks!

[Manuelcamposcosta]

@johnsonshiue but you said previously "Yes, a component can be adaptive only in one Model State"

What do you mean by primary? Is it the same as the master?

From my experience model states in parts can't never be adaptive, buy you said something different 

[designing.windcam]

I have the same problem as you told.
When assemblies or parts have only one model state, I can make it adaptive anywhere, even at the same or different level. But when I create another state of the model, adaptability is disabled. If I remove all other model states and leave only Master, the adaptivity reappears.
So I think it's possible to adapt only parts and assemblies with only one model state.
Have you solved this problem?

[johnsonshiue]

Hi Manu,

I think my prior reply was a bit confusing. Let me rephrase it for clarity. Adaptive workflow has two major limitations in Model States as you have seen.

1) When the component (sub or part) has non-Primary Model State, the component itself cannot be made adaptive. The same rule applies to iPart/iAssembly members.

2) In an assembly, a component (sub or part) with only Primary Model State can be adaptive. However, its adaptivity can be active only in one of the Model States in the top-level assembly. This behavior can also be seen in an iAssembly factory containing an adaptive part or subassembly.

If you are seeing otherwise behaviors not described as above, please let me know. We may have a bug here.

As I mentioned earlier, I personally think Model States and Adaptivity are mutually exclusive at the moment. When you attempt to use Adaptive workflows with Model States, you will run into limitations sooner or later. It is because Model States cannot fully dictate Adaptivity. Some relationship needs to be managed outside of the Model State table. I hope this reply provides more clarity.

Many thanks!

[Manuelcamposcosta]

I think you are wrong in the sentence:

"However, its adaptivity can be active only in one of the Model States in the top-level assembly."

When you say in one of the model states it's means there are others than the primary but accordingly to your first point 1) if you have two or more model states there can't be adaptivity, and I'm experiencing that, so I think your first sentence is enough.

Basically there is no room for adaptivity when there are two or more model states, considering the primary counts as one model state.

[johnsonshiue]

Hi Manu,

I think we are going around the circle. The a component (sub or part) has multiple Model States, it loses its ability to become adaptive. When you right click on it in an assembly, the Adaptive option is grayed out. This is what you are seeing.

My statement is about the following. You can try it out and see if I am lying.

1) Open an assembly with a part or create one from scratch.

2) Make the part adaptive.

3) In the assembly, create a new Model State. You will see the part becomes unadaptive.

4) Activate the other Model State. The part will become adaptive.

Many thanks!

[designing.windcam]

You said "4) Activate the other Model State. The part will become adaptive."
So can you send iam file to illustration ?

[johnsonshiue]

Hi Folks,

Absolutely, here is a very simple dataset to show the behavior. The assembly has two Model States and it contains a part. This part can be adaptive in Model State1, while it is not adaptive in Primary (Master).

The same behavior exists in iPart/iAssembly for a long time. As I mentioned earlier, when a component becomes an iPart/iAssembly factory or it has a non-Primary Model State, the table drives changes. Any cross-part relationship becomes tricky.

In this simple case, the part itself cannot have a non-Primary Model State. When you do that within the part itself, it cannot be made Adaptive in any assembly at all.

Many thanks!

[designing.windcam]

I mean model state of component of assembly. Is there any way to create model state of part and keep its adaptability in assembly ?

[johnsonshiue]

Hi! I believe I have mentioned it already that it is not supported. Once the adaptive component itself has a non-Master (non-Primary) Model State, it cannot remain adaptive within the hosting assembly.

Many thanks!