Exposing/Accessing AutoCAD System Variables

Hi @john.brady​ ,

Drawing variables not set by FME are generally taken from the chosen Template file. If you have a DWG file that is already set up with the appropriate values, please use that as a Template file for the writer. By default, the AutoCAD writers are configured to only use the drawing settings and definitions from the template file, not any of the actual data in them.

Thank you for looking into this and responding @daveatsafe​ ,

Our concern at the moment is the AutoCAD reader (ACAD); (is a distinction between Reader/Writer being made in your reply?)

We do have a template file (of sorts) that we are currently using in our Reader configuration testing. Our concern is that we also have test datasets that should render a specific way because of these BASE/INSBASE setting adjustments made in them but they do not render as expected in FME vs what we see in the AutoDesk env. We have a requirement to be able to detect (and report) the scenario depicted by our test cases but thus far we are at a loss as how to rectify/satisfy the requirement.

Hi @john.brady​ ,

Thank you for the clarification. I'm sorry for my misunderstanding.

I think there is a way to do the verification, by using FME's DWG writer to create a DXF file from the DWG file, then examining the DXF as a text file to find the settings.

I am attaching an annotated workspace that will let you examine INSBASE and UCSBASE. For documentation on the DXF format, please see http://images.autodesk.com/adsk/files/autocad_2014_pdf_dxf_reference_enu.pdf" target="_blank">https://web.archive.org/web/20171013020945/http://images.autodesk.com/adsk/files/autocad_2014_pdf_dxf_reference_enu.pdf

@daveatsafe​ ,

Thank you so much for taking the time and providing this workbench.

I apologize for my delay in follow up.

Thank you for the lead on the use of the dxf as the file does contain the information we are looking to validate

We are now attempting to extend our use of the dxf to check for Proxy Objects/Entities (ie non-native AcDb features, as those derived from AEC applications or ObjectARX applications (if understand that bit correctly ;)) as the DXF documentation appears to support that level of reporting and we believe we've found those entries in our testing dxfs