SOLIDWORKS 2023 confirmed bugs

[IndianaDave]

I definitely have a non-standard layout. I remember one time my VAR remoted in, and you would think I had asked them to do Cad in Word Perfect. They were absolutely lost because the buttons aren't where they expected them.

I use my "S" key for absolutely everything. I have no toolbars or anything on my screen...
Everyone is lost when they sit down at my computer.

[mp3-250]

lol, I've had that in 2019, the tooltip would span across the entire screen. What a P.I.T.A. that was.

They probably have a specialized team for messing up with the UI.
Something like "interactive user experience improvement group", but
managed by monkeys hitting on the keyboards the whole day...

[DavidWS]

We just updated from sw22sp5 to sw23sp5 and faced first annoying issue:

If drawing view has tangent edges hidden, it's impossible to dimension structural members. When you switch to tangent edges with font, you can dimension. Anyone else has this same behaviour?

image.png


EDIT:
Found fix SPR1254289
"workaround: In SW2022, it works if Options > Selection > Selection of hidden edges > ‘Allow selection in HLR and shaded mode’ option is selected"

We have also run across this annoying behavior, but can't repeat it in all instances.

Another work-around for us for this annoying bugger is to change the view to hidden lines showing to be able to dimension those silhouette edges.

[bnemec]

We have also run across this annoying behavior, but can't repeat it in all instances.

Another work-around for us for this annoying bugger is to change the view to hidden lines showing to be able to dimension those silhouette edges.

Check your graphics drivers on the various machines. Not talking about the typical "certified driver" cop-out. It might be worth while to try various driver versions, depending on which version of SW you're running.

We have mostly identical CAD work stations throughout the department. Thanks to windows updates and other unknown randomness the installed driver version does vary. I had kept mind at 443.66 for a long time, but now trying 474.82. Hoping when we get to 2023 we can just use latest driver, but we've had various issues with the 500 series nVidia drivers on SW 2019SP4. Unfortunately, Windows update seems to keep installing the 500 drivers.

We recently had very inconsistent behavior with how Decals were showing in models. Turns up we had four different machines behaving differently due to four different drivers installed.

[mattpeneguy]

Check your graphics drivers on the various machines. Not talking about the typical "certified driver" cop-out. It might be worth while to try various driver versions, depending on which version of SW you're running.

We have mostly identical CAD work stations throughout the department. Thanks to windows updates and other unknown randomness the installed driver version does vary. I had kept mind at 443.66 for a long time, but now trying 474.82. Hoping when we get to 2023 we can just use latest driver, but we've had various issues with the 500 series nVidia drivers on SW 2019SP4. Unfortunately, Windows update seems to keep installing the 500 drivers.

We recently had very inconsistent behavior with how Decals were showing in models. Turns up we had four different machines behaving differently due to four different drivers installed.

Quit using decals...

[bnemec]

Quit using decals...

Right, that would be nice.

Maybe we should switch to Wrap and Emboss...

[ryan-feeley]

Unfortunately, Windows update seems to keep installing the 500 drivers.

You need to take control of the graphics driver version to get consistent performance from Solidworks.

Do a *clean install* of the latest driver from a software branch that is certified to work with your version of solidworks, and then lock to that driver version until you experience some other bug that a newer version will actually fix. Typically you'd click a button called "advanced" on the driver installer to access the clean install option.

There are a few different ways to prevent driver updates. I've always done it with the Group Policy Editor under "Administrative Templates > System > Device Installation > Device Installation Restrictions > Prevent installation of devices that match any of these ids". I got that procedure years ago from this answer on superuser to How do I stop Windows 10 from updating my graphics driver? . The Group Policy Editor is not available on "Home" versions of Windows.

There are other ways that block driver updates for *all devices*:

• Var Hawkridge for windows 10
• Var Javelin-Tech for windows 11

but I prefer the procedure that applies a restriction to only the graphics card since generally I do want Windows to keep my other drivers up-to-date.

Be aware that one downside to my method is a group policy rule will prevent *any update* to the graphics driver. Even one that you do manually. So you must temporarily disable the rule in the future if you want to update the driver version, and then reconfigure it.

[mp3-250]

Saw this the other day. Make an aux view and a create a center line or trying to align it with another view, notice the view origin is completely off center...

BR Article: BR10000372717
Status: Open

Align Vertical/Horizontal by origin causes the centreline in an auxiliary view to move to the wrong position
Portfolio / Domain: SOLIDWORKS Desktop / E-Apps
Product: Drawings
OS: Windows 10 64 bits
Detected level(s): SOLIDWORKS 2023 SP5
Platform: n/a
Description

Steps to reproduce:
1. Open drawing
Notice >> There are two standard views - Front and Right Side view
2. Create Auxiliary view of the Front View
3. Place the Auxiliary view and then apply centrelines to it.
4. Break alignment between auxiliary view and Front view.
5. Align the auxiliary view to Right Right Side view by "Align Vertical by Origin"
Notice >> The centreline in an auxiliary view are at wrong position


Current Result: Centreline in an auxiliary view move to the wrong position outside the view

Expected Result: Centreline in an auxiliary view should remain at expected position

Closure Information
This issue is reported to Dassault Systèmes development team.

[mp3-250]

You need to take control of the graphics driver version to get consistent performance from Solidworks.

Do a *clean install* of the latest driver from a software branch that is certified to work with your version of solidworks, and then lock to that driver version until you experience some other bug that a newer version will actually fix. Typically you'd click a button called "advanced" on the driver installer to access the clean install option.

There are a few different ways to prevent driver updates. I've always done it with the Group Policy Editor under "Administrative Templates > System > Device Installation > Device Installation Restrictions > Prevent installation of devices that match any of these ids". I got that procedure years ago from this answer on superuser to How do I stop Windows 10 from updating my graphics driver? . The Group Policy Editor is not available on "Home" versions of Windows.

There are other ways that block driver updates for *all devices*:

• Var Hawkridge for windows 10
• Var Javelin-Tech for windows 11

but I prefer the procedure that applies a restriction to only the graphics card since generally I do want Windows to keep my other drivers up-to-date.

Be aware that one downside to my method is a group policy rule will prevent *any update* to the graphics driver. Even one that you do manually. So you must temporarily disable the rule in the future if you want to update the driver version, and then reconfigure it.

I tried multiple drivers, starting with the one linked in the certified official list, still flagged as not certified.
Also the exact driver version seems to be retired or not more available.
Is this another bug in 2023?? Or just their certification process gone nuts??

example for our typical workstation

Tested on R525 U6 Version 528.89

Click on the link R525

Version: R525 U7 (528.95) ????

it is me or 528.89 is not available?
I tried the driver SW links and it is not certified according to RX.
Are they bulling us?

[mp3-250]

I have found other bugs with PDM administration.
AGAIN another bug that causes the settings to NOT be saved...

It happened multiple times when adding removing users from & to PDM groups, or enabling & disabling PDM access.
It seems that if you have the user search opened and you modify the properties they are not saved even if you click the SAVE icon after modifying the user properties. open the user properties again and they are unchanged.

This is ridicolous for an ADMINISTRATIVE front end. How we can administer a system with a set of tools that fail to setup the software they are designed to setup??

[mp3-250]

Check your graphics drivers on the various machines. Not talking about the typical "certified driver" cop-out. It might be worth while to try various driver versions, depending on which version of SW you're running.

We have mostly identical CAD work stations throughout the department. Thanks to windows updates and other unknown randomness the installed driver version does vary. I had kept mind at 443.66 for a long time, but now trying 474.82. Hoping when we get to 2023 we can just use latest driver, but we've had various issues with the 500 series nVidia drivers on SW 2019SP4. Unfortunately, Windows update seems to keep installing the 500 drivers.

We recently had very inconsistent behavior with how Decals were showing in models. Turns up we had four different machines behaving differently due to four different drivers installed.

@bnemec after months of 2023 I am tempted to suggest you to wait for 2024 SP5. 2023 has too many strange things happening to us and looking at cad dashboard crashes and hangs way more than 2022.

[mp3-250]

This is a graphic glitch, a strange one. It seems related to the BR below.
Tried with graphic acceleration OFF and with the SW empty templates.

• Step to reproduce:
  
  1. Create an empty assy1
  2. Save it on disk
  3. Create an empty assy2
  4. Save it on disk
  5. Insert a couple of assy2 into assy1
  6. Select one of the planes (or origin) of assy1
  
  Graphic area highlights the selected entity for each assy2 inserted into assy1 even if the selected entity is in assy 1.

Now try to draw a 3D Sketch and a sketch in assy1 and drag in another assy2.
Actually I saw this bug as I inserted a component with a piping route sketch inside an assy and the scree was completely messed up, with the sketch misaligned and out of origin so I paniked for a second wondering what the heck was going on. LOL

Selection in assemblies will always select assembly planes instead of medel (<-SIC!) if they are visible/shown.
Portfolio / Domain: SOLIDWORKS Desktop / E-Apps
Product: User Experience (UX)
OS: Windows 10 64 bits
Detected level(s): SOLIDWORKS 2023 SP3
Platform: n/a
Description
1. Open any assembly file. 2. Go to Hide/Show Items > Make planes visible 3. Try to select model edge/face. 4. Notice >> if there is plane in front/background of the model, the plane is highlighted and selected instead of model.
Closure Information

Issue is not reproducible in future versions (SW2024)

Level Closure Type
SOLIDWORKS 2024 SP0 Unreproducible

[SPerman]

I am doing some simple FE on this part. I've hidden this sketch dozens of times. Every time I solve, it unhides itself.

[DanPihlaja]

I am doing some simple FE on this part. I've hidden this sketch dozens of times. Every time I solve, it unhides itself.

image.png

It is possible that it changes display states when it solves? If so, make sure it is hidden in the other display state.

[SPerman]

It is possible that it changes display states when it solves? If so, make sure it is hidden in the other display state.

There is only one display state.

[SPerman]

Here is a GIF.

[HercalloY]

There is only one display state.

Just an idea for a check.... check that DisplayStates are NOT linked to configurations (and delete any extra ones if it was and they display after unlinking). If already unlinked... i out of ideas.