I just installed 2017 and noticed that when a selected object is highlighted, it looks noticeably different than 2016. In 2016, if you pick something like a dimension, it clearly looked dashed (preselectioneffect set to 0, selectioneffect set to 0 in 2016 and 2017). But in 2017, it almost appears like a dashed line over a solid line and doesn't appear fully dashed. And it's not all lines. If I pick a dimension, one of the extension lines looks normal and one has the odd behavior.
![2017 2017](/uploads/1/2/5/3/125369882/741435809.png)
If I turn off HA it's fine, but that's not an option. Card is a FirePro W5000 which is showing up as certified. Seems OK if I set Preselectioneffect and Selectioneffect to 1, but I'd prefer not to.Is anyone sle seeing this?Title edited for clarity byDiscussionAdmin. I am using that driver. I sent an email to Autodesk and they responded that it looks like an HQ Geometry bug and sure enough turning off HQGeom fixes it. Similarly, if I have 2 perpendicular lines, sometimes the line looks like it correctly ends at the other and a simple zoom of one mouse wheel turn will make it look like it extends past it. The 2 images below are the same geometry with one click different zoom.
AutoCAD 2017 highlighting looks different than 2016 I just installed 2017 and noticed that when a selected object is highlighted, it looks noticeably different than 2016. In 2016, if you pick something like a dimension, it clearly looked dashed (preselectioneffect set to 0, selectioneffect set to 0 in 2016 and 2017).
I'm finding it on 2 different computers both with different cards.He said he would pass it along so hopefully it will get fixed. I received a response from Autodesk and their answer did in fact correct the problem. This was their full response:Hi Steve,I got a response back on this question, it is a change made somewhat purposely.
It can be turned off without turning the HQGEOM off, but I am not sure if you will like the turned off result (I am not 100% sure what the impact is to you).If you type 2DRETAINMODE and change it to 0 it should turn off this effect. It is a hidden value.2dretainmode is one of the HQGEOM settings. See if turning it off causes you no other concerns. It is whether the graphics data is cached on the video card memory though so it could be that having the cached graphics is ideal for you. Try it out and see if you see problems that don’t exist with it on.If you like it that way, perfect, but if you don’t then it is a bit of a problem because the problem can’t be fixed with the 2dretainmode on is what I am hearing.
The team may be able to fix it in a future release with more working of the graphics caching, but it is not “hotfix” level fixing. The graphics caching is new to 2017, so it may be that you haven’t really noticed or used it or had any benefit from it. But it does use video card memory to do what RAM was doing/ not doing before. So benefits are going to be use case specific.
The more RAM you had, the less likely this change was to have an impact. So, I wanted to see if you could check for a day or two if you didn’t see a difference.Switching this variable completely solved the problem and I have had no other ill effects from changing it and I have had it this way for a few weeks now.
The odd thing is that the end of the description did not correlate with my situation because they said that you are more likely to see the problem with less RAM, but I have 32GB so that should have been fine. Either way, if anyone is seeing this problem that I originally described, setting 2DRETAINMODE to 0 solved it.
Thanks to Daniel at Autodesk for solving it.