Hi,
How do you get a fix for a critical bug? I have a regression in Microstation CE U17 that is disabling some of my primary functions for every project. Not only that, Microstation CE U17 is destroying custom information in the dgn files, so even if the file is opened in a previous version, the dgn file has lost our critical information.
I have created a "critical bug" SR. The result is that I got a bug number. In my SR, I noted that I needed this bug fixed "this week", not the next month, or the next release (whenever that comes), or the next year, etc. Typically, a bug report gets addressed in a year or two. I have bug reports from multiple years ago that still have not been fixed. So when my critical bug that needs to be fixed immediately (which was close to a month ago) gets a bug number, that does not mean much.
1) How do I get a critical bug fixed in a reasonable amount of time (a couple days to a couple weeks)?2) We've been paying Bentley since the release Mstn V8i(SS3) without a reliable product to show for that money. To this point, there are still outstanding bug reports about issues that we have to go back to Mstn V8i (SS3) to do, because there are no work-arounds for these items in Mstn CE. How do we get a refund for these Select fees that are not producing proper results?
--Thanks,--Robert Arnold
May be your only recourse is to revert to r16 and hope they fix your issues for r18.
RobertArnold said:How do we get a refund for these Select fees that are not producing proper results?
Let me know if you get any joy for this. Microstation sucks. I estimate I've paid them over 30k$, definitely cancelling Select this fall.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley