s are carried over solely via code even for tasks related with K2 (for a vast variety of reasons mostly related with "communications" to/from other CAD apps used in a real-life BIM driven AEC pipeline [where GH plays a small role]).
If 2 is OK with you, drop a word.…
just the geometry. I think this may be of interest to many, not only for Peacock users, so I did it in a separate project.
This may be a continuation of the work of Andrew Heumann, Create Snippets With Grasshopper.
http://www.grasshopper3d.com/profiles/blogs/create-snippets-with-grasshopper
Download:
https://www.dropbox.com/sh/pvhmcf9e42mv5gq/AABf1xTrW08korM0207kpqnHa?dl=0
Is the first time I make a form with controls so I launched a public beta for those who want to collaborate. You can find the VS project on GitHub.
https://github.com/DanielAbalde/GhBrickBox
NEW RELEASE http://www.food4rhino.com/app/brick-box
Any feedback is welcome.
Music: Deaf Kev - Invincible…
this, you'll have no horizontal force at the roller, but you will have it at the pinned support. If you wouldn't, then the structure will be displaced.
Usually, in 2 dimensional structures, if you want to know if an articulated structure is isostatic (as opposed to hyperstatic, which is what you have right now) is to use the following formula:
b+c-2·n=0;
b being the number of bars, c the number of constraints you have and n the number of nodes. In your case: b=19, c=3 (displacements constrained in X, Z at your pinned support and only constrained in Z at your roller support) and n=11, so: 19+3-2·11=0.
I recommend you to download the app SW Truss, as it's very useful to check your results instantly.…
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.…
sive:
It is using up all or a lot of the cycles on the app UI thread. So there's no computing power left over to handle mouse events, keyboard events and paint events.
It is using up more memory than the computer physically has, so Windows starts paging (i.e. using the hard-disk as a memory space). Since disc read/write access is orders of magnitude slower than RAM read/write speed, this will slow down everything.
Some other application is using a lot of computing power/memory and Windows deems that app more important than Rhino.
8GB might not be enough if Rhino needs more than 5GB or so to run. Windows will take up ~2, other apps will take up ~1 unless they are also doing heavy lifting, so you have about 5 left over for Rhino+Grasshopper+++. It is not difficult to make Grasshopper use lots of a memory, but its also not demanded. If you generate 5000 complicated Brep objects, they are going to have to be stored somewhere.
However I cannot comment from here about whether your problem is processor or memory related, or both.
…
glass panel).
2. This actually means that the parts on duty they don't differ that much. Meaning that we can use an "average" size (and "local" topology) acting as the Jack for all trades.
3. Meaning that we can effectively solve the abstract topology with an abstract app the likes of GH and then place in properly defined coordinate systems all the real-life bits and nuts ... closely "emulating" a pro solution (that could "adjust" the parts as well).
4. This means that one particular C# needs more lines of code since as it is it defines cable axis on a per nod to node basis ... but in fact these are defined as the min segment between curves (circles to be exact).
5. Additionally the end part of each strut differs depending on how many pairs of stabilizing cables are used (either 2 or 1). Meaning some lines of code more for defining the proper coordinate systems for the instance definitions.
6. This is the reason that I've postponed mailing to you the 4 horsemen (because PRIOR finishing the whole you MUST define what parts to use: the classic bottom-top design approach).
But in order to receive the Salvation (aka: Apocalypse) you MUST answer correctly to a simple puzzle:
Provided that money is no object, pick your car:
1. Ferrari 245 (Less is more)
2. Lancia Stratos (Lethal).
3. Cobra 427 (Men only)
4. Ford GT40 (Mama mia)
5. Ariel Atom (Mental)
6. Aston Zagato GTB4 (Sweet Jesus)
7. Fulvia HF Fanalone (THE racer)
8. Lambo Miura (Enough said)
9. Lotus Elise (Just add lightness)
10. Alfa Romeo 8C Competizione (In red)…