How is everyone liking Solidworks 2022 SP1?

[Bradfordzzz]

How is this working for you?

Wanting to take the leap ... but nervous.

[AlexLachance]

Haven't tried it and don't know on which you are but I'd advise you to not do so and wait it out a bit. 2022 doesn't seem any better then 2021 so far and 2021 was a disgrace of a release for a company to have and leave as is.

[Damo]

I am still trialling 2022. It was a desperation move in the hopes of some improvements. 2021 truly was terrible. I had multiple issues with stability.
But so far, noticeably less broken mates and crashes in 2022 than 2021. It's still too early to really tell at this stage.

But at least they've put the "Save All" Button back where it belongs in the Save Icon Dropdown..
2021

2022

A promising sign to be sure.
You would not believe how often my own muscle memory would betray me.. And I would wait for the Publish to eDrawings dialog to open just so I could close it and move on .. All the while shaking my fists at the sky..
That is soooo frustrating that they would just change this for no good reason I can think of..

But.... I am still experiencing annoying graphics glitches in drawings. Have done since about 2016.. No end of frustration in sight..

(This has plagued me thru multiple versions and across several PC's.
Others among you must have seen this issue too.. )

[Bradfordzzz]

I was hoping the 2022 would at the very least be better than this train wreck 2021, but I'm thinking it might be better the devil you know.

[Glenn Schroeder]

I'm still using SW2022 sp 0, but I have no complaints. I will qualify that by saying I rarely suffer the stability and/or slow issues other people report.

[Damo]

I was hoping the 2022 would at the very least be better than this train wreck 2021, but I'm thinking it might be better the devil you know.

Brad, What version are you currently using..?

[tsmith]

I am still experiencing annoying graphics glitches in drawings. Have done since about 2016.. No end of frustration in sight..
Graphics Glitch.png


(This has plagued me thru multiple versions and across several PC's.
Others among you must have seen this issue too.. )

Same here, been looking for a solution for my team. It's random for us, sometimes there and others not, we've even taken to doing multiple 'save as pdf' and 'print as pdf' and then editing a full 'clean' drawing pack back together. Even busted out photoshop last week to fix a drawing.

We also jiggle the 'draft' and 'high quality' radio button as that will sometimes shake the tree enough to get it to subside. Full restarts and other black magic also are inconsistent solutions.

It happens on multiple machines, of various configs, with the same file and different files, as well as with a variety of pdf print drivers, including windows default, bluebeam, adobe, and the SW provided version of adobe which tells me it's something to do with how SW converts the file before 'printing' or 'exporting'.

You'd think this would be an important thing to fix.

OH, and back on track, using 2022 SP1, but I've had this problem off and on since 2018.

[Damo]

Same here, been looking for a solution for my team. It's random for us, sometimes there and others not, we've even taken to doing multiple 'save as pdf' and 'print as pdf' and then editing a full 'clean' drawing pack back together. Even busted out photoshop last week to fix a drawing.

We also jiggle the 'draft' and 'high quality' radio button as that will sometimes shake the tree enough to get it to subside. Full restarts and other black magic also are inconsistent solutions.

It happens on multiple machines, of various configs, with the same file and different files, as well as with a variety of pdf print drivers, including windows default, bluebeam, adobe, and the SW provided version of adobe which tells me it's something to do with how SW converts the file before 'printing' or 'exporting'.

You'd think this would be an important thing to fix.

OH, and back on track, using 2022 SP1, but I've had this problem off and on since 2018.

Sometimes just switching from HLR to HLV, or shaded, can do the trick.. But not often..
The official workaround I was given is to open the model from within the offending view, do a full rebuild, return to drawing and rebuild. As this "mostly" does the trick, it is minimal "business impact" and no further action seems required from developers. And so I deal with it.

For me it happens intermittently, but too frequently, when I copy a view in attempt to alter the display state demonstrating next assembly steps..
It happens in some multi-body parts too.. But likely for different reasons.

Wow... Busting out photoshop is an interesting workaround..

[Bradfordzzz]

Brad, What version are you currently using..?

2021 SP5.1 ... which i why i want to switch so bad ... which is also why i am so hesitant.

[Damo]

2021 SP5.1 ... which i why i want to switch so bad ... which is also why i am so hesitant.

yeah.. I'm feeling that. I updated out of desperation..
But, to be fair, 2022 is no worse. And I find I am crashing a lot less..

[Bradfordzzz]

yeah.. I'm feeling that. I updated out of desperation..
But, to be fair, 2022 is no worse. And I find I am crashing a lot less..

Thats very helpful information. I am hoping to crash less .. thats for damn sure.

[ellundo]

Our group is making the jump this week. We skipped SW2021 and are moving up from SW 2020 which for us hasn't been to bad once we got to SP5.

[SPerman]

Please give us an update after you get settled in. I'm still on 2020, and I am waiting for more feedback on 2022 before making the move.

[Alin]

If you use drawings, upgrading to SW 2022 is a must for two reasons:
1. Graphics acceleration (10 to 50 times faster viewport refresh rate than SW 2021)
2. Saving detailing data is now a document setting. You can uncheck that option for the drawing templates, to ensure all your small drawings have small file sizes and save fast and check it only for the large drawings to ensure that you can use the detailing mode for them.

There are several important enhancements that could make certain users upgrade sooner rather than later:

• https://www.engineersrule.com/fast-draw ... ssemblies/

• https://www.engineersrule.com/coordinat ... -and-axes/

• https://www.engineersrule.com/quick-and ... on-tables/

Based on my personal experience and from what I see when working with clients, SW2022 SP1.0 is pretty much bomb proof compared to the same early SPs from older versions. Crashes are very rare on certified hardware.

[Glenn Schroeder]

If you use drawings, upgrading to SW 2022 is a must for two reasons:
1. Graphics acceleration (10 to 50 times faster viewport refresh rate than SW 2021)
2. Saving detailing data is now a document setting. You can uncheck that option for the drawing templates, to ensure all your small drawings have small file sizes and save fast and check it only for the large drawings to ensure that you can use the detailing mode for them.

There are several important enhancements that could make certain users upgrade sooner rather than later:

• https://www.engineersrule.com/fast-draw ... ssemblies/

• https://www.engineersrule.com/coordinat ... -and-axes/

• https://www.engineersrule.com/quick-and ... on-tables/

Based on my personal experience and from what I see when working with clients, SW2022 SP1.0 is pretty much bomb proof compared to the same early SPs from older versions. Crashes are very rare on certified hardware.

@Alin,

The third one in your list is one I'm enjoying.

Are you going to write one about this: http://help.solidworks.com/2022/English ... cef350#Pg0?

[AlexLachance]

If you use drawings, upgrading to SW 2022 is a must for two reasons:
1. Graphics acceleration (10 to 50 times faster viewport refresh rate than SW 2021)
2. Saving detailing data is now a document setting. You can uncheck that option for the drawing templates, to ensure all your small drawings have small file sizes and save fast and check it only for the large drawings to ensure that you can use the detailing mode for them.

There are several important enhancements that could make certain users upgrade sooner rather than later:

• https://www.engineersrule.com/fast-draw ... ssemblies/

• https://www.engineersrule.com/coordinat ... -and-axes/

• https://www.engineersrule.com/quick-and ... on-tables/

Based on my personal experience and from what I see when working with clients, SW2022 SP1.0 is pretty much bomb proof compared to the same early SPs from older versions. Crashes are very rare on certified hardware.

So, how many bugs have been introduced this time? How many of these features actually work? How many have been broken introducing all these 'features'? Is the "enhanced graphic performance" ever going to work or will it always be a major issue causer?

[Bradfordzzz]

So ... we took the leap this weekend. Today is day one.

So far I have crashed twice opening a file that opens fine in 2021 Sp5.1.

gonna give it a week and get feedback from all of the designers. I will let you know our findings.

[Alin]

@Alin,

The third one in your list is one I'm enjoying.

Are you going to write one about this: http://help.solidworks.com/2022/English ... cef350#Pg0?

You mean this one?

[Glenn Schroeder]

You mean this one?

I watched that when she gave it. I just wondered if you're going to do an article on it.

[Alin]

I watched that when she gave it. I just wondered if you're going to do an article on it.

Thanks for the suggestion. Good one!

[berg_lauritz]

So ... we took the leap this weekend. Today is day one.

So far I have crashed twice opening a file that opens fine in 2021 Sp5.1.

gonna give it a week and get feedback from all of the designers. I will let you know our findings.

Here for the updates on this one. We have 2021 SP4 and we are not really happy.... 2022 introduces the coordinate systems which will be a must have for our automation plans. So in about 10 weeks we want to update...

[Alin]

So, how many bugs have been introduced this time? How many of these features actually work? How many have been broken introducing all these 'features'? Is the "enhanced graphic performance" ever going to work or will it always be a major issue causer?

Lots of rhetorical questions above.
I have the "enhanced graphics performance" checked and I have not encountered major issues in SP1.0.

[Bradfordzzz]

Mirroring issue with Solidworks 2022 SP1

Here is the preview (settings are identical to the settings used in Solidworks 2021 Sp5.1

Here is the result

This has occurred on 4 different computers.
all using the same settings, and all settings have been verified to the settings of Solidworks 2021 Sp5.1

Any ideas?

[AlexB]

I'm also following this one. We haven't been super happy with the handling of large assemblies in 2021 SP5.1. We upgraded from 2018 SP5 and everything was great there and working as expected.

Previously, when a component is suppressed, its mates get suppressed with it. This is useful in configurations so you don't have to suppress all the mates with the part you're suppressing.

Now, several of our assemblies have suppressed sub-assemblies. However, the mates associated with these suppressed sub-assemblies are throwing an error and it's driving me crazy that something so simple is so broken.

I'll likely download 2022 and start playing around with it to see what has changed and if the upgrade is worth it on our end. The only issue is implementing this (I believe) requires a global PDM update, which is a huge headache.

With that said, are there any known problems or must-have performance improvements with PDM 2022 that users have noticed?

[AlexLachance]

Lots of rhetorical questions above.
I have the "enhanced graphics performance" checked and I have not encountered major issues in SP1.0.

Rhetorical, but still valid though. 2021 is a great example, prove me wrong.

[Frank_Oostendorp]

Lots of rhetorical questions above.
I have the "enhanced graphics performance" checked and I have not encountered major issues in SP1.0.

All depends on what you call major. What minor issues did you encounter, Alin?

[zxys001]

So, how many bugs have been introduced this time? How many of these features actually work? How many have been broken introducing all these 'features'? Is the "enhanced graphic performance" ever going to work or will it always be a major issue causer?

..what bugs?

[Alin]

All depends on what you call major. What minor issues did you encounter, Alin?

In SP0, sometimes after closing Assembly Visualization, some components of the assembly are shown in wireframe. A CTRL+Q refreshes the graphics data.
Have not yet encountered this problem in SP1.0. Will let you know if I experience such issues again.

[Alin]

Rhetorical, but still valid though. 2021 is a great example, prove me wrong.

Why would I prove you wrong? As our great PM likes to say... everyone experiences things differently.

Joke aside, let's talk specifics (ideally one at a time). Tell me what does not work well in 2021 and we can try to repro in 2022.

[Alin]

Now, several of our assemblies have suppressed sub-assemblies. However, the mates associated with these suppressed sub-assemblies are throwing an error and it's driving me crazy that something so simple is so broken.

Please do not get crazy. Try this pill:

[AlexLachance]

Why would I prove you wrong? As our great PM likes to say... everyone experiences things differently.

Joke aside, let's talk specifics (ideally one at a time). Tell me what does not work well in 2021 and we can try to repro in 2022.

It's easier to list what works then what doesn't from all the things I've read. I didn't have the time to troubleshoot the program so I didn't bother moving to it, just like I'm not on 2022 right now and probably won't move to it, unless there's a major improvement.

Your article showing all the top10 ideas that have been implemented is pretty cool, but it's pretty sad that you had to go back up to 20 years for the percentage to be reasonably high. If you look at the past 10 years, there's barely 50% of the top10 implemented.

I know you're a VAR, trust me I'm as passionate about SolidWorks as you are, but the state it is in is unacceptable and defending it in anyway is simply counter-productive.

[AlexB]

Please do not get crazy. Try this pill:

image.png

Hi @Alin,

I did check that box, but unfortunately it will never produce any errors even if there are supposed to be (in my opinion). For example, if I delete the component but its mates weren't deleted with it, I'd like to know if there's an error of missing mate references. Unchecking this box will ignore those cases as well.

This worked as expected in 2018 and I'm not sure why the functionality changed so drastically with it.

[Alin]

Hi @Alin,

I did check that box, but unfortunately it will never produce any errors even if there are supposed to be (in my opinion). For example, if I delete the component but its mates weren't deleted with it, I'd like to know if there's an error of missing mate references. Unchecking this box will ignore those cases as well.

This worked as expected in 2018 and I'm not sure why the functionality changed so drastically with it.

When you delete a component, without deleting its children (that includes its mates), those mates can be represented as suppressed or with errors. That is what that option is all about.

That being said, there is a much better way to display the various states for the mates. Simply RMB on the Mates folder and choose "Group mates by status".

The mates will be grouped in folders like:

• Solved

• Errors

• Over Defined

• Suppressed

• Suppressed (Missing)

[Alin]

I know you're a VAR, trust me I'm as passionate about SolidWorks as you are, but the state it is in is unacceptable and defending it in anyway is simply counter-productive.

I am not defending anything; I simply like to talk specifics. Simply stating that SW sucks or that the new version is worse than the previous one is interesting information, but that's about it. It cannot be used as a base for a constructive discussion.

It's easier to list what works then what doesn't from all the things I've read.

I'll bite. What works?

[AlexB]

That being said, there is a much better way to display the various states for the mates. Simply RMB on the Mates folder and choose "Group mates by status".

@Alin That's something I haven't seen before. I think that should mostly solve this issue. I appreciate the continued insight you provide, thanks!

[Glenn Schroeder]

Hi @Alin,

I did check that box, but unfortunately it will never produce any errors even if there are supposed to be (in my opinion). For example, if I delete the component but its mates weren't deleted with it, I'd like to know if there's an error of missing mate references. Unchecking this box will ignore those cases as well.

This worked as expected in 2018 and I'm not sure why the functionality changed so drastically with it.

I believe you said above that when you suppress a component its mates aren't being suppressed, but are showing errors. I can't help you with that, but maybe I can help with mates when you delete a component. When you delete a component you should be getting this dialog box.

image.png (16.38 KiB) Viewed 20396 times

If the "Delete child features" box is selected, like in the screenshot, then the mates involving this component will also be deleted. If that box isn't checked then the mates won't be deleted, and will show an error.

If you aren't getting this dialog box then check for dismissed messages, and turn it back on. While I will readily complain about messages that don't have a "Don't show again" box and should, in my opinion the Confirm Delete dialog box shouldn't have that option. There are too many situations where you may or may not want certain options when deleting that this one should stay active.

[AlexLachance]

I'll bite. What works?

There was a new feature introduced in 2021 that I read about but unfortunately do not recall exactly what it is that worked wonderfully and answered a lot of people's needs. I think I had read about it in one of your articles and then saw more people talking about it, but my memory's not top right now.


That being said, there's been plenty of constructive criticism made that has yet to be answered, their platform is another great example. How long will it take them to get the DS tag next to DS representatives? That must be one heck of a feature to introduce for it to take this much time, if it isn't I can't imagine how much time something that demands work would take.

[dave.laban]

So this bug (SPR 1034006) was apparently fixed in 2022 A1, can anyone confirm?

1. Insert a hole callout in a drawing for a countersunk hole:

2. Use the dropdowns to change only the precision of the angle (I don't need the trailing zeroes).

3. Watch and be infuriated as all the parameters are changed to match the precision set on the angle, so you have to go in and manually update the precision on the other two parameters too.

I'm also awaiting fixes for the following bugs but don't know if the performance has changed / improved since 2019 that I'm still on anyway.

SPR 480273: 'Combine same sizes' does not group all holes of same size in hole table
SPR 1120901: Flag note gets dangled when attaching to the balloon, if 'Balloons per Line' property is changed in the same command.
SPR 1129914: *Generic* Jogged ordinate dimensions inserted by Model Items - do not keep alignment in the ordinate chain for the rotated views
SPR 1131390: Filter to display shaded cosmetic threads in Document Properties is toggled off by turning off Hide/Show > Hide All Types
SPR 1160483: Changes in the Unit Precision settings of combined hole data in the Hole Table do not propagate to individual holes after disabling 'Combine same tags' (or 'Combine same size') option

[AlexB]

Watch and be infuriated as all the parameters are changed to match the precision set on the angle, so you have to go in and manually update the precision on the other two parameters too.

I've run into this too for a hydraulic manifold with so... many... hole callouts. It seems to me that once that is changed, only the "Thread Description" follows it. I was able to go in and get all the other parameters to have different precision, but the Angle and Thread Description always matched. It's tedious, but I did end up getting it to work okay. But yes, I really hope it's fixed in upcoming versions.

[AlexLachance]

So this bug (SPR 1034006) was apparently fixed in 2022 A1, can anyone confirm?

1. Insert a hole callout in a drawing for a countersunk hole:
image.png

2. Use the dropdowns to change only the precision of the angle (I don't need the trailing zeroes).
image.png

3. Watch and be infuriated as all the parameters are changed to match the precision set on the angle, so you have to go in and manually update the precision on the other two parameters too.
image.png


I'm also awaiting fixes for the following bugs but don't know if the performance has changed / improved since 2019 that I'm still on anyway.

SPR 480273: 'Combine same sizes' does not group all holes of same size in hole table
SPR 1120901: Flag note gets dangled when attaching to the balloon, if 'Balloons per Line' property is changed in the same command.
SPR 1129914: *Generic* Jogged ordinate dimensions inserted by Model Items - do not keep alignment in the ordinate chain for the rotated views
SPR 1131390: Filter to display shaded cosmetic threads in Document Properties is toggled off by turning off Hide/Show > Hide All Types
SPR 1160483: Changes in the Unit Precision settings of combined hole data in the Hole Table do not propagate to individual holes after disabling 'Combine same tags' (or 'Combine same size') option

In 2 years, you should get an e-mail to tell you these SPR's have been closed, but fear not, they will not be fixed.

[Alin]

So this bug (SPR 1034006) was apparently fixed in 2022 A1, can anyone confirm?

Confirmed.

[dave.laban]

Super, thanks.

[Glenn Schroeder]

This is probably the most annoying thing I've found with 2022: https://www.cadforum.net/viewtopic.php?t=1669

[Alin]

This is probably the most annoying thing I've found with 2022: https://www.cadforum.net/viewtopic.php?t=1669

[Glenn Schroeder]

image.png

Thanks @Alin . If they fix that and the terrible workflow for the new temporary axis selection I'll be a happy old man.

[Frank_Oostendorp]

In SP0, sometimes after closing Assembly Visualization, some components of the assembly are shown in wireframe. A CTRL+Q refreshes the graphics data.
Have not yet encountered this problem in SP1.0. Will let you know if I experience such issues again.

Would you like a list of items I still think are a major issue in SolidWorks 2022 SP 0.0? (Still have to start testing SP1.0)
A. 4K display with SolidWorks 2022 SP0.0 and Windows 10
- Depending on settings, only part of text is shown in the menu.
(All certified hardware in use, correct drivers installed.)
(Probably blame Microsoft for this? But other software I use do not show these effects.)

[Bradfordzzz]

Be advised !

* Mirroring is broken in Solidworks 2022 SP1 *

Our VAR is investigating further now.

[Frank_Oostendorp]

Be advised !

* Mirroring is broken in Solidworks 2022 SP1 *

Our VAR is investigating further now.

Just a minor issue. Is it mirror in sketch, mirror feature in part, mirror part in assembly or all of these?
All work fine in SolidWorks 2022 SP0.0.

[Bradfordzzz]

Just a minor issue. Is it mirror in sketch, mirror feature in part, mirror part in assembly or all of these?
All work fine in SolidWorks 2022 SP0.0.

Mirror feature in part seems to be working, but mirror parts in an assembly and mirror sketch in assembly have issues.

[HDS]

I have seen Windows 10 do this in the included programs and OS. So Microsoft has the same problem. Regardless SW will have to fix it instead of waiting for MS.

Would you like a list of items I still think are a major issue in SolidWorks 2022 SP 0.0? (Still have to start testing SP1.0)
A. 4K display with SolidWorks 2022 SP0.0 and Windows 10
- Depending on settings, only part of text is shown in the menu.
(All certified hardware in use, correct drivers installed.)
(Probably blame Microsoft for this? But other software I use do not show these effects.)