Hi
I have just updated to 2017 and in doing so;
Is this an inherent issue with 2017?
Can anyone point me in a better direction to a solution?
Cheers.....
Hi
I have just updated to 2017 and in doing so;
Is this an inherent issue with 2017?
Can anyone point me in a better direction to a solution?
Cheers.....
Do you know this one ? SAS (superautoscript)
It is not in English...
About Autoscript : isn't that an external application ? Did you APPLOAD it, at least ?
I'm sure someone who knows it wil help you to find the file to load if you don't know.
Do you know this one ? SAS (superautoscript)
It is not in English...
About Autoscript : isn't that an external application ? Did you APPLOAD it, at least ?
I'm sure someone who knows it wil help you to find the file to load if you don't know.
Hi Dean,
I have loaded this, and loaded its cui as well as the arx file. (Similar to when I had loaded this in previous versions of AutoCAD). The Autoscript menu appears but wen lauching (either via an 'autoscript' in the command line or via the menu drop-down, I get the 'unknown command' error.
Thought I was missing something....
Hi Dean,
I have loaded this, and loaded its cui as well as the arx file. (Similar to when I had loaded this in previous versions of AutoCAD). The Autoscript menu appears but wen lauching (either via an 'autoscript' in the command line or via the menu drop-down, I get the 'unknown command' error.
Thought I was missing something....
I'm not having any issues running it here, I use it all the time.
Reach out to the author/creator of Autoscript for support.
I'm not having any issues running it here, I use it all the time.
Reach out to the author/creator of Autoscript for support.
I know this is old, and you must have solved the problem or found a different product to do what you need, but when we ran into the same problem this is how we solved it. Perhaps it will help others, since I was looking for the solution online, and found this thread, but nothing particularly helpful in it.
In our case we were running a macro (I don't know if this is always the case with AutoScript). In that case, in addition to making sure the location hosting the script called by "Autoscript" is in the "Support File Search Path" in the AutoCAD options, you also need to make sure that path is added to the "Action Recorder Settings" - "Additional Actions Reading File Locations" so the macro created can be found.
Once that path is added, go to the "Manage" tab in AutoCAD, and in the "Action Recorder" pane on the ribbon, there is a drop-down box, which is likely empty. Click on that drop-down box and select your script from the list (which populates after you point to it in the options) to make that script the current item in the "Play" list and then try running AutoScript again.
I know this is old, and you must have solved the problem or found a different product to do what you need, but when we ran into the same problem this is how we solved it. Perhaps it will help others, since I was looking for the solution online, and found this thread, but nothing particularly helpful in it.
In our case we were running a macro (I don't know if this is always the case with AutoScript). In that case, in addition to making sure the location hosting the script called by "Autoscript" is in the "Support File Search Path" in the AutoCAD options, you also need to make sure that path is added to the "Action Recorder Settings" - "Additional Actions Reading File Locations" so the macro created can be found.
Once that path is added, go to the "Manage" tab in AutoCAD, and in the "Action Recorder" pane on the ribbon, there is a drop-down box, which is likely empty. Click on that drop-down box and select your script from the list (which populates after you point to it in the options) to make that script the current item in the "Play" list and then try running AutoScript again.
Can't find what you're looking for? Ask the community or share your knowledge.