Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rhino 6 Compatibility issues #15

Open
mayafox opened this issue Jul 3, 2019 · 7 comments
Open

Rhino 6 Compatibility issues #15

mayafox opened this issue Jul 3, 2019 · 7 comments

Comments

@mayafox
Copy link

mayafox commented Jul 3, 2019

Attempting to import the Wren grasshopper files into Rhino 6 causes unrecognized object errors for Elefront and Human. Attempting to have the package management resolve the issues automatically fails, as no package with the correct version is found.

@timmythomas
Copy link

The WREN GH file wants Elefront version 0.1.0.0. The current version is 4.2.
The WREN GH file wants Google Drive for GH (Leafcutter?) version beta 1. No plug-in found.
I am not sure if these are easy fixes. Please, advise. Thanks.

@pfmephisto
Copy link

@timmythomas
Leafcutter can still be found on GitHub
That said, it dosen't work with Google Sheets anymore.

Therefore I want to see if I can change the script to function with. A regular excel file first.
Does anyone still have the original Google Sheets File so I could use it as a template?

@kiskovce
Copy link

Hi @pfmephisto ,

can You give us little more info what is/ how to use Leafcutter to avoid EleFront issue in Rhino 6. , please?

*can be EleFront 0.1.00 "ElefrontProperties.rhp" found here in community?

@pfmephisto
Copy link

Hi @kiskovce,

I'm not sure which issue with Elefront you are having, but if I remember correctly I'm using the latest version from Food4Rhino.
But I can check for you net time I'm at my PC.

As far as other issues. When I open the file it's far from perfect. I have one Cluster that has a strange exclamation mark that I have not seen other wise before. Some connections seem to be missing and there are some issues with the list order inside some components.

But honestly I've just started meticulously going through each cluster and understanding what it does.

@kiskovce
Copy link

Hi @pfmephisto ,

thank you for your reply and interest.
my Wren - Rhino 6 issue:

I tried to open WikiHouse_WREN(v4.3).gh_ in Rhino but it can't open because "Unrecognize Object "

image

So I fond elefront at https://www.food4rhino.com/app/elefront and downlead it manually and install according readme.txt.

But I can't still open WikiHouse_WREN(v4.3).gh_ because Unrecognize Object EleFront.

Can be this solve by update WikiHouse_WREN(v4.3).gh_ with newer version of elefront?

Thank you for your support.
MK

@melhof
Copy link

melhof commented Aug 5, 2020

Still here experiencing all the above issuess now over a year later.
How do we cry for help, so that the WikiHouse developers will listen and (help to) solve this problem?
@claytonprest @Alastairparvin

@pfmephisto
Copy link

pfmephisto commented Aug 16, 2020

@melhof If you are able and willing to tinker around with the script, I have started reworking some of it in my fork of the project inside the development branch. It's far from solved and still does not fully support all the origin functionality. But it is good enough for the project we had planed. Sadly that project got sidelined for now due to COVID-19 and I'm not sure when I'll get back to working on the wikiHouse.
But I'll try to make some time next week to clean up the branch and push my latest changes.
https://github.com/pfmephisto/Wren/tree/development

In terms of getting help form the wikiHouse developers. From my limited insight is seems they have moved on and are developing a new system they call blackbird, which as of now is still in beta. This means that, they have a guide for the new system, but development of an automatic configurator has not been finished yet.
Also it seems that they are moving away fron grasshopper in favour of a web based solution.

In my opinion, if there is still a wish to use the Wren system even in the light that in a couple of years there might be a new version. Then an effort should be made to rewrite it from the ground up and simplify it along the way. As the way it is now it runs quite slowly an in written very confusingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants