minor updates and fixes. Some components require at least Rhino 5 SR12. After installing the pufferfish1-7.gha, please close Rhino completely one time to avoid potential assembly reference errors with the "Twisted Box" components.…
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!…
ood4rhino.com/app/wasp
Wasp Newsletter: https://mailchi.mp/e0ccee5c4e32/wasp_newsletter
Source Code: https://github.com/ar0551/Wasp
---
In this bonus tutorial, we will explore how to use the new SubD tools available in Rhino 7 to simplify the workflow of creating organic geometries from Wasp aggregations. We will use a set of lines as attributes, and convert them to SubD using the MultiPipe component. We will then see how to convert seamlessly between Control Mesh and SubD object.
Download the tutorial files: https://bit.ly/organic_wasp_05
Full Series Playlist: https://www.youtube.com/playlist?list=PLCn3-_9Z4-E6dfKDLUjQUG3w8rxrPrTHN…
some weird engine, you know, he he) IS NOT like designing plain vanilla AEC things.
Therefore features/calculation methods/capabilities as found in MCAD apps (considered off topic by many in our trade) are mandatory for certain types of designs.
Anyway and if we forget FEA stuff, currently I have 3 C# goals:
(1) master the art of controlling the placement of existed blocks in GH defined topology(done),
(2) master the art of baking blocks(done) and
(3) master the art of baking heavily nested blocks that NX/Catia can understand (progress is slow).
…
Or if this doesn't work the the lines who's end points Y value doesn't match
5) join all remaining curves. this gives you polylines for each row.
6) From these you can extract control points that will be on differrent branches
i would demonstrate this but i'm stuck watching the wedding at a friend's and until mcneel makes a rhinoid with gh app you'll have to wait 'til later…
omponents and Revit means Dynamo.
Both are masterminded by the very same fella (Robert Aish: an ex Bentley R&D head, then Autodesk paid more [life sucks]).
AECOSim eats Revit for breakfast but has a far steeper learning curve ... meaning that the masses would opt for Revit.…
emble machines (and require custom Articles for specs, cost pre-estimation and the likes).
Putting yourself against that "forest" you should answer the question N1: you want to just use (the unsafe option) these or cross the Rubicon and collaborate in some way with the software vendors? (the safe option plus numerous benefits: knowing what's in the pipeline years ago, solving bugs in no time etc etc etc).
The question N2 is: do you get involved (or you want to) in "developing" all that the one way or the other? If yes using what "platform"? (so to speak).
The question N3 is: what are your estimations concerning the future in our trade? (count the tremendous acceleration of things as well plus the unavoidable AI factor (sooner or later)).
By answering these 3 ... you can easily answer the other questions of yours.
Bad news: future is past already.…