possible bug - nodes dont work after GH restart

Hi

my students start to report that few nodes in their GR
fail to work when they reopen Rhino and GH in a later time.

For example the revolve does not generate the surface anymore.
It is only orange colored.

Deleting the node and adding a new one fixes it for that moment.

Any tips?

Replies to This Discussion

Permalink Reply by David Rutten on October 14, 2009 at 11:38am

Does pressing F5 also fix the problem? There is a bug with the auto-update logic in 0.6.0019. I already fixed it but it won't be available until the next public release, 2~3 weeks away.

--
David Rutten
david@mcneel.com
Seattle, WA

Permalink Reply by Suryansh Chandra on October 14, 2009 at 4:22pm

I have had similar problems... and there is no assured solution that always works. Sometimes its F5, sometimes copying and pasting the affected node works, and sometimes just replacing it with another one from the toolbar. With a VB node, sometimes I have had to create another empty node, redo all the inputs/outputs and then paste the entire code from the original to get it to work.

The image parsing component's behavior is even more peculiar. I always try to keep image locations relative to the filepath of the main file, but obviously when they change computers, the absolute path cannot remain the same. If GH doesn't find the image, it doesn't give any warnings, but simply removes the image parsing component, and snaps all outgoing connections to the top left corner of the canvas. This can get very messy if the output is connected to several places... it takes a while to figure out what goes where. I think a reliable 'make path relative' will be quite handy. Or perhaps a warning saying 'image not found' instead of the node disappearing.

Thanks.

Permalink Reply by David Rutten on October 14, 2009 at 5:13pm

Ouch... that sounds pretty nasty. I'll see about getting that fixed.

--
David Rutten
david@mcneel.com
Seattle, WA

RSS