I like controls, and surfaces, and 3D + paper sketching, and designing helmets.
I love Rhino and Grasshopper and GHGL and the depth of real-time experimentation that is opened up.
So damn cool. That is a lot of work. Well done!
MultiProject-Genus-Collection-2025RED144.pdf (7.0 MB)
Thanks Scott.
The automation of the PDF package is the documentation step that I am most excited by this week. Designed to be used myself for sketching or delivered at the end of a guided session.
The automation of the PDF package is the documentation step. The PNG files are generated from 24 Grasshopper scripted view captures.
There is a main project name, Cerebrax in this example, which is either sequential with each new project or selectable. Each saved sequence occupies a named iteration save slot, with 50 slots available ranging from Flash to Peak.
The series of saved images are previewed and added to a PDF packaging list. QR codes link to saved files of the definitions for the helmets geometry and the texture structure settings for recall later.
The PDF build is then executed with a button click and runs as an externally threaded process. The system remains operational during the minute or two it takes to build the 28-300+ page print PDF.
The completed PDF is then printed and bound for use in hand sketching and working out structural development.
The attached PDF file is a resolution downscaled draft example.
This is insane, thanks for sharing! Can you tell us more about the custom user interface you are using to drive the model?
Also, for the gallery, the first image you post is used. You might pick another one as the first image that better fits the gallery aspect ratio.
The interface is built in OSC Pilot and Processing/Java.
OSC (Open Sound Control) is a protocol for networking sound synthesizers, computers, and multimedia devices for musical performance or show control. It functions as a modern successor to MIDI, using UDP network packets to transmit messages between applications and devices with low latency and high resolution data transfer.
The protocol proved applicable to Grasshopper parameter control by transmitting numerical values and trigger messages from external control interfaces directly into parametric definitions. This enables hands-off parameter adjustment during design iteration without keyboard/mouse interaction with the Grasshopper canvas.
Several UI authoring programs exist for creating OSC control surfaces: TouchOSC, Lemur, OSCpilot, and open-source options like Open Stage Control. Each provides drag-and-drop interfaces for building custom control layouts with sliders, rotary encoders, XY pads, and button arrays that output OSC messages.
OSCpilot demonstrated the most flexibility for the requirements of this workflow. The program’s architecture together with Processing allowed mapping physical rotary encoders and other MIDI/OSC hybrid devices into a unified control system feeding parameter streams into Grasshopper components via UDP port monitoring.
I’ll add these explainer screens for now and edit in the further explanations.
Screen capture of complete Windows desktop. Four applications visible, Rhino for geometry on 4K with Processing dashboard overlay, OSC Pilot on Dell 2K touchscreen, with main Processing application showing Encoder legend and indicators.
Parameter pins
are toggled on ( round light bulb switches on the interface).
This is the first workspace, or page, controlling the 2D outline of the helmet. These factors can be edited anytime during the development and are updated whenever a previously saved definition is loaded.
UI parameter control elements arranged relative to the geometry 2D plan location. Slider indicators are reversed to coordinate with the relative movement of the linked geometry. Example the forward and rearward length of the helmet. Vertical slider adjusts the width, as a horizontal slider has no spatial correlation.
Spatial mapping or positional mapping is applied when intuitive. A large parameter set needs as many “hints” as possible for design flow. ( A wall of unified horizontal left to right sliders changes the mental domain of the process. Less design, more engineering )
Dial Ui elements are used for angles and associated “throws” or magnitudes.
Common Menus across all workspaces.
The “legend” or key to the Dial Box and it’s mapping to the parameters of the current workspace. Moving a slider on the touchscreen highlights the related encoder proxy and vice versa.
Workings described in greater detail here. Hybrid UI for GH Definition, OSC and Dialbox
thanks @nxakt for the additional information. Looking at your portfolio, it looks you’ve been designing helmets for at least 20 years, so that explains the dedication to this subject! Very inspiring and impressive.
Thanks, and Rhino3D since the beta days, about '97
Have had this concept for a helmet parametric toolkit for over a decade, built the first steps in Grasshopper at the time. Skills and interfaces improved and I was inspired to use Rhino to push this project as far as I can. I have been positively surprised at every step of the way with the capabilities of Rhino and Grasshopper.
Huge respect for the professionalism and spirit of McNeel.