SW 2022 SP2 - First Thoughts

[jcapriotti]

The elimination of the free DraftSight version was particularly onerous. I get it, it’s not going to be free forever. Saying that, let me know and I would have gladly paid the then $50 cost for the low end version. Instead, it’s arbitrarily turned it off without notice, the perpetual license was eliminated and it’s now a subscription at a rate that I’m not going to fork out for something I used 2-3 times a year. Nice work guys. My VAR was extremely embarrassed about the whole thing.

You can get the perpetual license still but you have to buy the Enterprise version at $599.

https://trimech.com/products/draftsight-enterprise-perpetual-license

Question is, what’s your alternative? AutoCAD is subscription only, so is Nanocad. BricsCAD is priced similar to DraftSight Enterprise. This is industrywide and I imagine in a few years it will be worse.

There are a few free options that you could maybe use if you don’t need to do much (Librecad, Nanocad free, etc.)

[bentlybobcat]

I’ve been using nanocad free, but extremely infrequently.

It’s a bit of a concern considering where it’s written.

[zxys001]

I don’t think anyone is begrudging their need to make money. We all have to eat.
.. they don’t care about individual users any longer…

Bravo, well said!

[Mike_Gera]

Is anybody having a problem with random temporary axes appearing in SW 2022 SP 2.0 on Windows 11?

[berg_lauritz]

I did not.

To be honest, I have no good reason to upgrade. If we hadn’t decided to install PDM, I would still be off license and 2022 wouldn’t even be an option.

I was reluctant to perform the upgrade in the first place, but there are some new features in 2022 I wanted to investigate. There are no new features that are revolutionary, and even though 2020 has a few issues that affect me, I know what they are and how to work around them. I wasn’t going to invest extra time upgrading all of my files, just in case I decided to go back. If the reason for my slowness was that all of my files are still 2020, so be it.

It was close enough to what I experienced after one of the 2019 service packs that I started having PTSD and couldn’t get that S*** off of my computer quick enough. I know others didn’t have the same experience, but for me I lost about 1/3rd of my productivity staring at “solidworks is busy.” I have no desire to do that to myself again.

So you did not upgrade the files? I don’t think there is a fair comparison possible without upgrading the files. Or does it not affect the performance anymore?

[SPerman]

You are correct. It was not a true fair comparison. Maybe if I had invested another day in upgrading all of my files I would have a different experience. Or maybe I would have wasted another day and a half and still reverted. I’m comfortable with the decision I made. I would recommend anyone do whatever level of testing they feel comfortable with before upgrading.

[SPerman]

Is anybody having a problem with random temporary axes appearing in SW 2022 SP 2.0 on Windows 11?

If you haven’t already, try toggling “enhanced Graphics” and see if that makes a difference.

[Mike_Gera]

If you haven’t already, try toggling “enhanced Graphics” and see if that makes a difference.

Will give it a try, thanks.

[nevillew]

LOL!

Kinda like the free version of DraftSight…

On the ‘Draftsight not free anymore’ nonsense by Dassault…
After about a year or 2 of using something else, out of curiosity I tried again to see if it would open a file, without telling me I need to pay.
Lo and behold it works again - I’m wondering if if in their corporate body they have developed some sort of conscience or heart of some kind and thought about us individual users keeping the promise of always being free. . . .

I’ve canned my subscription of SNOTWorks.
Down this part of the world it costs in excess of $2000 just to maintain a sub with standard version.
Just not worth it when they keep tinkering around the edges with fluffy stuff and breaking other existing functionality.

[Tera]

Is there anything wrong with Pack & Go in SW2022 SP2?

It seems I can not Pack & Go an assembly. The task ends without any error, but the new assembly is full of broken references. I really hate SW.

[Frank_Oostendorp]

@Tera,
yes, Pack&Go does not update references in new saved assembly. Supposed to be fixed in SP3.0.

[Tera]

@Tera,
yes, Pack&Go does not update references in new saved assembly. Supposed to be fixed in SP3.0.

Why something that has been working for years breaks in an update?
Is it possible to uninstall SP2 and go back to SP1 without uninstalling the whole application?


Thanks.

[Glenn_Schroeder]

Is there anything wrong with Pack & Go in SW2022 SP2?

It seems I can not Pack & Go an assembly. The task ends without any error, but the new assembly is full of broken references. I really hate SW.

1.png

Pack and Go works fine in SW2022, as long as you don’t try to re-name components as part of the process (or at least it does for me). Fortunately, since we got the ability a few years to re-name components within an Assembly that’s not as big a deal as it would have been otherwise.

[Frank_Oostendorp]

Pack and Go works fine in SW2022, as long as you don’t try to re-name components as part of the process (or at least it does for me). Fortunately, since we got the ability a few years to re-name components within an Assembly that’s not as big a deal as it would have been otherwise.

Right, Glenn. In your case it doesn’t seem to be a big problem. In our case, it is a huge problem, costing us many extra hours. I am staying at SolidWorks 2019, postponing upgrading. Amazed by the number of issues in the last three versions of SolidWorks.

[AlexLachance]

Right, Glenn. In your case it doesn’t seem to be a big problem. In our case, it is a huge problem, costing us many extra hours. I am staying at SolidWorks 2019, postponing upgrading. Amazed by the number of issues in the last three versions of SolidWorks.

This is a good representation of SolidWorks for the last 2 to 3 years I’d say, if not more.
image.png

[Tera]

Pack and Go works fine in SW2022, as long as you don’t try to re-name components as part of the process

All components are virtual. So there’s no renaming.
Can you test if pack & Go has any problem with virtual parts?

thank you.

PS : Are you using SP2?

[Glenn_Schroeder]

All components are virtual. So there’s no renaming.
Can you test if pack & Go has any problem with virtual parts?

thank you.

PS : Are you using SP2?

1. It worked fine with a virtual Part.

2. Yes, I’m using SW 2022 sp 2.0.

3. Why can’t you re-name virtual Parts from the Assembly tree?

[Tera]

3. Why can’t you re-name virtual Parts from the Assembly tree?

I don’t. Not that I can’t. I simply select pack & go, then Replace the old name to new name (using replace all).
The assembly has 158 parts. All sheet metal. 102 parts are OK. the rest ends up with broken references.
No matter how many times I repeat this, the same result.
I’ve been using Pack & Go regularly, never had this problem before.

Thanks for testing and letting me know the result.

[jcapriotti]

TeraDid this work in a previous version? We are on 2019 and it seems I ran across this before and it was related to virtual components not updating. Problem affects assembly renames in PDM as well as the “update references” code cannot ‘reach’ into virtual components that are embedded inside an assembly file to update the in-context links.

I find several SPRs on this…all fairly old.

[Glenn_Schroeder]

@TeraDid this work in a previous version? We are on 2019 and it seems I ran across this before and it was related to virtual components not updating. Problem affects assembly renames in PDM as well as the “update references” code cannot ‘reach’ into virtual components that are embedded inside an assembly file to update the in-context links.

I find several SPRs on this…all fairly old.

image.png

Back around that time I had problems with virtual parts getting left behind when doing a Pack and Go. I didn’t use them often, and even then it was usually just one per Assembly, so I stopped using them altogether.

The problem with re-naming files during the Pack and Go operation is new with SW2022 (at least I didn’t have the problem with older versions).