Are there any changes in the Rhino.Compute console window?
Unfortunately, nothing is changing on rhino.compute console.
At some point the rhino.compute has crashed and it started to listen localhost:6500 when relaunched.
Thus I have re-cloned compute and app.server in a fresh new folders and now it is working properly.
However, when I try to run examples from localhost:3000/view rhino.compute terminal becomes unresponsive and example page loads indefinitely.
What is the difference between localhost:3000/view and localhost:3000/examples/ ? It seems that /view files are .gh solutions and /examples are .js solutions right?
the /view endpoint attempts to read the inputs and outputs from the gh definition and generates a UI. This only works for inputs such as numbers (makes a number slider). This won’t work for definitions that require other inputs such as points or geometry. The /examples endpoint hosts specific examples (html and js) developed for each GH definition. Here we show how to use other kinds of inputs like curves and points.
1 Like
This is very interesting.
So basically, if the rhino.compute doesn’t need to the input you’ve mentioned (assuming I don’t need to visualize it on web), then it can technically produce the outcomes without html and js right (meaning that it can be simply made like /view endpoints )?
1 Like
that’s the idea of the /view endpoint
1 Like
Most of the /example files are working, however some of the examples such as branchNodeRnd.gh and most of the /view files are not loaded on the browser.
As shown on the screenshot above, the GrasshopperDefinition.cs got an error of saying:
Exception thrown System.NullReferenceException: ‘Object reference not set to an instance of an object.’
and needed to restart the whole process all over again.
On the other hand, it doesn’t show any error on the rhino.compute terminal though.
I’ve updated the appserver to use the latest rhino3dm.js 7.14.0. This fixed some of the other issues you were seeing.
1 Like