RunScript Error

[Anonymous]

Hello!

I've been using AutoCAD in education for awhile now and I'm really satisfied with it's performance, but I've noticed a bug. In older versions (2013 and older) .SCR files work normally when calling a Run Script command which loops in such a way that it can make an animation (e.g. rotating objects), but in the new 2017 version the software stops responding after Running such a script. I have an installation with an education license and tried updating it with Autodesk Desktop App, but it didn't fix the problem. Can you help me? Thanks in advance!

Robert

[Alfred.NESWADBA]

Hi,

with release 2015 there was a major update with the handling of graphic card (and so raising performance!). That modification might be the reason that a script with a lot of screen handling runs differently.

One idea would be to disable the graphic acceleration (command _GRAPHICSCONFIG) and see if that works better then.

If you can upload the script and the drawing we might also test it on our systems.

HTH, - alfred -

[Anonymous]

Thank you for your quick reply.

Disabling the graphics accelerator and anything related, doesn't really fix the problem. I've uploaded the drawing and the script in a ZIP.

Is there an alternate way then? I've even tried adding a DELAY in script, but it didn't help. The program still lags.

[Alfred.NESWADBA]

Hi,

your script with your drawing is working well on my system, so it may depend on missing service packs for your AutoCAD 2017, using command _ABOUT the dialog shows that:

Or updating the graphic card might help.

Which graphic card and operating system are you using?

- alfred -

[Anonymous]

I have 1.2 update. OS Windows 10 Pro 64bit, Intel(R) HD Graphics Family.

I have another laptop with Windows 7 Ultimate, 32bit. ATI Radeon Xpress series. That one has no updates.

The issue occurs on both PCs.

[Alfred.NESWADBA]

Hi,

>> I have 1.2 update.

Thx for the info, missed that, installed it and ... wow, seems to be slower than without Update 1.2. But I do have a lot of applications open (which I can't close for now), maybe that is the reason why it looks slower.

Please find attached how it works on my system now:

- alfred -

[Vinayv4v]

Hi,

I think its a variable issue. Some variables need to be changed when running scripts.

Like OSNAPCOORD <0>

Turn off your OSNAP

FILEDIA <1>

What message you get on command line when running the script. Please post a screen shot.

It works perfect on mine too.

Press F2 and check whether the script is intialized and break at a particular step or not.

[Anonymous]

Thanks Alfred, but as you can see it lags, I mean the animation lags. Tried to remove the delay from the script, but nothing changes.

Maybe I should try to install update 1.1? Or did they fix this in AutoCAD 2018? Does anyone have that version?

Hi Vinay! Tried those commands, but it doesn't work for me.

It is strange, cuz I have 8GB of RAM and I don't have that many system process and APPS running in the background. It must be something else.

If you want/need I can capture the screen while running the script in an older version of AutoCAD (e.g. 2013), so you can see how smoothly the animation appears?

[Alfred.NESWADBA · Accepted solution]

Hi,

I have now tried with 2013 to compare the speed.

Yes, 2013 runs the movement much more fluently.

I also have tried 2018 and it's running the same speed as shown in my animated gif before.

BUT: change your visual style to "Wireframe" instead of "2D-Wireframe" ... and you are back 😉

(that is valid for 2017 as well as 2018 as I have tried these 2 versions ... and I guess also on previous releases with the new graphic-handling)

- alfred -

[Anonymous]

It seems that one solved my problem. It is odd that it runs more smoothly in Wireframe, rather than in 2D-Wireframe mode.

Thank you, Alfred for your dedicated time and for your help!

[Alfred.NESWADBA]

Hi,

>> It is odd that it runs more smoothly in Wireframe, rather than in 2D-Wireframe mode.

The difference is that in style "Wireframe" the graphic card is more involved and does most of the work ... whereas in "2D-Wireframe" the calculation is done by the CPU (using a graphic emulation before transferring the screencontent to the graphic card).

- alfred -

[Anonymous]

I see. Thanks again!

Have a nice day! 🙂