2023 SP5 is now available

[Bradfordzzz]

Lets see how this ones goes.

[AlexLachance]

Downloading!

[AlexLachance]

Jesus f*** christ, how hard is it to fix a damn language bug? Requesting a hotfix to my VAR right now.

image.png (21.53 KiB) Viewed 10036 times

[Bradfordzzz]

Jesus f*** christ, how hard is it to fix a damn language bug? Requesting a hotfix to my VAR right now.

image.png

why am i not surprised.

[AlexB]

Jesus f*** christ, how hard is it to fix a damn language bug? Requesting a hotfix to my VAR right now.

image.png

That was a fast download! Sad to see they just keep missing the details

[AlexLachance]

That was a fast download! Sad to see they just keep missing the details

Not too shabby of a connection we have!

[Bradfordzzz]

Not too shabby of a connection we have!
image.png

Really nice !

image.png (29.12 KiB) Viewed 10012 times

[DanPihlaja]

Not too shabby of a connection we have!
image.png

Wow. We are "almost" as good. LOL

[AlexB]

Wow. We are "almost" as good. LOL

image.png

That's about what I'm rolling with. I've at least got my test environment set up for PDM to make sure our workflows and add-ins aren't broken after the update. Working on the admin image to test as well. Should be up and testing this afternoon.

[AlexLachance]

Wow. We are "almost" as good. LOL

image.png

My home is at 150MB download and 25MB upload and that's ample enough for my needs. Being in one of the regions with the most SMB in Canada has that advantage. My collegue with 6 kids has a 1.2GB download for his home connection which I find absurd

[Frederick_Law]

Jesus f*** christ, how hard is it to fix a damn language bug? Requesting a hotfix to my VAR right now.

Lost in translation .....

[AlexLachance]

So far, none of the bugs we reported are fixed and there is no distinctive difference between SP4 and SP5.

[AlexB]

I would have liked to see the Admin Image settings file working but the bug(s) still exist to where it won't remember some of the options I'm selecting. Oh well, guess I have to go through the hassle of writing my own common settings script to go along with the one I made for PDM settings.

This is so user friendly for admins

[SPerman]

Can anyone check and see if they've unbroken the display of configuration names and part descriptions?

I'm not sure this ever made it onto SW radar. I was given an SR, but can't find it on the platform.

viewtopic.php?p=23859&hilit=2022#p23859

[zxys001]

Jesus f*** christ, how hard is it to fix a damn language bug? Requesting a hotfix to my VAR right now.

image.png

[AlexB]

Can anyone check and see if they've unbroken the display of configuration names and part descriptions?

I'm not sure this ever made it onto SW radar. I was given an SR, but can't find it on the platform.

viewtopic.php?p=23859&hilit=2022#p23859

Still the same it seems

[mp3-250]

Obviously the recent wave of windows 11 updates that broke explorer inside the PDM vault is not going tobe addressed and make it even to SP5.

And it is going to be even harder to keep PDM workIng under old Sw versions as wIndows 10 support comes to an end.

viewtopic.php?t=3051

[mp3-250]

I would have liked to see the Admin Image settings file working but the bug(s) still exist to where it won't remember some of the options I'm selecting. Oh well, guess I have to go through the hassle of writing my own common settings script to go along with the one I made for PDM settings.

This is so user friendly for admins

Those options do not cover basic settings like color schemes, and many others so I have to go down the SW hell of registry again... a minefield.
User interface show different options depending on the environment (drawings, modelling assembly) it seems. 2023 and stil a mess of settings, configuration files, mysterious templates (solidworks 98 beta ones still around and kicking)

[mp3-250]

Jesus f*** christ, how hard is it to fix a damn language bug? Requesting a hotfix to my VAR right now.

image.png

@AlexLachance consider you are very lucky.
with asian languages they keep to break things every odd version. like edrawings export that shown a placeholder name instead of double byte characters for assy components.

like assy01, 02, 03 ...part01, 02.. instead of your real names and descriptions.

"sorry no fix until next version" they said.

coming from siemens nx, sw is such a clown show it is almost sad to watch.

[SPerman]

coming from siemens nx, sw is such a clown show it is almost sad to watch.

I agree 100%.

[mattpeneguy]

Jesus f*** christ, how hard is it to fix a damn language bug? Requesting a hotfix to my VAR right now.

image.png (21.53 KiB) Viewed 9826 times

Just seeing this. I agree, that's terrible...Get them to change it back from French to 'Murican!

[ReeceB]

Jesus f*** christ, how hard is it to fix a damn language bug? Requesting a hotfix to my VAR right now.

image.png

BTW this can easily be fixed client side by the following:

Regedit > HKEY_CURRENT_USER\SOFTWARE\SolidWorks\SOLIDWORKS 2023\General

Set "Use English language feature names" to 1

[mp3-250]

BTW this can easily be fixed client side by the following:

Regedit > HKEY_CURRENT_USER\SOFTWARE\SolidWorks\SOLIDWORKS 2023\General

Set "Use English language feature names" to 1

1) Why a registry key modification is needed when that setting is inside the system option??

2) It is a workaround unless it returns 押し出し1 instead of Extrude1

[ReeceB]

1) Why a registry key modification is needed when that setting is inside the system option??

The option is greyed out for all our users, I assume due to the user accounts being set to english so the only way to adjust it is via the registry that we could see. Updating everyone via a group policy update made it easy at least.

[AlexLachance]

BTW this can easily be fixed client side by the following:

Regedit > HKEY_CURRENT_USER\SOFTWARE\SolidWorks\SOLIDWORKS 2023\General

Set "Use English language feature names" to 1

It can be done without a registry edit by editing the settings, but that is besides the point. We are a french speaking company, some employees do not understand english as well as me, changing the setting is a temporary fix that brings a minor issue on the side. It makes all features in english and forces some users to have to rely on the feature's icon rather then name.

Thanks for mentioning the work-around though, it could help others which might not mind the feature naming as much. Personally, I wouldn't mind but the company choice was to keep our feature names in french and live with the few nameless features since we barely work in surfacic mode.

[Bradfordzzz]

ok ... so where are we with 2023 ? working? Issues? good to go (ish)? anything major to watch out for? Like .. you cant make drawings anymore or some crazy thing?

[AlexLachance]

Good to go-ish. I haven't encountered anything major. There's still some little graphic issues but they aren't major, just somewhat annoying. The language bug is still present but that won't affect you since you're running the english version and not La-Version-Française

[AlexB]

I haven't encountered anything major, however I just switched to a Win11 system from Win10 at the same time so that part wasn't much fun. We've been using 2023 for about 3 weeks as a company and I haven't had any issues from our users.

Minor quirk - Design checker files no longer work when they're stored in PDM. To fix it, I had to go to the cached file and tick the read-only property off (something that is usually a bad idea in PDM). Now they work again...

[Bradfordzzz]

Good to go-ish. I haven't encountered anything major. There's still some little graphic issues but they aren't major, just somewhat annoying. The language bug is still present but that won't affect you since you're running the english version and not La-Version-Française

I haven't encountered anything major, however I just switched to a Win11 system from Win10 at the same time so that part wasn't much fun. We've been using 2023 for about 3 weeks as a company and I haven't had any issues from our users.

Minor quirk - Design checker files no longer work when they're stored in PDM. To fix it, I had to go to the cached file and tick the read-only property off (something that is usually a bad idea in PDM). Now they work again...

Thanks for the feedback Alex(s) !! Whats the correct plural form of more than one Alex? Alexi? Alexes? Alexs?

[SPerman]

If the plural of helix is helices, wouldn't that make them Aleces?

[AlexLachance]

If the plural of helix is helices, wouldn't that make them Aleces?

As long as it ain't Alesse

[Bradfordzzz]

If the plural of helix is helices, wouldn't that make them Aleces?

Apparently .. lots of people want to know the answer to this ! LMAO

[jcapriotti]

image.png

Apparently .. lots of people want to know the answer to this ! LMAO

There are lots of "experts" on the internet. You know more than 50% of people believe they are above average.

[DennisD]

There are lots of "experts" on the internet. You know more than 50% of people believe they are above average.

And you, Jason, your very existence makes the upper half of the Bell Curve possible!

[jcapriotti]

And you, Jason, your very existence makes the upper half of the Bell Curve possible!
image.png

That's why we should be using median instead of average

[AlexLachance]

Just fell upon a bug that is making us revert back to SP4.

The bug is more something we caused upon ourselves but it is something that worked before and now is buggy so it's still a bug nonetheless.

Basically we standardized components inside our company. The standard component remained and the ones that were duplicates had their configuration call-out the standard component number. Well in SP5, the BOM comes out right, but the balloons come out with * on them... Reporting this to my VAR.


It would require hundred of hours of work to fix the issue at the root on our end while I think it's something very feasible to tweak for SolidWorks, since it worked previously, and still somewhat works.

[SPerman]

I think DSS has adopted the "agile" model but has kept the old naming. For the last couple of releases, SP5 has bugs that didn't exist in SP4. That's not how it is supposed to work.

[AlexLachance]

I think DSS has adopted the "agile" model but has kept the old naming. For the last couple of releases, SP5 has bugs that didn't exist in SP4. That's not how it is supposed to work.

I believe they tweaked something in how BOM's work in 2023 but I don't remember exactly what. I'm guessing that is what caused the issue to arise. What you say would make sense too, concidering their approach for the cloud version.

[AlexLachance]

Just fell upon a bug that is making us revert back to SP4.

The bug is more something we caused upon ourselves but it is something that worked before and now is buggy so it's still a bug nonetheless.

Basically we standardized components inside our company. The standard component remained and the ones that were duplicates had their configuration call-out the standard component number. Well in SP5, the BOM comes out right, but the balloons come out with * on them... Reporting this to my VAR.


It would require hundred of hours of work to fix the issue at the root on our end while I think it's something very feasible to tweak for SolidWorks, since it worked previously, and still somewhat works.

My VAR just called me to tell me that there was an update on my Dashboard(which there wasn't) saying that Dassault required more information. I told him, do you understand the problem? He answered Yes.

I asked him have you talked with them to try and understand what clarification they need? He pretty much started to backpedal and say it was no use for him to do so because he would then have to contact me to relay the information.

Let's just say he wasn't very pleased with me telling him "Go do your job first, then contact me to tell me what clarification you require or else I can clarify just about anything, my birth date, the name of my dog, the color of my eyes, etc... The point being that you need to tell me what I need to clarify or else I'm just speculating on my end"

Worst part is, there's a full text description of the issue explaining the problematic behavior and the correct behavior. There are also 2 RX reports with videos attached in them displaying the issue in one and the correct behavior in the other. I also displayed the issue to the technician beforehand and he assured me he understood what the issue was.

Gotta love interacting with anything that relates to Dassault..

[Bradfordzzz]

My VAR just called me to tell me that there was an update on my Dashboard(which there wasn't) saying that Dassault required more information. I told him, do you understand the problem? He answered Yes.

I asked him have you talked with them to try and understand what clarification they need? He pretty much started to backpedal and say it was no use for him to do so because he would then have to contact me to relay the information.

Let's just say he wasn't very pleased with me telling him "Go do your job first, then contact me to tell me what clarification you require or else I can clarify just about anything, my birth date, the name of my dog, the color of my eyes, etc... The point being that you need to tell me what I need to clarify or else I'm just speculating on my end"

Worst part is, there's a full text description of the issue explaining the problematic behavior and the correct behavior. There are also 2 RX reports with videos attached in them displaying the issue in one and the correct behavior in the other. I also displayed the issue to the technician beforehand and he assured me he understood what the issue was.

Gotta love interacting with anything that relates to Dassault..

Makes you wonder what "value" the "value added resellers" are actually adding.
Might as well just put Solidworks in a box, and sell it at Staples, or Best Buy.

[bnemec]

FIFY

Makes you wonder what "value" the "value added resellers" are actually adding.
Might as well just put Solidworks in a box, and sell it at Staples, or Best Buy Amazon Wish or Etsy.

[Bradfordzzz]

FIFY

LOL ... Temu