Revit can't handle AutoCAD hatch

[drubinoff]

I have a vector-based logo from my client. I want to use it for a sign on my building model.

I have exported the logo from Illustrator to AutoCAD.

In AutoCAD I have created a solid hatch within outlined letters. No problems. Looks great.

I try to bring it into a Revit family. The letter outlines come in but, as for the hatch within the letters, I get the following error:

"One or more hatch regions were found in the imported file with unconnected boundaries. These hatch regions will be ignored."

If AutoCAD can figure it out the boundaries, why can't Revit?

[damon.sidel]

My guess is that the letter outlines are made up of tiny line segments. If some are too small, Revit is going to not import/delete them. Then you won't have a continuous boundary and the hatch cannot be made.

For logos, I've found that you either have to redraw them or use a raster image.

[drubinoff]

My guess is that the letter outlines are made up of tiny line segments. If some are too small, Revit is going to not import/delete them. Then you won't have a continuous boundary and the hatch cannot be made.

For logos, I've found that you either have to redraw them or use a raster image.

Thanks. The logo seems to be made up of splines. What I would like Autodesk to resolve (if you're listening, cher Autodesk) is get Revit to read those splines as well as AutoCAD. If AutoCAD can read 'em, get

[MikeJarosz]

Revit has a minimum line length. In my experience this impacts two areas: fonts converted to lines/polygons and aluminum curtain wall extrusions. Both objects usually are created using tiny line segments, often smaller than the Revit minimum. The usual error that Revit reports after encountering one of these lines is "line is too short". You can search this forum for that phrase. It has been discussed hereabouts many, many times. There are workarounds.

As for your observation "if AutoCAD can do it.......", that attitude will not gather much sympathy in this forum. As someone who has learned four different CAD systems over the years, I can tell you that every software company decides what objects they will include in their software, and more importantly, HOW they will represent them. Acad hatches are a leftover from early Acad when no one had electrostatic plotters that could plot solid fill. Since everyone had pen plotters, fills in Acad were all hatches. Everyone quickly learned that dense line work could substitute for solid fills. It sounds like you have such a file. Anyone working in modern CAD systems will tell you that hatching as a substitute for solid fill is a dinosaur that died off long ago.

You also mention that you exported the logo from Illustrator to Acad. Translations for one file format to another are frequently imperfect, often because of the way the software company chose to represent their data. Consider yourself lucky if your data comes out usable after translating from one format to another. It wouldn't surprise me that splines fall into the category of "difficult to translate". Revit is fully 3D. It bet the accurate representation of a 3D spline requires a PHD in math!

Let's look at this from another perspective. If Revit can do it, why can't Acad? Revit can convert units from feet and inches to decimals of a foot, then into meters and back again to fractional inches without ever changing the size of an object. Why can't Acad do that?

We could start a list of what Revit can do that Acad can't. I bet it would turn out to be the longest continuous post on this forum.