Wooly Path Problem

[DanielPiker]

I’m guessing it might be that you need to set the reference to the solver dll for the scripted component.
Are you on Mac? There’s some guidance here for how to do that

Deform mesh internal edges without changing the shape

Yep, as a long term macOS user, I’m aware of that. Thanks for the absolute path to the dll. Entering this when prompted for an unresolved reference solved the issue I had! [Screenshot 2020-03-02 at 19.38.02] @DanielPiker, @dan, entering the path into the dialogue, instead of the whole app renaming business seems to be a better, less unprofessional idea (for a pro app)!! Another long-term solution could simply be to make Rhino/Grasshopper aware of where official dependencies (like K2) are loc…