Excessive crashes with PCDmis

everything mentioned above is good stuff. In addition, each user ID that logs into Windows on that PC will need to have these registry keys and folders (at bottom) set to administrative and read/write permissions.

I do not think your problems are resource related.  Unless you are opening large (>100mb) *.CAD routines I highly doubt additional RAM (or upgrading graphics card) will net any gain whatsoever.

I also advise if you are using a network folder to store any PCDMIS files (PRG's, PRB's, etc) don't.  Copy them locally to that machine's hard drive and set them as read only if you need configuration management sustained.

Per the Hexagon support page, the following is what they say is required:
“If I do not have local admin access can I still run PC-DMIS?
May 25, 2018•Knowledge
Details
Yes- if the end user is denied local admin access on their PC to run PC-DMIS, then ask IT to make the following changes to the application's install folders and registry branches below.

Grant the user's account full permissions on all of our Hexagon application folders here:

• C:\Program Files\Hexagon (64-bit installs)
• C:\ProgramData\Hexagon

In the registry you should also explicitly give the same user full permissions to the following branches:

• HCU\Software\Hexagon
• HKLM\Software\Hexagon
• HKLM\Software\Wow6432Node\Hexagon
• HU\.DEFAULT\Software\Hexagon

louisd said:

In the registry you should also explicitly give the same user full permissions to the following branches:

• HCU\Software\Hexagon
• HKLM\Software\Hexagon
• HKLM\Software\Wow6432Node\Hexagon
• HU\.DEFAULT\Software\Hexagon

This only applies to older versions (before 2022 I think).  Settings are now stored in .json format in the following folder locations...

C:\ProgramData\Hexagon\PC-DMIS\version

C:\Users\username\AppData\Local\Hexagon\PC-DMIS\version

.

Where username is the Windows user account name and version is the PC-DMIS version (e.g. 2024.2)

What about the HU\DEFAULT\SOFTWARE\Hexagon? I believe that is the directory permission required for PC-DMIS 50 Converter/ print functionality. I had my IT give permissions to all of these directories just in case, even though I am using 2023.2.

Is there an updated permissions needed documentation for the versions that started using json files instead of registry?

Thanks for the corrections Neil Challinor ! I had no idea all that changed. :D 

-I'm stuck in FDA GMP controls.  we use rev2018r2, so all this newer stuff hasn't hit me yet.

Does Hexagon test this stuff. If it is a resource issue it should be obvious with just basic testing.

PC-DMIS does not have a good track record for stability.  It is a train-wreck that never ends....

V3.7 is very stable and crash-free with only 2 exceptions.  memory leaks (not often) and round slots.  Sometimes the first time you pick a round slot in a program it will crash, but then start up Pcdmis again, and no problems picking them for the rest of the program.

2018 R2 SP14

2019 R1 SP11

2020 R1 SP15

2021.1 SP11

2022.2 SP7

2023.1 SP9

2023.2 SP12

Looks like 2022 is the gold standard with only 7 service packs needed. 

Hexagon uses a group of Beta testers called "customers" to test their software. 

The biggest thing that Hexagon does that is just plain wrong on so many levels is that they don't allow you to download a service pack for a product you already purchased unless you maintain an SMA. If I purchase ANY other software the SP's and support are provided for the product I purchased. This is type of behavior that drives people to other products. 

It's gonna be interesting to see what happens in the next few years once some other companies hammer down on the CMM integrations for their software. 

Just yesterday I was working on a part, at about 99% completion I realized that I put the secondary alignment feature on the opposite side of the part.... and all that was required to correct the error was two mouse clicks. No muss, no fuss, no "do you wish to update the nominals for literally everything and break the rest of the program? And at the same time over-write all the hand key-ed nominals cuz my drawings are trash here" 
Maybe someday... 

It's gonna be interesting to see what happens in the next few years once some other companies hammer down on the CMM integrations for their software. 

Just yesterday I was working on a part, at about 99% completion I realized that I put the secondary alignment feature on the opposite side of the part.... and all that was required to correct the error was two mouse clicks. No muss, no fuss, no "do you wish to update the nominals for literally everything and break the rest of the program? And at the same time over-write all the hand key-ed nominals cuz my drawings are trash here" 
Maybe someday... 

Here's how the cycle goes...

1) Introduce "new" version with "additions & enhancements". You need to keep that SMA gravy train going so you need to release something each year to appear to be making the software better in some way

2) Break things that are core functionality and have worked in that past while adding things that aren't necessary for 99.99% of people in metrology

3) Scramble to try and fix all those problems when people complain or just release another version .X and say use this... it's better

And so on, and so on... 

Usually the "solution" proposed is to disable this or do it this other way that's convoluted and wasted time, or you just don't know how to use the software right. Give me a break. The software crashes more than any software I've ever used, and that's saying a lot. PC-DMIS has become the perpetual Windows ME. 

I've been on and off this User board or it's earlier versions for more than 20 yrs. I've been reading Matt's posts for years. (God bless you, Matt!) This isn't something new that I don't understand. This is a bad way to do business, IMO. 

The thing I find fascinating is that people will defend this software and get bent out of shape if you knock it. It's like Stockholm Syndrome. 

Oh well. I'm just 1 person. C'est la vie

Maybe this is very hard to believe, but the state of the software has become much better compared to the older releases. More stable, the PRG-cannibalism has pretty much stopped (PC-DMIS eating it's own programs), the moody bugs are very far in between... With that said, there are still some things that is the polar opposite to other softwares user interfaces and some other quirks. I for one, would not go back if I got to choose.

I agree with you Zen Cat. Why change a profitable business model. The main improvements I see now are to keep the customers attention on Hexagons products portfolio using nexus.