Puma technically consists of two plugins, (1) a command for Rhino and (2) components for Grasshopper. Now Puma will generate the model in the Rhino viewport.
It is best practice to put RPKs next to the Grasshopper document or in a subdirectory. Puma will ask you to save the document, so it can store the path to the RPK relative to the document.
Install Puma from the Puma market place at food4rhino.Tutorial 9 and export the "Parthenon" CGA rules to a RPK (see Creating a Rule Package). Quick Startĭownload and open the "Street Segment" example or create a scene from scratch: Redistribution or web service offerings are not allowed unless expressly permitted.
Commercial use requires at least one commercial license of the latest CityEngine version installed in the organization. Puma is free for personal, educational, and non-commercial use. Comprehensive RPK examples are available below. An RPK includes assets and a CGA rule file which encodes an architectural style. Puma requires so-called rule packages (RPK) as input, which are authored in CityEngine. Consequently, the user can change any attributes of the building or street models easily by connecting them to other Grasshopper components. The building or street models stay procedural during the entire design or planning workflow.
Complicated export-import steps are no longer needed, which also means that the procedural models do not need to be “baked” anymore. Therefore, a Rhino artist or designer does not have to leave their familiar Rhino environment anymore to make use of CityEngine’s procedural modeling power. It provides a Rhino command and Grasshopper components which enable the execution of CityEngine ‘rules’ within a Rhino scene. Puma is a plugin for Rhino3D and Grasshopper.