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.
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.
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.
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.
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.
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
I tried to post over on the SW forums, but that was a waste of time. Cannot publish, cannot upload images etc…
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.
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?
So useful!