hexagon logo

Computer Specs for PCDMIS 2023.1

Hi All,

We are having issues with PCDMIS 2023.1 and after research and testing have come to the conclusion that we need to update our outdated pcs to be more inline with current specs,

Anyone who has upgraded also for this reason or has upgraded easily / using a spec that has had little to no issues with PCDMIS 2023.1 can you please tell me the spec and if you know price please so i can pitch this to my top management.

Thanks in advance
  • We have a computer that is mostly to spec bar the graphics card but even then it is a P4000, what I'm looking for is what other people who are using pcdmis 2023.1 for what spec they are using as we are having A lot of issues. I was aware already of the standard specs
  • Hi All,

    We are having issues with PCDMIS 2023.1 and after research and testing have come to the conclusion that we need to update our outdated pcs to be more inline with current specs,

    Anyone who has upgraded also for this reason or has upgraded easily / using a spec that has had little to no issues with PCDMIS 2023.1 can you please tell me the spec and if you know price please so i can pitch this to my top management.

    Thanks in advance


    What is the PC you are using? Whatever you get it should have the fastest single processing speed and as much RAM as you can afford. Graphics card I think an NVIDIA RTX series, consider how much scanning you are doing. I have an engineering PC so my processor is an i9 -13900K, 3000 Mhz, 24 cores, 32 logical processors. and my graphics a an RTX A2000 12GB


  • What is the PC you are using? Whatever you get it should have the fastest single processing speed and as much RAM as you can afford. Graphics card I think an NVIDIA RTX series, consider how much scanning you are doing. I have an engineering PC so my processor is an i9 -13900K, 3000 Mhz, 24 cores, 32 logical processors. and my graphics a an RTX A2000 12GB


    Currently we are using a Dell Z4 Series with P4000 Graphics card and 32gb of ram with a i7-9800X CPU.
  • What kind of issues were / are you having? Maybe the group can point to some tweaks to get you by. I am running a similar PC out in the shop and I am not having any problems with the newest version of PCDMIS. Slow path lines, slow report generation. graphics display reporting issues wont speed up with a more powerful computer. Some of these items are version / feature issues, setting issues.
  • Our computer is a Dell P3630 with a Core i3 9100, 16GB of RAM and a Quadro P620. We use 2021.2 TTP only. I've also run this machine using a Dell laptop with the low power Intel processor and integrated graphics.
  • So the issues I'm having are crashing when switching between auto features, for instance I can do lots of vector points but if I switch to a auto circle it'll crash my software, i went through this issue with hexagon and if they remoted on we could re-create the error for them to see however whenever we would try to re-create the issue the same on there pcs in hexagon the issue was not present, the only difference being the machines.
  • I am seeing something similar Offline. Have you tried a different version? Also try creating a few features at a time, save then move on. I will see what it does in 2023.2. Chances are there is a bug, i would not spend money on a PC until they figure this out.
  • I hate being a broken record here, but if your organization can accept running a few SW revisions back, you are no longer effectively a beta tester for the product.

    I work in medical (FDA IQ/OQ/PQ qualified process restrictions), so revising to a newer rev takes quite a bit of paperwork. We stay at least one year behind the current rev. that way we are using a version of the software that has already been vetted with the gamut of maintenance releases and service packs (2019R2 is our current release). Using latest revision of this software (without an absolute NEED) is literally begging for drama like this.
  • Its really weird but its program dependent on if it crashes or not, for instance one program I'm doing crashes after every switch so I have to do what I need in say vector points, save, switch to circle which will crash my software, then carry on and vice versa. but then another program I'm working on has had (Touch Wood) Barely any crashes. If it was a bug wouldn't PCDMIS have also crashed on the hexagon test? (Test was done with a know problem program that could be repeatable crashed on all our computers here but on hexagons software could not be forced to crash)