Unity for Architectural Visualization — Save 50%
Transform your architectural design into an interactive real-time experience using Unity with this book and ebook
This article by Stefan Boeykens, the author of Unity for Architectural Visualization, discusses the use of lights, shadows, and Lightmapping in Unity for Architectural Visualization.
(For more resources related to this topic, see here.)
Basic light sources
You use lights to give a scene brightness, ambience, and depth. Without light, everything looks flat and dull. Use additional light sources to even-out lighting and to set up interior scenes. In Unity, lights are components of GameObjects. The different kinds of light sources are as follows:
- Directional lights: These lights are commonly used to mimic the sun. Their position is irrelevant, as only orientation matters. Every architectural scene should at least have one main Directional light. When you only need to lighten up an interior room, they are more tricky to use, as they tend to brighten up the whole scene, but they help getting some light through the windows, inside the project. We'll see a few use cases in the next few sections.
- Point lights: These lights are easy to use, as they emit light in any direction. Try to minimize their Range, so they don't spill light in other places. In most scenes, you'll need several of them to balance out dark spots and corners and to even-out the overall lighting.
- Spot lights: These lights only emit light into a cone and are good to simulate interior light fixtures. They cast a distinct bright circular light spot so use them to highlight something.
- Area lights: These are the most advanced lights, as they allow a light source to be given an actual rectangular size. This results in smoother lights and shadows, but their effect is only visible when baking and they require a pro-license. They are good to simulate light panels or the effect of light coming in through a window. In the free version, you can simulate them using multiple Spot or Directional Lights.
Most current games support some form of shadows. They can be pre-calculated or rendered in real-time. Pre-calculation implies that the effect of shadows and lighting is calculated in advance and rendered onto an additional material layer. It only makes sense for objects that don't move in the scene. Real-time shadows are rendered using the GPU, but can be computationally expensive and should only be used for dynamic lighting. You might be familiar with real-time shadows from applications such as SketchUp and recent versions of ArchiCAD or Revit.
Ideally, both techniques are combined. The overall lighting of the scene (for example, buildings, street, interiors, and so on) is pre-calculated and baked in texture maps. Additional real-time shadows are used on the moving characters. Unity can blend both types of shadows to simulate dynamic lighting in large scenes. Some of these techniques, however, are only supported in the pro-version.
Imagine we want to create a sun or shadow study of a building. This is best appreciated in real-time and by looking from the outside. We will use the same model as we did in the previous article, but load it in a separate scene. We want to have a light object acting as a sun, a spherical object to act as a visual clue where the sun is positioned and link them together to control the rotations in an easy way. The steps to be followed to achieve this are as follows:
- Add a Directional light, name it SunLight and choose the Shadow Type. Hard shadows are more sharply defined and are the best choice in this example, whereas Soft shadows look smoother and are better suited for a subtle, mood lighting.
- Add an empty GameObject by navigating to GameObject | Create Empty that is positioned in the center of the scene and name it ORIGIN.
- Create a Sphere GameObject by navigating to GameObject | Create Other | Sphere, name it VisualSun.
- Make it a child of the ORIGIN by dragging the VisualSun name in the Hierarchy Tab onto the ORIGIN name.
- Give it a bright, yellow material, using a Self-Illumin/Diffuse Shader. Deactivate Cast Shadows and Receive Shadows on the Mesh Renderer component.
- After you have placed the VisualSun as a child of the origin object, reset the position of the Sphere to be 0 for X, Y and Z. It now sits in the same place as its parent. Even if you move the parent, its local position stays at X=0, Y=0 and Z=0, which makes it convenient for a placement relative to its parent object. Alter the Z-position to define an offset from the origin, for example 20 units. The negative Z will facilitate the SunLight orientation in the next step.
- The SunLight can be dragged onto the VisualSun and its local position reset to zero as well. When all rotations are also zero, it emits light down the Z-axis and thus straight to the origin.
- If you want to have a nice glow effect, you can add a Halo by navigating to Components | Effects | Halo and then to SunLight and setting a suitable Size.
We now have a hierarchic structure of the origin, the visible sphere and the Directional light, that is accentuated by the halo. We can adjust this assembly by rotating the origin around. Rotating around the Y-axis defines the orientation of the sun, whereas a rotation around the X-axis defines the azimuth. With these two rotations, we can position the sun wherever we want.
Real-time lighting is computationally very expensive. If you don't have the latest hardware, it might not even be supported. Or you might avoid it for a mobile app, where hardware resources are limited. It is possible to pre-calculate the lighting of a scene and bake it onto the geometry as textures. This process is called Lightmapping, for more information on it visit: http://docs.unity3d.com/Documentation/Manual/Lightmapping.html
While actual calculations are rather complex, the process in Unity is made easy, thanks to the integrated Beast Lightmapping. There are a few things you need to set up properly. These are given as follows:
There are several settings, but we start with a basic setup that consists of the following steps:
- Usually a Single Lightmap suffices. Dual Lightmaps can look better, but require the deferred rendering method that is only supported in Unity Pro.
- Choose the Quality High modus. Quality Low gives jagged edges and is only used for quick testing.
- Activate Ambient Occlusion as a quick additional rendering step that darkens corners and occluded areas, such as where objects touch. This adds a real sense of depth and is highly recommended. Set both sliders somewhere in the middle and leave the distance at 0.1, to control how far the system will look to detect occlusions.
- Start with a fairly low Resolution, such as 5 or 10 texels per world unit. This defines how detailed the calculated Lightmap texture is, when compared to the geometry. Look at the Scene view, to get a checkered overlay visible, when adjusting Lightmapping settings. For final results, increase this to 40 or 50, to give more detail to the shadows, at the cost of longer rendering times.
There are additional settings for which Unity Pro is required, such as Sky Light and Bounced Lighting. They both add to the realism of the lighting, so they are actually highly recommended for architectural visualization, if you have the pro-version.
On the Object sub-tab, you can also tweak the shadow calculation settings for individual lights. By increasing the radius, you get a smoother shadow edge, at the cost of longer rendering times. If you increase the radius, you should also increase the amount of samples, which helps reduce the noise that gets added with sampling. This is shown in the following screenshot:
Now you can go on and click Bake Scene. It can take quite some time for large models and fine resolutions. Check the blue time indicator on the right side of the status bar (but you can continue working in Unity). After the calculations are finished, the model is reloaded with the new texture and baked shadows are visible in Scene and Game views, as shown in the following screenshot:
Beware that to bake a Scene, it needs to be saved and given a name, as Unity places the calculated Lightmap textures in a subfolder with the same name as the Scene.
In this article we learned about the use of different light sources and shadow. To avoid the heavy burden of real-time shadows, we discussed the use Lightmapping technique to bake lights and shadows on the model, from within Unity
Resources for Article:
- Unity Game Development: Welcome to the 3D world [Article]
- Introduction to Game Development Using Unity 3D [Article]
- Unity 3-0 Enter the Third Dimension [Article]
|Transform your architectural design into an interactive real-time experience using Unity with this book and ebook|
eBook Price: $20.99
Book Price: $34.99
About the Author :
Stefan Boeykens is an architect-engineer from Leuven, Belgium. After graduation, he was involved in architectural practice for about 4 years, before returning in 2007 to KU Leuven for his PhD on the integration of Building Information Modeling (BIM) in the design process. He worked on a variety of research and education projects, ranging from CAD and BIM, to metadata for architectural archives and cost simulations. His main research interests are BIM 3D modeling, and visualization, digital historical reconstruction, parametric design, programming, and interoperability between a variety of software tools, with a special focus on open BIM.
He is quite literate with software in general, with extensive expertise on ArchiCAD, AutoCAD, SketchUp, Rhinoceros, Excel, Solibri, Processing, CINEMA 4D, Ableton Live, Photoshop, Illustrator, CorelDRAW, Artlantis, and Unity. He likes cross-platform approaches, even more since switching to OS X. Hard disks are always too small for him.
Stefan Boeykens is currently employed by the Department of Architecture at the Faculty of Engineering Sciences at KU Leuven, Belgium. As a teacher, he is responsible for the Architectural Computing courses and teaches students how to use AutoCAD, SketchUp, ArchiCAD, Solibri, CINEMA 4D, Rhinoceros, Grasshopper, and Unity.
He is the author of the CAD-3D.blogspot.com blog, which discusses CAD, 3D, and BIM, with a particular interest in free and educational software for architects and interoperability.
Under the name of stefkeB he is active online in various platforms and networks.
He is also a schooled guitar player, both classical and electric, with a keen interest in musical composition in a variety of styles, including progressive rock, pop, metal, electronic experiments, and purely acoustic songs, in English and Dutch, but often also instrumental. As stefkeB, he records everything at home, using Ableton Live mainly. Some of his music can be heard on Soundcloud and Bandcamp. All his compositions are available under a Creative Commons license (CC-BY-NC-SA), by choice.
Unity for architectural visualization is his first actual book, but he has written countless software tutorials; recorded an extensive set of video-tutorials, freely available on Youtube; and has written several academic publications that have been presented on conferences worldwide.