SW 2022 SP4 EV - first thoughts

[Bradfordzzz]

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.

[AlexLachance]

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

[Bradfordzzz]

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

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.

[AlexLachance]

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.

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..?

[Glenn Schroeder]

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.

Has this issue been fixed?

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

[Bradfordzzz]

Has this issue been fixed?

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

Hi Glenn,

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

[Bradfordzzz]

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..?

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.

[TRKemp]

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".

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.

[Bradfordzzz]

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".

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.

[TRKemp]

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

[AlexLachance]

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

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

[TRKemp]

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.

[bentlybobcat]

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

Thanks

[Bradfordzzz]

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

Thanks

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.

[AlexLachance]

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.

I think they're improving the mirror feature

[Bradfordzzz]

I think they're improving the mirror feature

It wouldn't surprise me.

[bentlybobcat]

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.

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.

[DennisD]

image.png (7.2 KiB) Viewed 11858 times

FIFY

[Bradfordzzz]

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

Thanks

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

[berg_lauritz]

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)

[SPerman]

Solidworks just figured out there's value in a real coordinate system. I'm sure in a decade or so the will flush out the functionality.

[berg_lauritz]

Anybody else experiences this:

tabs show up in a wrong colour in dark mode - making any font on it unreadable:

Raised an SPR for this. Incredible that the dark mode is broken!

The Dark theme is applied for the UI of SolidWorks and not the toolbars at the moment, which remain white. SolidWorks has therefore issued SPR #1241703 "Ability to display toolbar dropdown list with dark theme" and will notify you once the status of the SPR changes.

[SPerman]

I did some testing on SP4.0 this afternoon. I cloned my database and upgraded all of the parts to 2022.

So far, I haven't come across any weirdness to put me off upgrading. I assume the problems I saw on an earlier release have either been fixed or were created by my files still being 2020.

OpenGL is a no go for my video card even with the 2022Q3 driver. (Radeon Pro WX 7100) Rotating even a small assembly is choppy compared to that being turned off.

I didn't see any weirdness with Enhanced Graphics, so I'm going to leave that on until it causes an issue.

[Bradfordzzz]

I did some testing on SP4.0 this afternoon. I cloned my database and upgraded all of the parts to 2022.

So far, I haven't come across any weirdness to put me off upgrading. I assume the problems I saw on an earlier release have either been fixed or were created by my files still being 2020.

OpenGL is a no go for my video card even with the 2022Q3 driver. (Radeon Pro WX 7100) Rotating even a small assembly is choppy compared to that being turned off.

I didn't see any weirdness with Enhanced Graphics, so I'm going to leave that on until it causes an issue.

All of the issues that were affecting us seem to have been resolved with SP4. Thats not to say that SP4 doesn't have bugs ... there may be many that are there that we just haven't experienced yet, or that are within features that we might not be using or haven't used yet.
Hopefully, that's the same for the majority of people.

[SPerman]

I decided to give OpenGL another go now that I'm in my production environment. I guess my card just doesn't have enough horsepower. The highlighting below is realtime.

I am a GIF. Click me!

[acmall]

I don't think what you are seeing is normal, I have the older W7100 graphics card and it is not having the issue that you are showing.

Which setting are you turning on/off?

[SPerman]

There is only one OpenGL setting that I am aware of.

It could be related to the fact that I don't like circles to look like stop signs, so this is turned way up.

[AlexB]

I decided to give OpenGL another go now that I'm in my production environment. I guess my card just doesn't have enough horsepower. The highlighting below is realtime.

I am a GIF. Click me!

Opengl.gif

I think I've seen that when my OS updated the graphics driver without me noticing. I installed driver after driver starting with newest and going back until it seemed fast and stable. (This was for an old card that is no longer supported)

Maybe try a few different drivers to see if it improves things?

[SPerman]

Is there some magic to OpenGL that justifies jumping through these hoops? I'm fine working with it turned off.

[DanPihlaja]

Is there some magic to OpenGL that justifies jumping through these hoops? I'm fine working with it turned off.

Some good reading here:
https://gamedev.stackexchange.com/quest ... ring-today

[jcapriotti]

Is there some magic to OpenGL that justifies jumping through these hoops? I'm fine working with it turned off.

Which are you referring to, the "Use software opengl" setting in SolidWorks?

[XHawkeye]

I decided to give OpenGL another go now that I'm in my production environment. I guess my card just doesn't have enough horsepower. The highlighting below is realtime.

I am a GIF. Click me!

Opengl.gif

My guess, SW isn't using your graphic card.

Have an old computer ( i7-3770 old) that would only run SW in software openGL mode because it only had cpu graphics. It did the same thing as shown in your example. Was given a GTX980 (don't ask) and problem solved after getting a big enough PSU to power the 980.

[Frederick_Law]

OpenGL is a no go for my video card even with the 2022Q3 driver. (Radeon Pro WX 7100) Rotating even a small assembly is choppy compared to that being turned off.

Let's clear up a few things.
SW use OpenGL ALL THE TIME. You CANNOT turn it off.
So if your video don't support OpenGL, SW can't use it.

The ONLY OpenGL setting in SW is: Use Software OpenGL.
It means: use software emulation to bypass hardware (graphic card).
Which means VERY slow graphic.
It is used to test if graphic card is the problem for graphic issue.

So you've turned on the wrong thing.

[Frederick_Law]

Let's clear up a few things.
SW use OpenGL ALL THE TIME. You CANNOT turn it off.
So if your video don't support OpenGL, SW can't use it.

The ONLY OpenGL setting in SW is: Use Software OpenGL.
It means: use software emulated graphic card to bypass hardware graphic card.
Which means VERY slow graphic.
It is used to test if graphic card is the problem for graphic issue.

So you've turned on the wrong thing.

[bnemec]

Of the ~25 CAD work stations we have I'd guess about half of them had the display(s) connected to the mother board instead of graphics card. Mostly when users were moving to home or back to office over the past couple years.

I actually lost some sleep worrying about how we have designers/engineers/drafts people that don't know how to plug a display into a workstation with a graphics card.

I have a driver version I trust for our workstation/card/SW version, after that I check which display port the cable is connected to. Just throwing that out.

[AlexLachance]

Let's clear up a few things.
SW use OpenGL ALL THE TIME. You CANNOT turn it off.
So if your video don't support OpenGL, SW can't use it.

The ONLY OpenGL setting in SW is: Use Software OpenGL.
It means: use software emulation to bypass hardware (graphic card).
Which means VERY slow graphic.
It is used to test if graphic card is the problem for graphic issue.

So you've turned on the wrong thing.

Well explained.

As stated, using "Use Software OpenGL" is pretty much asking the program to emulate the OpenGL process to see if your graphic card is the one causing issues(by not being able to do OpenGL for instance). It's not supposed to enhance anything as far as I'm aware either, even though I've heard plenty of people claiming such things.

If SoftWare OpenGL is better then Graphic card OpenGL, it means that the computer has more "processing speed" remaining for OpenGL treatment then the graphic card could provide, which would resume itself as having a shitty graphic card as you stated.

[HerrTick]

Same "first thoughts" I have with EVERY SolidWorks release...

Why, oh, WHY must they have annual releases?

Oh, yeah... Profit!

[SPerman]

Which are you referring to, the "Use software opengl" setting in SolidWorks?

That is the only one I am aware of.

Of the ~25 CAD work stations we have I'd guess about half of them had the display(s) connected to the mother board instead of graphics card.

This machine has a 4 port card with three monitors plugged in. None of them are plugged into the onboard graphics port.

Let's clear up a few things.
SW use OpenGL ALL THE TIME. You CANNOT turn it off.
So if your video don't support OpenGL, SW can't use it.

The ONLY OpenGL setting in SW is: Use Software OpenGL.
It means: use software emulation to bypass hardware (graphic card).
Which means VERY slow graphic.
It is used to test if graphic card is the problem for graphic issue.

So you've turned on the wrong thing.

So the "Use OpenGL" setting in solidworks is for diagnostic use only, and not intended for daily use?

This is the post that started me down this rabbit hole. (I know Fred only comes here to bash SW, but I'm stuck with an AMD and SW, so I expected to see a performance improvement.) Clearly I don't understand what this setting does in SW.

"AMD Rearchitects OpenGL Driver for a 72% Performance Uplift"
https://www.tomshardware.com/news/amd-r ... nce-uplift

[jcapriotti]

@SPerman That setting is for use when you're having trouble with a card.....it disables the OpenGL and instead uses "Software Opengl emulation". Its ways slower. If you had no card that support Opengl, it would be greyed and checked.

[SPerman]

Thanks to all for educating me. @matt there might be value in pulling the OpenGL conversation into its own thread. I've kind of stomped all over the 2022SP4 conversation.

On that front, it seems to be doing great, other than PEBCAK errors.

[Frederick_Law]

There is NO "Use OpenGL" option.

Only this:

Use software OpenGL-01.jpg (1.4 KiB) Viewed 11066 times

[AlexLachance]

That is the only one I am aware of.



This machine has a 4 port card with three monitors plugged in. None of them are plugged into the onboard graphics port.



So the "Use OpenGL" setting in solidworks is for diagnostic use only, and not intended for daily use?

This is the post that started me down this rabbit hole. (I know Fred only comes here to bash SW, but I'm stuck with an AMD and SW, so I expected to see a performance improvement.) Clearly I don't understand what this setting does in SW.

OpenGL could be seen as a programming language to allow your graphic card and processor to communicate together

If you'd like to read up on it;
https://openglbook.com/chapter-0-prefac ... pengl.html

Resumed:

On the most fundamental level, OpenGL is a software interface that allows a programmer to communicate with graphics hardware. Of course, there is much more to it than that

[Frederick_Law]

OpenGL could be seen as a programming language to allow your graphic card and processor to communicate together

Like VB and C# for SW macro. OpenGL is "VB".

[Bradfordzzz]

Let's clear up a few things.
SW use OpenGL ALL THE TIME. You CANNOT turn it off.
So if your video don't support OpenGL, SW can't use it.

The ONLY OpenGL setting in SW is: Use Software OpenGL.
It means: use software emulation to bypass hardware (graphic card).
Which means VERY slow graphic.
It is used to test if graphic card is the problem for graphic issue.

So you've turned on the wrong thing.

This is really great information. Thank you for sharing this.

[bnemec]

Like VB and C# for SW macro. OpenGL is "VB".

I thought it was an API of sorts to the graphics driver. Sort of a "universal" language to the layer between applications/OS and the various GPU architectures.

[Frederick_Law]

I thought it was an API of sorts to the graphics driver. Sort of a "universal" language to the layer between applications/OS and the various GPU architectures.

They are API. A higher level "Library" that hide hardware from developer.

Looks like Vulkan will replace OpenGL.
I think SW is testing Vulkan.

[AlexLachance]

They are API. A higher level "Library" that hide hardware from developer.

Looks like Vulkan will replace OpenGL.
I think SW is testing Vulkan.

[berg_lauritz]

Logical.

[tsmith]

They are API. A higher level "Library" that hide hardware from developer.

Looks like Vulkan will replace OpenGL.
I think SW is testing Vulkan.

The Viking roaming about the afterlife sim game 'Valheim' is testing Vulkan as well, it works great for murdering wild pigs.


But back to SP.4 any red flags?
Did they fix the it takes a million years to save your file issue? or CTD on clicking save from SP2?

[SPerman]

This is a strange issue, but it only started after I upgraded to 2022. Some of my assemblies now open as "Shaded." These assemblies are released in PDM, so I know I didn't somehow change them. I ONLY uses "Shaded with edges", so this isn't something I would have ever changed.

edit: I guess this could have happened when I updated all of the files to 2022. I used #task to do this.