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
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…
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).…
simple, there are many symetries in 3 main planes. So I used arcs rotated 45° from the main planes and I generate a pentagon which was mirrored and rotated many times.
At the end there are 24 pentagons and 8 hexagons so 32 faces, 54 points/vertex and 84 edges.
It could generate some others tessalation styles
…
ASS 2017 Conference in Hamburg, Germany. Join them to:
Learn how to use simulation-based optimization in Grasshopper
Learn about the differences between optimization algorithms in Grasshopper and when to use them
Learn how to assess the performance of optimization algorithms
Learn about differences between single and multi-objective optimization algorithms
Experiment with benchmark problems
Experiment with optimization problems from your own practice and research (bring your own optimization problems)
Experiment with optimization and visualization tools not yet released publicly
Thomas and Judyta are researchers in architectural design optimization. Thomas is the lead developer of the machine learning related optimization tool Opossum and Judyta a co-developer of the particle swarm optimization tool Silverye. Adrian is the founder and the owner of Architektura Parametryczna – the biggest Polish consultancy company in parametric design. (Find Thomas’ and Judyta’s work on ResearchGate here and here.) Registration closes on Tuesday, July 25, 2017.
Registration through the IASS website:
https://express2.converia.de/frontend/index.php?folder_id=943
Facebook event page:
https://tinyurl.com/ycv24m8g
…
r this or that etc etc).
3. I would strongly advise to use some decent feature/dimension driven CAD app in order to create families of concrete deck/beam(s) profiles "manually" (the good old way PLUS recording history and using parameters for the steps taken). Find a friend who knows, say, AECOSim and ask for a small demo on that matter (specifically ask what DDD is [Dimension Driven Design]). Then you can have these in Rhino/GH, define some topology, do the "solid" and if 1M of decks/beams are required rather use instance definitions and plane to plane transformations (that's what the Orient component does) instead of creating 1M clone objects.…
discussions during this period.
The major topics discussed for GH2 during this period will be:
Documentation/Help
GHA/Cluster/VB/C# App-Store
Localization (i.e. languages other than English)
Constraint Engine implementation
Improved VB/C#/Python development tools
Multi-threading the solver
Building a Mac version
If you feel something important was left out, please let us know here. Note that incremental improvements and bug-fixes are not worth discussion as we'll try and get around to them no matter what. Topics on this list have to fit the "Are we going to try and do X?" format.
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 4:07am on October 11, 2013
n splitting curves and then join them to create the region; but I'am looking for a more straightforward solutions. 3- I know some plugins like clipper could do this, but I'm looking for more flexible solutions.
4- I tried Brep[] CreatePlanarBreps(IEnumerable<Curve>) in ghpython, but it doesn't work.
…
You can create Design Options using the Iris Layer component!
For each set of geometries that you create, you can assign a layer and define whether it will be visible or not in Virtual Reality on the
Added by IrisVR to IrisVR at 8:34am on January 23, 2017