HATCH PROBLEM IN 2017
Check your setting for the HPMAXLINES system variable. Stone patterns can be complex, with a lot of small line segments. Once your hatch has more lines than the value set in HPMAXLINES, the hatch will not be generated. Valid values are between 100 to 10,000,000, inclusive.
By nothing, you mean that if you take a "small" hatch that was working when HPMAXLINES was set to 40000 and made it slightly larger, it still does not work with HPMAXLINES set to 10000000?
Can you share the hatch pattern file, so that others can try to reproduce your problem? It will also be helpful to know what scale factor you have applied to the hatch pattern and how large an area you are able to successfully hatch, as well as how large an area you would like to hatch.
I am not able to reproduce your results, in a relatively small hatch area (10'x10'), using either HONEY or GENERAL_HONEYCOMB.
Are you hatching a really large area? Is that area located a very, very long way from 0,0,0 in the current coordinate system?
The graphics in your sample file are nearly 467,000,000 feet from 0,0,0. At that distance, non-orthogonal patterns like HONEY are going to have issues due to rounding errors, as there are limits to how many decimal places can be included in the pattern.
*HONEY, Honeycomb pattern 0, 0,0, .1875,0.10825317547305483084546539634412, .125,-.25 120, 0,0, .1875,0.10825317547305483084546539634412, .125,-.25 60, 0,0, .1875,0.10825317547305483084546539634412, -.25,.125
Honey has a lot more decimal places than most of the other non-orthogonal patterns, most likely because only one number needs more than four decimal places. At the distance you are from 0,0,0, I am surprised that the 24 scale comes out relatively well. As you have discovered, setting the hatch origin closer to the actual hatch, when you cannot move the graphics closer to 0,0,0, will reduce issues with rounded values.
I am not certain about the ragged hatch boundaries, but I imagine it is also due to the great distance from 0,0,0.
