Hi David, Yes i did run the installer and it completed "successfully".

Hi Amir, Thanks for the link. I do have some Metahopper and Flux in the graph, but it is not even saving the rhino file. It fails to load the dialog box and simply stops at saving to gh file to wherever it already is...

Hi Andy. Thanks...To answer your question: no, not yet, and I'm not sure what approach we'd take to doing so. It seems that many such plug-ins also accompany Rhino plug-ins too, or reflect other ambitions for their authors, particularly related to more customized installation setups. Freighter identifies and flags those (automatically adds to the readme.txt some basic info about where the dependencies are stored on the author's machine). Our idea thus far has been that if a plug-in has its own installer and separate resource directories, it's probably best to direct any user to use the author's special installer. But I would for sure be interested to hear your opinion on it if you think it would be useful to try to track down + port related files...

@DavidStasiuk. Nice work. Does this also bundle up dependencies that are referenced in a .ghlink file? I know some people will store their dependencies in other directories and was wondering if you're tool account for that.

When you make "freight" from a definition, the above is the interface that shows you all of the third-party dependencies in the file. It lets you choose to include them as you like.

Then it makes a file structure inside of a target folder:

In the "Dependencies" folder are all of the checked dependencies. So you zip up the whole folder, and send it to whoever you want to be able to use your def. Then, when they run the .exe, it copies and unblocks any plug-ins in the Dependencies folder that aren't currently loaded on the user's machine.

We plan on making a bunch of simple enhancements, and will start up the beta soon...sign up if you like!