• Create Account

\$2

Like
0Likes
Dislike

# Ray Lighting

By Robert Nagy | Published Apr 27 2005 07:17 AM in Graphics Programming and Theory

 If you find this article contains errors or problems rendering it unreadable (missing images or files, mangled code, improper text formatting, etc) please contact the editor so corrections can be made. Thank you for helping us improve this resource

Abstract
In this paper I present a method for creating realistic shadows using a ray tracing technique. The technique calculates the shadows in advance and then adds them to the scene at runtime. Therefore it is not suited for real-time calculations. By using angle based theoretical sun rays the method is able to calculate the shadows shape and brightness in a realistic way. The brightness of the points in the shadows is calculated using a greyscale that simulates the amount of light reaching the different points. To simulate the influence the points have on each other the shadows are blurred. The technique is mainly focused on creating realistic shadows but simplicity is also an important factor.

1. Background

1.1 Introduction
Shadows are a common part of the world. Adding them to your 3D graphics will add a whole new degree of realism. Without shadows scenes often feel unnatural and flat which confuses the viewer. Over the year several techniques have been developed to create these important shadows.

Because terrain is static and doesn't change in shape or position there is no need to recalculate the shadows each frame. Therefore the best choice for terrain rendering is static shadows. In this paper I am going to present a way I have developed to calculate the shadows of a terrain using static shadows calculations. By calculating the shadow based theoretical sun rays the method will be able to create smooth and realistic shadows. The method is characterized with the following features:

• Vertical angle based calculations. Giving great flexibility in the positioning of the light source. Offering the ability to simulate different times of a day.
• Soft shadows. The shadows brightness is based on a greyscale. Simulating the amount of light reaching the different points. Giving the shadows more depth and greatly increasing the amount of realism.
• Static shadows. Shadows only have to be calculated once which increases the performance of your engine.
• Not bound to any specific API. The method may be implemented in almost any terrain engine.
• Basic calculations. Making this method a good alternative for both beginners and more advanced programmers.
2. The Algorithm

The ray lighting method draws a theoretical ray with an specific angle from each point on the x-axis. It then checks each point on that ray starting from the shadow's maximum width (based on the heightmap's highest point) against the heightmap to see if the terrain intersects the ray. If it does this point will cast a shadow on each point that precedes it that is below the ray. Figure 1 should give you a better understanding.

The method needs a way to calculate the rays' height at different points. For this it uses some trigonometry.

This leads to the following equation:

The tan function uses radians for calculation and there has to be made some changes for use of degrees. A full revolution, 360 degrees is the same as 2π. To convert from degrees to radians it has to multiply the angle by the fraction (360/2π) or (180/π).

Since the ray is not a vertical line the method can't stop calculating the RayOriginX when it reaches 0. Terrain won't be included if the terrain is higher than the ray at 0. Since the ray never is vertical there will most certainly be terrain that is not included. To prevent this the calculation needs to continue in the –X direction. The distance it has to go is calculated with the following equation:

Figure 2 illustrates the problem and its solution.

Since different amounts of light reache the ground at different points the different points will have a different amount of brightness. If this is not included in the calculations the shadows will look flat and non-realistic. To simulate the amount of light intersecting the different points a greyscale is used from which the brightness is calculated. This will make points closer to the shadow's origin darker than the ones further away, giving the shadows more depth and making the terrain's outline more visible. Figure 3 illustrates this.

The shadow starts from ShadowOriginX which is the x-coordinate of the highest point that intersects the ray. To keep all the shadows' brightness the same regarding their height, position, etc., a constant greyscale using the coordinates within the current greyscale is used to calculate the different points' brightness. This is shown in Figure 4.

Two variables are needed to hold the x-coordinate of the shadow's origin (ShadowOriginX) and the shadow greyscale's height (ShadowY). Then a variable is used for the greyscale's maximum brightness (because it should be able to modify the shadow's brightness). Then there is an equation to calculate the brightness of the different points.

The equation calculates the x and y-coordinates for the point in the small greyscale. It then divides them with the greyscale's x and y-sizes to get a percentage of the entire greyscale, then multiplies that percentage with the maxBrightness value which is the constant greyscale's size.

These are not physically correct calculations but they give very realistic results. They give the shadows more depth and blends the shadows into brighter areas.

The sun is a large light source causing the shadows to be blurred. The shadows will be blurred by getting the mean value of all the points in the shadow and its neighbours. This way the points get a bit brighter or darker depending on the brightness of surrounding points. The points in the direction of the sun won't be a part of the calculations since they don't reach the shadow.

3. Implementation

3.1. Variables
/////////////// /* Variables */ /////////////// // Tells if there is a shadow. bool Shadow; // Holds the coordinates for the shadow greyscale. int ShadowOriginX; int ShadowY; // Hold the values for the rays' height and the terrain-maps' height. float RayY; // Coordinate positions variables. int RayOriginX, MapX, z, MapY; // The angle in which the rays intersect the x-axis. int Angle = 45; // The max height on the terrain-map. int MaxMapHeight = 255; // The max shadow brightness and. int MaxShadowBrightness = 255; // The size of the terrain int MapSize = 128; /* Pre-calculations */ // Get the tan value for the angle that is used. float TanAngle = float( tan(Angle*3.14159/180) ); // Calculate the maxHeightExtension int MaxHeightExtension = int(MaxMapHeight/TanAngle); // Set all points on the lightmap MaxShadowBrightness for (z = 0; z < MapSize; z++){ for ( MapX = 0; MapX < MapSize; MapX ++){ LightMap[MapX][z] = MaxShadowBrightness; } }
3.3. Colouring the Light Source
To simulate a warm red sunset or add a bit of a mystic blue light to a scene the brightness values have to be modified. The shadows becomes coloured by multiplying the brightness value for red, green and blue with the specified amount of colour. Using the equation Intensity = brightness * colour, the colour values are sent to the API:

ColorToAPI ( (GetBrightnessAtPoint( x, z ) * Red ), (GetBrightnessAtPoint( x, z ) * Green), (GetBrightnessAtPoint( x, z ) * Blue ) );
3.4. Horizontal Rotation
By inverting the coordinates the light source will be rotated. To rotate the light source 180 degrees and set the light direction X+, calculations of RayOriginX start from MapSize towards 0 and MapX from 0 towards RayOriginX.

for ( RayOriginX = -(maxHeightExtension); RayOriginX < MapSize-1; RayOriginX ++ ){ for ( MapX = RayOriginX; MapX < RayOriginX + maxHeightExtension+1 && MapX > 0; MapX++ ){ To calculate in the direction of Z+ or –Z the x and z variables have to be exchanged.

MapY = HeightMap[z][MapX]; ShadowY = HeightMap[z][ShadowOriginX]; LightMap[z][MapX] = 200 * ( float(shadowX-x2)/float(shadowX-x1)+ MapY/ShadowY ); This will allow the light source to rotate 90 degrees horizontally. However this is not the best way to do it. The heightmap and textures may be rotated and the shadows then calculated which would give the same results as rotating the light source.

3.5. Optimizations
Without soft-shading some optimizations are possible that will sacrifice quality for performance. Faster calculations may decrease the initialization time of the application.

4. Results
The algorithm has been added to a demo from the book “3D Terrain Programming” by Trent Polack. The shadows shapes become similar to the objects casting them. Using soft-shading and blurring they blend out into the surroundings and become a natural part of the scene. The light source has great flexibility in vertical rotation but not as much in horizontal rotation. Using the optimized implementation the performance was increased by 21% at the sacrifice of soft shading.

4.1 Images
The following screenshots are taken using the demo and demonstrate the appearance of the shadows. The shadows are calculated using a ray intersecting the x-axis at 70 degrees and a maximum brightness of 200.

Picture 1.1 Without detail texturing and texturing.

http://images.gamedev.net/features/programming/raylighting/image011.jpg
Picture 1.2 With detail texturing.

http://images.gamedev.net/features/programming/raylighting/image012.jpg
Picture 1.3 With detail texturing and texturing.

http://images.gamedev.net/features/programming/raylighting/image013.jpg
Picture 2.1 Without detail texturing and texturing.

http://images.gamedev.net/features/programming/raylighting/image014.jpg
Picture 2.2 With detail texturing.

http://images.gamedev.net/features/programming/raylighting/image015.jpg
Picture 2.3 With detail texturing and texturing.

5. Acknowledgements
A special thank goes to my family and all my friends who have supported me with many comments and ideas.

6. References
[1] Trent Polack, Focus on 3D Terrain Programming.

[2] Matthew Strathan, Real-Time Heightmap Self-Shadowing Using the Strider Technique.

[3] Mircea Marghidanu, Fast Computation of Terrain Shadow Maps.

[4] Charlie 'Chazz' Van Noland, Slope Lighting Terrain.

[5] Kevin Hawkins, Dave Astle, OpenGL Game Programming.

[6] Wendy Stahler, Beginning Math and Physics for Game Programmers.