Matchline appears on a sheet different from where I draw it

[will_kershnerBXZFS]

I have both site plan sheets for land use and site plan sheets for architecture and I'm trying to use the matchline function to break up overall site plan views for each of them. My problem is this: when I draw a matchline on the land use site plan view it appears in the architecture site plan view. What gives?

I DO use view templates for land use views/sheets and matchline is turned on. I DO NOT use view templates for architecture site plan views/sheets and matchline is also turned on. Anything I can try?

[ToanDN]

---

@will_kershnerBXZFS wrote:

I have both site plan sheets for land use and site plan sheets for architecture and I'm trying to use the matchline function to break up overall site plan views for each of them. My problem is this: when I draw a matchline on the land use site plan view it appears in the architecture site plan view. What gives?

I DO use view templates for land use views/sheets and matchline is turned on. I DO NOT use view templates for architecture site plan views/sheets and matchline is also turned on. Anything I can try?

---

Turn off Annotation > Matchline for any views or view templates hat you don't want to see them.

[will_kershnerBXZFS]

The problem is that they don't show up where I DO want to see them, and DO show up where I DON'T want to see them.

The first is what it looks like for the view template where they ARE visible.

The second is what it looks like where they AREN'T visible.

As you can see...they're both checked.

 

[ToanDN]

They may be hidden in view via element overrides.  Reveal hidden elements and see.

[jvpantin2]

As @ToanDN said, you can control matchline visibility from view templates or hiding them by views. But also remember that matchlines are level-constrained elements, you must check top constraint levels to match all floor plans. Probably in your site plan or upper plans they don't show because on Top Constraint parameter  "Unlimited" value is not selected.

[will_kershnerBXZFS · Accepted solution]

Thank you for the suggestions, all of the things you guys suggested could have been the issue but it ended up being that more 'CORE' workset was hidden in certain view templates. Silly, silly, silly.