3D Texturing Risk Assessment & Management 3 — Questions and Answers
Question 1: What risk does floating-point precision loss introduce when baking 32-bit HDR textures down to 8-bit for a mobile game?
- UV seams become invisible
- Subtle gradient information is lost, causing banding artifacts in smooth surfaces (Correct answer)
- Polygon normals flip direction
- Texture coordinates shift by one pixel
Correct answer: Subtle gradient information is lost, causing banding artifacts in smooth surfaces
Quantizing HDR data to 8-bit per channel discards fine gradient steps, producing visible banding on smooth surfaces like skin or sky.
Question 2: Which scenario best illustrates a 'scope creep' risk in a texturing contract?
- The client approves the final texture sheet on the agreed date
- The client repeatedly adds new props requiring textures after the contract was signed, without adjusting the fee (Correct answer)
- The artist voluntarily adds extra detail to impress the client
- The studio changes the render engine mid-project with the artist's knowledge
Correct answer: The client repeatedly adds new props requiring textures after the contract was signed, without adjusting the fee
Scope creep occurs when deliverables expand beyond the original agreement without corresponding compensation or timeline adjustment.
Question 3: A studio is using a licensed texture library and plans to ship textures derived from it. What risk must be assessed before delivery?
- Whether the textures use power-of-two resolution
- Whether the library's end-user license agreement (EULA) permits commercial use in shipped products (Correct answer)
- Whether the textures contain transparency channels
- Whether the original artist used Substance Painter or Photoshop
Correct answer: Whether the library's end-user license agreement (EULA) permits commercial use in shipped products
Many texture libraries restrict commercial or game-shipping use; failing to verify EULA terms exposes the studio to copyright infringement liability.
Question 4: What is the primary risk of disabling mipmapping for textures applied to distant geometry in a real-time scene?
- UV padding becomes insufficient
- Aliasing artifacts and texture shimmer appear as geometry recedes from the camera (Correct answer)
- Ambient occlusion maps bake incorrectly
- Texture compression introduces green fringing
Correct answer: Aliasing artifacts and texture shimmer appear as geometry recedes from the camera
Without mipmaps, the GPU samples full-resolution textures on tiny distant polygons, causing high-frequency aliasing and flickering.
Question 5: When performing a risk review of a texture pipeline handoff, which documentation gap poses the highest delivery risk?
- Missing Pantone color reference numbers
- No specification for expected texture channel packing (e.g., which channels hold roughness, metallic, AO) (Correct answer)
- Absence of a physical measurement unit legend
- No record of which CPU rendered the textures
Correct answer: No specification for expected texture channel packing (e.g., which channels hold roughness, metallic, AO)
Without channel packing specifications, the receiving pipeline may misinterpret which data is stored in each channel, breaking material shading.
Question 6: An artist uses procedural textures exclusively during production but the delivery format requires baked bitmap files. What risk does this create?
- Procedural nodes will automatically export at 72 DPI
- Resolution and tiling decisions must be locked at bake time, making later adjustments costly (Correct answer)
- Normal maps will invert during baking
- The alpha channel will be lost permanently
Correct answer: Resolution and tiling decisions must be locked at bake time, making later adjustments costly
Baking procedural textures commits them to a fixed resolution and tile count, so changing either requires re-baking the entire texture set.
Question 7: Which practice best reduces the risk of UV seam visibility caused by tangent-space normal map baking mismatches?
- Increasing polygon density along seam edges
- Matching the tangent basis of the baking application to the tangent basis used by the target render engine (Correct answer)
- Using triplanar projection instead of UV unwrapping
- Reducing texture resolution to 512x512
Correct answer: Matching the tangent basis of the baking application to the tangent basis used by the target render engine
Tangent space normals are relative to the mesh's tangent basis; a mismatch between baker and renderer produces visible lighting discontinuities at seams.
3D Texturing Risk Assessment & Management 3
What risk does floating-point precision loss introduce when baking 32-bit HDR textures down to 8-bit for a mobile game?