AnsweredAssumed Answered

Configurations vs Display State

Question asked by Jody Wilkerson on Feb 2, 2011
Latest reply on Feb 15, 2011 by Jody Wilkerson

Like • Show 0 Likes0
Comment • 4

Hi All,

I have a trailer design that has approximately 100-150 parts and sub-assemblies and I am trying to configure our model to cover all of the different options that we can sell it with. My problem is I now have 18 configurations with a couple more to add and the file size is 19M. It appears that each new configuration adds about 1M to the file size. I have had issues with SW crashing when I try switch configurations or just look at the screen wrong. I am concerned that the file is getting too big. I have 12G of RAM but the other users here only have 6G.

I have also set up 4 display states for the fender options so I can turn them show or hide them no matter what configuration I am in.

I guess my real question is "Is it better to set-up different configurations for the different options or just show or hide them with display states?"

I am just getting back into SolidWorks after going to the "Dark Side" of ProE last year with my old job. I am glad to be back in the light of SolidWorks but I never used configurations that much and only for toolbox parts not in assemblies.

Any help or advice would be greatly appreciated.

Have a great day!

Jody

No one else has this question

Outcomes

Jerry Steiger Feb 4, 2011 4:33 PM

Jody,

I don't use Display States much, but my understanding is that they are lighter weight than configurations.

Having said that, your 19MB file is only 1.9% of 1GB, so why worry? I have to admit that one of my compatriots had trouble in his XP32 days opening our 50MB main assembly, but I think it has more to do with the size of the parts, some of which approach or exceed the assembly size. I'm still on XP32 and don't have any trouble opening the assembly.

Jerry Steiger

Actions

Dave Lelonek Feb 5, 2011 6:44 PM

Jody,

I generally use configs when I have different mate requirements or different parts used / not used. One config could contain many display states depending on what you really want to show, especially in drawings.

From my experience, when using display states, I have only altered the visibility and display type of a part(s). Configs are needed if you want to show the door closed verse open so to speak.

So, you could have two configs: Door open, Door closed. But each config could also have a transparent verse solid display state.

I think you already know this but I wanted to point it out. So, if you are only looking to alter the way the model looks, I would use display states. If you need to alter part(s) positions, I would use configs.

Actions

Dwight Livingston Feb 6, 2011 8:55 AM

Jody

18 configurations shouldn't be a problem. To help performance, I'd look first to your mating scheme. SW has to solve mates for each configuration, so if your scheme is complex (advanced mates, parts mating to other parts, parts mating to more than one part, unnecessary mates) you may get your performance problems there.

As to configurations versus display states, I'd also choose according to my plan for documention. I would consider a tabulated drawing, driven by a design table, with a configuration for every possible saleable item. That works best, as long as the table doesn't get too big.

Dwight

Actions

Jody Wilkerson @ Dwight Livingston on Feb 15, 2011 11:08 AM

All,

Thanks for all the help. I ended up with 19 differnt configurations and 4 display states. The display states are used for the fender options so that no matter what configuration I used I could show the different options for the fenders. The file size ended up around 15M after I cleaned it up the model and got rid of the extraneous stuff. I did notice that the file size would change depending on the active configuration when the file was saved.

Dwight,

Thanks for your comments on the complex mates. The mates in this model where very complicated. I tried to simplify them without losing design intent. This seemed to help.

Thanks,

Jody

Actions

4 Replies

Jerry Steiger Feb 4, 2011 4:33 PM
Mark Correct
Correct Answer
Jody,

I don't use Display States much, but my understanding is that they are lighter weight than configurations.

Having said that, your 19MB file is only 1.9% of 1GB, so why worry? I have to admit that one of my compatriots had trouble in his XP32 days opening our 50MB main assembly, but I think it has more to do with the size of the parts, some of which approach or exceed the assembly size. I'm still on XP32 and don't have any trouble opening the assembly.

Jerry Steiger
Like • Show 0 Likes0
Actions
Dave Lelonek Feb 5, 2011 6:44 PM
Mark Correct
Correct Answer
Jody,

I generally use configs when I have different mate requirements or different parts used / not used. One config could contain many display states depending on what you really want to show, especially in drawings.

From my experience, when using display states, I have only altered the visibility and display type of a part(s). Configs are needed if you want to show the door closed verse open so to speak.

So, you could have two configs: Door open, Door closed. But each config could also have a transparent verse solid display state.

I think you already know this but I wanted to point it out. So, if you are only looking to alter the way the model looks, I would use display states. If you need to alter part(s) positions, I would use configs.
Like • Show 0 Likes0
Actions
Dwight Livingston Feb 6, 2011 8:55 AM
Mark Correct
Correct Answer
Jody

18 configurations shouldn't be a problem. To help performance, I'd look first to your mating scheme. SW has to solve mates for each configuration, so if your scheme is complex (advanced mates, parts mating to other parts, parts mating to more than one part, unnecessary mates) you may get your performance problems there.

As to configurations versus display states, I'd also choose according to my plan for documention. I would consider a tabulated drawing, driven by a design table, with a configuration for every possible saleable item. That works best, as long as the table doesn't get too big.

Dwight
Like • Show 0 Likes0
Actions
- Jody Wilkerson @ Dwight Livingston on Feb 15, 2011 11:08 AM
  Mark Correct
  Correct Answer
  All,
  
  Thanks for all the help. I ended up with 19 differnt configurations and 4 display states. The display states are used for the fender options so that no matter what configuration I used I could show the different options for the fenders. The file size ended up around 15M after I cleaned it up the model and got rid of the extraneous stuff. I did notice that the file size would change depending on the active configuration when the file was saved.
  
  Dwight,
  
  Thanks for your comments on the complex mates. The mates in this model where very complicated. I tried to simplify them without losing design intent. This seemed to help.
  
  Thanks,
  
  Jody
  Like • Show 0 Likes0
  Actions

Configurations vs Display State

Outcomes

Related Content

Recommended Content