What it is and the problem it solves
Texture mapping is a technique for projecting 2D image data onto 3D models. It solves the problem of adding surface detail—like brickwork or skin—without modelling every bump or crack as geometry.
How it works
It works by assigning UV coordinates to 3D geometry, then for each screen pixel, tracing into the 3D scene to find which polygon is hit and using the corresponding UV values to sample colour from a 2D texture. Inverse mapping processes per-pixel; forward mapping processes per-texel. Perspective-correct mapping uses 3D vertex positions and 1/z interpolation; affine mapping interpolates linearly in screen space.
What works
Inverse mapping works reliably for rasterisation: each pixel gets exactly one sampled texel (with filtering). Diffuse mapping—its original form—works for flat lighting conditions. Perspective-correct mapping works for accurate texture placement on foreshortened surfaces.
What does not
Forward mapping produces gaps and overlaps on screen because it cannot guarantee every pixel receives a texel. Affine interpolation fails under perspective distortion, causing texture skew on receding surfaces. The method itself does not resolve aliasing, filtering, or mipmapping—those are later additions.
What it changes
It changes how surface detail is represented: from hand-coded shading or procedural patterns to reusable, artist-authored 2D image data mapped onto arbitrary geometry. It decouples appearance from topology, enabling richer visual fidelity without increasing polygon count.
Is it worth your time
Yes—if you work with real-time 3D rendering, GPU pipelines, or graphics software development. It remains foundational, but its core mechanism is now abstracted behind APIs and hardware units; understanding it matters only when debugging visual artefacts or optimising sampling paths.
