SW 2022 SP4 EV - first thoughts

SOLIDWORKS SW General
1

I have just downloaded and tested the mirroring function.
I can confirm that the first testing’s of this have finally worked.
I will do more testing, but so far so good on the mirroring bug being resolved.

2

That is some wonderful news, I’m glad to hear they’ve finally adressed a crucial issue, especially one that was inconvenient to you

3

Thanks man.
I will be doing more testing today, and I also want to do some for the Packngo.
Hopefully the issues here have also been addressed.

4

Are you seeing any improvements in terms of response time or overall functionalities now that it’s ‘workable’..? How does it compare to other ‘workable’ versions..?

5

Has this issue been fixed?

https://www.cadforum.net/viewtopic.php?t=1669

6

Hi Glenn,

Yes .. it looks like this issue has also been resolved.

7

I haven’t crashed yet. Performance feels the same so far. its just that some of the features work now where they didn’t before.
I wonder what has been broken in the process.

8

I’ll bite.

Could you confirm that this SPR was fixed?:

SR# – 1-23626682349
SPR# – Description

1194201 - Assemblies - External References, Virtual Components: Virtual Component external references status becomes out of context after parent assembly is renamed

You should be able to tell by seeing if this “search” box is present when you browse to an assembly in windows explorer, RMB, and select “Rename”.

image.png
image.png664×346 160 KB

In 2019 SP.5, when you wanted to rename an assembly, you had the option to check “include virtual components” and then hit “search” . It would then populate the virtual component references in the assembly and make sure they were redirected to the new name ensuring no broken references. This was missing in 2020 - hence the requested SPR.

Thank you.

9

You should be able to tell by seeing if this “search” box is present when you browse to an assembly in windows explorer, RMB, and select “Rename”.

image.png
The search feature appears to have been removed in 2022.

The packngo does work with virtual components with that option turned on and maintains the references.

Hope that helps.

10

Ok, thanks for checking for me. It was supposedly “fixed” in SP.2.

Dear Tyler,

This is a courtesy e-mail to notify you that the following issue, which you reported through your local SolidWorks reseller, is addressed in 2022 b2. This Service Pack is available to download from the following area of the SolidWorks web site:

Please note that this message is sent from an automated mailer program, so please do not reply to this message. If you have any questions concerning the problem you reported, please contact your local SolidWorks reseller.

Thank you for taking the time to report this problem to your reseller, and for helping to make SolidWorks a better product.

Thank you,

Dassault Systèmes SolidWorks Corp. Technical Support

SR# – 1-23626682349
SPR# – Description
-----------------------

1194201 - Assemblies - External References, Virtual Components: Virtual Component external references status becomes out of context after parent assembly is renamed

11

It is fixed, duh! It doesn’t do any bugs anymore, so it’s concidered fixed! :laughing:

12

I suppose it is possible that they were able to “fix” it without the use of the search button that collected all of the virtual component references, but that seems unlikely. I suppose I won’t know until I try it at some point in the future. SP5 perhaps.

13

Is there any idea of when SP4.0 will drop?

Thanks

14

its normally only a couple of weeks after the EV drops, which was almost a month ago now. Not sure what the hold up is.

15

I think they’re improving the mirror feature

:laughing:

16

It wouldn’t surprise me. ;;

17

Thanks.

My IT peeps have drug their feet so long on upgrading us to v2022, that I was hoping sp4.0 was out for them to install.

I checked this morning and there was no sign of it.

18

FIFY

19

SP4 is now released in case you haven’t received notification yet.

20

Just tried it out and of course… why would a feature be implemented everywhere already?
Here the downfalls:

The coordinate system planes/axis are not available to pick in all features:|

  • You can not select a custom plane for the bounding box from a coordinate system (but if you make a plane that is coincident with the plane of this coordinate system you can select THAT PLANE!)
  • you can not select the axis of a coordinate system as a reference to add as a texture direction (however if you make a ref. geometry: axis that is coincident with the coordinate system axis you CAN SELECT THE AXIS TO DO THIS)