@mjmiddle How would the FileSettings metadata object behave in a different SpaceClaim project (i.e. if I used the same scscript in a different scdoc)? Does the FileSettings object capture just the export settings or is there other captured information that might cause a discontinuity between SpaceClaim projects? I ask because once I received an error to the effect of "FileSettings object is not defined" - that is, I had to manually record an export for it to be defined. On another occasion I was able to use the scscript without having to manually record an export. I would like for other users to be able to use the script without any manual intervention so if I can understand the origin of the previously mentioned discrepancy then maybe I can address it.