CAD Forum

Many of my assemblies have exploded views for the guy on the floor building the machines. Every time I open one of those assemblies, it defaults to the exploded view, even though the configuration being shown isn't exploded. Is this normal SW behavior? SW 2022 SP5.

I don't use exploded views very often, but I thought it opened the file in whatever form it was when it was last saved. I assume you collapse it, save, and it still opens exploded?

I opened it from the parent assembly. It opens to the configuration used in that assembly, but the parts are in the position of the exploded configuration, not the one used in the assembly, or shown as selected in the configuration manager.

I could probably create a post like this daily, but chose not to because it rarely leads to anything other than another SPR I'm attached to.

I decided to record a GIF to better show what was going on. I got this instead.

I had to reboot after 10 minutes of waiting. I love SW.

I looked in the KB and there are a few different entries regarding exploded views showing when they shouldn't. I couldn't reproduce any though.

I tried to open my sub-assembly that uses and exploded view from 2021 SP5 and 2022 SP5 and all opened in the collapsed state.

I can only imagine that the offending assembly may have been last saved with the exploded view active. If I think like Solidworks, when you open via the parent assembly, it may not realize that it needs to collapse the exploded view before changing the active configuration to the one you wanted. Even if you open it from your parent assembly, the exploded view still shows.

AlexB wrote: ↑Wed Mar 01, 2023 4:42 pm I can only imagine that the offending assembly may have been last saved with the exploded view active. If I think like Solidworks, when you open via the parent assembly, it may not realize that it needs to collapse the exploded view before changing the active configuration to the one you wanted. Even if you open it from your parent assembly, the exploded view still shows.

You are probably correct. The exploded drawing were the last thing I did in those assemblies.

I still don't understand how this isn't a bug. There is no exploded view for the configuration that is selected. I don't care what state it was in when the file was last saved. If you open a configuration that doesn't have an exploded view, the assembly should not appear exploded.

Here is another one. (This came from a customer, so I don't know the history of this assembly.)

The assembly isn't exploded, but the explode lines are showing.

We were on 2022 SP05 for a couple years and I never experienced any of that behavior personally.

That is definitely strange.