2018 hatch problem

[stephenm]

Hi All,

We have a job drafted in Autocad 2017, we opened the drawing in 2018 & all the hatch is not showing correctly.

Hatch is changing to different layers & hatch patterns as well as boundaries for hatch are being ignored in some cases.  The screenshot is of a stair, the 2018 version shows hatch on the stair treads, where 2017 shows none.

We saved in 2018 (showing incorrectly) then opened in 2017 & it shows as it should.

Hatch is able to be changed to the correct pattern & layer within 2018 and saves but this isn't a good option as a fix.

Is there a command that needs changing or is just a hatch bug that requires a fix?

Cheers

Steve

[Alfred.NESWADBA]

Hi,

can you show the DWG file too?

So we can look if we get the same display ...

- alfred -

[Alfred.NESWADBA]

Hi,

one additional info, there exists already a first update for AutoCAD 2018 (something about annotative objects), can be installed by Autodesk Desktop App, maybe that solves this issue.

- alfred -

[dieters]

Hi Stephen,

Yes, if you could even post a portion of your drawing file, we would like to look at it. If you can't do this publicly, go ahead and email it to me at

dieters@you_know_who.com.

Thanks,

Dieter

[stephenm]

Thanks for the quick response Alfred & Dieter.

I wblock'd the area for you both to check out.

We checked the Autodesk Desktop App and it says that all updates have been installed.  I can only guess when we installed the fix had come with it.

Regards

Steve

[Alfred.NESWADBA]

Hi,

I can see that the hatch within the *error file looks strange. But on the other hand I opened your *ok file in AutoCAD 2018 and the hatch looks ok, at least looks equal to opening that file with AutoCAD 2017.

So to make sure: when you open the *ok file you get again troubles with the hatches?

>> it says that all updates have been installed

If you don't know whether you up-to-date with AutoCAD start command _ABOUT, in the dialog you can see the version of your product, should be now

O.61.0.0 AutoCAD 2018.0.1

(that is only valid for today, not for future readers in a year or so! 😉 )

What is strange for me is that there were already 2 updates within the last 48 hours, but both show the same release. The names of the updates are

• AutoCAD_2018.0.1_64bit.exe
• AutoCAD_2018.0.1_64bit_r2.exe

Could get critical for support to not know which of those two fixes were installed when both fixes show the same product-version 2018.0.1 😉

- alfred -

[dieters]

Hi Stephen,

Thanks for providing the DWG files. When I open them both in AutoCAD 2016 or 2017, they appear the same. But when I open them both in AutoCAD 2018, there's a difference in the hatch boundary. Hmmm.

I sent your files to our test engineering people for their evaluation. Let's see what they find out.

Thanks for letting us know.

Dieter

[dieters]

Alfred,

Thanks for checking into this problem as well.

Incidentally, for keyboard guys like me, a fast way to check version numbers is by entering _VERNUM at the Command prompt.

Dieter

[nrz13]

I've always used ABOUT (ESC to exit) to see the version number.  This method also shows you the service pack level installed.  I don't get that with _VERNUM.

[Alfred.NESWADBA]

Hi,

>> fast way to check version numbers is by entering _VERNUM at the Command prompt.

Does not show which of that two fixes is installed.

_VERNUM shows "O.62.0.0"

_ABOUT shows "O.61.0.0 AutoCAD 2018.0.1" ==> so at least this gives the info "there is a fix installed"

- alfred -

[dieters]

nrz13 and Alfred,

Yes, good point. Here's another sample comparison:

ABOUT       M.107.0.0 AutoCAD 2016 SP1

_VERNUM  M.107.0.19 (UNICODE)" (read only)

Thanks,

Dieter

[stephenm]

Found the update this morning, but the issue still shows on 2018, but not on 2017.

I tried saving as the 18 format and reopening to see if the file type could fix but no luck.

Cheers Alfred for the idea.

[stephenm]

Thanks Dieter,

Hopefully they can find out what the problem is.

The hatch boundary change is something I have never seen before when starting in a new release.

I did upgrade this morning to 0.61.0.0  which was released 3 days ago & is the only available update for us on the Autodesk App currently.

Regards

Steve

[Alfred.NESWADBA]

Hi,

>> but the issue still shows on 2018, but not on 2017

May I ask you for the two drawings you have sent:
The file 2017 hatch working ok.dwg was (that was my understanding) the file before you opened it in 2018.

And when you open that file the hatch looks different depending on you open that with 2017 or 2018. ... is that correct?

Because when I open that file in both releases I can't see any difference (whereas I do not have any XRefs that exists in that drawing, that could be a difference).

- alfred -

[lim.wendy]

Thank you for submitting your question in our discussion forums. The issue that you describe has been
reported to Autodesk and is being researched by our development team. I apologize for any inconvenience in the meantime.

[Anonymous]

has anything been resolved? We are having the same problem in 2018. 

Thanks 

Tracy

[dieters]

Hi Tracy,

As I mentioned, we're aware of the problem, but please understand that I can't comment on work in progress or future fixes.

Major defect fixes are always noted in the Readme for any product update.

Dieter

[Anonymous]

This command worked for our problem.  It was a problem with the density of the hatch. 

(setenv "MaxHatch" "1,000,000")

Thanks, 

Tracy

[Anonymous]

Hi all,

I found a solution:

[telze33]

Has this problem been resolved?  I ran into it on a drawing previously created on 2016 or 2017, and now my gravel hatch is not showing up - even though it's there.  In speaking with CADMasters, Inc., it is also an issue in 2019.  How is it that we pay thousands of dollars for a software package and something as fundamental as a Hatch pattern is not showing up properly for 2 straight releases without being fixed?! 

Autodesk needs some competing software so that they can step their game up.