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.
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.
@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.
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.
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.