How come that one normally made layer is lost in a fence file operation? Only one layer! When checking the original file again, everything is there. After two, three more trials, same story…. Any idea?
Ingemar
It would be helpful if you provided actual details.
What product are you using (with version #)?
What file type (since you state LAYER rather than level I assume you normally use AutoCAD or AutoCAD files)?
What tool, setting & workflow are you using (obviously the Fence File command/tool)?
Microstation CONNECT - 10.17.2.61
ORD - 2021 R1 10.10.1.3
ORD 2022 R1.1 - 10.11.3.2
ORD 2022 R3 - 10.12.2.4
Microstation v8i SS 10 - 08.11.09.919
Power InRoads v8i - 08.11.09.615
ProjectWise - 10.0.3.453
Ingemar Saevfors said:How come that one normally made layer is lost in a fence file operation? Only one layer! When checking the original file again, everything is there. After two, three more trials, same story…. Any idea?
what fence option setting are you using? always works for me...
I think you need to use fence clip clip otherwise if an object isnt fully contained by the fence it can't copy the object hence no level copied
also only turned on visible levels will be captured from captured elements.. not sure if this works with ref attachments... but it should work...
Can you post a sample dgn for one of us to test with..
It may just be the type of element used and where it came from .. I have been getting some strange and wonderful files from open roads designers and in v8i it just doesnt like them...
you havent told use what your using is it V8i or Connect ed or what else? This can make a big difference
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
Hi,
It is Microstation v8i ss4, sure all levels are on. Thanks for suggesting fence clip, but it didn´t work either.
I made an unorthodox trick: I copied the original file and then simply deleted unnecessary elements.
Thanks anyway for your attention.
Good to hear you found a quick work around but .....
Does this happen all the time with different files?
Or just the file in question?
.. I've never seen this behavior in any version to date ...
For benefit of others can you test this and report back as its pretty bad fault if its all the time with all your files...
Are you using xrefs too?