Any ideas how to check which lines are missing shp symbols when opening a DWG file? The message "could not find SHX font [dgnlstyle]" is not very informative as I would like to know which line was not correctly converted to DWG. The missing symbols are replaced with dots or question marks but it is only visual indicator or is there some way to actually scan and find those broken lines?
Hi Mary B., I know the complexity of a file but there is not such a tool as Oto asked so my suggestion is to try to post on the programming forum to find a VBA that is able to do it.
For now, you can only have the error message without all the information that you are asking for, you can write on the Idea Community this needed implementation: communities.bentley.com/.../
https://microstation.ideas.aha.io/ideas/MSR-I-696
Done!
MaryB
Microstation 08.11.09.919Power GeoPak 08.11.09.918Power InRoads 08.11.09.918
Benedetta Ridolfi said:I suggest creating a new post in the programming forum. Maybe there could have a VBA who can help you
Oto said:[Programming Forum] How to check which lines are missing shp symbols when opening a DWG file?
When peering into the intimate details of a file, particularly a file originating from another application, VBA is not a good tool for the job. VBA's purpose is to automate user actions, which it does very well.
Understanding DWG content and why MicroStation fails to interpret it is not a user task. It requires someone knowledgeable about file formats and how MicroStation's DWG schema is designed to accommodate those dusty corners of another app. VBA is not a substitute for a MicroStation DWG expert.
The AutoCAD guru at Bentley Systems was Don H. Fu, but I haven't seen any activity from him in recent (2021) times. Is there a new Bentley Systems DWG expert?
Regards, Jon Summers LA Solutions
Many elements can use the same line style. Reporting each and everyone of them in the text window is probably not desired. Reporting only the first instance may be better, but it still does not address your concern of locating all elements that use the same line style. Most users care about getting the missing font resolved in the delivery. Benedetta's suggestion of using the config vars to locate the output fonts is the right way to address the issue. Once you know where your SHX fonts are located through the SaveAs process, you can deliver your the font files to the correct target folders based on the product (ACAD, MicroStation, etc) that will use them.
I actually don't care about specific elements. I care about the linestyle in general. As in, which linestyle is using the font that is missing?
Yes, seeing that a font is missing is helpful so that I can go to people and ask them if they can send it to me. But it would be even better to be able to have an answer when they ask "What do you need it for?" (Your ditch flowline...)