still finding lots of issues in files that it seems only V8's verify dgn is capable of fixing.
Are there any plans to update this to Connect, or provide some kind of file fixer?
I see from other threads that there is a tool FixRange? however NO documentation. where is this, how do I use? I have been able to load using mdl load FixRange but then can find no tool, or key-ins to run????
VerifyDGNThere is no Connect version of this tool. If you have any file related issues, kindly log a Service Request and email the files for review.
FixRangeRe-evaluate the cached ranges of all elements in the file.Load/Execute: mdl load fixrangeKey-ins: set rangeLinks: click here
Thanks Leonard,
however submitting file related issues is not a practical solution. Support is not generally the quickest for a start so expecting us to send a file off and wait for it to be fixed is not workable.
As is normal, these kind of issues do not show themselves when we have acres of time to spare, generally they occur at the business end when time is of the essence and affect multiple files or references. I need a way that I can fix these things without having to resort to support.
Thanks Duncan for this list.
To take it forward we will require supporting files for each of those cases. Additional details like which software/version/format these files originated from will help.
It may take a while to collate definite examples of all these Leonard as we tend to fix, or remake when encountered.
I too find it crashes more frequently than v8i, but it's clearly not file dependent. Just happens randomly. I can say I haven't lost work or corrupted a file in years.
"Reproduce the error, please describe the steps to cause error and include file" is Bentley speak for wtf. I've been on this bus for a few weeks now. Very time consuming and often not fruitful. The techs have been very helpful, just not always real knowledgeable. It is hard.
Always been curious, what happens to those little message we send off when a crash happens? You may not always get that particular option, but I've sent off dozens.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
Another consideration would be to ensure you are backing up your file regularly
https://communities.bentley.com/products/microstation/w/microstation__wiki/19488/automatic-backup-of-design-dgn-files
There are also 3rd party MDL's for automatic backups available one of which is provide by this German user.
The copyrights of these tools are not from Bentley I cannot upload it for you but you may download it here:
www.t-haberstroh.de/backup_V8.ma
RegardsAndrew BellTechnical SupportBentley Systems
Alternatively, Bentley could provide a dgn repair tool. I fail to see the logic in not doing so. we waste more time, and so do bentley support.
Duncan
This is another classic case of Bentley not giving the administrators a the tools we need to be able to review our dgn files and better options to repair them..
Pre V8 we had EDG.. post V8i we had a keyin that is next to useless..... AXIOM have the tools but far too expensive, this needs to be FREE and offered by Bentley.
I raised this IDEAS... please vote.
https://communities.bentley.com/products/microstation/i/design_review/dgn_and_dwg_repair_tools
Completely agree Ian. I voted on your idea over a year ago I think. Partly raised this thread to highlight the lack of action.
I keep a copy of V8 so I can open files into it and verifydgn, which fixes so many issues. My simple question was why remove it from Connect in the first place. as if there was no need for it
That's exactly why we still have V8i installed, too. Some files can only be handled and repaired by V8i. We don't need that option very often but then it comes in really handy.