I would like to have a few people see if they can reproduce the bug I'm having in AutoCAD 2015.
I've attached a basic example drawing with two overlapping hatches. While drawing a line (or DIST command or similar) over the hatches while "Ignore hatch object" is unchecked in OPTIONS > Drafting Tab > Object Snap Options, I get a very serious lag in AutoCAD 2015 where no lag existed in previous versions. My sample drawing with a small hatch has about a 15 second delay, but with larger, more realistic hatch sizes, the delay is several minutes.
I've been working with AMD on this bug, but they have ruled out it being a graphics driver issue and have determined it's an application issue.
Thanks!
Solved! Go to Solution.
Solved by nrz13. Go to Solution.
I mentioned to have "ignore" off to setup the correct parameters for reproducing the problem. In an ideal world, I wouldn't ever have to snap to hatches and I could just check that box and not worry about it. The kicker is that in 2014 and below, there was no lag at all either way on the exact same setup.
Thanks for testing it for me.
Indeed, this only appears to be reproducible in 2015. It does only happen with dense, overlapped hatch patterns. You can avoid the issue by turning off a layer which contains one of the hatch objects, or you could also increase the scale of one or both of the hatch patterns. I tried both of them set to 10 in your drawing, and there was only a brief stutter as I was drawing the line over the hatch objects.
This is not to say that everything is all well and good, though. I looked internally here and this program behavior has been logged with software development as something for them to investigate further. For now, it appears that the best workaround is the one you've found, unchecking the box for ignoring hatch objects in Object Snap Options.
Zac:
Adjusting the scale size won't work for us because we use hatches to indicate materials (among other things) and those only look correct at the scales we've already set.
Checking the box to ignore hatches isn't a good work-around either because we frequently snap to hatches. If I remember to change it back and forth, it would be more manageable. But the instant I don't think of it, I'll either have to wait for several minutes for AutoCAD 2015 to recover, or I'll have to force the program to close (crash it) and potentially lose data or corrupt the file.
It's not a great situation.
Agreed, it's certainly not ideal. Hopefully, we can get a fix out soon to return things to the way they worked previously, with regard to this hatch snapping issue.
If you'll need to toggle between ignoring hatches and including them in object snapping, you could create a couple new commands to do that. I tried it here, and put the commands onto a toolbar. You could also put them onto a ribbon panel.
For the command to include hatches in object snapping operations, the macro is ^C^C_OSOPTIONS2 (where the 2 is actually on the next line in the
macro, after a carriage return (use the Long String Editor [...] button to access that dialog)).
For the command to ignore hatches in object snapping operations, the macro is ^C^C_OSOPTIONS3 (where the 3 is actually on the next line in the macro, after a carriage return (use the Long String Editor [...] button to access that dialog)).
I've attached a couple of icon image files that I created to represent each command.
Zac:
Thanks for trying to help out as best as you can for now. I already created a LISP routine to toggle back and forth, but unfortunately, remembering to switch back and forth manually is the problem.
If anyone else is interested, here's the code to put in a .lsp file:
(DEFUN C:HS ()(if (= 3 (getvar "OSOPTIONS"))(setvar "OSOPTIONS" 2)(setvar "OSOPTIONS" 3))(PRINC))
Hi Ron-C and nrz13,
Thank you both for reporting the problem. While trying identfy the best solution for this, may I know why you need to snap to hatch patterns?
Hypothetically, if hatch patterns are treated as an annotation object (like text, you cannot snap to the center of "O"), will that be a problem to you?
Off the top of my head, we use snaps on ceiling plans where the hatch is the ceiling grid and we snap light fixtures, diffusers, etc. to the grid. We also use snaps on elevations to specify a new base point relative to an existing hatch so they align as desired. I'm sure there are probably other applications, but that's what comes to mind at the moment.
Hello,
Same problem here, we use hatch patterns for our floor layouts and need to snap to hatch to insert accessories in the grid.
Can Autodesk give information if this will be resolved within a short time?
I was able to test different graphics cards to see if a better card would improve performance. Unfortunately only the NVidia K5000 Card solved the problem for 90% but this will be an investment of at least € 1.800,00 for every PC with AutoCAD in our office! If Autodesk can improve this function as it worked before we would highly appreciate it!
Hope to hear from you.
Thanks.
Hi,
Sorry for the trouble. Your feedbacks have been passed to the development team.
We started using Civil3D 2015 a week ago tomorrow and many of us are having this issue when creating and editing hatch patterns.
Hello,
I have got the same problem in my construction office. I have spent a lot of money to have 2015 version of AutoCAD and instead of increasing productivity of workers I got this annoying and time-consuming issue. So, I am writing to ask about effects of Your work to solve this problem? It passed many months since it has been announced.
Regards
I have found that it is the 'intersection' snap specifically, that causes my AutoCAD 2015 to lag. If you disable that it appears to run smooth.
Hope that helps
Christopher:
Now that we've had 2 service packs and a new release (2016) without resolution to this major performance bug, can we get a better update on when this will be fixed? Thanks.
I use hatching in the same way and I've had this problem since Architecture 2014. I had the same with 2015 and I am now trying 2016. Both 2015 and 2016 will not snap to the intersection of the hatch. So now having just upgraded to Architecture 2016 I still have to 2014. What fun.
I confirm this bug on 2016.
The workaround with disabling 'intersection' snap is working (but I don't like it at all).
Hope for a fix soon.