I don't believe you're hurting yourself having both. I'm pretty sure that having all configurations instead, using some of them to suppress components instead of hiding them with configurations, would increase file sizes.
Totally Agree. Config is the best for your drawing while display state is for viewing or rendering options
Display states + configurations = lots of headaches.
I use display states to differentiate assembly steps/rendering. I hide the parts I don't want for the views. Then I create exploded views with the visible parts for assembly instructions.
I find display states to be more stable than configurations just for the simple fact that you don't have to deal with mates being suppressed/different. I have gotten away from configurations because of the "trees of blood" you'd get if people aren't doing things correctly.
"Trees of Blood" - I like that analogy - totally agree with the configurations - we parted ways as well. One level deep is ok to a point, but start going sub-assembly inside another sub-assembly inside another.............. that's when things really slow down, plus never ever cleanly rebuild, plus put in a circular rebuild in your sketches, the blue wheel will just keep spinning.
I know our workflow is a lot different then job shop or even a custom design shop, I would rather use the save as copy or pack & go long before I pile up on the configurations...
Sloppy equations and sloppy configurations are nothing but trouble down the road...
I get a little annoyed at times knowing there are posts like this out there and SolidWorks folks don't chime in. How about instead of posting about feature enhancement requests, SW guys looked at posts like this.
Really, which is lighter on the SW software, configurations or display states?
It used to be Display States were lighter, but not since 2017 just puked all over performance.
When can we have stable performance back from 2017?
I can't turn down my drawings any more.