SP3

[Uncle_Hairball]

In case you missed it, D'assault has finally released SP3.

[Glenn Schroeder]

Thanks. If I get bored I may download it, but sp 0.1 is working pretty well for me.

[Ronan]

I just installed it. Finally moving to SW 2023. Was on a training course last week on SW motion and that was being run on SP2.1 and was pretty stable. So will let you know how it goes.

[AlexLachance]

I'll be following this thread closely as we'll soon be getting our server upgrade and then upgrading SolidWorks to 2022 or 2023 depending on the comments that come out from SP3.

[TTevolve]

I kept getting solidworks background downloader telling me I have the update yesterday, I turned it off after the 7th or 8th time it popped up the message.

[SPerman]

Solidworks has ruined me. I have no confidence that SPn+1 is going to be any better than SPn. Things will be fixed. Other things will be broken. I'm not sure when I will be brave enough to upgrade from 2022. (Which has plenty of issues, but I know what they are.)

[AlexLachance]

Solidworks has ruined me. I have no confidence that SPn+1 is going to be any better than SPn. Things will be fixed. Other things will be broken. I'm not sure when I will be brave enough to upgrade from 2022. (Which has plenty of issues, but I know what they are.)

You're on 2022, you're in no hurry to upgrade. We're on 2019 which is why we are updating.

In my opinion, I don't think it's worth upgrading from one version to another unless you have some significant issues. It is worth to upgrade when your version is starting to be out-dated(3 to 5 years).

[SPerman]

If I had my druthers, I would still be on 2018.

[AlexLachance]

If I had my druthers, I would still be on 2018.

I'd stay on 2019 if we could but CustomTools 2024 won't be compatible with SW 2019.. The kind of little things that forces updates :/

[bnemec]

I'd stay on 2019 if we could but CustomTools 2024 won't be compatible with SW 2019.. The kind of little things that forces updates :/

Doesn't sound very custom if you cannot keep the version of SW you want.

Edit: clarified later the version is forced by DSS and the "Gold Partner" stuff. So it's as custom as the creator can keep it.

[AlexLachance]

Doesn't sound very custom if you cannot keep the version of SW you want.

I believe it's an obligation if they want to remain "gold partners" or something along that line.

[bnemec]

I believe it's an obligation if they want to remain "gold partners" or something along that line.

Ah yes. That makes sense.

[mattpeneguy]

We're finally moving to Windows 10. Does anybody know what the fix between SP2 and SP2.1 was?
Being on Windows 7 I can't run the installation manager and grab SP2.1, but we've got SP2 because I downloaded it at home and brought it on a USB drive.
We're definitely not going to SP3 until it gets some real world experience...I've seen the horror stories.

[zwei]

I too would like to stay on 2018 if not because of our PDM no longer support older version..

Recent version of SWx just break too much of their existing of core functionality...

[bnemec]

2019 was current when we switched to SW so that's what we have; I wish we would have used 2018. Actually, no, in hindsight I wish we would have not switched CAD systems, but anyway. I'm seriously considering updating PDM to 2023 and leaving CAD at 2019 for a while. There are a few enhancements in PDM that I think will be helpful. CAD, not so much.

[Hansjoerg]

....updating PDM to 2023 and leaving CAD at 2019 for a while

Four Versions between PDM and SWX? Is that possible? Is there not a limit of max. 3 Versions ?

[jcapriotti]

....updating PDM to 2023 and leaving CAD at 2019 for a while

Four Versions between PDM and SWX? Is that possible? Is there not a limit of max. 3 Versions ?

Officially no. I've been told it works, you just won't get much in the way of support. We are testing the same now where I work, 2023 PDM with SolidWorks 2019.

[AlexB]

Officially no. I've been told it works, you just won't get much in the way of support. We are testing the same now where I work, 2023 PDM with SolidWorks 2019.

I think the confusion is with the compatibility of the PDM Add-in for Solidworks. As long as the PDM version of the client installed matches the PDM version on the server, there should be no issues. The add-in within Solidworks just isn't supported to work past like 2? versions and may force itself to be disabled. Using PDM via the Explorer window will definitely still work.

[jcapriotti]

I think the confusion is with the compatibility of the PDM Add-in for Solidworks. As long as the PDM version of the client installed matches the PDM version on the server, there should be no issues. The add-in within Solidworks just isn't supported to work past like 2? versions and may force itself to be disabled. Using PDM via the Explorer window will definitely still work.

You will get the warning when launching SolidWorks. However, so far the add-in seems to work fine. Still testing though.

PDM 2023 sp2.1
SolidWorks 2019 sp5

[AlexLachance]

Not many comments about SP3 yet... Anybody dared..?

[TTevolve]

We have one workstation on SP3.0, have not had any issues that we don't have with SP2.1

I was planning on staying on 2022 for a while, but my boss went and ran the update and didn't change from the default so he got 2023. After he opened a few of our larger assemblies I had no choice. So for 2023 hasn't been to bad. Only thing I have noticed is when opening up a design table in excel I loose the file/edit/view/insert/tools menus across the top of the screen. Supposedly this was fixed in 2023 but it doesn't appear it was.

I definitely like the properties summary box for when you have configurations. Anyone that has properties changing across configurations parts should consider upgrading for that.

[AlexB]

I'm slightly annoyed that modifying random settings via the Admin Installer Settings file don't appear to work reliably still.

What I told it to do:

image.png (2.5 KiB) Viewed 13032 times

What it did:

image.png (1.97 KiB) Viewed 13032 times

It's like they're actively trying to make this way more difficult than it needs to be.

[Glenn Schroeder]

Thanks. If I get bored I may download it, but sp 0.1 is working pretty well for me.

I had time last week so downloaded and installed it. So far so good on a very brief sample.

As most of you probably know, when SW2022 (I think) came out it introduced a bug in Pack and Go where if you re-named Parts during the process the new Assembly would reference the old files instead of the new, renamed ones.

That bit me again last week while I was still on sp 0.1. After installing it I tried again and it worked like it was supposed to. I'm not getting too excited yet, but it gives me hope.

[DennisD]

I had time last week so downloaded and installed it. So far so good on a very brief sample.

As most of you probably know, when SW2022 (I think) came out it introduced a bug in Pack and Go where if you re-named Parts during the process the new Assembly would reference the old files instead of the new, renamed ones.

That bit me again last week while I was still on sp 0.1. After installing it I tried again and it worked like it was supposed to. I'm not getting too excited yet, but it gives me hope.

@Glenn Schroeder, was that bug given an SR#? Did the Release Notes for SP3.0 address it? I'm no longer on subscription so I cannot check.

[Glenn Schroeder]

@Glenn Schroeder, was that bug given an SR#? Did the Release Notes for SP3.0 address it? I'm no longer on subscription so I cannot check.

I believe it was given an SR, since I submitted it to my VAR and they could duplicate it. I haven't looked at the release notes. If I get time I will try to get that information.

[TTevolve]

I believe it was given an SR, since I submitted it to my VAR and they could duplicate it. I haven't looked at the release notes. If I get time I will try to get that information.

It was definitely fixed in 2022 SP5.0, I was waiting for that bug to be fixed before I went to 2022 and we straight to sp5 when we installed it back at the beginning of the year.

[Glenn Schroeder]

It was definitely fixed in 2022 SP5.0, I was waiting for that bug to be fixed before I went to 2022 and we straight to sp5 when we installed it back at the beginning of the year.

I'm not disputing that, but if so it got broken again with SW2023 sp 0.1, because it happened to me using that version last week.

[mp3-250]

I'm slightly annoyed that modifying random settings via the Admin Installer Settings file don't appear to work reliably still.

What I told it to do:
image.png
image.png

What it did:
image.png
image.png

It's like they're actively trying to make this way more difficult than it needs to be.

this is why I do it overwriting the registry. color schemes are a bit tricky as if you have say 3 base schemes there are 4 settings groups In the registry: the first one is the "current" which could be based on a selected scheme plus user customizations on single item that superseded the scheme setting.
if you overwrite the registry you hsve real full control, but you must be very careful.

[gristle]

I've just updated to SW2023 SP3 and some surface features are not being named automatically. So far I have Offset srf, Sweep srf, Planar srf and Knit that are not being named. SW is naming them --1, --2, --3 etc. Boundary srf is being named correctly, as is Ruled srf. Has anyone else had this issue?

The top knit in the image was created before I updated, which is the expected behaviour. The bottom knit is the behaviour after updating.

sw2023-sp3-issue.jpg (17.7 KiB) Viewed 12803 times

I tried to post over on the SW forums, but that was a waste of time. Cannot publish, cannot upload images etc...

[blaird]

I can confirm I have the same issue in SW2023 SP3 when creating surfaces. Thankfully I'm only on day 2 of testing here in a standalone environment.

Have you reported to your VAR?

[gristle]

Ok, thanks for confirming.
I tried reinstalling SP3 but that did not help. I've rolled back to SP2.
I'll report to my VAR now.

Edit - reported...

[john@layketool.com]

I haven't noticed anything new that they "broke" during the upgrade to 3.0. One thing they did fix that was driving me was the decimal precision randomly switching to 6 place decimals all of the time.

[Hansjoerg]

Source: https://cadforum.net/viewtopic.php?p=29998#p29998

I found this Bug in another thread in this forum

[Alin]

Ok, thanks for confirming.
I tried reinstalling SP3 but that did not help. I've rolled back to SP2.
I'll report to my VAR now.

Edit - reported...

Known bug: BR10000356957: Surfaces created in 2023 SP3.0 are created with incorrect feature name. (Surface Features are name --1 then --2, etc.

[Alin]

A huge bug in SP3:
BR10000357296: Unable to select through assembly primary planes

[SPerman]

How in the heck do things like this appear in SP3? The whole point of service packs is that they are an improvement over what you already have.

Like I said, I've got Solidworks PTSD. I don't know how I will ever find the courage to try a new version.

[JSculley]

A huge bug in SP3:
BR10000357296: Unable to select through assembly primary planes

Huge? A minor annoyance at best for me. The primary planes are hidden in all my templates.

[Alin]

Huge? A minor annoyance at best for me. The primary planes are hidden in all my templates.

They are hidden in all my files, too. That being said I am using the magic “Q” key to temporarily reveal them when I needed. So useful!

Press Q, select a plane, start a sketch. The plan hides automatically once you clicked out of it.

Or, hover over a component, press Q, select a plane, hover over another, press Q, select a plane, mate, click outside, planes are back to invisible.

Once you use this technique, plus the breadcrumbs, you no longer need the FeatureManager for 95% of the tasks. You see your modeling productivity skyrocketing and you get hooked. That is why this is a major bug for the power-users.

[Glenn Schroeder]

They are hidden in all my files, too. That being said I am using the magic “Q” key to temporarily reveal them when I needed. So useful!

Press Q, select a plane, start a sketch. The plan hides automatically once you clicked out of it.

Or, hover over a component, press Q, select a plane, hover over another, press Q, select a plane, mate, click outside, planes are back to invisible.

Once you use this technique, plus the breadcrumbs, you no longer need the FeatureManager for 95% of the tasks. You see your modeling productivity skyrocketing and you get hooked. That is why this is a major bug for the power-users.

I just learned about that this morning from Betty Baker's weekly email tip. It looks like it will come in very handy for those of us who don't like a bunch of reference geometry in the way all the time, but use planes often for mating. Has it always been a thing, or is that a recent enhancement that zipped right past me?

[Alin]

I just learned about that this morning from Betty Baker's weekly email tip. It looks like it will come in very handy for those of us who don't like a bunch of reference geometry in the way all the time, but use planes often for mating. Has it always been a thing, or is that a recent enhancement that zipped right past me?

New in SW 2023. For SW 2020-2022 users, you can use the Show Primary Planes toggle button (I assigned the "P" key for it).

[Alin]

I just learned about that this morning from Betty Baker's weekly email tip. It looks like it will come in very handy for those of us who don't like a bunch of reference geometry in the way all the time, but use planes often for mating. Has it always been a thing, or is that a recent enhancement that zipped right past me?

Many times I find the "P" key more useful than the "Q". This is an old video recorded before "Q" was a thing.

https://youtu.be/viMRuZs_caw

[acmall]

New in SW 2023. For SW 2020-2022 users, you can use the Show Primary Planes toggle button (I assigned the "P" key for it).

Q to temporarily show planes is working for me in SW2022

[doobes]

This is new:



Is this English?

The DS Offering?

Whiskey Tango Foxtrot?

[AlexLachance]

This is new:



Is this English?

The DS Offering?

Whiskey Tango Foxtrot?

What the heck..?

[bnemec]

This is new:



Is this English?

The DS Offering?

Whiskey Tango Foxtrot?

Goal is to confuse the customer into ignorant non-compliance.

[doobes]

For the curious here are the ELA and the CLOSA documents:

https://agreements.3ds.com/AV0000000361 ... -V12.1.pdf

https://agreements.3ds.com/AV0000000723 ... 13.1.1.pdf

Interesting

[Per S]

This was a nice feature i was looking for a long time. One can see the description name on insert.

[AlexLachance]

Welp, we got our new server, so I'll be testing SP3 on some of our products to see how it handles them and if it's too buggy it'll be 2022 SP5.

[AlexLachance]

Did some tests this weekend, everything seems to be working alright on 2023 SP3 for us. We should be moving to it on friday. Crossed fingers.

[Ronan]

Has anyone seen this is SW 2023 SP3.0

What is _$$ dummy@@_
The files open ok and Ctrl Q does get rid of it.