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.…
s for some solution "as it is" no matter the cost? (that's an extra stupid approach, very old fashioned). Do you use EvoluteTools Pro and/or Kangaroo for "optimization" ?
2. What is the FEA/FIM stuff in use? Do you expect "from/back" interactions? (If this is not doable ... increase this or that etc etc).
3. Do you validate real-life components with FEA/FIM? By what means you design these components? - present and/or future (inside Rhino?). This makes things "interesting" in a variety of ways (we need to extensively talk about that - Skype). The problem is that Rhino IS NOT a feature driven solid modeling app and thus ... a "certain" bottleneck arrives in no time: In the CATIA world you design ("MANUALLY") a parametric history driven component that "complies" to his parent "directives" (say: the Topology) and/or "imposes" his rules to his parent. This is what we call top<>bottom design approach (would become a standard across the AEC industry pretty soon: in around 123 years give or take some). This is far and beyond from what Rhino can do - but we DO make real-life things don't we?
4. Are all these things under a BIM umbrella ? What BIM? What type of details (blue prints) you deliver? (or you just make the thing?).
5. By what means cost is restricting/encouraging the solution? By what means you get feedback from component(s) cost that is outsourced? (i.e. outside your company). Do you monitor all things via some RDBMS? (that's Data Base).
6. What are the long term plans for dealing with such solutions? Using what apps (even in theory for the moment).…
sites the likes of Code Project etc etc) that may fit to your workflow/goals. Also the available literature/printed manuals/e-manuals/books etc etc.
3. Take into account the quality of the available editors (like VS etc etc). That said the "build-in" GH editor is a bit of a crap (but it's OK for smallish/not complex coding).
4. Most importantly: // computing is the holly grail these days (and it would become the standard in the years to come: either via trad CPU cores or via CUDA/Tesla type of stuff)... thus take into account ... well ... the obvious.
BTW: If 1 is true and there's some workflow around that involves many apps ... try to write code that is as "GH neutral" as possible.…
tructures)
Bad news: real-life AEC trusses are far and away from lines.
Ugly news: Rhino is NOT an AEC app by any means nor it would ever be. For AEC app I mean the known 3 (Allplan, Revit and my favorite: AECOSim) and/or proper MCAD apps (like CATIA/NX). In plain English : without exporting (meaning (a) bake in nested blocks + (b) export via STEP) proper structured data (assembly/component) this WIP case is absolutely useless.
why may you ask.
well ... trusses are made with numerous shop drawings like this, that's why:
more soon.
best, Peter…
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).
…
nite a zillion of "solids" (closed polysurfaces in Rhino speech) you need a decent solid CAD app. Rhino is a surface modeller ... meaning that you should narrow your search towards the right girl.
3. Personally I work with Microstation (same 3d core engine as Siemens/NX [ParaSolids]) and CATIA/NX. The difference in speed for doing things like these ... well ... find a friend who works with any of these and experience it first hand. …
next level.
This Parametric Design course will provide the participants with the necessary knowledge and ability to use Grasshopper, a free visual programming plugin in Rhinoceros; you will be guided through a series of hands-on exercises that highlight NURBS modeling and its concepts. We will introduce Grasshopper as a graphical algorithm editor tightly integrated with Rhino’s 3D modeling tools. You will also learn how Rhino is used to render models for visualization, translate 3D models for prototyping, and export 3D models into 2D CAD or graphics programs.
English is the course main language.
Location: Düsseldorf city center
Registration and buying Tickets
www.digitalparametrics.eventbrite.de
Course Calendar:
4 Days 6 hours each
Total duration 24h
2 weekends
Date:
Sat. 17 - Sun. 18 June
Sat. 24 - Sun. 25 June
10:00 - 17:00
Getting Started in Rhino. 2 days (17 - 18 June)
Getting Started in Grasshopper. 2 days (24 - 25 June)
-----------------------------------------------------------------------
Participants will be given a certificate of participation at the end of the course.
-----------------------------------------------------------------------
Course fees:
Professionals: 600€ (excl. MwSt.) Students: 500€ (excl. MwSt.) Students need to provide: Copy of current student ID or proof of student enrollment at University/School.
Group discounts:
Group of 3 professionals: 3x500 = 1500€ (excl. MwSt.)
Group of 3 Students: 3x400 = 1200€ (excl. MwSt.)
Participants are kindly asked to bring their own laptops and have pre-installed Rhino + Grasshopper.
Useful Resources:
Rhinoceros Installation (90 days full version trial available): http://www.rhino3d.com/download
Rhinoceros for Mac (includes Grasshopper) http://www.rhino3d.com/download/rhino-for-mac/5/wip
Grasshopper Free Installation: http://www.grasshopper3d.com/page/download-1
Grasshopper Free Plugins: http://www.food4rhino.com/app/lunchbox http://www.giuliopiacentino.com/weaverbird
Main Tutor:
Rihan
M.A. Dipl.Ing. Architect
Architect at RKW Architektur + Düsseldorf
For any questions about the course, please email: info@immersive-studio.com…
UI - obvious if you recall who's developing MODO):
https://www.youtube.com/watch?v=A5Fd2jOgus4
https://www.youtube.com/watch?v=SkYwpyZNJcs
https://www.youtube.com/watch?v=pK3Q9BQSK4w
A small "bit" coming directly from the US movie industry:
https://www.youtube.com/watch?v=syZdi08_Sco&list=PLIHQjWXPloi_Q...
https://www.youtube.com/watch?v=kPj_Ey2IT9E
2. Trad AEC BIM apps (AECOSim - my favorite, Revit - no thanks, Allplan - no thanks) use RPC cells for similar tasks (an RPC cell is in fact a "DataTree" of images). In the past I did several figure animations (I'm not doing this any more: boring to the max):
http://help.archvision.com/products/bentley-microstation/getting-st...
3. Maya of course does everything (it's a unique amalgam of mesh and nurbs tools), but is totally unsuitable for AEC work.
https://www.youtube.com/watch?v=IVViMQHjjMw
So, assuming that you are in the AEC bandwagon, your options are:
a. AECOSim as the total "umbrella" for AEC matters.
b. MODO as the most innovative app out there.
c. Quest3D as the best VR app out there.…
it within the same smart umbrella? Or put it differently: is it worthy to exploit/consider/evaluate GH methods and development orientations that could "approximate" Utopia?
Let's split the case into segments:
The parametric part thing (although critical) is complex and rather beyond the scope of GH. Affects Rhino far more than GH. That said Microstation has 3 levels for doing this (but forget Microstation and/or Gen Comp).
So for a start we can focus in GH acting as a "composer" in 3D place of all the required (hopefully real) parts for the job. Parts must be nested AND readable as such by an external AEC app.
I'll post here (soon I do hope) all the parts that are required for assembling this. I mean individual static "blocks" that we assume (wrongly) that remain static: I mean we presuppose that the whole GH geometry is fixed (thus this is really a smart sketch of some sort) and no further changes are on schedule (that MAY affect parts).
That said I prefer an incomplete Utopia (one thing that "does" it all, or it thinks that does it) than a myriad of individual apps that take input one from the other and promise the Holly Grail (and/or delivering it). The core reason that I use Microstation as my basic platform is exactly that (obviously with a certain price to pay: bugs, shortcomings, wrong concepts in places etc etc etc).
Best, Peter
…
lines, dedicated MCAD apps, BIM apps, team work AND elevators as well: if you design something "variable" and then attempt to service it via a "static way" (Revit) you'll discover that you are wasting your time. I can list you a lot of WOW towers that failed on that (elevator) matter ... but this wouldn't be polite for the designers: so let's continue.
2. The other critical thing is the system that does the skin: since "liquid" is the new WOW (it shouldn't) the task of "faceting" a facade and doing it with a system that doesn't leak (in the long term), doesn't pop the panels out of the frames and it doesn't cost the GNP of Nigeria ... well ... is not that simple.
3. It's a very common mistake for some future Architect to "skip" (even mentally) "trivial" matters like these ... but if you get used on this type of thinking you'll gonna pay a heavy price (as an Architect).
So my advise is: whilst you are after "form(s)" sketch frantically the nuts and bits of that form (not to mention ... er ... hmm... the elevators, he he).
best…