hexagon logo
Register Sign in
  • Replies 39 replies
  • Subscribers 224 subscribers
  • Views 559 views
  • Users 0 members are here
Options
Related

The Future of PC-DMIS BUGS

Jambo The Rambo
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
Parents
  • 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...
  • in reply to A-machine-insp
    Of course - but my "beef" is that there are too many issues and the issues related to calculation done in the software must be priority one - which it seems it is not. As an example, autofeature filtering issues (the filtering isn't done at all), the UPR value maxes out at 1000 which is bonkers, etc.

    In the end, you will have programs that were made when it was working, program that contains workarounds when it didn't work etc, etc. That stuff needs to be more thoroughly tested prior to release. And if it were discovered prior to release but released anyway, it needs to filed as "known issues" in the readme - but there aren't any, ergo, they didn't test it/find it/chose to not say anything?
Reply
  • in reply to A-machine-insp
    Of course - but my "beef" is that there are too many issues and the issues related to calculation done in the software must be priority one - which it seems it is not. As an example, autofeature filtering issues (the filtering isn't done at all), the UPR value maxes out at 1000 which is bonkers, etc.

    In the end, you will have programs that were made when it was working, program that contains workarounds when it didn't work etc, etc. That stuff needs to be more thoroughly tested prior to release. And if it were discovered prior to release but released anyway, it needs to filed as "known issues" in the readme - but there aren't any, ergo, they didn't test it/find it/chose to not say anything?
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement