Rhp files of Tunny are not loaded

Plug Ins
, ,
1

Hello @hiron san and all,

I’ve been using Tunny 1.3.2.
Recently, it has become that some rhp files (Tunny.LicenseManager.rhp, Tunny.RhinoPlugIn.rhp) are not properly loaded, which leads to the inaccessibility to Tunny.

a
a506×325 27.1 KB

*ロード中にエラーが発生しました: An error has occurred while loading files.

Here are a few things that I’ve been trying:

  1. Confirmed the security of rhp files are disabled
  2. Updated Rhino8 to the latest build
  3. Manually deleted .tunny_env and .tunny_dev_env directories
  4. Manually dragged two rhp files (which I mentioned above) into Rhino canvas
  5. Re-installed Tunny itself

However, nothing seems to work well.

Also, 1.3.2 is the only Tunny version that is inside
%USERPROFILE%\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Tunny,
so I don’t think conflicts of rhp files are the cause.

I would appreciate if you have any ideas how to solve it.
Thank you!
Satoshi

2

Hi @Satoshi_OE san,

Thank you for reporting this issue.
To clarify, does this error only appear with version 1.3.2 and not with version 1.2 or others?

3

Thank you for the reply.
I’ve uninstalled v1.3.2 then installed v1.2.1 via Package Manager.
While installing v1.2.1, it seems that initialization failed for the same rhp files (TunnyLicenseManager.rhp and TunnyRhinoPlugin.rhp).

image
image663×507 95.4 KB

4

Hello, I’ve also tried installing v0.12.0 via Package Manager.
It turned out that v0.12.0 runs successfully without any errors.

5

Hi @Satoshi_OE

Since the cause remains unknown, I’ve modified the system to boot without licensing if rhp fails to load.
Could you please verify this works with the following versions?

6

Hi @hiron , thank you for sharing the latest .yak file!

I’ve just remembered that I once set Rhino environment to .NETFramework 4.8 in order to handle Octopus, and forgot to modify this settings to .NETCore 8. Changing this settings to .NETCore 8 by SetDotNetRuntime command has solved the issue! (FYI, I’ve confirmed the shared .yak file works with .NETCore 8 and does not work with .NETFramework4.8.)

Thank you very much for taking time!!

1 Like
7

The following has been added to this response regarding the issue: