I’m using GeometryGym to replicate a curtain wall from the example file on the technical site.
Few of the components I have, seem to be different, and behave differently than the ones in the example file(although they have the same name.) which makes the workflow a bit confusing. Am I using the wrong version?
Also, in the attached file, changing the height slider somehow seems to affect the visibility/position of the object(in a very weird way - refer images). Could you let me know if I’m doing something wrong?
The problem here is a top down approach I used for IFC when I started creating the plugin.
Ie you effectively create a project, then use a hierarchy approach for site, building, building stories, spaces, assemblies, elements etc.
The benefit (and primary reason) for this is if you create an ifc concept, it’s included in the single database for the grasshopper script/canvas.
We are considering a “next gen” approach of bottom up. Ie you create the inputs such as material/profile, then the elements, then assemblies, the spatial structure. The benefit of this is you could generate multiple ifc data sets on the same canvas, but without care an element might not be wired into a host and be orphaned out of a dataset. There’s also the dilemma then if an object is immutable.
So back to your query. The assembly is being previewed, and because the panel is downstream, it’s not triggering a refresh of the upstream components. I need to think and research a good way to resolve this.
Let me know if this makes sense. In the short term, disable the preview of the assembly and rely on the preview of the components without dependents.
Well it makes sense as to why we see the inconsistencies. I’m currently working on both(top-down and bottom-up) for different projects. I will try implementing the top-down approach first, to understand the flow. Yes, I can (for now) just preview the final outputs.
Is there any place I can check for the component’s update logs or some kind of documentation? I seem to have to(guess) come up with -what goes where- since a few components(that I have) are different from the ones in the example files.
I have been working on adapting my logic according to GeoGym’s top-down approach. I am now stuck at another place where for some(or the same) reason, the geometries are being displaced. Could you check my file and let me know what can be improved?
I have a sample facade with <100 Surfaces(Curtain Wall elements) which need to be sorted by Floor, and exported as an IFC file. My goal is to make reusable clusters that help others use the project setup without getting too much into the details. So, disabling the component, and re-enabling it every time is not very convenient, especially if thee user is not a GH user.
Problem: A few (The first from each branch)panels get misplaced, similar to the original question file above.
Thanks for the post. The reproducible case is helpful, and identified a bug.
I’ve just updated the downloads page with new builds. Let me know if this doesn’t resolve this issue for you or if you have other suggestions and questions.
