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
I agree. It been a while since I have used another software. I would be very interested in a demo of Polyworks CNC CMM. I do know that the company I work for are interested using Polyworks for the arms. We will have to see if Hexagon can get it together. It is unlikely they will.
That's what I have been told. Polyworks free viewer has caught there attention. From what I heard this will work with the CNC CMM software too. It would be the Arms first then move forward to the CMM's. It depends on the new arm and laser that's in the works.
Great. Unforunately, when i was still with Hex PW would flat our refuse to let us try/play with their CNC CMM software so i have no experience with it but i do have experience with the arms/scanning (including the photogrammetry) portions of PW. I loved it.
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?