ans to manipulate PC easily (I mean we have a couple of CNC routers... just no staff to run them... thanks middle management) Plus the Lexan is uncomfortably close to my tutors work (he using Correx). And Honestly unless it was sheet (rather then corrugated) then it wouldn't be the desired aesthetic.
I think if it was to change to PC then I would get rid of the nodes as we know them and just connect the PC to itself from the mid point of each line (fully realising the semi-monocoque style. This would forgo the acute angle annoyance.
I agree that the larger would lend itself to MERO style, but as it is with the extrusion being 4*3mm its tiny screws would drive me bonkers. I would use NX or something for a component based approach.
If it was going to take this to the next level then a rethink of materials etc would mean a more stable work flow/object/outcome, but now I'm past the point of no return (not as dramatic as that sounds). Although it does all seem to be falling apart at the last hurdle [dun dun dunnn!!] ;)
…
the output to a panel and stream the content to the same file. On the 32 win7 the definition will stop here until I plug in a timer to the file path component, then the number will increase at the interval I set. But on the 64 win7 once I made the panel stream the content to the same file, it would start the cycle automatically without me plug in a timer at all, which quickly resulted in freezing of the whole program.
I'm intended to use the same logic to create some real time form finding definition, but with the 64 win7(which is my laptop at home) keep doing that, I'm wondering if anyone would know what's causing the issue.
Thank you so much.…
e is the important part of the script:
Rhino.Display.RhinoView rv = (string.IsNullOrWhiteSpace(view)) ?
doc.Views.ActiveView :
doc.Views.Find(view, false);
if(rv==null)
return;
rv.CaptureToBitmap(false, true, false).Save(filepath, format);
See the SDK for more info: http://4.rhino3d.com/5/rhinocommon/html/AllMembers_T_Rhino_Display_RhinoView.htm…
edia and technology. Under the umbrella of MASSv.1.0 Robots and Cyborgs International Workshop and will be supported by a series of lectures. The workshop will integrate the use of a robotic fabrication with Virtual Reality. …
edia and technology. Under the umbrella of MASSv.1.0 Robots and Cyborgs International Workshop and will be supported by a series of lectures. The workshop will integrate the use of a robotic fabrication with Virtual Reality.
…
hopper concepts and Parametric design. Design professionals from all industries are welcomed. Rhino intermediate level is required to attend this class. You will need to bring a PC laptop with Rhino 5.0 and latest Grasshopper installed.
Registration already started! Limited seats available.
To register:http://www.akiyomatsuoka.com/#!rhino-training-schedule/con8…
e any simple way of getting my hands on the values of the parameters for the Pareto-front configurations ? For the moment I'm dealing with them by Copy-Pasting the list of data on a panel...
2. The data is given like a % of the parameters' sliders. Can't we get the slider values directly ?
3. Is there an easy way to view the shapes on Rhino while "travelling" on the Pareto-front ? I was thinking of clicking on the Octopus Pareto-front shape (line or surface) while having the corresponding parameters configurations (thus shape) on Grasshopper (and Rhino).
4. Finally, is it just my PC or why can't we see the shapes evolving while the algorithms is processing ?
Those features might be coming in the next versions of Octopus but still, if you have any idea of how you would deal with my questions for now...
Thanks in advance
Thomas…
add another "trivial" constrain to the puzzle (for instance the PC sheets are 1.2*2.2m > meaning the obvious). This is addressable ONLY via the black bill (don't even think to use GH components for solving similar stuff).
3. One-off nodes are probably OK BUT for larger scales you'll need MERO type of approach > meaning assembly/component concepts > meaning dealing with instance Rhino definitions: blocks in plain English (don't even think to use GH components for solving similar stuff).
4. "Engulfing" type of strut extrusions are rather the best option (use aluminum in this case) > meaning profiles that can "wrap" the triangle content edge (be that "paper" or Lexan/PC).
5. The whole thing appears "easy" but on a pro level is rather quite challenging and obviously totally undo able without the black pill.
6. So: mesh relaxation <> adapter topology matters <> pack issues <> component design <> triangle content design <> cost <> you named it (for <> read "interact").
Such a "simple" case ... eh? …