AutoCAD 2017 - Wipeout Lag Bug

[nrz13]

In AutoCAD 2017, when moving, copying, drawing, etc. over a wipeout with many vertices, the program completely bogs down and becomes unresponsive for several minutes.  This behavior is similar to what was experienced in AutoCAD 2015 and 2016 with dense hatches and may be related, but I did not experience this problem with wipeouts in either 2015 or 2016.

In the attached drawing, try to move or copy the line to the right through the areas with the circles (where the vertices are densest).  Be prepared to hit the ESC key a dozen times unless you have time to wait.

[nrz13]

No, I haven't tested it on my work system yet...it's still too early for that.

So far, it looks like only Alfred and I can reproduce this issue.  So maybe finding the common denominator there, aside from what has already been posted, will help.

Here's a little bit about my setup:
- Windows 8.1 64-bit

- Migration from AutoCAD 2016 on same computer

- NVIDIA consumer graphics card (although problem persists with or without hardware acceleration on)
- All hardware acceleration boxes on except HQ GEOM (grayed out)
- DX11 card, but AutoCAD using it as DX9 only
- Options → Display → Display resolution set to:  20000 / 50 / 10 / 50
- Maximized AutoCAD window
- No Ribbon
- No Command Line
- Dynamic Input On
- Keyboard command input only
- Logitech Setpoint software installed for custom mouse shortcuts
- OSNAPS on
- 1 Custom Toolbar (viewport, layers, layer properties)
- Properties palette open

[Alfred.NESWADBA]

Hi,

bad info's ... I can't reproduce it any more.

What happened to my system in the meantime:

• one difference was that I installed the hotfix1 for AutoCAD 2017. But that hotfix does not handle that problem (not listed in the readme) and even if it would repair this I don't have an explanation why AutoCAD 2016 also does not show this issue any more.
• the maybe more important difference on the system was that I installed some versions of Visual Studio and well, that are a lot of systemfiles (e.g. VC++ redist's, Framework's) which are updated or replaced). Maybe the VS++ Redist repair way (>>>click<<<) or Framework repair could help. But that is more guessing than thinking that this would be a real solution.

Very, very sorry! If I get the issue again producible, I'll come back.

- alfred -

[nrz13]

Thanks, Alfred.  I also installed Hotfix 1, just in case, but that hasn't helped.  I'll have to keep monitoring over time as I keep testing it out to see if I can think of anything else.  It seems very much limited to my system so far, though.  I'll look out for any Windows updates as well.

Thanks everyone for your responses and help!  I'll report back if I find out any more information.

[stevetamplen]

I think Alfred might be on to something.

The C++ components (when they are not working properly) are responsible for all kinds of errors, and when you have any corruption in those elements, you can't even install AutoCAD. The dreaded 1603 error, for example, is caused by C++ errors.

When you get some time, you might want to go to the link Alfred sent and do a remove/reinstall of those components to see if that removes the lag.

[nrz13]

I'll look into it and report back – thanks!

[nrz13]

I removed all the Microsoft C++ entries as directed and reinstalled them one-by-one, also as directed.  I restarted and launched AutoCAD, but alas, the problem remains.

I did notice that if I zoom in (not all the geometry is visible on the screen) and try to draw, copy, etc. over the wipeout that I don't have the problem.  Given the response so far, it seems like it may just be an issue with my particular setup.  After more testing, we may install 2017 on our work computers, at which time I can test with that computer as well.

Thanks everyone for your replies and suggestions!

[stevetamplen]

Please let me know if you need any more assistance.

I will be happy to continue to assist you in trying to determine where the problem in your system is.

[nrz13]

Thanks, Steve.  If you have anything else for me to try, let me know.  I don't know what else to try at this point since it seems like an isolated case at this point.

[stevetamplen]

There are only two things I can think of.

Alfred is running a similar card to yours, a GTX 970M, but he is using DirectX 11 and driver version 10.18.13.6451

You have a GTX 680MX, running DirectX 9 and a driver version 9.18.13.3523 (335.23).

You could try upgrading to DirectX 11 to see if it makes a difference.

You could try the newest Nvidia driver version 364.72 listed for 8.1-64bit, or maybe something in between to see if that helps.

Other than that, I can't think of anything else at this point.

[nrz13]

My card is running as DirectX 11 (or should be anyway), but AutoCAD is misreporting it.  I've tried to get it to show DX11 before and the instructions in the Autodesk Knowledgebase didn't work for me.

I will look into a new driver, though.

[nrz13]

I installed the newest GTX 680MX driver, 364.72 / 10.18.13.6472 (2016-03-21), but the problem persists.  I then went into the Environmental Variables in System Properties Advanced Options and set the GS_DEVICE to Dx11.  It is now reporting Dx11 (not sure why it accepted the Dx11 this time and not before).

However, the problem still persists.

I also found another point of clarification to re-create the issue.  When I'm moving the line, I only experience the lag when my cursor/crosshairs pass through the affected area as well.  If I move the line with the cursor above or below, it's fine.  That work-around is great for this small test, but in real-world drawings, I won't necessarily have a free area to take the cursor through without the lag.

[Alfred.NESWADBA]

Hi,

>> When I'm moving the line, I only experience the lag when my cursor/crosshairs pass through

>>the affected area as well.  If I move the line with the cursor above or below, it's fine

Well, the reason for that could be that wipeout does not support arcs, only lines for the border. And in the critical area the basic objecs are arcs, so wipeout creates a lot of small segments.

BTW: how did you create the wipout? My AutoCAD tells me that wipeout can only be built based on polylines with line-segments.

Depending on the zoom factor the object snap now finds just 1 or maybe 50 segments within the aperture box ... and in case of many segments (many endpoints, intersectionpoints, ...) it now has to proceed to get the one that is the closest one to the mid-point of the aperture box.

Just my 2c why it uses more performance when you are close to the arcs.

- alfred -

[nrz13]

Alfred:

I use a LISP routine to create an approximation of circle and arc wipeouts from segmented polylines.  I know why it would be a higher performance hit there as opposed to other areas; what I don't know is why my hardware can't handle it in 2017 while it can in 2016 and earlier versions.  There is a small lag in 2016 on the same test file, but it's 1-5 seconds vs. about 30 seconds for 2017.

[stevetamplen]

@nrz13

After looking over this whole thread (again) I did have a thought, about the software you said you have installed for mouse shortcuts:

"Logitech Setpoint software installed for custom mouse shortcuts"

Have you tried uninstalling the mouse software to see if it makes a difference? ...or maybe just disabling it so you can test the system for this issue.

Probably won't make any difference, but I hate to leave a problem hanging when there are still things left to try.

[nrz13]

Disabling the Logitech software didn't change anything.

[stevetamplen]

Just checking back in to see if there is any new info you have discovered regarding this issue.

I HATE unsolved problems!

[nrz13]

No, it still locks up when going over complex wipeouts.  If I remember, I turn object snaps off before passing over complex wipeouts, but if I forget, I wait.

[stevetamplen]

Hey, I just wanted to touch base here and let you know that I am leaving Autodesk at the end of the month, so I will not be able to monitor this thread going forward.

If you need someone at Autodesk you can contact John Vellek or S. Emmsley.

[nrz13]

Okay, thanks for the info, Steve.  Best wishes to you in your next endeavor.

[elshawadfy]

Most likely this is related to weak graphics capabilities (regardless of the accaeration on or off)

I can't offer a slution, but i cn offer a temporary fix  if we can call it that..

You can make make both the wipe ot and it's poly frame a block, and close the latyer of wipe outs - keaping the frames layer on while working.., and turn the wipe outs back off..

Why not just turn their layer off?-  Because you may accidently move the drawing keeping the wipeout behind..

--------------

I think you should also consider lowering the resolution of the segments generated by your tracing software.. Revise its options, and decrease segments.. If it uses autocad settings for curves, lower those temporarely until you get wipeout and raise them back aagain afterwards..