Issues with the DOCUMENT LINKS component

[Ish]

I am using the rhino inside Revit plugin and I am getting issues with the “document links” component. I am using geometry from a referenced revit file in my workflow.

Sometimes the component doesn’t work and it gets red, saying the document is a cloud document. But sometimes it works, and also I have tried to load the component in non-cloud documents, and I get the warning as well… looks like a bug. But maybe there’s a solution to make it work consistenly?

[Japhy]

Hi Ish, Can you provide a screen shot on how you are using the component?

In 1.4 last week there is a fix that deals with a revit api name change that may be related to your issue.

BIM360 Linked Revit Models - Rhino Inside

@eirannejad I agree. The issue I’m running into is that the component is not giving me any of the valid loaded links if there are any unloaded links on a drive that it cannot access. If I keep those links in the model and cull the nulls on the link component I am getting “No data was collected…” even though there is a valid loaded link from BIM360 in the model. When I have both unloaded and loaded BIM360 links the component works and just shows the loaded links, its just with the inclusion of un…

Thanks for reporting.

[Ish]

I was about to show you the screenshot of the error, but now after opening up my pc its working ok again…

I keep getting this weird behavior when sometimes works and sometimes not… and the files are the same all the time…

[Ish]

Ok this morning I opened the document again and now I got the error:

[Japhy]

Try expanded your ZUI on the Links component (small plus sign on your screen shot above) and feed in the active doc first, then select the Doc you need with a Value Picker component.

[Ish]

I tried and I still got the same issue (any more thoughts?):

[Japhy]

What version of Rhino.Inside.Revit are you in? This should be fixed in 1.4

BIM360 Linked Revit Models - Rhino Inside

Ok I pushed a change (coming next week with 1.4 release / currently available in latest WIP) that changes how the linked documents are collected. Far simpler now but the Revit API issues still stand: In Revit 2020/21, the mixed linked models are correctly collected but anything with Autodesk Docs:// is not recognized as linked models by the API (DB.Document.IsModelInCloud returns false). see the missing Cloud Ids in the example below [Screen Shot 2021-11-24 at 10.23.59] In Revit 2022 API wor…

[Ish]

I’m using 1.3 something. Which is the one available in Rhino.Inside®.Revit by default.

Where can I get the 1.4?

[Japhy]

In the options you can get the Stable, Release Candidate or WIP (Daily Build)

[Ish]

Thanks Japhy,

I got the 1.4 installed and the problem persists… screenshot:

[Japhy]

Can you provide more information on the environment you are working in?

I see that it’s Revit 2020.2, where are the linked files being hosted?

[Ish]

Sure, take a look at the link paths:

[Japhy]

Thanks, We’ll take a look and try to can reproduce this.

[Japhy]

Can you get the latest Daily Build and give it a try? There is a recently updated fix implemented there. Thanks.

[Ish]

Yes! I will let u know how it goes

[Ish]

With the latest version 1.5.8019.38343, I got a different error:

“1. RhinoInside.Revit.GH: Object reference not set to an instance of an object.”

[Japhy]

Ok, Thanks for reporting.

[Ish]

No worries. Let me know if you find a solution or fix the bug! We are using this to automate a huge project. Its very handy and having that component working properly will make our lives much better

[kike (Kike Garcia)]

Hi @Ish,

What about now on 1.5?

We added also an ouput with the link itself to query for its location in the projects and the ability to filter by the link Name.

Does it work wih your setup?

[Ish]

hi Kike,

can you be a bit more specific? The last screenshot I shared is from the 1.5?

If I could specify the location of the linked file, I think that would work. How can I do that? Can you share an example please?