Project Aero: Procedural Content Creation in Houdini
Subscribe:  iCal  |  Google Calendar
7, Mar — 1, Jun
Copenhagen DK   25, Apr — 8, May
Gyeonggi-do KR   25, Apr — 28, Apr
Copenhagen DK   25, Apr — 29, Apr
Vilnius LT   2, May — 4, May
Latest comments

this is an Excellent article, the way its set out with the vids and pics. very technical but not rambley. I learnt alot out of it.

by Eric
5 hours ago

Bob would have been proud

by Krzysztof Czerwiński
9 hours ago

Congratulations Lukas:) Amazing piece of 3D parametric shader:) thank You for sharing Your knowledge:)

Project Aero: Procedural Content Creation in Houdini
7 April, 2017
Denis Kozlov is doing some magic with Houdini. His Project Aero, the software he developed for rapid design of aircraft concepts, is a great example of procedural possibilities. 

Basically, Project Aero is a set of tools meant for procedural content creation inside Houdini. So, it is not a standalone product and you need to Houdini to use the toolkit. There is a detailed breakdown of this project here

Project Aero – fast and very dirty interaction demo from Denis Kozlov on Vimeo.

You can find more technical details in the original article On Wings, Tails and Procedural Modeling.

By no means Project Aero is complete or flawless, but hopefully it takes the concept far enough to illustrate the benefits and possibilities of procedural creation of 3D assets. Getting another individual version of the same model is a matter of seconds. Automatic non-identical symmetry and procedural surface aging controlled by few high-level sliders also help to escape “the army of clones” issue that 3D models sometimes suffer from. Deeper variations like repainting or restyling the skin and panels are done in a breeze. The set of detail modules is easily extendable and parts of the existing design can be swapped and reused. Depending on the toolset’s design objectives, generated models could be automatically prepared for integration into a particular pipeline (Like textures could be baked out, LODs automatically created and parts named in a chosen convention, exhausts and moving parts marked with special dummy locators or attributes, etc).

And of course the workflow is non-linear from both design and development perspectives. The first means that you can always go back and change/adjust something at the previous stages of work without having to redo the later steps (like a change in the wing position on a hull of a finished model will make all the related surfaces recalculate to allow for the new shape). And the second refers to the ability to use the toolset while it’s being developed, which means that in a production environment artist wouldn’t have to wait for a TD to finish his work – the tools would be updating in parallel, automatically adding new features to the designs already being worked on.

Denis Kozlov 

Project Aero has been created as an internal tool and is not currently available for sharing or distribution. The developer is interested in collaboration on development of procedural content creation systems, but restricts these opportunities to commercial projects only.

Source: Denis Kozlov

Leave a Reply