Callout Visibility

[gordie_v]

I an having problems with Visibility Of callouts.

In Some views they are not visible
in some they are

I applied the same view template to all views
I checked for invisible objects
the views that the callouts make are fine I just can' see the reference
If i try to create a new callout it creates the view but gives warning about created Item not visible.

One view shows a callout that is a reference but will not show callouts that
create views.

am I missing some new "feature"?

[Calvn_Swing]

I'd go to a view, make a callout, check to see that it created a view, and hopefully you'll get the "not visible" message. Check your Visiility Graphics settings to make sure callouts are on. It may be that your View Template has them turned off...

Also, you probably know this already, but callouts are only visible in the view you create them in. You cannot make a callout appear in another view. You have to make a reference other view callout if you want it on multiple views...

I haven't had any issues with callouts in RA2008 or 9.1

Good luck!

[gordie_v]

No the callout visibility is the first thing I checked

there maybe a possibility that they were hidden in view prior to upgrading to 2008, But i'm not sure about that.

[Mike Sealander]

Callouts are either detail callouts or plan callouts. Detail callouts can be made in plan, but they won't show up on your plan. When you make the callout, make sure it's a plan, not a detail. I just had this problem.

[gordie_v]

The callouts are all floor plans, (Enlarged circulation)
the callout views are fine, and when i richtclick and go to Referring views it takes me to the plan where the callout is missing.

[aaronrumple]

The callouts are all floor plans, (Enlarged circulation)
the callout views are fine, and when i richtclick and go to Referring views it takes me to the plan where the callout is missing.
A. Are callouts turned on for the view? Visibility Graphics > Annotation > Callouts
B. Is the detail view property "Hide at scales coarser than" set equal or smaller than the parent view? (Highest probability of being wrong if the scale of the parent view was ever changed.)
C. Does the callout show when you float your mouse over where the callout should be? (R 9.1 and prior)
D. Is the callout outside the parent view's crop region. turn off the crop region to check...

[Calvn_Swing]

I'm betting it's the hide at scales coarser than...

I forgot about that one, and it seems to fit...

[gordie_v]

None of the above

I have now had this problem in a second file
if I turn off the crop region then the callouts show up

so I used a masking region and hide elements to simulate a crop region
if I were to recreate the plan then it would work, but it is a project that has already been sent out for permit so I don't want to make too many changes.

[aaronrumple]

None of the above

I have now had this problem in a second file
if I turn off the crop region then the callouts show up

so I used a masking region and hide elements to simulate a crop region
if I were to recreate the plan then it would work, but it is a project that has already been sent out for permit so I don't want to make too many changes.
What version/build are you using? This was a known bug in the 2008 beta, but was supposedly fixed for the final release. If not, then you should get the file to support as soon as possible.

[joshua]

Wanted to bump this to see if anyone has received a solution yet. I also lose call-outs when crop region is on.
j

[gordie_v]

I ended up turning off crop region and using masking region to simulate

you can also recreate the view and they should show up

[james.detzel]

I have experienced this same bug mentioned above on two of the projects in the office that we upgraded to 2008, but not on others. Interestingly, we have experienced two other apparent bugs related to crop regions:

In one case, which I posted about a week or two ago, the actual crop region was invisible despite being activated and turned on. It could only be accessed by using the Reveal Hidden Elements tool.

In the other case, I had a filled region in a detail that was visible on my screen but did not show up when printed. When the view's crop region was deactivated, the filled region would print just fine.

I wonder if anyone is having these problems with files started in 2008 or if it is limited to files that have been upgrade from 9.1.

[rekstrom]

I just upgraded a very large project last week to 2008 and am also having this problem. I have many crop regions and need solutions fast. Hopefully someone from Autodesk is listening and can get a patch out to fix the problem.

[james.detzel]

Besides the method mentioned above of "simulating" a crop region by using a masking region, I have used only one other workaround: Although the original callout is not visible, you can make a new callout that references the original (the same thing you would do create a similar detail callout elsewhere in your drawings) and these callouts are visible. In my experience it is only the original callout that is hidden by the crop region being activated. Of course, in a big project the re-creation of all the original views can cost a good chunk of time.

[aaronrumple]

This should have been in the read me file as it was identified in the beta testing.
Users should be cautious as a new project from an old template will be affected as well.

Some day Autodesk is going to get hit with a product liability lawsuit over something like this. Imagine the time and liability burden it is putting on offices that are naturally unaware of this issue. If they were any other company, they would have to issue a warning to all the customers and a recall.

Imagine if a critical callout for a structural detail went missing. It could be another Hyatt-Regency collapse all over again (which was basically started with a drafting error.)

[jtl]

I am having a similar problem but I can't tell if people have seen this same thing.

When I create a detail callout (not floor plan callout) on a floor plan the callout is not visible. It is not present even when the Reveal Hidden Elements is activated. The detail is created, but there is no way to get the callout to show on the plan. This only happens with the detail callout. The floor plan callout displays fine.

Is this a bug? It is not a visibility setting as I can tell.

[aaronrumple]

It is a bug and this is the thread about the bug....

[nnguyen]

we have this problem too. it occurs mainly on our dependent views. it seems like if we move the crop region too close to our model, the callouts disappears or if we move the crop region too close to the callout, it disappears too. sent a support request to our reseller. will probably do the same to Autodesk.

what we had to do, is to have the crop region bigger than we would like to so that the callouts will show in the parent and the dependent view. just creates a big "view" region on the sheet. cheers! time for beers!

[s.messing]

It is a bug and this is the thread about the bug....
As usual, Aaron is correct. Autodesk knows about this bug and is in the process of coming up with our first major bug fix of arch 2008. One of our power users discovered it and we are expecting the fix asap. Our solution for now is to let it slide, but only because no one has a deadline this week. You could get the callouts back by any of the methods discussed above. A couple of people have chosen to turn off the crop to get ahold of the callout, but that is certainly not ideal for us, so we are just sitting tight while they grind it through in the factory.

Hold on tight boys and girls.
Hopefully the fix will be here shortly.

Cheers,
Stephen

[Baldwin_4-6-0]

Gordie_v,

We are having the same problem.
It is a BIGa FATa JUICY STINKa BUG.

We WERE going to upgrade to Revit Arch 2008 until we tried to upgrade a 9.1 Project & we discovered this Callout BUG, we are not going to upgrade until this bug is (hopefully) fixed in the next release.

Revit 2008 is probably fine if you start a project in it, I would be very careful if you or your firm has been using Revit for a few years like us, we have too many projects for Revit 2008 to potentially screw up.

Be Careful.. test Revit 2008 on an older project that has been bid or built already and for Goodness sake save a copy before you upgrade it.

[s.messing]

Gordie_v,

We are having the same problem.
It is a BIGa FATa JUICY STINKa BUG.

We WERE going to upgrade to Revit Arch 2008 until we tried to upgrade a 9.1 Project & we discovered this Callout BUG, we are not going to upgrade until this bug is (hopefully) fixed in the next release.

Revit 2008 is probably fine if you start a project in it, I would be very careful if you or your firm has been using Revit for a few years like us, we have too many projects for Revit 2008 to potentially screw up.

Be Careful.. test Revit 2008 on an older project that has been bid or built already and for Goodness sake save a copy before you upgrade it.
Though Baldwin's tone is harsh, he raised two very important (and hopefully obvious) points:
You should NEVER upgrade without archiving the project.
You should always test a project after the upgrade before actually using it.
[Of course, there's a 3rd point that should be mentioned just because: You should not upgrade (unless you absolutely have to) before a deadline]


After the archive and upgrade, you should give yourself a little time to check out the new release, look through all of your sheets, and have a couple of people play around in the model. If there is nothing glaring missing, you can/ should upgrade.
If you find a large insect such as this callouts thing, you will find it on day one and not, as some people do, in week two or three. As you catch this stuff, you can make a decision whether the upgrade is worth the bug or potential undiscovered bugs. We have already saved so much time in our projects because of the new release that the bug (although unpleasant) is not life threatening.

So everyone, Revit, like everything else, is not perfect. You are taking a calculated risk, but it can be pretty rewarding if you are cautious.

Good luck,
Stephen

[aaronrumple]

...As you catch this stuff, you can make a decision whether the upgrade is worth the bug or potential undiscovered bugs.
Note that this bug was uncovered in beta testing. However, Autodesk chose not to include the issue in the readme file....

[s.messing]

Note that this bug was uncovered in beta testing. However, Autodesk chose not to include the issue in the readme file....
OUCH! Maybe I should stop giving the factory a shiatsu and start looking at the facts a little more closely. Thanks for pointing this out, Aaron. If it was a known issue during Beta, it should definitely have been mentioned to the loyal following who were ready, waiting, and upgrading!

That seems totally wrong that Autodesk would not at least let us know about this potential hazard...

[dhamlin]

I was having this same problem, and it appears that it also has to do with having crop regions turned on - thanks for the insight. I'm using Arch 2008. Has anyone found a solution to this yet?

[Baldwin_4-6-0]

Though Baldwin's tone is harsh,
Harsh Smarsh..

You can replicate the error when you place the callouts as Detail View: Detail View Callout and then you have to turn on Crop View & Crop Region Visible and actually crop part of your building.

Only in our template file can I replicate the error, I cannot replicate the error with the Revit 9.1 default.rte template.

We have a ton of older projects created with our template that cannot be upgraded due to this Revit 2008 bugger.

First of all I really really enjoy Revit and it's legacy is just begining, however we are frustrated at our firm. Autodesk gives us this nice shiny new release that we(our firm) cannot use due to a known bug. This issue smells like the smelly smell that smells smelly. I just want to use their new release and now we have to wait until the next one. And also we cannot upgrade our Revit Structure due to waiting for the next release.. and the Revit Structure 2008 is sweet.