Fictitious lines appearing

[Anonymous]

I am noticing some short, fictitious lines appearing on my screen.  The show up at vertices and seem to remain in place at the final endpoint.  Is this a feature I can turn off?

Thanks!

[Anonymous]

I am noticing some short, fictitious lines appearing on my screen.  The show up at vertices and seem to remain in place at the final endpoint.  Is this a feature I can turn off?

Thanks!

[pendean]

Post the DWG file, not a picture.

OR insert the problem file into a working file and see if that fixes it.

[pendean]

Post the DWG file, not a picture.

OR insert the problem file into a working file and see if that fixes it.

[Anonymous]

Attached is a sample .dwg.  I have removed much of the bulk but any setting should be saved.

In the event that it matters, I am using 2013 Full.

[Anonymous]

Attached is a sample .dwg.  I have removed much of the bulk but any setting should be saved.

In the event that it matters, I am using 2013 Full.

[pendean]

1. you are in the wrong forum, this is for DWF files and the programs that read them.

2. I can't seem to replicate the problem in R2016 here: is this a sudden new problem for you, or is this a first for a contour file from another user or vendor or software?

[pendean]

1. you are in the wrong forum, this is for DWF files and the programs that read them.

2. I can't seem to replicate the problem in R2016 here: is this a sudden new problem for you, or is this a first for a contour file from another user or vendor or software?

[Anonymous]

1) Oops!  If you would be so kind as to direct me to the correct forum, that would be much appreciated.

2) This is a new problem.  I am current on all updates.  I updated following the problem but observed no improvement.

To clarify, these truly are fictitious lines.  These horizontal segments cannot be selected and there is no vertex associated with the line.  I have made an additional observation - when I start a polyline and undo a segment, the previous segment still prints to the screen even though my new polyline starts from the previous vertex.  All these problems point to a graphics driver in my mind.  Thoughts?

[Anonymous]

1) Oops!  If you would be so kind as to direct me to the correct forum, that would be much appreciated.

2) This is a new problem.  I am current on all updates.  I updated following the problem but observed no improvement.

To clarify, these truly are fictitious lines.  These horizontal segments cannot be selected and there is no vertex associated with the line.  I have made an additional observation - when I start a polyline and undo a segment, the previous segment still prints to the screen even though my new polyline starts from the previous vertex.  All these problems point to a graphics driver in my mind.  Thoughts?

[pendean]

Try turning off hardware acceleration in AutoCAD (3DCONFIG command in R2013) and see if it is a graphics card issue or not.

[pendean]

Try turning off hardware acceleration in AutoCAD (3DCONFIG command in R2013) and see if it is a graphics card issue or not.

[Anonymous]

I tried 3DCONFIG - no dice there.

[Anonymous]

I tried 3DCONFIG - no dice there.

[pendean]

So here is a test: download and install AutoCAD2017 and run it in trial mode, open this file, and see if the problem exists. Does it?
This will at least identify if the problem is R2013 or a graphics card.

BTW, did you check to see if Autodesk has a diver for your card here http://usa.autodesk.com/adsk/servlet/syscert?id=18844534&siteID=123112

[pendean]

So here is a test: download and install AutoCAD2017 and run it in trial mode, open this file, and see if the problem exists. Does it?
This will at least identify if the problem is R2013 or a graphics card.

BTW, did you check to see if Autodesk has a diver for your card here http://usa.autodesk.com/adsk/servlet/syscert?id=18844534&siteID=123112

[Anonymous]

I also use 2013 LT and 2016 Full (for a myriad of uninteresting reasons).  This problem does not carry over into either of those versions.

[Anonymous]

I also use 2013 LT and 2016 Full (for a myriad of uninteresting reasons).  This problem does not carry over into either of those versions.

[pendean]

OK, so it's program specific then.

Any chance you can log into your PC as an all new user with your admin rights and trying to run R2013 to see if the problem tags along?

[pendean]

OK, so it's program specific then.

Any chance you can log into your PC as an all new user with your admin rights and trying to run R2013 to see if the problem tags along?

[Anonymous]

Interesting - I created a new user with admin rights and did not experience the problem.  What does that mean?

[Anonymous]

Interesting - I created a new user with admin rights and did not experience the problem.  What does that mean?

[pendean]

It means you found a solution 🙂 albeit a painful one.

If sticking with R2013 worth it? Not sure what the story is behind your newer software of course.

[pendean]

It means you found a solution 🙂 albeit a painful one.

If sticking with R2013 worth it? Not sure what the story is behind your newer software of course.

[Anonymous]

I use a lot of third party plug-ins.  One of the packages is produced by a company that was bought out - but the new owner has not released updates that work with newer versions of AutoCAD so I am stuck with 2013 (hopefully only temporarily).  I use 2016 for other third party packages that are still being updated regularly.

Thanks for the help.

[Anonymous]

I use a lot of third party plug-ins.  One of the packages is produced by a company that was bought out - but the new owner has not released updates that work with newer versions of AutoCAD so I am stuck with 2013 (hopefully only temporarily).  I use 2016 for other third party packages that are still being updated regularly.

Thanks for the help.

[Emmsleys]

Following up on your thread, were you able to find a solution or a workaround?

Did any of the posts in the thread help with the issue?

Please use the Accept as Solution for those post’s that helped. It may benefit other users who might have a similar question or issue.

Thanks for your time.

[Emmsleys]

Following up on your thread, were you able to find a solution or a workaround?

Did any of the posts in the thread help with the issue?

Please use the Accept as Solution for those post’s that helped. It may benefit other users who might have a similar question or issue.

Thanks for your time.

[Anonymous]

I found a workaround, although it isn't very feasible for day-to-day use.  I have expended a great deal of effort relative to the size of the problem and am unwilling to continue chasing down the source.  Simply put, I am living with the issue which is more of an annoyance than a real problem.

[Anonymous]

I found a workaround, although it isn't very feasible for day-to-day use.  I have expended a great deal of effort relative to the size of the problem and am unwilling to continue chasing down the source.  Simply put, I am living with the issue which is more of an annoyance than a real problem.