Ray casting

<h2 id="concept">Concept</h2>

<p>Ray casting is the most basic of many <a href="/facts/Computer_graphics/lapBE8wv">computer graphics</a> <a href="/facts/Rendering_(computer_graphics)/YYxfnmAq">rendering</a> algorithms that use the geometric algorithm of <a href="/facts/Ray_tracing_(graphics)/n6qpap2q">ray tracing</a>. Ray tracing-based rendering algorithms operate in <a href="/facts/Image_and_object_order_rendering/sBCmqL0f">image order</a> to render three-dimensional scenes to two-dimensional images. Geometric <a href="/facts/Ray_(optics)/PgUEC7Sm">rays</a> are traced from the <a href="/facts/Projective_geometry/rHKSaEbx">eye</a> of the observer to sample the light (<a href="/facts/Radiance/5kS1FhpD">radiance</a>) travelling toward the observer from the ray direction. The speed and simplicity of ray casting comes from computing the color of the light without recursively tracing additional rays that sample the radiance incident on the point that the ray hit. This eliminates the possibility of accurately rendering <a href="/facts/Reflection_(physics)/BhcjDs79">reflections</a>, <a href="/facts/Refractions/S8kvSKzM">refractions</a>, or the natural falloff of <a href="/facts/Shadow/f9zpBgFQ">shadows</a>; however all of these elements can be faked to a degree, by creative use of <a href="/facts/Texture_(computer_graphics)/9gDTsuXN">texture</a> maps or other methods. The high speed of calculation made ray casting a handy rendering method in early real-time 3D video games.
</p><p>The idea behind ray casting is to trace rays from the eye, one per pixel, and find the closest object blocking the path of that ray—think of an image as a screen-door, with each square in the screen being a pixel.  This is then the object the eye sees through that pixel.  Using the material properties and the effect of the lights in the scene, this algorithm can determine the shading of this object.  The simplifying assumption is made that if a surface faces a light, the light will reach that surface and not be blocked or in shadow.  The shading of the surface is computed using traditional 3D computer graphics shading models.  One important advantage ray casting offered over older <a href="/facts/Scanline_rendering/nmJC2rbn">scanline algorithms</a> was its ability to easily deal with non-planar surfaces and solids, such as <a href="/facts/Cone_(geometry)/2c9GIzYD">cones</a> and <a href="/facts/Sphere/jywYLNM2">spheres</a>. If a mathematical surface can be intersected by a ray, it can be rendered using ray casting. Elaborate objects can be created by using <a href="/facts/Solid_modelling/12J69aud">solid modelling</a> techniques and easily rendered.
</p><p>From the abstract for the paper "Ray Casting for Modeling Solids":<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> 
</p>
<blockquote>
<p>To visualize and analyze the composite solids modeled, virtual light rays are cast as probes. By virtue of its simplicity, ray casting is reliable and extensible. The most difficult mathematical problem is finding line-surface intersection points. So, surfaces as planes, quadrics, tori, and probably even parametric surface patches may bound the primitive solids. The adequacy and efficiency of ray casting are issues addressed here. A fast picture generation capability for interactive modeling is the biggest challenge.
</p>
</blockquote>

<p>Light rays and the camera geometry form the basis for all geometric reasoning here. This figure shows a pinhole camera model for perspective effect in image processing and a parallel camera model for mass analysis.  The simple pinhole camera model consists of a focal point (or eye point) and a square pixel array (or screen). Straight light rays pass through the pixel array to connect the focal point with the scene, one ray per pixel. To shade pictures, the rays’ intensities are measured and stored as pixels. The reflecting surface responsible for a pixel’s value intersects the pixel’s ray.
</p><p>When the focal length, distance between focal point and screen, is infinite, then the view is called “parallel” because all light rays are parallel to each other, perpendicular to the screen. Although the perspective view is natural for making pictures, some applications need rays that can be uniformly distributed in space.
</p>
<h3>Concept Model</h3>
<p>For modeling convenience, a typical standard coordinate system for the camera has the screen in the X–Y plane, the scene in the +Z half space, and the focal point on the −Z axis.
</p>

<p>A ray is simply a straight line in the 3D space of the camera model. It is best defined in parameterized form as a point vector (X0, Y0, Z0) and a direction vector (Dx, Dy, Dz). In this form, points on the line are ordered and accessed via a single parameter t. For every value of t, a corresponding point (X, Y, Z) on the line is defined:
</p>
X = X0 + t · Dx
Y = Y0 + t · Dy
Z = Z0 + t · Dz

<p>If the vector is normalized, then the parameter t is distance along the line. The vector can be normalized easily with the following computation:
</p>
Dist = √(Dx2 + Dy2 + Dz2)
D'x = Dx / Dist
D'y = Dy / Dist
D'z = Dz / Dist

<p>Given geometric definitions of the objects, each bounded by one or more surfaces, the result of computing one ray’s intersection with all bounded surfaces in the screen is defined by two arrays:
</p>
Ray parameters:   <i>t</i>[1], <i>t</i>[2], …, <i>t</i>[n]
Surface pointers: S[1], S[2], …, S[n]

<p>Where n is the number of ray-surface intersections. The ordered list of ray parameters, t[i], denote the enter–exit points. The ray enters a solid at point t[1], exits at t[2], enters a solid at t[3], etc. Point t[1] is closest to the camera and t[n] is furthest. 
</p><p>In association with the ray parameters, the surface pointers contain a unique address for the intersected surface’s information. The surface can have various properties such as color, specularity, transparency with/without refraction, translucency, etc. The solid associated with the surface may have its own physical properties such as density. This could be useful, for instance, when an object consists of an assembly of different materials and the overall center of mass and moments of inertia are of interest.
</p>
<h2 id="ray-casting-applications">Ray Casting Applications</h2>
<p>Three algorithms using ray casting are to make line drawings, to make shaded pictures, and to compute volumes and other physical properties. Each algorithm, given a camera model, casts one ray per pixel in the screen. For computing volume, the resolution of the pixel screen to use depends on the desired accuracy of the solution. For line drawings and picture shading, the resolution determines the quality of the image.
</p>
<h3>Line Drawings</h3>
<p>To draw the visible edges of a solid, generate one ray per pixel moving top-down, left-right in the screen. Evaluate each ray in order to identify the visible surface S[1], the first surface pointer in the sorted list of ray-surface intersections. If the visible surface at pixel location (X, Y) is different than the visible surface at pixel (X−1, Y), then display a vertical line one pixel long centered at (X−½, Y). Similarly, if the visible surface at (X, Y) is different than the visible surface at pixel (X, Y−1), then display a horizontal line one pixel long centered at (X, Y−½). The resulting drawing will consist of horizontal and vertical edges only, looking jagged in coarse resolutions.
</p><p>Roth’s ray casting system generated the images of solid objects on the right. Box enclosures, dynamic bounding, and coherence were used for optimization. For each picture, the screen was sampled with a density of about 100×100 (e.g., 10,000) rays and new edges were located via binary searches. Then all edges were followed by casting additional rays at one pixel increments on the two sides of the edges. Each picture was drawn on a Tektronix tube at 780×780 resolution.
</p>
<h3>Shaded Pictures</h3>
<p>To make a shaded picture, again cast one ray per pixel in the screen. This time, however, use the visible surface pointer S[1] at each pixel to access the description of the surface. From this, compute the surface normal at the visible point <i>t</i>[1]. The pixel’s value, the displayable light intensity, is proportional to the cosine of the angle formed by the surface normal and the light-source-to-surface vector. Processing all pixels this way produces a raster-type picture of the scene.
</p>
<h3>Computing Volume and Moments of Inertia</h3>
<p>The volume (and similar properties) of a solid bounded by curved surfaces is easily computed by the “approximating sums” integration method, by approximating the solid with a set of rectangular parallelepipeds. This is accomplished by taking an “in-depth” picture of the solid in a parallel view. Casting rays through the screen into the solid partitions the solid into volume elements. Two dimensions of the parallelepipeds are constant, defined by the 2D spacing of rays in the screen. The third dimension is variable, defined by the enter–exit point computed. Specifically, if the horizontal and vertical distances between rays in the screen is S, then the volume “detected” by each ray is:
</p>
S × S ×  (<i>t</i>[2]-<i>t</i>[1]  +  <i>t</i>[4]-<i>t</i>[3]  + … + <i>t</i>[n]-<i>t</i>[n-1]) / L

<p>where L is defined as the length of the direction vector. (If already normalized, this is equal to 1.)
</p>
L = √(Dx2 + Dy2 + Dz2)

<p>Each (<i>t</i>[<i>i</i>]-<i>t</i>[<i>i</i>-1])/L  is a length of a ray segment that is inside of the solid.
</p><p>
This figure shows the parallelepipeds for a modeled solid using ray casting. This is a use of parallel-projection camera model.</p>
<h2 id="inout-ray-classification">In–Out Ray Classification</h2>

<p>This figure shows an example of the binary operators in a composition tree using “+” and “−” where a single ray is evaluated.
</p><p>The ray casting procedure starts at the top of the solid composition tree, recursively descends to the bottom, classifies the ray with respect to the primitive solids, and then returns up the tree combining the classifications of the left and right subtrees.
</p><p>This figure illustrates the combining of the left and right classifications for all three binary operators.
</p>

<h2 id="realistic-shaded-pictures">Realistic shaded pictures</h2>
<p>Ray casting is a natural modeling tool for making shaded pictures. The grayscale ray-casting system developed by Scott Roth and Daniel Bass at GM Research Labs produced pictures on a Ramtek color raster display around 1979. To compose pictures, the system provided the user with the following controls:
</p>

View

<ul>
        <li>Viewing direction and position</li>
        <li>Focal length: width-angle perspective to parallel</li>
        <li>Zoom factor</li>
    </ul>

Illumination

<ul>
        <li>Number of light sources</li>
        <li>Locations and intensities of lights</li>
        <li>Optionally shadow</li>
        <li>Intensities of <a href="/facts/Shading/ewcDEfda">ambient light</a> and background</li>
    </ul>

Surface reflectance

<ul>
        <li>% reflected <a href="/facts/Diffuse_reflection/wG9w4tAX">diffusely</a></li>
        <li>% reflected <a href="/facts/Specular_reflection/dwVIqLVb">specularly</a></li>
        <li>% <a href="/facts/Transmittance/xlyCG7ks">transmitted</a></li>
    </ul>

<p>This figure shows a table scene with shadows from two point light sources.
</p><p>
Shading algorithms that implement all of the realistic effects are computationally expensive, but relatively simple. For example, the following figure shows the additional rays that could be cast for a single light source.</p>
<p>For a single pixel in the image to be rendered, the algorithm casts a ray starting at the focal point and determines that it intersects a semi-transparent rectangle and a shiny circle. An additional ray must then be cast starting at that point in the direction symmetrically opposite the surface normal at the ray-surface intersection point in order to determine what is visible in the mirrored reflection. That ray intersects the triangle which is opaque. Finally, each ray-surface intersection point is tested to determine if it is in shadow. The “Shadow feeler” ray is cast from the ray-surface intersection point to the light source to determine if any other surface blocks that pathway.
</p><p>Turner Whitted calls the secondary and additional rays “Recursive Ray Tracing”.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> [A room of mirrors would be costly to render, so limiting the number of recursions is prudent.] Whitted modeled refraction for transparencies by generating a secondary ray from the visible surface point at an angle determined by the solid’s index of refraction. The secondary ray is then processed as a specular ray. For the refraction formula and pictorial examples, see Whitted’s paper.
</p>
<h2 id="enclosures-and-efficiency">Enclosures and efficiency</h2>
<p>Ray casting qualifies as a brute force method for solving problems. The minimal algorithm is simple, particularly in consideration of its many applications and ease of use, but applications typically cast many rays. Millions of rays may be cast to render a single frame of an animated film. Computer processing time increases with the resolution of the screen and the number of primitive solids/surfaces in the composition.
</p>

<p>By using minimum bounding boxes around the solids in the composition tree, the exhaustive search for a ray-solid intersection resembles an efficient binary search. The brute force algorithm does an exhaustive search because it always visits all the nodes in the tree—transforming the ray into primitives’ local coordinate systems, testing for ray-surface intersections, and combining the classifications—even when the ray clearly misses the solid. In order to detect a “clear miss”, a faster algorithm uses the binary composition tree as a hierarchical representation of the space that the solid composition occupies. But all position, shape, and size information is stored at the leaves of the tree where primitive solids reside. The top and intermediate nodes in the tree only specify combine operators.
</p><p>Characterizing with enclosures the space that all solids fill gives all nodes in the tree an abstract summary of position and size information. Then, the quick “ray intersects enclosure” tests guide the search in the hierarchy. When the test fails at an intermediate node in the tree, the ray is guaranteed to classify as out of the composite, so recursing down its subtrees to further investigate is unnecessary.
</p><p>Accurately assessing the cost savings for using enclosures is difficult because it depends on the spatial distribution of the primitives (the complexity distribution) and on the organization of the composition tree. The optimal conditions are:
</p>
<ul><li>No primitive enclosures overlap in space</li>
<li>Composition tree is balanced and organized so that sub-solids near in space are also nearby in the tree</li></ul>
<p>In contrast, the worst condition is:
</p>
<ul><li>All primitive enclosures mutually overlap</li></ul>
<p>The following are miscellaneous performance improvements made in Roth’s paper on ray casting, but there have been considerable improvements subsequently made by others.
</p>
Early Outs
If the operator at a composite node in the tree is − or & and the ray classifies as out of the composite’s left sub-solid, then the ray will classify as out of the composite regardless of the ray’s classification with respect to the right sub-solid. So, classifying the ray with respect to the right sub-solid is unnecessary and should be avoided for efficiency.
Transformations
By initially combining the screen-to-scene transform with the primitive’s scene-to-local transform and storing the resulting screen-to-local transforms in the primitive’s data structures, one ray transform per ray-surface intersection is eliminated.
Recursion
Given a deep composition tree, recursion can be expensive in combination with allocating and freeing up memory. Recursion can be simulated using static arrays as stacks.
Dynamic Bounding
If only the visible edges of the solid are to be displayed, the ray casting algorithm can dynamically bound the ray to cut off the search. That is, after finding that a ray intersects a sub-solid, the algorithm can use the intersection point closest to the screen to tighten the depth bound for the “ray intersections box” test. This only works for the + part of the tree, starting at the top. With – and &, nearby “in” parts of the ray may later become “out”.
Coherence
The principle of coherence is that the surfaces visible at two neighboring pixels are more likely to be the same than different. Developers of computer graphics and vision systems have applied this empirical truth for efficiency and performance. For line drawings, the image area containing edges is normally much less than the total image area, so ray casting should be concentrated around the edges and not in the open regions. This can be effectively implemented by sparsely sampling the screen with rays and then locating, when neighboring rays identify different visible surfaces, the edges via binary searches.
<h2 id="anti-aliasing">Anti-aliasing</h2>
<p>The jagged edges caused by aliasing is an undesirable effect of point sampling techniques and is a classic problem with raster display algorithms. Linear or smoothly curved edges will appear jagged and are particularly objectionable in animations because movement of the image makes the edges appear fuzzy or look like little moving escalators. Also, details in the scene smaller than the spacing between rays may be lost. The jagged edges in a line drawing can be smoothed by edge following. The purpose of such an algorithm is to minimize the number of lines needed to draw the picture within one pixel accuracy. Smooth edges result. The line drawings above were drawn this way.
</p><p>To smooth the jagged edges in a shaded picture with subpixel accuracy, additional rays should be cast for information about the edges. (See <a href="/facts/Supersampling/15ysD7bJ">Supersampling</a> for a general approach.) Edges are formed by the intersection of surfaces or by the profile of a curved surface. Applying "Coherence" as described above via binary search, if the visible surface at pixel (X,Y) is different than the visible surface at pixel (X+1,Y), then a ray could be generated midway between them at (X+½,Y) and the visible surface there identified. The distance between sample points could be further subdivided, but the search need not be deep. The primary search depth to smooth jagged edges is a function of the intensity gradient across the edge. The cost for smoothing jagged edges is affordable, since:
</p>
<ul><li>the area of the image that contains edges is usually a small percentage of the total area; and</li>
<li>the extra rays cast in binary searches can be bounded in depth (that of the visible primitives forming the edges).</li></ul>
<h2 id="history-of-ray-casting">History of ray casting</h2>
<p>For the history of ray casting, see <a href="/facts/Ray_tracing_(graphics)/n6qpap2q">ray tracing (graphics)</a> as both are essentially the same technique under different names. Scott Roth had invented the term "ray casting" before having heard of "ray tracing". Additionally, Scott Roth's development of ray casting at GM Research Labs occurred concurrently with Turner Whitted's ray tracing work at Bell Labs.
</p>
<h2 id="ray-casting-in-early-computer-games">Ray casting in early computer games</h2>

<p>In early first person games, raycasting was used to efficiently render a 3D world from a 2D playing field using a simple one-dimensional scan over the horizontal width of the screen.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> Early first-person shooters used 2D ray casting as a technique to create a 3D effect from a 2D world. While the world appears 3D, the player cannot look up or down or only in limited angles with shearing distortion.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a><a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a>  This style of rendering eliminates the need to fire a ray for each pixel in the frame as is the case with modern engines; once the hit point is found the projection distortion is applied to the surface texture and an entire vertical column is copied from the result into the frame.  This style of rendering also imposes limitations on the type of rendering which can be performed, for example depth sorting but <a href="/facts/Depth_buffering/HTyzcKbx">depth buffering</a> may not.  That is polygons must be full in front of or behind one another, they may not partially overlap or intersect.
</p>
<h3><i>Wolfenstein 3D</i></h3>
<p>The video game <i><a href="/facts/Wolfenstein_3D/7sPdmrwV">Wolfenstein 3D</a></i> was built from a square based grid of uniform height walls meeting solid-colored floors and ceilings. In order to draw the world, a single ray was traced for every column of screen <a href="/facts/Pixel/UzwBvXBV">pixels</a> and a vertical slice of wall <a href="/facts/Texture_mapping/9gDTsuXN">texture</a> was selected and scaled according to where in the world the ray hits a wall and how far it travels before doing so.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a>
</p><p>The purpose of the grid based levels was twofold — ray-wall collisions can be found more quickly since the potential hits become more predictable and memory overhead is reduced. However, encoding wide-open areas takes extra space.
</p>
<h3><i>ShadowCaster</i></h3>
<p>The <a href="/facts/Raven_Software/DIHtR2S8">Raven Software</a> game <i><a href="/facts/ShadowCaster/k4DuatdD">ShadowCaster</a></i> uses an <a href="/facts/ShadowCaster/k4DuatdD">improved Wolfenstein-based engine</a> with added floors and ceilings texturing and variable wall heights.
</p>
<h3><i>Comanche</i> series</h3>
<p>The <a href="/facts/Voxel_Space/0UdJ2Nq7">Voxel Space</a> engine developed by <a href="/facts/NovaLogic/Qcr3q4Qt">NovaLogic</a> for the <a href="/facts/Comanche_(video_game_series)/HakWbom4"><i>Comanche</i> games</a> traced a ray through each column of screen pixels and tested each ray against points in a <a href="/facts/Heightmap/EwXCqTY7">heightmap</a>. Then it transformed each element of the heightmap into a column of pixels, determined which are visible (that is, have not been occluded by pixels that have been drawn in front), and drew them with the corresponding color from the texture map.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a>
</p>
<h3>Beyond raycasting</h3>
<p>Later <a href="/facts/MS-DOS/fVrrz1uN">DOS</a> games like <i><a href="/facts/Doom_(1993_video_game)/KA6n0GoY">id Software's DOOM</a></i> kept many of the raycasting 2.5D restrictions for speed but went on to switch to alternative rendering techniques (like <a href="/facts/Binary_space_partitioning/sn9MhTSB">BSP</a>), making them no longer raycasting engines.<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a>
</p>
<h2 id="computational-geometry-setting">Computational geometry setting</h2>

<p>In <a href="/facts/Computational_geometry/eeaotQtl">computational geometry</a>, the ray casting problem is also known as the ray shooting problem and may be stated as the following query problem: given a set of objects in <i>d</i>-dimensional space, preprocess them into a <a href="/facts/Data_structure/yNsNvL1I">data structure</a> so that for each query ray, the initial object hit by the ray can be found quickly. The problem has been investigated for various settings: space dimension, types of objects, restrictions on query rays, etc.<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a> One technique is to use a <a href="/facts/Sparse_voxel_octree/505a3cfB">sparse voxel octree</a>.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Ray_tracing_(graphics)/n6qpap2q">Ray tracing (graphics)</a> A more sophisticated ray-casting algorithm which considers <a href="/facts/Global_illumination/CbQX6CWM">global illumination</a></li>
<li><a href="/facts/Photon_mapping/t58p6V7w">Photon mapping</a></li>
<li><a href="/facts/Radiosity_(computer_graphics)/qN75qQgV">Radiosity (computer graphics)</a></li>
<li><a href="/facts/Path_tracing/fxhaM84b">Path tracing</a></li>
<li><a href="/facts/Volume_ray_casting/bnCjkUUR">Volume ray casting</a></li>
<li><a href="/facts/2.5D/yYrVGBAY">2.5D</a></li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="http://leftech.com/raycaster">Raycasting example in the browser.</a> (unavailable)</li>
<li><a href="http://adrianboeing.blogspot.com/2011/01/raycasting-two-planes-in-webgl.html">Raycasting planes in WebGL with source code</a></li>
<li><a href="http://pouet.net/prod.php?which=61298">Interactive raycaster for the Commodore 64 in 254 bytes (with source code)</a></li>
<li><a href="http://pouet.net/prod.php?which=78044">Interactive raycaster for MSDOS in 64 bytes (with source code)</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Roth, Scott D. (February 1982), "Ray Casting for Modeling Solids", Computer Graphics and Image Processing, 18 (2): 109–144, doi:10.1016/0146-664X(82)90169-1 <a href="/wiki/Doi_(identifier)" target="_blank">/wiki/Doi_(identifier)</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Voelker, H. B.; Requicha, A. A. G. (December 1977). "Geometric modeling of mechanical parts and processes". Computer. 10. <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Requicha, A. A. G. (December 1980). "Representation for rigid solids: Theory, methods, and systems". ACM Computing Surveys. 12 (4): 437–464. doi:10.1145/356827.356833. S2CID 207568300. <a href="/wiki/Doi_(identifier)" target="_blank">/wiki/Doi_(identifier)</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>.Newman, W.; Sproull, R. (December 1973). Principles of Interactive Computer Graphics. Mcgraw-Hill. <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
<li id="fn:5"><p>Scott D Roth (1982). "Ray casting for modeling solids". Science Direct. Elsevier. pp. 109–144. doi:10.1016/0146-664X(82)90169-1. Retrieved 20 January 2025. <a href="https://www.sciencedirect.com/science/article/abs/pii/0146664X82901691" target="_blank">https://www.sciencedirect.com/science/article/abs/pii/0146664X82901691</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li>
<li id="fn:6"><p>Whitted, Turner (June 1980), "An Improved Illumination Model for Shaded Display", Communications of the ACM, 23 (6): 343–349, doi:10.1145/358876.358882, S2CID 9524504 <a href="/wiki/Doi_(identifier)" target="_blank">/wiki/Doi_(identifier)</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li>
<li id="fn:7"><p>"Ray Casting (Concept) - Giant Bomb". Retrieved 31 August 2021. <a href="https://www.giantbomb.com/ray-casting/3015-1517/" target="_blank">https://www.giantbomb.com/ray-casting/3015-1517/</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li>
<li id="fn:8"><p>"Ray Casting (Concept) - Giant Bomb". Retrieved 31 August 2021. <a href="https://www.giantbomb.com/ray-casting/3015-1517/" target="_blank">https://www.giantbomb.com/ray-casting/3015-1517/</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li>
<li id="fn:9"><p>Looking up and down in a raycasting game - y-shearing, change pitch #Shorts, 23 November 2021, retrieved 2023-09-28 <a href="https://www.youtube.com/watch?v=JJEN08XBiyA" target="_blank">https://www.youtube.com/watch?v=JJEN08XBiyA</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li>
<li id="fn:10"><p>Wolfenstein-style ray casting tutorial by F. Permadi <a href="http://www.permadi.com/tutorial/raycast/" target="_blank">http://www.permadi.com/tutorial/raycast/</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li>
<li id="fn:11"><p>Andre LaMothe. Black Art of 3D Game Programming. 1995, pp. 14, 398, 935-936, 941-943. ISBN 1-57169-004-2. <a href="/wiki/Andre_LaMothe" target="_blank">/wiki/Andre_LaMothe</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li>
<li id="fn:12"><p>"ADG Filler #48 - Is the Doom Engine a Raycaster? - YouTube". YouTube. 19 June 2015. Archived from the original on 2021-12-12. Retrieved 31 August 2021. <a href="https://www.youtube.com/watch?v=96nFJIxW-34" target="_blank">https://www.youtube.com/watch?v=96nFJIxW-34</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li>
<li id="fn:13"><p>"Ray shooting, depth orders and hidden surface removal", by Mark de Berg, Springer-Verlag, 1993, ISBN 3-540-57020-9, 201 pp. <a href="/wiki/ISBN_(identifier)" target="_blank">/wiki/ISBN_(identifier)</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li>
</ol>

Ray casting open-in-new

Ray casting