Elements from a linked file not showing up

So I think I've found what I'd call a really dumb bug with Revit.
I love the fact that I can create a new workset and have it not turned on in my views by default (saves me a ton of time going through each view to turn stuff off). However when my RS model is linked into the RA model these elements are NOT VISIBLE AT ALL. They don't show up. The only way around it that I've found was to create a new workset and move put the stuff from the invisible workset on the new one; oh and now I have to go through all my views and turn it off.
Did someone not have their cup of Joe when they came up with this?
If I can't control a workset in a linked file, how am I supposed to know this stuff is there. Conversely, how do I know that my stuff shows up in the RA and RMEP models if I were to create a workset like this.
IMHO they should either fix this major bug or get rid of that check box.
Or am I just missing something here. This would seem like a major problem to me.
Any thoughts? Is this a know Revit issue? And if so, Why hasn't it been fixed? These are the kinds of things that make me want to toss this program and go back to ACA. At least there I can take visual control of a "Linked" file.

Click View tabGraphics panelVisibility/Graphics.
Click the Revit Links tab.
Select the linked model or linked model instance to modify.
Click the button in the Display Settings column.
If you selected a linked model instance, select the Override display settings for this instance check box.
In the RVT Links Display Settings dialog, click the Basics tab, and select one of the following:
By Host View. When you select this option, the nested linked model uses the visibility and graphics override settings specified in the host view.
By Linked View. When you select this option, the nested linked model uses the visibility and graphics override settings specified in its parent linked model. You can also select the project view to display for the linked model.
The Linked View drop-down list contains all available plan, RCP, section, elevation, and 3D views from the linked model. The list is dependent on the view you are currently applying visibility and graphic settings for. For example, if you are in an elevation view, only elevation views populate the Linked view list. For 3D views, the type of 3D view you are currently viewing dictates what populates the list (if you are viewing a perspective 3D view in the host model, only perspective 3D views from the linked model display in the Linked View list, and the same applies for orthographic 3D views).

NoteIf the linked model has annotations that you want to display in the project, the annotations must be in either a plan, RCP, parallel section, or parallel elevation view in the linked model. (If you select a section or elevation view that is not parallel, view-specific elements, such as annotations and details, and view specific appearance of non-view specific elements, such as datum extents and leaders, do not display.) You can then select the By Linked View or Custom option to select the view to display in the project.
Custom. From the Nested links list, select one of the following:
By Parent Link applies the visibility and graphic override settings specified for the parent linked model. In other words, the settings of the parent link control the nested link. For example, if walls in the parent link display as blue, then walls in the nested link will also display as blue.
NoteIt is only possible to control categories in the nested link which also exist in the parent link.
By Linked View applies the visibility and graphic override settings specified in the top-level nested linked model. The top-level nested linked model is the first nested linked model. For example, you have the host model, a linked model (the parent link), and then a model that is linked into the parent link (the nested link). The nested link is considered the top-level nested linked model. The nested link will display in the linked model as it does in the parent link. You can open the parent link to have full control of the nested link.
Click Apply to view your changes.
Click OK to exit the RVT Link Display Settings dialog.


Does this help?

Cheers...........

We noticed this issue back in Revit 2009. It is quite inconvenient for the exact reasons that you stated.

Our current Workset creation process states to never uncheck the "Visible by default in all views" check box since the other disciplines have no way of making them visible when they link in that file.

That tell me an extremely complex way to fix a problem that I shouldn't have to deal with.
The archies can't use my "linked" view. They won't match up. 7 layers of steel need to be separated out so my fabricator and erector can figure out the complex geometry the they (the archies) created. So that's not an option. And if I try the Host view, they didn't show up either. I tried the "custom" and turned everything one. Still no go.
I have all these little part plans for the canopy, the entrance overhang and the vestibule framing, with another roof over the top. If I put this on one view, You'll never be able to figure this out.

Quote:

---

Originally Posted by bcgatti

We noticed this issue back in Revit 2009. It is quite inconvenient for the exact reasons that you stated.

Our current Workset creation process states to never uncheck the "Visible by default in all views" check box since the other disciplines have no way of making them visible when they link in that file.

---

Ok, so you didn't find a workaround for this one either.
If it happens, I think the only way around it is it create a new workset and dump that stuff on it.

By Linked View is the only way to circumvent items on a workset set in default invisibility in a Linked Model.

It also means that they would have to create all the views for you in their model, so you could set yours to By Linked View.

As a general rule, i tell users the only time worksets should be set to *not visible by default in all views* is if it is an IN HOUSE item that consultants will never need to see.

This is just another of the reasons that i dont let people here use Worksets for visibility controls.

1. You cant access Linked Model workset visibility in general (aside from load/unload),
2. The visible-by-default issue, only workable by Linked Views.
3. You cant access VG Overrides for Worksets in View Templates.

All in all, these three make it so using worksets for visibility control just isnt worth it to me.

This is crazy. I am having the exact same problem the author of this post is having. Would it be so difficult for the Autodesk programmers to allow for workset manipulation in linked models?? Due to the size of the project we're working on, it is not feasible for me to make all worksets ON by default. In fact, aside from the linked model problem, it only makes sense to have them all OFF by default, and let people turn on the worksets their working in. The alternative means serious element overload whenever we create a new view.

It shouldnt mean element overload at all. First of all, it makes sense for users to only LOAD the worksets they need, when they need them.

Worksets being VISIBLE by default, well of course they should be.

Whats visible in a view should depend on where the view is, what the view is looking at, how far the view is looking, and at what point in time the view is doing the looking (phases).

Ive never understood the desire or overhead complexity of using Worksets for this, given everything else we have to mitigate visibility issues.

If nothing works - check Phasing in Properties and select None to Phase Filters.

The issue was "Fixed" with an update that Autodesk did. Worksets not visible in view by default can now be seen thru links.