Rese arch MEETUP is an annual international conference and networking event to bring together practitioners and theorists of computational design in architecture, experts in digital manufacturing and related contemporary thinkers and philosophers. The current edition will take place on 4 April 2018 in Paris. Together with Pecha Kucha on 5 April 2018 it will be the main event of the DATASCAPES Fest 2018 hosted by VOLUMES Paris, a coworking and maker space for design and open innovation.
The event is a mid-size informal gathering of peer designers and researchers in the field of computational design in architecture. Each of the speakers holds a 20 minutes long lecture followed by 10 minutes Q&A session. The purpose is to update the peers of each other’s projects, agendas, and research. It is also a great opportunity to meet in person and arrange future collaborations in a professional, yet friendly and relaxed environment.
Karamba is a parametric structural engineering tool which provides accurate analysis of spatial trusses, frames and shells.
Karamba is fully embedded in the parametric design environment of Grasshopper, a plug-in for the 3d modeling tool Rhinoceros. This makes it easy to combine parameterized geometric models, finite element calculations and optimization algorithms like Galapagos.
The new work in progress version for Karamba is now available. It now contains a dedicated installer for Rhino 6 as well as many other new features!
A full list of new features and bug fixes can be found here
VisualARQ includes a built-in IFC import and export plug-in which makes it possible to exchange VisualARQ and Rhino models with Revit (and other AEC software packages) using IFC 2×3 files.
How does it work?
Export from Rhino to IFC:
To save the entire model, go to (File > Save as..) and save the model as an IFC file.
To save part of the model, select the objects to export, and go to (File > Export) and save the model as an IFC file
Import IFC files into Rhino: Open a new file (File > Open…) and select the IFC file to import. Make sure you have selected the IFC 2×3 Building Model (*.ifc) file type or All compatible file types.
Import IFC files into Revit: Go to Open > Open IFC and select the IFC file.
What information do IFC files store?
IFC files store any “built-in” information from VisualARQ objects (i.e “Volume, Height or Area of a wall), and also custom parameters added to VisualARQ and Rhino objects. This video shows how to create custom parameters to add information to any kind of geometry. This information is read by Revit when opening the IFC file.
How are VisualARQ objects recognized in Revit?
The VisualARQ objects, once they are exported to IFC and opened in Revit, are recognized in Revit by their object type (walls as walls, beams as beams, etc…). Revit will understand the imported objects as native Revit objects or Generic Models depending on how objects have been created in VisualARQ.
The table below describes whether Revit reads geometry from IFC files as Standard Revit objects or Geometric objects:
Standard objects: Objects identified by Revit as native parametric objects. Styles are recognized as Revit families and objects can be fully edited.
Geometric Objects: The object’s geometry is recognized by Revit. The object type is identified but no parametric features are available.
In Rhino 6 for Windows, we’ve fully embraced Grasshopper – the wildly popular visual programming language – by “baking it in.” Grasshopper is no longer beta; it’s a stable development environment. We’ve also rewritten some features and renovated workflows that needed fundamental overhauls to make them truly productive. These are the highlights…
The long beta period is over: Grasshopper, the world’s most beautiful programming language, is now a full-fledged part of Rhino. Used in some of the most ambitious design projects of the past decade, Grasshopper, like Rhino, has become a robust development platform. Grasshopper provides the solid foundation for many incredible third-party components ranging from environmental analysis to robotic control.
Presentation is key: during nearly every phase of design, you need to communicate, getting “buy-in” from clients, customers, collaborators, or the public at large. We’ve improved Rhino with the aim of helping you present your work: be it “quick and dirty” or “high-res glossy.” With major changes to Rendering, Materials, or just plain capturing the viewport, it’s now easier and faster to present, discuss, make decisions, and iterate.
Rhino’s new display pipeline is faster, more stable, and uses features found on modern graphics hardware, like GPU sensitive shaders and memory optimizations. This results in fewer GPU-specific display glitches and more consistent, beautiful, and frequent frames, even with large models. In some conditions, display speed can be up to 300% faster.
Modeling is just one part of the design process; you also need to show how to build what is on the screen. We’ve refined many parts of the documentation workflow, from a completely reworked annotation-style interface, to better DWG support, and RichText throughout. It’s now easier to convey accurately and clearly the what and the how of your design.
Small quirks add up to painful paper cuts over the course of a prolonged modeling session. In Rhino 6, we’ve fixed hundreds of minor bugs and consolidated disparate – but similar – features into single commands, making Rhino much more refined.
Rhino is more than just a modeler. With a rich ecosystem of plugins and an open set of development tools, Rhino is quickly becoming the development platform for those seeking to push the envelope of design. Rhino 6 brings major improvements to our free SDKs, with API refinements, better documentation, and more access to Rhino commands from Grasshopper.
We’re constantly improving Rhino. Rhino 6 users have access to the Serengeti community and our Work-In-Progress (WIP) builds. The WIP builds are where we are developing future features like SubD support, Grasshopper 2, a new real-time rendering engine, and much more.