topic Re: Bad definition of FENCELINE1 AT Line XXX in AutoCAD Forum

Bad definition of FENCELINE1 AT Line XXX

Anonymous — Mon, 18 Sep 2017 16:11:25 GMT

In AutoCAD 2018,I am getting Bad definition line types when I load a linetype from a previous AutoCAD version. It works on 2017 but an error message on 2018.

Re: Bad definition of FENCELINE1 AT Line XXX

john.vellek — Mon, 18 Sep 2017 16:21:43 GMT

Hi @Anonymous,

Do you get a similar error if you use Fenceline2? I am wondering if the ltypeshp.shx is missing or inaccessible.

Here is the definition from my working AutoCAD 2018:

*FENCELINE1,Fenceline circle ----0-----0----0-----0----0-----0--
A,.25,-.1,[CIRC1,ltypeshp.shx,x=-.1,s=.1],-.1,1

I have also attached my ltypeshp.shx for you to put in your Support folder.

Please select the Accept as Solution button if my post solves your issue or answers your question.

Re: Bad definition of FENCELINE1 AT Line XXX

Anonymous — Mon, 18 Sep 2017 16:42:28 GMT

I am getting it for fenceline2, batting, zigzag, tracks and other linetypes that was created and defined in 2017.

Re: Bad definition of FENCELINE1 AT Line XXX

chriscowgill7373 — Mon, 18 Sep 2017 16:48:33 GMT

per @john.vellek it more than likely has to do with missing shx or other font files as specifed in the LIN file for those items. The definitions exist in 2018 as well, they've been around for quite a while, unless you've modified the default lin definitions within 2017. Can you post your LIN file so we can compare it with the stock acad.lin file?

Re: Bad definition of FENCELINE1 AT Line XXX

Anonymous — Mon, 18 Sep 2017 16:50:16 GMT

These are the definitions for the linetypes in error for 2018

Re: Bad definition of FENCELINE1 AT Line XXX

Anonymous — Mon, 18 Sep 2017 16:53:14 GMT

See attached. I am also getting Missing SHX message when I open files of previous version

Re: Bad definition of FENCELINE1 AT Line XXX

chriscowgill7373 — Mon, 18 Sep 2017 16:55:30 GMT

place the file that John provided in the same directory as your acad.lin file and the errors should all go away.

Re: Bad definition of FENCELINE1 AT Line XXX

john.vellek — Mon, 18 Sep 2017 16:57:51 GMT

Hi @Anonymous,

Please verify that the ltypeshp.shx exists in your support folder. The path is similar to this one:

C:\Users\vellekj\AppData\Roaming\Autodesk\AutoCAD 2018\R22.0\enu\Support

I have provided a copy of mine in my prior post.

If it exists and is still having problems then do a Reset Settings to Default which will reestablish search paths.

Please select the Accept as Solution button if my post solves your issue or answers your question.

Re: Bad definition of FENCELINE1 AT Line XXX

Anonymous — Mon, 18 Sep 2017 19:01:25 GMT

It exist but still getting the error message when you tried loading a linetype in ACAD.lin I don't get that error message when using AutoCAD 2015 or 2017. It's only in 2018. The support file folder is in the option settings alread. And the file ltypeshp.shx is in the support folder

Re: Bad definition of FENCELINE1 AT Line XXX

john.vellek — Mon, 18 Sep 2017 19:04:40 GMT

Hi @Anonymous,

Can you rename the existing file and then put my file in that folder? Also, please check that the folder gives you full read-write permissions and that it is in the Trusted path.

Please select the Accept as Solution button if my post solves your issue or answers your question.

Re: Bad definition of FENCELINE1 AT Line XXX

Anonymous — Mon, 18 Sep 2017 19:21:58 GMT

I used your file

Re: Bad definition of FENCELINE1 AT Line XXX

john.vellek — Mon, 18 Sep 2017 19:26:22 GMT

Hi @Anonymous,

It is possible that the SHAPE is damaged. Try changing out the shape in the linetype file to see if it helps. Here is an article that describes this process.

Please select the Accept as Solution button if my post solves your issue or answers your question.

Re: Bad definition of FENCELINE1 AT Line XXX

Anonymous — Mon, 18 Sep 2017 19:38:14 GMT

I can’t help but be confused. How was it damaged? It’s a default shx file that comes with the software. I used both 2015 and 2017 ltypeshp.shx (they both worked) and for some reason the 2018 was corrupted. Also on some of my drawings when opened with 2018, I get an error message – One or more SHX files are missing. What would you like to do?

The missing file was ep.shx

Re: Bad definition of FENCELINE1 AT Line XXX

john.vellek — Mon, 18 Sep 2017 19:42:23 GMT

Hi @Anonymous,

Have you checked to see that the EP.SHX is in your C:\Program Files\AutoDesk\AutoCAD 2018\fonts folder?

Can you attach one of the files that is showing these errors? The article I provided in my last post also discusses how some style might incorrectly be referencing the ltypeshp.shx. I would like to see if that is what is happening in the file you provide.

Please select the Accept as Solution button if my post solves your issue or answers your question.

Re: Bad definition of FENCELINE1 AT Line XXX

chriscowgill7373 — Mon, 18 Sep 2017 19:45:42 GMT

It is possible that there was a bad install download. Can you confirm that you updated to the latest updates? I dont recall this being an issue, but it certainly wouldnt hurt to verify you are using the most current version. At the commandline type _VERNUM and report back the number that displays on the commandline.

Re: Bad definition of FENCELINE1 AT Line XXX

Anonymous — Mon, 18 Sep 2017 19:51:58 GMT

_VERNUM = "O.154.0.0 (UNICODE)" (read only)

Re: Bad definition of FENCELINE1 AT Line XXX

john.vellek — Tue, 19 Sep 2017 22:46:17 GMT

Hi @Anonymous,

Can you provide a sample file that shows this problem? I would like to see if the error happens on my side too.

Re: Bad definition of FENCELINE1 AT Line XXX

Anonymous — Wed, 20 Sep 2017 14:38:08 GMT

I had it fixed by reloading the software and copied the 2017 ltypeshp.shx to the 2018 support folder.