Urgent Request! After a recent Rhino WIP update, Rhino Inside does not seem to work

Hi

Our team has been working on the geometry server using Resthopper based on Rhino Inside only supported by Rhino WIP. We took the reference from the Github source of Compute and Resthopper developed last year.

After Rhino WIP update(for the most recent version), we no longer get the geometry output from the server with Rhino Inside. We have not checked whether Rhino Inside is working or not, but at this point, our geometry server equipped with Rhino Inside(Resthopper) does not yield any geometry calculation upon the request.

Could you please check the recent update regarding this matter?

Also, we want to make sure that our geometry server is working promptly at least with the previous version of Rhino WIP. Is it possible for us to use the previous version of Rhino WIP without any expiration date? This is important, as in case our web service may not work suddenly upon the recent update of Rhino WIP, we need to go back to the previous version of Rhino WIP which worked well.

Look forward to hearing from you soon.

Best

John

Hi John,

Could you please send us the link to the exact Resthopper repository you are using?

Can you share any other information about this? Any error message or log file you can share with us?

Hi

Here is the link that we took the reference from. We looked at ResthopperEndpoint.cs from Rhino Compute repository.

Before the recent update, the following code line (line 434 from the code) took some time for geometry calculation.

param.CollectData();
param.ComputeData();

After the update, the operation ends without giving any geometry output, while it does not also give any error message.

The grasshopper file we created usually took around 1~2 seconds with the previous verision Rhino WIP, but now the computation ends within milliseconds without any result.

When we reinstalled the Rhino WIP with the previous version (7.0.19163) it worked well again as usual. The current version we have a problem with is 7.0.19183.

Look forwards to hearing from you soon.

Best

John

Thanks for the info, I think is a good start point to see what happened.

@j.chun would you be willing to test a few internal builds of the WIP in between those dates? That would be the quickest way to determine exactly when the problem started so we can figure out what code changes caused this.

Hi @stevebaer

Thanks for the message. Sure. My team is willing to test those internal builds of the WIP.

Could you please send me the link that I can access the list of the previous builds?

At this point, I can only download the latest version.

@kike @stevebaer

Hi All

I am wondering whether our team can get the link to the previous WIP installation file at least at this point? I hope that the investigation for this problem is being resolved by McNeel team.

Thank you

Best

John

Sorry about that; holiday weekend here in the States.

Here’s a list of WIPs to try

7.0.19184.15575 (2019-07-03 15:57:00)
7.0.19184.12335 (2019-07-03 12:33:00)
7.0.19184.07195 (2019-07-03 07:19:00)
7.0.19184.02175 (2019-07-03 02:17:00)
7.0.19183.22165 (2019-07-02 22:16:00)
7.0.19183.19205 (2019-07-02 19:20:00)
7.0.19183.14155 (2019-07-02 14:15:00)
7.0.19183.10495 (2019-07-02 10:49:00)
7.0.19183.10495 (2019-07-02 10:49:00)
7.0.19183.05225 (2019-07-02 05:22:00)
7.0.19182.22235 (2019-07-01 22:23:00)
7.0.19182.17065 (2019-07-01 17:06:00)
7.0.19182.13385 (2019-07-01 13:38:00)
7.0.19182.10145 (2019-07-01 10:14:00)
7.0.19182.05015 (2019-07-01 05:01:00)
7.0.19182.03195 (2019-07-01 03:19:00)
7.0.19182.00325 (2019-07-01 00:32:00)
7.0.19180.08435 (2019-06-29 08:43:00)
7.0.19179.20585 (2019-06-28 20:58:00)
7.0.19179.18435 (2019-06-28 18:43:00)
7.0.19179.15205 (2019-06-28 15:20:00)
7.0.19179.13365 (2019-06-28 13:36:00)
7.0.19179.08215 (2019-06-28 08:21:00)
7.0.19179.06385 (2019-06-28 06:38:00)
7.0.19179.01195 (2019-06-28 01:19:00)
7.0.19178.23365 (2019-06-27 23:36:00)
7.0.19178.18215 (2019-06-27 18:21:00)
7.0.19178.14505 (2019-06-27 14:50:00)
7.0.19178.09345 (2019-06-27 09:34:00)
7.0.19178.04285 (2019-06-27 04:28:00)
7.0.19177.23115 (2019-06-26 23:11:00)
7.0.19177.21285 (2019-06-26 21:28:00)
7.0.19177.16135 (2019-06-26 16:13:00)
7.0.19177.12425 (2019-06-26 12:42:00)
7.0.19177.05455 (2019-06-26 05:45:00)
7.0.19177.00385 (2019-06-26 00:38:00)
7.0.19176.19235 (2019-06-25 19:23:00)

1 Like

Thank you, Steve

We did not know that WIP has been being updated as much frequently as it is shown in the list above.

We found out that the issue was raised from the version 7.0.19182.13385.

WIP (version 7.0.19182.10145) works fine.

Look forward to hearing from you soon.

@kike @stevebaer

I wonder if this is related the the recent break in GhPython as reported at

Hi John,
It would be great to know if the latest V7 WIP (released a few minutes ago) fixes the problems you were seeing. If this isn’t fixed in the latest WIP, we really need to dig in and figure out what is wrong as soon as possible.


Thanks,
-Steve

1 Like

Hi @stevebaer

Thanks for the update!

It is working now.

Best

John

1 Like

Hi Steve, I am new to this forum and recently downloaded the Rhino WIP 7.0.19204.08205 and Rhino Inside for Revit. I am more from the support team and helping user installing the tool after recent lunchtime demonstration from McNeel. I can install the Rhino WIP and Inside on machine using our admin account and after installation all work fine in my admin account. But once the users are back to their standard account, they are unable to use Rhino Inside within Revit. Can you please advice and any further assistance would be much appreciated

Hi Asfakur,

Currently, RhinoInside Revit is installed in the user account at %APPDATA%\Autodesk\Revit\Addins\%RevitVersion%\ the installer copies there a file RhinoInside.Revit.addin a folder called RhinoInside.Revit.
If you move those files to C:\ProgramData\Autodesk\Revit\Addins\%RevitVersion% it should be available for all user accounts on that PC.

Eventually, the installer should install in all user accounts, as you expected.

1 Like