Dear Forum,does anyone know what file or seed is used in the creation of the new dgn when a file fence [ff=] is used?
Hi Andi,
AFAIK the ff command makes a copy from the original file, it does not use a different seed file.
Mit freundlichen Grüßen / Best regards Volker Hüfner
| AB_DATE Engineering Software | ab-date.de |
Thank you.ive searched a few forums and see the command SF=, what is this?And is there a better way ti remove graphics only from one file when trying to fix corruptions.Does FF= remove all Material Pallettes?My issue is corruptions in a file. My way to remove them is:FF= graphics,Ref FF'd graphics into Project Seed to confirm its in the correct seed,Run VerifyDGNRun FixRangeCompress All
i find FF is a great way of removing what i call 'background' corruptions, items you cannot see but seem to be picked up and kept in by Microstation. I dont think i 'merge' of one file into another would do this, at least my tests would suggest not.A recent example on a Project where i did this, reduced file size dramatically where nothign else would, and solved major corruption issues by simply following my workflow.
Unknown said:i find FF is a great way of removing what i call 'background' corruptions,
then I do not understand, why you would like to set another seed file?
If you like to use a different seed-file all workflows will be:
1. create new file
2. transfer elements
independent from the technique.
i find after i have FF'd, then take that FF file, copy a Project Seed to merge new FF fiel into, i am finding the fiel sizes fall. I dont know if thats the process i use which creates the size reduction, or the file which was used initially to create the data is poor quality, but thats what i am finding
Merge reference, FF=, Reference and Copy are all methods that can get rid of corruptions found in files that may have come from various sources. I think the more important thing you're overlooking is what are these "corrupt elements" or files size issues that you are trying to clean out? Maybe you could provide an example design file for us to check what is contained in the file. Where did these elements or data originate? Have they come from other companion Bentley products, third party sources, other file formats etc.? It's a bit difficult to provide a solution if we don't know the problem.
RegardsAndrew BellTechnical SupportBentley Systems
id love to know where the corruptions come from too, but when working on a large Project with mutliple suppliers and supply chains, these things happen and its hard to know. You can feed back your findings but the system in place means that managing these files means you dont have edit rights.The Supply Chain use files independantly and dont use them all together so corruptions and file sizes dont matter as much. Its when its federated together that these things manifest themselves, hence these processes to try and find the issues, understand them, feed them back.