How to use Grasshopper Tekla Live Link in Rhino 8 and Rhino 7?

[Jenny_Thoon]

Can I use the Grasshopper Tekla live link in Rhino 8 and Rhino 7 , at the same time ???

[sebastian.lindholm]

Yes no problem, though to get the link to work in Rhino 8 use the SetDotNetRuntime command and set it to NETFramework, then restart Rhino.

Cheers,

-b

[Szymon_Lubas]

Hello,

I have the problem with Rhino 8 and Tekla 2023 SP5.
I downloaded:
the newest version of Rhino 8 in Polish language
tekla live link 2023.1.15 from tekla warehouse
and put proper file in grasshopper libraries

I still not see Tekla - label in grasshopper
I try to use SetDotNetRuntime - but the Rhino give me “unknown command”

Can you help me in that topic?

[Rajeev2 (Rajeev)]

Check the GHA file is unblocked or not

[Szymon_Lubas]

I checked it but the file was unblocked.
I found a solution yesterday. Problem was with 1.15 version of live link.
Sebastion Lindholm in another topic at forum released 1.16 version of Tekla live link so I downloaded new version.
The second step is to use SetDotNetRuntime command in Rhino 8 and set NETFramework, then restart Rhino.
Thank you, for your message

[Zezza]

Hello Sebastian,

Could you please guide how to force Tekla Grasshopper component to compute via Rhino 7 if both Rhino 7 and Rhino 8 installed on the system? Any possibility for a switcher in the component window? I feel that I read somewhere your reply on this point, but could not find it now.

Thank you!

[sebastian.lindholm]

Hi Zezza, at the moment the GH component will use the latest installed version which is Rhino 8 in your case - there’s really no good way to get around that without uninstalling Rhino 8.

My hope is that we can find a way to get the same behavior regardless of the Rhino version used. But as there still are some issues with Rhino 8 we might need to create two different versions of the GH component. Or indeed some kind of switch, I’ll have a think about that.

Cheers,

-b

[Zezza]

Hello Sebastian,

Thank you for the reply! Got it!

I had an issue with a license upgrade for Rhino 8 and could not continue my work with Rhino 7 as the GH component was trying to compute via Rhino 8. Also thought this way and was about to uninstall Rhino 8, but finally got my license for Rhino 8 settled down.

Right now for me, the main drawback with Rhino 8 is the well known for you issue with old C# scripts. My colleagues in a different office bought Rhino 8 recently and do not have Rhino 7 with them. As very few of my definitions do not contain C# scripts, it is really a headache for me now. Any workarounds over there or should I start recreating the C# scripts in Rhino 8?

Thank you!

[Zezza]

Hello again Sebastian,

Is it so, that C# scripts of GH in Rhino 8 do not work via GH component in Tekla?
Tried to download the latest assemblies of the both link itself and component from your Google drive links, but still looks the same.
While working in a “live” connected model, they work fine.
.

[sebastian.lindholm]

Hi Zezza,

Yes old C# scripts have been an issue. I think we’ve got it to work now with Rhino 8.4 however.

When did you download the latest version? Added an update here two days ago for testing:

https://drive.google.com/drive/folders/1ASnmQUpP7rkC7vjthVTFF9nGkvJyfOz_?zx=i61muk2ssm5v

Uninstall the old one first from the Extension Manager in Tekla.

This update will place a copy of System.Collections.Immutable.dll into the GH Component dll folder. Check that you get this result after install:

I’d be great if you can confirm whether this works or not using Rhino 8.4.

Cheers,

Sebastian

[Zezza]

Hello Sebastian,

Thank you for the detailed reply!

@sebastian.lindholm

Yes old C# scripts have been an issue.

I sound silly to myself, but old C# scripts from Rhino 7 do not work in Rhino 8 as such. I have replaced them with Rhino 8 C# script components.

@sebastian.lindholm

I think we’ve got it to work now with Rhino 8.4 however.

My Rhino version is Version 8 SR4 (8.4.24044.15001, 2024-02-13).

@sebastian.lindholm

When did you download the latest version?

Just yesterday. I always check in those two Google folders for the updates before approaching you.

@sebastian.lindholm

Check that you get this result after install:

Checked. It is there:

@sebastian.lindholm

I’d be great if you can confirm whether this works or not using Rhino 8.4.

So here we are, it does not work with the above mentioned conditions!

[sebastian.lindholm]

Oh bugger, thought we had it!

Just to clarify though:

@Zezza

I sound silly to myself, but old C# scripts from Rhino 7 do not work in Rhino 8 as such. I have replaced them with Rhino 8 C# script components.

Are you saying that Rhino 7 C# components don’t work at all when using Rhino 8? I.e. regardless of the GH component.

And that Rhino 8 Script components do work, but not when triggered through the GH component?

Do you get any message from the components (balloon popup) when they fail?

Cheers,

Sebastian

[Zezza]

@sebastian.lindholm

Are you saying that Rhino 7 C# components don’t work at all when using Rhino 8? I.e. regardless of the GH component.

Rhino 7 C# components work with a direct connection. Via GH component they do not work at all, the messages are as following:
[ ERROR from the “C#” component ] Solution exception:Method not found: ‘System.Collections.Immutable.ImmutableArray1<Microsoft.CodeAnalysis.Diagnostic> Microsoft.CodeAnalysis.Emit.EmitResult.get_Diagnostics()'. [ ERROR from the "C#" component ] After Solution exception:Method not found: 'System.Collections.Immutable.ImmutableArray1<Microsoft.CodeAnalysis.Diagnostic> Microsoft.CodeAnalysis.Emit.EmitResult.get_Diagnostics()’.
[ ERROR from the “C#” component ] Before Solution exception:Method not found: ‘System.Collections.Immutable.ImmutableArray`1<Microsoft.CodeAnalysis.Diagnostic> Microsoft.CodeAnalysis.Emit.EmitResult.get_Diagnostics()’.

@sebastian.lindholm

And that Rhino 8 Script components do work, but not when triggered through the GH component?

Do you get any message from the components (balloon popup) when they fail?

Rhino 8 Script components do work directly. Via GH component they do not work. No any message comes. As some of them just for text modification, I was trying to attach a panel with Output2 name to get in GH component whether this text at all comes C# script, it is empty (what is in Output panel comes properly):

I could show it live via Teams to you if it is possible for you. As it is very crucial for me now. If you are in Espoo, I could come even in person!

[sebastian.lindholm]

Hi,

I used to get that error as well. That’s what the System.Collections.Immutable.dll in the GH component folder should take care of, but apparently only on my machine

As a test, could you try to disable the Rhino version of the file by renaming it:
C:\Program Files\Rhino 8\System\System.Collections.Immutable.dll

e.g. like this:

And then check if the Grasshopper component now works (probably need to restart Tekla in between).

Note that without this file, Rhino will show an error on manual launch and GH can’t load any scripting components. So this is just for a quick test - give the file back its name when done

Cheers,

-b

[Zezza]

Hello Sebastian,

Now with the proposed disablement of the file, C# scripts get triggered properly via GH component!

Now, I have GH component active in Tekla that which initiated with the disabled file and, after enablement the file back, I have Rhino as well. So, it sounds as a workaround with which I could proceed for the time being. Thx for the trick!

[Zezza]

Hello Sebastian,

Is there any other workaround how to handle this, a bit inconvenient if an user does not have admin rights?

@sebastian.lindholm

I used to get that error as well. That’s what the System.Collections.Immutable.dll in the GH component folder should take care of, but apparently only on my machine

Could it be that you run Rhino/Tekla with admin rights? And I, normally, do not use admin account to start programms?

[sebastian.lindholm]

Hi Zezza,

@Zezza

Is there any other workaround how to handle this, a bit inconvenient if an user does not have admin rights?

Here’s another user reporting that it seems to work on the latest Rhino 8.5:

Live link works but not as component Rhino 8. C#?

Thanks Sebastian! BTW, I Enjoyed you presentation with Kriss, it actually made me start working with Rhino and Tekla. Thank you so much for this. Anyway, last night after closing Rhino, it installed an update so now I have Rhino 8.5.24072. And now the component works!. I do have this error when loading the component for the first time in Tekla. [image] after that, a window pops up from Tekla to report the incident. Once I closed it, Tekla stops responding for a few seconds and then everythi…

So maybe give 8.5 a try?

I also added a Rhino version selector to the latest GH component release that you can use if you have Rhino 7 installed and prefer to use that

Download here:
https://drive.google.com/drive/folders/1ASnmQUpP7rkC7vjthVTFF9nGkvJyfOz_?usp=sharing
Remeber to uninstall the old one first from the Extension Manager, and set the version before loading a definition.

@Zezza

Could it be that you run Rhino/Tekla with admin rights? And I, normally, do not use admin account to start programms?

No, there shouldn’t be any elevated rights, so don’t think that’s the difference. Might be other installs registering competing dlls with the system that somehow gets used instead, but that’s hard to pinpoint (at least for me ).

Cheers,

-b

[Zezza]

Hello Sebastian,

@sebastian.lindholm

Here’s another user reporting that it seems to work on the latest Rhino 8.5

Yes, thank you, I saw that comment and installed it yesterday, much better now. However, I still get an error window when loading GH component for the first time in Tekla. Please find TeklaStructures.crash.log attached. Tekla works further though.
TeklaStructures.crash.log (52.8 KB)

I struggle now with C# scripts that refer to Tekla API - they do not proceed via GH component, though with a live link, they work fine. Have you encountered such kind of cases? As an example of the code that does not work - please refer to the attached CS.cs file (exported from a C# script, the code itself is from this forum Tekla Weld).
CS.cs (2.3 KB)

@sebastian.lindholm

I also added a Rhino version selector to the latest GH component release that you can use if you have Rhino 7 installed and prefer to use that

Great, thank you for that! These issues with old/new C# scripts make life trickier in terms of the same definitions to be working in the both versions. Though, I felt much more comfortable and stable with Rhino 7, it seems to be that anyway would need to tackle Rhino 8 somehow.

@sebastian.lindholm

No, there shouldn’t be any elevated rights, so don’t think that’s the difference. Might be other installs registering competing dlls with the system that somehow gets used instead, but that’s hard to pinpoint (at least for me ).

Ok, no problems, this was just a guess!

[Zezza]

Hello Sebastian,

@Zezza

I struggle now with C# scripts that refer to Tekla API - they do not proceed via GH component, though with a live link, they work fine. Have you encountered such kind of cases? As an example of the code that does not work - please refer to the attached CS.cs file (exported from a C# script, the code itself is from this forum Tekla Weld ).
CS.cs (2.3 KB)

I have managed to trigger them with a panel named “Solve”.

[sebastian.lindholm]

Hi again,

@Zezza

However, I still get an error window when loading GH component for the first time in Tekla.

Thanks for posting the log, I think we got rid of the support tool popup with this update:

https://drive.google.com/drive/folders/1ASnmQUpP7rkC7vjthVTFF9nGkvJyfOz_?usp=sharing

I also abandoned the custom System.Collections.Immutable.dll in this latest tsep as, at least on my machine, that’s not needed any more in Rhino 8.5 and the scripting components work fine. Fingers crossed!

@Zezza

I struggle now with C# scripts that refer to Tekla API - they do not proceed via GH component, though with a live link, they work fine.

Yes noticed the new Script components have changed type information in the latest Rhino SR, they should now be triggered automatically again.

Cheers,

-b