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.

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.

I found version 3.7 has a lot of memory or resource leaks.  When I work on a machine running 3.7 I need to keep this in mind that it will shut down after a specific number of features are executed.  I doubt most users would see this but since I do things a bit differently it really stands out.  Version 3.7 might be the worst.

everyone else (except you) have said V3.7 MR3 (not the earlier releases) is in the top 3 or 4 releases ever made.

recently had a program for a part with 2116 features as well as dimensions for each one as well as most of them having 2D distance dimensions between them for a roughly 200 page report.  not a bit of problems with 'memory leaks'.  the only time the memory leaks are an issue is when you go through multiple programs (open, close, open, close, open, close) really fast.  the memory leak showed up by making the edit window a color other than what it should be (usually red or green, sometimes black), it would be that color while in the process of opening, once open it would go back to normal, when that happened, close Pcdmis and reopen it, problem solved for a long time.

Matthew D. Hoedeman Version 3.7 was definitely one of the better versions and for almost all users this would be true.  In my case I noticed issues when using VB in this particular version of PC-DMIS.  It was so bad I knew that after running a specific number of measurements that I had to close the software otherwise it would be closed for me.  I have only seen this problem with version 3.7 (nothing newer or older had the same issues).  Most users are not using VB for regular part programs so they would never run into this.  I just wanted to clarify what I was talking about earlier.