Detail Item family creates huge selection area in view

[PDSF]

Hi all. I created a repeating detail item family called Zigzag.rfa to represent expanded metal lath in a plaster assembly. It works well for this, but it greatly expands the selection area of the view into which it is placed. This makes it a lot harder to select views in a sheet. Can anyone figure out why this is and what, if anything, can be done to eliminate this? TIA for any ideas.

[ToanDN]

For such a simple repetition, I would use a Repeating Detail Component instead of a Line Dased Detail family with an array.

[barthbradley]

I don't get it. This is what I see when I open your family. 

[PDSF]

---

@ToanDN wrote:

For such a simple repetition, I would use a Repeating Detail Component instead of a Line Dased Detail family with an array

---

Hmm, I thought that's what it is. It gets inserted using the Repeating Detail Component command. I'll have to study up on this. Thanks for pointing me in this direction.

[ToanDN]

---

@PDSF wrote:

---

@ToanDN wrote:

For such a simple repetition, I would use a Repeating Detail Component instead of a Line Dased Detail family with an array

---

Hmm, I thought that's what it is. It gets inserted using the Repeating Detail Component command. I'll have to study up on this. Thanks for pointing me in this direction.

---

You use a normal detail family, not a line based family, for a repeating component.

[PDSF]

OK, I looked into this and the family is in fact a detail family. I minimized the 4'-0" dimension that Barth wrote about, thinking that might have been the culprit, but it didn't make any difference. The selection area hasn't changed. Any other ideas?

[PDSF · Accepted solution]

I figured it out. When I reset the reference plane distance to 1/2" and reloaded, I didn't use the "overwrite parameter values" option, so it kept resetting to 4'-0". I use that option so rarely that I kind of forgot what it meant. Thanks for your help.

[ToanDN]

I am still not clear why you need to use a line based family in the first place.  It was a problem that shouldn't exist if you used the correct family template.