Output Data lost although it has the inputs

Hi,

I am using the latest version of grasshopper. I have this problem with grasshopper for quite a while; while I was working on a definition, sometimes I wanted to disconnect some components and try it out with another one. Once I did so, "disconnect" and I want to connect it again, it seems it loses its output data, although it is hooked the previous components and it has the input data inside, the component fails to give the output data. I need to disconnect and connect all the way back to get the data again, it is annoying. Do you know a way to fix this problem? I would be really happy to hear about it. Thank you in advance.

Attachments:

Screenshot 2015-01-25 13.07.26.png, 388 KB

Replies to This Discussion

Permalink Reply by Hannes Löschke on January 25, 2015 at 4:34am

Does it help to recompute the solution?

-> F5 (Solution>Recompute)

Permalink Reply by Iremnur Tokac on January 25, 2015 at 4:37am

I have tried, it works :) thank you so much!

Permalink Reply by David Rutten on January 25, 2015 at 7:26am

Does it happen with standard components as well?

Permalink Reply by ng5 Alex on January 25, 2015 at 8:19am

Hello David

this happens with standard components too. i have not understood if there are specific ones causing this, but recompute always solves the problem.

Permalink Reply by David Rutten on January 25, 2015 at 9:28am

Well it's good you have a solution to the bug, but I'd love to be able to solve the bug so you wouldn't have to recompute everything just to get at a single piece of data.

Permalink Reply by ng5 Alex on January 25, 2015 at 9:33am

Hello David,

Maybe you misunderstood my answer. I did not post this as a solution to the bug, but as a description of how this problem comes up and what happens when trying recompute.

Just trying to help, so.. i leave it here

good luck with the solution

Permalink Reply by Hannes Löschke on January 25, 2015 at 11:45am

Before we get into bugs and stuff.. does your canvas have a red border and displays a lock symbol at the left side?

Permalink Reply by ng5 Alex on January 25, 2015 at 12:02pm

Solver locked? No

Hannes the above described problem happens (to my pc at least) on the fly, while working with gh with the solver unlocked (of course) with no obvious pattern.

The only thing that is common, is that you delete a component that is enabled in a definition, after restoring the needed inputs with new or even the same component, at some part of the definition, with all the wires connected ok, not necessarily where the deleted component was, you have orange wire with no data.

This is only restored via recompute . It seems like at some point the solver stops.

Permalink Reply by Hannes Löschke on January 25, 2015 at 12:51pm

Just checking... we had a definition, that would not show up in viewport but was working once copied to a new definition until someone realized that the global preview option was set to "disable" in that specific file *facepalm*

If you could please post one such file with the orange wires, so David can check the file for bugs.

Permalink Reply by ng5 Alex on January 25, 2015 at 1:24pm

As it happens in a kind of random way, the best thing would be along with the file to have a video capture showing the canvas.

I will have the next gh seminar captured, i am sure at some point it will happen, though it is not certain.

Permalink Reply by ng5 Alex on October 21, 2015 at 10:48am

an update to this, until gh2 or other solution surfaces. instead of recomputing the whole definition, just re-plugging the orange wired output to its appropriate input makes things ok again.

RSS