Archive for the ‘Dependent Views’ Category

h1

Callout References with Dependent Views

April 27, 2011

Today I was confronted with an association problem in Revit 2011 with respect to a callout tag improperly referencing the sheet the callout was associated with.

The problem arose with four dependent views of a single composite plan.  Each quarter of the composite plan was placed on 4 separate sheets.  Let’s call them A1.1, A1.2, A1.3 and A1.4.  As soon as the first plan was placed on sheet A1.1 the callout assigned the referencing plan in the callout tag to A1.1, even though the quarter plan where the callout was visible was on sheet A1.3.

You would think that if the callout was hidden Revit would not see the reference and look for the next visible instance of the call out.  Well that is exactly what Revit does but crop regions are not deemed as visibility controls, so Revit thinks the callout is still there.  At least that’s my (non-developer) interpretation of what Revit is doing.

To resolve the problem I had to go to the plan on sheet A1.1, activate the view, turn off the crop region, right mouse click, then “hide in view” the offending callout and back out of the command structure.  So I expected the tag to reset the reference sheet but it didn’t, that is until I clicked on the call out and slightly moved one of the boundary control (blue dots) of the callout.  It immediately changed the referencing sheet to A1.2._____  A1.2?____  What?  I want sheet A1.3.

Well apparently the second dependent view to be dropped on a sheet was on A1.2 so Revit defaulted to the next active instance of the callout tag, which was on the quarter plan on sheet A1.2.  Consequently I had to repeat the procedure above for sheet A1.2.  Once I retouched the boundary control of the callout it updated to A1.3.  Finally!

This points to the fact that having the crop region in Revit act as the activator/deactivator based on visibility would be a nice upgrade as well as the fact that callout references don’t automatically update and require a re-initialization for the callout to rescan for the next visible instance of the referencing sheet.

Dependent Views, Gotta Lovem, Gonna Hatem!
Carl

05-14-12 Update:

Nothing like running into a problem again and thinking your previous solution would save the day.  So here’s an update to the original findings.  Section/Detail references will not update just by extending the section line.  I found you need to rotate them.  As little as one degree will trigger the update, then rotate it back and the proper sheet reference will stay.  That is provided you’ve “Cleared the Other References” see below.

If you are referencing a detail that you have placed on one of your dependent view sheets you are S.O.L. (sh@!*t out of luck).  Nothing will update this reference to the proper sheet where your dependent view is located.  It always points to the first dependent sheet location.  Just put an opaque text field over the improper sheet reference with the correct number.

Clearing the Other References : On this particular project I went to each of the other (3) dependent views including the originating plan and hid the duplicate detail references to make sure there were no cross-referencing issues and only left the detail ref. in the dependent view that was on the sheet I wanted the detail to reference. It successfully updated the references

I understand this is an issue that is on the developers list to correct. Hopefully Revit 2013 addresses this.  I was in 2012 when I posted this update.

Carl