hexagon logo

The Future of PC-DMIS BUGS

Hexagon reps in here? If so, can I ask why I am told to submit tickets or report bugs to help fix your software so frequently? Do you compensate my companies annual licensing fee for me talking the time to report a bug to improve YOUR software? Do I get a Hexagon coffee mug sent and an apology for hindering my job from which I make a living from? What about a t-shirt? Anything incentivized, other than its been reported and will be fixed in a SP WAY down the line when I have already figure out a work around to the issue.

I applaud the work I have seen members do to report these issues. I hope Hex, is in some way doing something for your efforts to improve their software

Thanks,

An avid PC-DMIS user from the future using PC-DMIS 2022 SP13 with a lot of the same issues with a different UI Slight smile
  • You get nothing, zilch, nada, zero.

    You'd think that you improve the software by filing these things, but that is a very, very slow turning wheel. Even bugs that affects calculations in PC-DMIS are not considered major ones. Let's just hope the user detects the bugs and issues before it affects their production (conforming/non-conforming) unknowingly...

    Shitty QA, if you ask me.
  • I get where you are coming from but it would be too time consuming to run the software through every single scenario that their customers do. If they did, it would be 5 years between releases and the rollout of new features we ask for would take forever. Who better to help test the software then the customers who put the software through its paces every day. We, as programmers, do more with the program in one day than they could do in 2 years because there are way more of us than their are of them.

    I get the frustration, trust me I do, but in the end you are helping make your job easier.

    That being said... I wouldn't say no to a nice Hexagon polo shirt...
  • Hey, I received a Hexagon travel mug when my partner and I finished the final project in the level 101 course in RI.
  • I'm going to 301 at the end of October so maybe I'll get something...
  • Man, lucky you. Have fun & let us know how the course goes.
  • I don't know how things are run at your place, but here, decisions ($$$) based on what the CMM reports say are made every day which calls for a software that is tested to the teeth to not spit out erroneous results. If you are a software developer and cannot understand the importance of this, you should really consider a job change.
  • The only thing I came back with was a nasty rash.
  • Did you go to RI? Why did you get a rash? DMIS Fever?
  • Hexagon reps in here? If so, can I ask why I am told to submit tickets or report bugs to help fix your software so frequently? Do you compensate my companies annual licensing fee for me talking the time to report a bug to improve YOUR software? Do I get a Hexagon coffee mug sent and an apology for hindering my job from which I make a living from? What about a t-shirt? Anything incentivized, other than its been reported and will be fixed in a SP WAY down the line when I have already figure out a work around to the issue.

    I applaud the work I have seen members do to report these issues. I hope Hex, is in some way doing something for your efforts to improve their software

    Thanks,

    An avid PC-DMIS user from the future using PC-DMIS 2022 SP13 with a lot of the same issues with a different UI Slight smile


    Gets a new job where they run *other CMM software*: "ah In PcDmis we can do that!"...."PcDmis is sooo robust"....."no it's not that difficult to use, it can be totally customized for any level"....."I so miss PcDmis"

    JK original poster you have a right to a voice, I have a feeling *they* are listening (more than I've ever seen or noticed) I'm just having a little fun with you, cheer up it could be worse somehow.
  • We rely on what the CMM report says too but we also realize that no software is 100% bulletproof and certain dimensions, regardless what the CMM says, will be dissected and verified to the best of our abilities either with the CMM or with manual checks.

    Again, I understand the frustration because we run into it here too, but realize the size of the team that would be required to run the software through every possible situation that it will encounter out in the field. I think you would get an update every few years and the cost would triple or more because of the manpower that would be required. Even after all that, there might still be some small bugs that would have to be worked through.

    I'm not trying to defend Hexagon or bash them, I'm just looking at it from a logical standpoint realizing the size and complexity of the software. They have done a good job so far and I'm sure the company I work for doesn't mind me spending a little time figuring some workarounds to some of these bugs and they have no problem with me sending crash reports and communicating with people, both on here and at Hexagon, to figure out some of these problems. I equate it to the machinists making a setup part out of cheaper material before making the part out of good expensive material. Not an exact equal but it's the best I can come up with at the moment.