ents instead of code ... it could yield a nightmare of components (and a myriad of parameters). For real-life designs I would never attempt to do this without code.
2. A certain experience with Kangaroo (or some min surf other thing since using K on these ... well may be the killing a mosquito with a bazooka thing). That said I'm a great admirer of Daniel's work. But on the other hand why not?
3. A "certain" experience with trusses/space frames.
4. A "certain" experience with instance definitions (that's not doable with GH components).
5. Years of experience with parametric feature driven MCAD apps - Image35 (NX/CATIA) for designing the real-life parts (that have NOTHING to do with "abstract" concepts).
In total I would say that a similar "app" with code (excluding the min surf/mesh thing) would require 6-10 full days of work (or even more).
BTW: https://www.google.com/url?q=http://www.grasshopper3d.com/forum/top...…
(probably during the course of installing some other apps)
Still Grasshopper is showing this error (I've installed the very latest build).
What do I do?…
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.…
in App store.
2. Modelo now supports VR! check out this video:
3. We've added a specular option in the rendering settings. So now you can have your design rendered a little bit shinny-er.
4. There is also a "filters" option in this panel, with which you can get some interesting image post processing effects. We are expanding this filter library, if you have any suggestions, please let us know.
5. This one is very important and has been requested by our customers for a long time. Now when you upload a model, you can grab the reviews(3d comments, screenshots,sketches) from your previously uploaded model! This works really conveniently if you use Modelo for your design review/presentation, cause you don't have to recreate the same 3d anchor views every time you made some changes to your design.
6. Also, our developer API is almost ready, which means if anyone is interested in developing a grasshopper plugin that works with Modelo, they can!
There are some many other updates and bug fixes happened. I don't want to list all of them here. Definitely stay subscribed with our newsletter. Modelo is thrived to grow into a more comprehensive platform! If you have any good ideas about our platform, please do not hesitate to let me know!
Here is our Youtube channel: https://www.youtube.com/channel/UCufBShhLtUQepsit9ilI-AA
Cheers
Qi…
Added by Suqi to Modelo at 1:24pm on October 18, 2016
nd me to kill him but give him my regards anyway) is still around in BirdAir Italy ... talk with him.
3. Hope that you understand that designing the "details" means some decent MCAD app + FEA + this + that. "Fusing" this with some abstract graphic editor like GH ... is ... er ... impossible (in real-life, you know, he he ). Generative Components on the other hand may qualify but requires a lot of time in order to fully master it (approx 2-4 years).
4. FormFinder ... well ... that's utterly Academic but on the other hand ... (good luck).
http://www.formfinder.at/main/software/team/
5. http://tecno.upc.edu/cotens/software.htm
6. This is the second best (after the BirdAir internal stuff) but costs an arm and a leg
http://www.ndnsoftware.com/
7. This is a !%$!%$ in the !%$%!$:
http://www.sofistik.com/no_cache/loesungen/fem/leichte-tragwerke/
My realistic (low cost) advise:
use K1/2 (especially if you are after "parametric" exploitation(s)) ... and then diversify tasks: stuff for the structural department, stuff for whom claims that he can(?) design the "details" ... whilst be in a constant contact with the membrane provider (and in fact: the contractor for doing the real thing as well)
…
ay to make some real-life proper nodes for that kind of T truss (we use machined balls solely for MERO KK type of normal trusses).
3. I'll post here soon a modular demo system suitable for this case (real-life for AEC purposes - NOT for decorative/artistic stuff, I don't care about that since I'm an engineer). This would include a policy for the X struts that require a variable linkage (the X angle). and in the same time a multi cable tensioner "bracket".
4. "Basic" coding next week for T trusses ? Er ... well ... are you kidding me right? I mean that ... hmm ...
5. C# things (about 2+K) around me are classified into 2 "groups": things that are weapons in the right hands and others that serve as demos/start points for mostly abstract cases. The former are internal the latter for public use. I'll remove some sensitive lines from a T truss C# maker and I'll post it here as a "guideline" ... for ...hmm... 4.
All in all:
Provided that you have system(s) on hand (see 3) that work 100% OK in an ideal world you'll need:
A. Something that does the general topology AND (especially) clash detection. Maybe Kangaroo as well as a "first pass" with regard rigidity of the structure in case that you don't adopt a classic T "configuration" (there are many > Google tensegrity).
B. Connectivity trees that relate nodes/edges and maybe faces (say for roofing panels/curtain walls etc etc). Without them is impossible to assemble the T thingy.
C: Something that places real-life "parts" as instance definitions and/or (optional) a "tracking variants history" ability.
D. A bullet proof way to EXPORT things (on an assembly/component schema, say: STEP214 - see C) into a proper BIM app (the likes of AECOSim/Revit) and/or into a MCAD app (the likes of CATIA/NX).
E. FEA/FIM in order to validate the structural ability of the components and the T truss itself.
F. Roofing/cladding/envelope components.
G. "Interactive" cost estimation(s) - T trusses are hideously expensive at least versus "classic" trusses (exactly like a planar glazing system that retails 3++ times more than a humble semi-structural one)…
y, he he) on that market segment (trusses and the likes) ... well ... you can't do anything in real-life without code. Too many reasons to list them here (indicative: connectivity Trees, member clash detection, instance definitions, managing solution variations talking to MCAD apps that do the parts in real-life ... blah, blah). If this is just an abstract exercise ... forget all the above.
3. Using a // (to the ground) "inner" surface (the 2 edges, that is) is tricky because without code you can't be sure where the whole procedure failed (a red component means nothing).
4. The weird big "component" provides ways to do things with surfaces (most notably: rebuild) that are not available as native components. Rebuild is critical when dividing surfaces
have fun, best, Lord of Darkness…
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.
…
ter proofing and er ... the obvious).
However the "assembly" must comply with some part naming system as found in BIM apps (my core app is AECOSim) and obviously with CSI type of specs and the likes. I fact I have a complete "app" that does this ... but (a) is strictly internal, (b) is written for AECOSim/Generative Components by yours truly.
Graphics is also a serious issue and especially combined ones: for instance imagine someone naive enough to use polystyrene [hence the vapor barrier] to do this type of disastrous roofing (meaning that DP is one thing, water absorption is another animal much much more important than DP itself > polystyrene absorbs all the condensate > Armageddon > Adios Amigos):
By combined I mean this "typical" scenario as well:
…
and Grasshopper installed, or Rhino 6. 2-Install GHPython from here (Rhino 5 only). 3-Select and drag all the userObjects (downloaded here) onto your Grasshopper canvas. 4-Restart Rhino Grasshopper.
Check out our example files to get yourself familiar with typical SkinDesigner workflows. Also SkinDesigner Tutorials will be posted in this YouTube playlist as they become available.
You should also feel free to post any questions, feature requests, or bug reports to the SkinDesigner Grasshopper Group as discussions. Finally, SkinDesigner is an open source project and all of the project’s source code is visible on SkinDesigner’s Github site as well as within the Grasshopper components (by double-clicking on them).
…