First attempt at hops fails to create I/O

If you’re using Hops (on Windows) then you should have to point anything to a local server or compute.geometry.exe… I believe whatever guide you might be looking at is out of date. When you install Hops (via the package manager), then every time you start Grasshopper, a rhino.compute instance will also automatically get started in the background. It’s hidden by default, but you can go into the Hops preferences and tell it to show the console window so you can see what’s happening. But, by default there is an instance that already gets started for you and hops is told to send things to that server unless you’ve modified the computer server URL. I would recommend installing the latest version of hops and uncheck the “Hide the Rhino.Compute Console Window” preference so you can see what happens when you start Grasshopper.
Next, it looks like you’re trying to use Elefront (or possibly some other plugins). Not all plugins are guaranteed to work with rhino.compute. Let’s start with a very basic example that has no 3rd party plugins in it. Add a Hops component to your canvas and right-click on it to set the path. Point the path to this file and see if it comes back with any information.
HelloWorld.gh (5.6 KB)

Hi Andy, Thank for your response.
My script only uses eleFront in the main grasshopper window, not in the Hops definition.

That being said, I downloaded HelloWorld.gh and did not work :frowning:


Just as a reference, these are the solver settings:

What happens if you delete the URL (http://localhost:8081) in the Hops URL preferences section (it should be empty) and then you restart Rhino/Grasshopper. After restarting, try loading the HelloWorld.gh file in the Hops component.

I have been working with IT in the company and I believe it is an issue isolated to my machine. The same Hops work on other machines in the office. We even went as far as uninstalling Rhino and purging all the gh apps in the Roaming folder. But still the issues remains. I think IT plans on re-imaging my machine or replacing it.

Thank you for your assistance Andy!

Actually it was an issue with vRay.
when I ran the compute.geometry file it returned an error with vRay. I downloaded the most recent vRay plug-in for Rhino and everything fixed itself!

compute.geometry log:

1 Like