3D Texturing Risk Assessment & Management 3

Question 1

What risk does floating-point precision loss introduce when baking 32-bit HDR textures down to 8-bit for a mobile game?

Accepted Answer

Subtle gradient information is lost, causing banding artifacts in smooth surfaces

Answer

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?

Accepted Answer

The client repeatedly adds new props requiring textures after the contract was signed, without adjusting the fee

Answer

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?

Accepted Answer

Whether the library's end-user license agreement (EULA) permits commercial use in shipped products

Answer

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?

Accepted Answer

Aliasing artifacts and texture shimmer appear as geometry recedes from the camera

Answer

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?

Accepted Answer

No specification for expected texture channel packing (e.g., which channels hold roughness, metallic, AO)

Answer

Without channel packing specifications, the receiving pipeline may misinterpret which data is stored in each channel, breaking material shading.

3D Texturing Practice Test