The next step is create the entablature and the part of the Peristyle roof that is visible
There is a potential problem and one that had me stumped for a while. As I mentioned surfaces created from a complex aggregate curve profiles like the detailed entablature will bog down computer memory and create huge files that are almost impossible to render in Rhino or any other program.
I use all three methods. This is because command scripting makes it easy and you get the benefit of all worlds depending on your particular needs.
Reminder: If you want to add textures to your polygon mesh files for rendering in Rhino you need to add them to the nurbs model before you mesh the model. This is because Rhino will then establish UV coordinates for the bitmaps that will translate into the polygon mesh. But if you mesh a nurbs object without any UV or a bitmap assigned to it there won't be any UV info to transfer. So if you want to texture your mesh objects for rendering in Rhino remember to texture map them when they are nurbs objects before you polygon mesh them.
Notice the entablature is really a picture frame molding in an abstract sense. In this case we can use shear first to find the correct in-between curve profile and than use the modeling commands Loft or for scripting sweep one Rail.
First the simple plane method. This is really good for fast visualization
|
! merge c:\tutorialscripts\entablature\entabprofile04.3dm selcurve sweep1 enter selcurve delete selnone |
The script creates a simplified flat Entablature and the sloping
parts of the Roof that are visible.
Create a more complex entablature by referencing the more complex curve profile. Import the entabprofile01.3dm file
|
! merge c:\tutorialscripts\entablature\entabprofile05.3dm selcurve sweep1 enter selcurve delete selnone |
The script creates this more true to life complex entablature
and roof. Select all and delete