Grasshopper inside Tekla doesn’t work anymore. I think it is since I installed Rhino8. With Rhino Beta in addition to Rhino 7, I haven’t had any problems. So it may well be that it has nothing to do with Rhino 8
I installed Visual Studio 2022 a few days ago testing the Tekla API. Could that be the problem?
The Tekla Live Link is also not working, version 2021.1.1
Error massages attached
After restarting Tekla and Rhino, the Live Link works fine. Only the Tekla Grasshopper component inside Tekla gives errors.
Hi, thanks for reporting.
The Grasshopper Component will use the newest version of Rhino it can find that’s not WIP, so it will switch to use the newly released final version of Rhino 8 if you’ve got that installed.
The problem is that Rhino 8 uses .NET 7 per default rather than the .NET Framework, which doesn’t seem to work with Tekla.
To get the Tekla-Grasshopper link to work from within Grasshopper with Rhino 8, the fix as per the article is to use the
SetDotNetRuntime command and set it to
NETFramework, then restart Rhino.
For Rhino.Inside and the Grasshopper Component the
SetDotNetRuntime isn’t respected apparently. Instead try this update that enforce the NET Framework:
[EDIT] This might need the link version 1.16, grab WIP here:
This still isn’t perfect, the Grasshopper loading fails when loading assembly GhPython (and Tekla crashes) at least for me.
So you might need to remove the file
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\Components\GhPython.gha
Let me know if you get the same issue and I can dig a bit deeper into this.
Thanks for the quick support!
I installed the new GH componet but then I still got some error messages and then grasshopper indeed got stuck on GHpython.gha. I deleted this one but then I am stuck with the following problem. Your new component needs a newer Tekla Live Link version 1.16 or newer. i have now version 2021.1.10
I have no more maintenance on my Tekla structures 2021 Full (cost me 20.000€ in 2019 en I paid 2 year maintenance of 4800eur/year). Trimble’s licensing policy forced me a several years ago to stop the maintance.
II think I can install a newer version, but I can’t download the file. I have no access to download the live link without maintenace.
Ah ok, I guess the link is considered a maintenance perk… however since I’ve already posted links to the 1.16 WIP elsewhere on this forum to validate fixes, try with this:
The CodeEditor message isn’t something I’ve encountered so let me know in case it still persists!
Thanks, it works.
The message from the script editor is stil comes up
I checked the never load check box, but it still comes up
Jan Van Loy
Hmm, can’t locate where that might originate from. For now maybe let’s hope it goes away once Rhino 8 stabilizes in future releases.
[EDIT] So I do get this same message with Tekla Structures 2021, not with 2023 though. The Grasshopper component plugin for both Tekla versions is exactly the same. After clicking OK everything seems to work fine.
Now I get another error message and Tekla’s GH component is trying to use Rhino 8 again.
any idea what could have happened?
Hi, so yes it will use the latest Final version of rhino that’s installed - Rhino 8 in this case.
Did you manage to get the 1.16 version of the link installed (copy-replace the .gha into the Components/Libraries folder of Grasshopper)? If it can’t find the Tekla components, maybe you need to unblock the file.
The live link works fine, see attachment, but the Rhino.Insite.Tekla (TS 2021 SP9) does not.
I have checked everything but I keep getting this error message. I have used the following TSEP GrasshopperComponentPlugin_1.3.tsep
Jan Van Loy
After the automatic update of Rhino8 and removing GHpyhon.gha again, it worked for a few moments but now the error message is back.
Jan Van Loy
In my previous post I had stated that I was working with GrasshopperComponentPlugin_1.3.tsep but that is not correct. I am working with the WIP version GrasshopperComponentPlugin_1.4-17.tsep that you gave me.
I tested both again but it doesn’t work.
I have renamed the Rhino8 programme folder (see screenshot) to make sure Tekla use Rhino 7 instead of Rhino8. This works but then I have to rename the folder every time I want to use Rhino8. can’t it be set that Tekla should always use Rhino7 until the problems are solved with Rhino8
Jan Van Loy
Hi Jan, sorry which error message do you refer to here? I get the Code Editor one in 2021 but otherwise it works fine (well after removing the GHPython…).
If possible I’d like to avoid having separate versions for Rhino 7 and Rhino 8 as that would require integrations to our build systems that makes everything more stiff. And there will soon be some users that haven’t got Rhino 7 installed so can’t count on that, on the other hand forcing it to always use the oldest version doesn’t feel progressive either… tough one.
I get this error message, see below.
Yesterday after updating Rhino 8.1, it worked as you describe for a while, but after a few tries, the fun was over and I got the below error message again.
The live link works fine with Rhino 8. The Rhino.Inside.Tekla is the problem.