basis).
2. Rhino does not have a proper object display capability (objects per layer per view basis and/or per "collections" per view).
3. TSplines does NOT have any on-the-fly coordinate system definition capability (making "edit" a pointless waste of time). A small example about what this means as regards view navigation matters: imagine "hoovering" along a myriad of 3d objects: if you choose/opt for it: the moment that you touch an element (that could define a vector): this instantly becomes the working plane Z axis (very common capability in top MCAD apps). Not the same as a SpaceNavigator controller mind (far from it).
If these 3 were available > rebuilding anything with TSplines could be a joy (and very fast: about 2 minutes for your mesh)
Get this as well - Load Rhino file first attached in my previous reply (just for fun: not for your case, but we could do an extra WOW MERO spaceframe out of this paranoid M mesh).
BTW: Exo W is "tricky"…
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).…
http://www.food4rhino.com/app/horster-camera-control-grasshopper
I think lady bug might gave a similar component too. Or you can try to find if someone has made a C# or VB component. http://developer.rhino3d.com/api/RhinoCommonWin/html/P_Rhino_Displa...…
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.…
to run at full screen. I've gone as far as using an iPad to use as the second monitor via AirDisplay (which actually works really well) but have never been satisfied with any setup that required you to look back and forth as if at a tennis match all day long.
Not long after first using Grasshopper 3+ years ago I've had the desire for a "Live Viewport" component that would allow a live image of the 3d geometry being generated directly in the canvas. Every once in a while I search the forums with the hope of finding a solution, but always come up empty handed. Someday this might exist although for now I have found what might be the next best thing to a native "Live Viewport" component and its enabled with a small app named Sticky Previews. This app uses the task bar preview feature within Windows 7's aero interface to create custom, floating preview windows from any open window currently running. I've only just discovered the app, but it seems to do the trick and has been stable and problem free so far. -- I will post an update if I find out that I might have spoken too soon. The install allows for a 30 day trial and is $15 bucks to purchase. I just found the app and don't know anything about this group that created the app. If you happen to know of them, Id be curious to find out more.
divided windows, cramped and slow;
unified window with floating rhino model preview;
link to the apps webpage;
http://www.ntwind.com/software/sticky-previews.html
Also works with other apps;
and the about me page screen shot;
…
Added by Tyler Selby at 11:25pm on November 26, 2012
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.…
cles always had only position (3 degrees of translational freedom).
Now they can also optionally have an orientation (3 degrees of rotational freedom), which are updated by the solver at each iteration.
This makes possible new types of goals based on these orientations. The first example of this is a more robust rigid body component, and collision between pairs of rigid bodies. These can be any closed solids, and do not need to be convex.
In coming weeks I will be posting more examples of Goals which make use of the 6dof nodes, including some scripted ones.
…
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…
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.…