Tube & Pipe assembly with model states?

[J_MacMillan]

Prior to 2022 I could use LODs to control the suppression states of Runs in my Tube and Pipe assembly from the top-level. Is this supported with Model States? I would like to create a model states and control the suppression of certain runs in the tube and pipe assembly, but there is no Model State node in the tube and pipe assembly. Thanks!

[johnsonshiue]

Hi! Unfortunately, Tube&Pipe, Cable&Harness, and Frame Gen partially support Model States. Only Master Model State is allowed. This is a limitation in Adaptive and Derive. Model States does not allow users to drive Adaptive or Derive.

Many thanks!

[GARRYFRASER8394]

I have this issue too, on very large models I now must work only in the master state with tube and pipe

[johnsonshiue]

Hi! To preserve the 2021 and earlier LOD behaviors, particularly when modeling C&H, FrameGen, and T&P , I suggest you use Design View Rep to hide the unneeded components. Also the adaptive solve will be enabled in all Design View Reps.

Many thanks!

[joel.jenks]

Is there any plan to reimplement this functionality with model states? Seems odd to replace LOD with Model states and drop off a big piece of it's functionality..

[johnsonshiue]

Hi Joel,

There is indeed ongoing discussion in terms of how to improve the workflows. INVGEN-66704 was reported to capture the requirement for now.

Many thanks!

[bforner]

Hello,

any progress on improving the use of model states with T&P as of yet?

cheers,

Ben

[johnsonshiue]

Hi Ben,

We continue to hear the need to support Model States in specialized component workflows. However, we don't have a good solution yet. In the meantime, I suggest you look into Design View Rep, whose behavior models are very similar to the traditional LOD.

Many thanks!

[justindelimo]

Hi @johnsonshiue.

For Model State functionality if you suppress a part in a run it loses its adaptivity and the part gets suppressed in all Model State, See If we Autodesk can make the Model state for Tube and pipes to have control as LOD 

[johnsonshiue]

Hi Justin,

The LODs are migrated to Model States in order to preserve the data integrity. However, if you want the LOD-like behaviors on 2022 and later, it is better to use Design View Rep (hiding components as opposed to suppressing components). You could hide components across levels. Also the adaptivity works in all Design View Reps.

Many thanks!

[NeilVK]

Hi @johnsonshiue.

Has there been any progress on this yet?  It is quite frustrating not having this functionality, especially when it was available in LOD.

Thanks Neil

[johnsonshiue]

Hi Neil,

Unfortunately, there isn't a progress on this particular request. I suggest you look into Design View Rep instead of Model States. You are allowed to hide components across levels, just like LOD suppress in the past.

Many thanks!

[bforner]

hey @johnsonshiue 

any progress to report on this at all? using design view reps in large scale T&P models isn't really practical as it uses alot of computing power and makes the whole process very 'clunky' compared to when LOD's were available

Thanks Ben

[johnsonshiue]

Hi Ben,

I wish I could share some update on this. But unfortunately, there isn't significant progress made in this particular request.

Many thanks!

[drosenfeldEAE6D]

I am having a similar issue. In my designs, I need variability in T&P across model states. Changing the view representations does not give changes across different model states. If I have placed in a valve and suppress it in a specific model state, the view representations will vary depending on whichever model state is selected. Simply changing the visibility of a part in the view representation will effect all model states, which is not desirable. And since I cannot suppress individual routes or runs in T&P, only the entire T&P assembly, this means that I essentially need to drop in a T&P assembly for each model state that I have. If one of my designs has 10 different T&P configurations, this means I need to recreate 9 additional T&P assemblies for each model state. Lots of rework and confusing links, especially if i need to generate a BOM from each model state. This is my understanding from how I am going through the T&P and model states so far.