Hi,
From time to time I experience that small acctions makes the file/Microstation to crash.
Today I have had several situations where MIcrostation just crash and disapear. It could be when I press CTRL+F (Save settings) or are moving a view on the sheet. I think it's an errror in the file that makes the program to break down. The question is if it's possible to run a scan of the file in question to see if something is gone bad in it. I mean, the data structure in te file is rather complex, so I could easily understand if an error could sneak into the file.
The problem is that with a bunch of references, added and a bunch of drawing views and and a sheet in the file it aren't a simple task just to start all over again. The file is to complex to just copy the elements from the bad file into a brand one. To redo it all could easily consume the most of a day. With a deadline coming up shortly it's not the thing to spend the time with.
Any suggestions? How do you guys handle situations like this ? Do you experience situations like this at all ?
If it means anything for someone, the Microstaion version is: 10.14.02.01
Thank you in advance
Ole Bro
Ole Bro said: The file is to complex to just copy the elements from the bad file into a brand one.
That's the best way I can think of. Start with a clean seed. Attached the file, use the Copy Attachments mode, merge in the main file. All that should be left is to change the reference nesting depths, if any.
Sometimes simply selecting everything and scaling by 1 or rotating by 0 will clear some issues.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
I like the idea of scaling the content of the file by 1 and insert it at 0,0,0. I will test this to see if it helps.
Thank you for the tip.
ORD Connect:10.08.01.033
MS Connect: 10.14.02.01
Projectwise: 10.00.03.49
run the compress function often, also the repair function while not very functional can help fix things.... my experience is that autocad objects copied into microstation like acad patterning and acad blocks can cause this kind of problem to happen more often... this used to happen even before connect..Bentley really need to give us a repair tool that has a gui and is more diagnostic
In the old days we had the DOS or command prompt tool Edg it allowed us to scan / check and repair individual files as well as batches...Having to rely on 3rd party tools like axiom file fixer really isnt good enough, come on Bentley its been nearly 20 years that we lost Edg... you really need to build and give use a GUI driven repair and diagnostic set of tools.. having to remake complex drawings without knowing what is going wrong is just going to allow the error to reoccur down the road..
Lorys
Started msnt work 1990 - Retired Nov 2022 ( oh boy am I old )
But was long time user V8iss10 (8.11.09.919) dabbler CE update 16 (10.16.00.80)
MicroStation user since 1990 Melbourne Australia.click link to PM me