, HVAC, blah blah).
BIM is NOT a parametric process at least having in mind graphical editors the likes of GH (or stuff the likes of Generative Components): it's a holistic data management approach. Some concepts used in BIM apps (for instance in AECOSim etc) the likes of "walls"/"openings" etc are "parametric" in the sense that allow auto perforation of this with that. On the other hand AECOSim is feature driven (since Microstation works in that "mode" as well) ... a thing that complex things even more with regard what is actually "parametric" and what not.
BIM is as good as the meta data structure is (especially the spec related aspect - Goggle MasterFormat and the likes). BIM AEC apps are notoriously incapable to work (without a lot of lines of code) with proper RDBMS. On the other hand Bentley Systems ProjectWise ... well ... but that's another animal (by no means a topic for the inexperienced).
In descending order or importance a contemporary AEC practice should use:
1. A general information "controller" like ProjectWise (who said/did what/when/why).
2. A Specs (say CSI - not the TV soap opera) management app.
3. Several Meta data RDBMS.
4. A BIM suite of apps.
5. Optionally some parametric thingy.
PS: For AEC ... when inviting the parametric thingy to the party you have only 2 options:
ProjectWise + AECOSim + Generative Ciomponents (my choice).
?? + Revit + Dynamo.
…
a close collaboration with them. Keep in mind that a membrane is 1% the "tissue" and 99% the nuts and bits that keep the tissue properly in place. In order to design bespoke nuts and bits you'll need a decent feature driven solid MCAD app (from CATIA/NX to Solidworks) - Rhino is NOT suitable for that type of work by any means.
The Catch 22 is that these specialized fellas they don't pay any attention to you if they don't know you ... but in order to know you ... blah, blah. …
depends on that data.
So, for instance, if my component is receiving 3 strings and at some point that data changes (structurally or "physically") I have to know it to wipe the old data in my third app and send the new one.
I know that with my clunky method I'm counting more events than necessary but at least I'm on the safe side, avoiding data collision on the third app. If you have any suggestion to improve the performance and the general behaviour of the event listening system I'll appreciate it.
Thanks.
Ángel.…
the distance between the points so the triangles it creates don't have very long sides.All my attempts were very far from the goal so I'm only uploading the population. Pictures 2 and 3 demonstrate how the software works and changes which dots to connect. The software can be found here: https://www.behance.net/gallery/10543937/Image-Triangulator-AppThank you very much!…
d fly with a Porsche flat six).
2. Added a double (nested) Anemone thing (and the Mateusz version) and some comments.
3. Added a stupid "arm maker" cluster ... primitive/ugly/pointless - see one prototype attached about how to do it (you'll need a top feature driven CAD app for this - notice the Teflon low friction ring).
4. In order to "adapt" the cluster arm you need some "stretch" capability (orient, scale et all are the 1st step). Of course putting the cluster into the 2*loop is the art of pointless (Mateusz misinterpreted my bitter comments as regards the "slow" thing, I had absolutely no intension to recreate "live" the arm).
be the Force (the dark option) with you all.…
Just spend 10 minutes watching youtube tutorial of Vray 3 and repeat:
https://www.youtube.com/watch?v=fRWANWkTouY&t=191s
Else-wise you will not learn anything and spend 10x more time because you do not know what you are doing...
For plants you can download textured proxies from here:
http://www.food4rhino.com/app/scatter
Grasshopper vray integration is also straight forward.
Chaos group did good job for user friendly interface.…