Blender Quiz: Explain Pbr Texture Sets Conceptually Albedo Roughness Metallic Normal Ao
10 questions · exam conditions
0:00
Explain Pbr Texture Sets Conceptually Albedo Roughness Metallic Normal AoQuestion 1 of 10

A texture set made for a specular-glossiness workflow includes a file named Surface_Glossiness. In Blender, the artist is using a Principled BSDF and finds that areas intended to be dull become shiny when the file is connected directly to Roughness.

Which adjustment most directly preserves the intended surface response?

Set the glossiness image to Non-Color, invert its values, and connect the result to Roughness.
Set the glossiness image to sRGB, connect it unchanged, and reduce the shader's Metallic value.
Set the glossiness image to Non-Color, connect it unchanged, and invert the normal map instead.
Set the glossiness image to sRGB, invert its values, and connect the result to Metallic.
← Back to quizzes

Blender Quiz

Blender Quiz: Explain Pbr Texture Sets Conceptually Albedo Roughness Metallic Normal Ao

Practice Explain Pbr Texture Sets Conceptually Albedo Roughness Metallic Normal Ao in Blender with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Explain Pbr Texture Sets Conceptually Albedo Roughness Metallic Normal Ao, giving you a quick way to practice the rules, question types, and explanations that matter most for Blender.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

A texture set made for a specular-glossiness workflow includes a file named Surface_Glossiness. In Blender, the artist is using a Principled BSDF and finds that areas intended to be dull become shiny when the file is connected directly to Roughness.

Which adjustment most directly preserves the intended surface response?

  1. Set the glossiness image to Non-Color, invert its values, and connect the result to Roughness. (correct answer)
  2. Set the glossiness image to sRGB, connect it unchanged, and reduce the shader's Metallic value.
  3. Set the glossiness image to Non-Color, connect it unchanged, and invert the normal map instead.
  4. Set the glossiness image to sRGB, invert its values, and connect the result to Metallic.
Explanation: When working with texture workflows in Blender, you need to recognize that specular-glossiness and roughness-metalness are two different PBR conventions — and they encode surface sharpness in opposite directions. Glossiness maps store high values for smooth surfaces, while Blender's Principled BSDF Roughness input expects high values for rough surfaces. These are mathematical inverses of each other. This is exactly why A is correct. First, setting the image to Non-Color tells Blender to skip gamma correction and treat the data as raw linear values — essential for any non-color data like glossiness, roughness, or masks. Then, inverting the values (using an Invert node) flips glossiness into roughness: a surface that was 0.9 glossy becomes 0.1 rough, which Blender now reads correctly as smooth. The result accurately preserves the artist's original intent. B fails on two counts: keeping the image as sRGB corrupts the data with gamma correction, and adjusting Metallic has no bearing on the glossiness-to-roughness conversion — those are separate channels entirely. C makes the critical mistake of leaving the glossiness values uninverted, so the dull/shiny relationship remains backward; inverting the normal map instead affects surface direction, not smoothness magnitude. D compounds multiple errors — sRGB encoding corrupts the data, and routing a glossiness map into Metallic controls the wrong physical property entirely, producing an unpredictable and incorrect result. A useful rule of thumb: any non-color data texture (roughness, AO, height, gloss) should be set to Non-Color, and when converting between specular-glossiness and roughness-metalness workflows, always invert the gloss channel.

Question 2

A texture file is documented as an ORM packed map: ambient occlusion is stored in red, roughness in green, and metallic in blue. An artist wants to use it with a Principled BSDF without altering the channel meanings.

Which setup correctly interprets the packed texture?

  1. Read it as Non-Color, separate RGB, and route red to AO use, green to Roughness, and blue to Metallic. (correct answer)
  2. Read it as sRGB, separate RGB, and route red to Metallic, green to Roughness, and blue to AO use.
  3. Read it as Non-Color, combine RGB, and route the combined color directly to the shader's Normal input.
  4. Read it as sRGB, separate RGB, and route red to Roughness, green to AO use, and blue to Metallic.
Explanation: When working with packed texture maps in Blender, two things must always be correct: the color space and the channel routing. Packed maps like ORM store raw data values — not visual color information — so the image texture node must be set to Non-Color. If you leave it as sRGB, Blender applies gamma correction and corrupts the numerical data, giving you wrong roughness and metallic values even if your routing is perfect. Option A is correct because it handles both concerns properly. Setting the image to Non-Color preserves the raw channel data, and the Separate RGB node then splits the image into its three channels exactly as documented: red → AO, green → Roughness, blue → Metallic. The AO value is typically multiplied into diffuse lighting rather than plugged directly into Principled BSDF, but the channel interpretation is accurate. Option B fails on two counts: it incorrectly uses sRGB (corrupting the data) and swaps the red and blue channels, routing red to Metallic and blue to AO — the opposite of what the ORM format specifies. Option C is a complete misdirection — combining RGB channels back together and feeding the result into the Normal input makes no sense for an ORM map; that's the workflow for normal maps using a Normal Map node, not packed data maps. Option D uses sRGB (wrong color space) and also scrambles the channel assignments, putting red to Roughness and green to AO. A reliable study habit: whenever you see a packed data texture (ORM, roughness, metallic, height), immediately think Non-Color + Separate RGB. If it's a color map, use sRGB. That distinction alone will resolve most texture setup questions.

Question 3

A tangent-space normal map authored for a DirectX-style convention is used in a Blender material expecting the opposite Y-axis convention. Details that slope along the tangent-space Y direction appear illuminated from the wrong side, while X-direction details behave correctly.

Which correction is most targeted?

  1. Invert the roughness map because reflection spread determines the apparent light direction.
  2. Invert every RGB channel before decoding the image with the Normal Map node.
  3. Invert only the normal map's red channel before connecting it directly to Base Color.
  4. Invert only the normal map's green channel before decoding it with the Normal Map node. (correct answer)
Explanation: Whenever you see a question about normal map artifacts in Blender, think about the coordinate convention difference between DirectX and OpenGL. Normal maps encode surface direction as RGB colors: red = X axis, green = Y axis, blue = Z axis. DirectX convention treats the Y axis as pointing downward in tangent space, while OpenGL (which Blender uses) treats it as pointing upward. When these conventions are mixed, only the Y-encoded details appear flipped — which maps exactly to the green channel. Since the passage tells you that only the Y-direction details are illuminated from the wrong side — while X behaves correctly — the fix is surgical: invert just the green channel before feeding the image into the Normal Map node. You can do this with a Separate Color node, run the G output through an Invert node, then recombine and connect to the Normal Map node's Color input. This corrects the convention mismatch without disturbing anything else. Choice A is a trap that conflates roughness (which controls highlight spread, not direction) with lighting direction. Inverting roughness changes how glossy the surface looks, not which way normals point. Choice B inverts all three channels, which would flip the X and Z axes unnecessarily — overcorrecting and introducing new errors in horizontal and depth information. Choice C inverts only the red channel, which handles the X axis; since the passage explicitly says X-direction details are fine, touching red makes no sense and would break what's already working. Remember this pattern: green channel = Y axis = the DirectX/OpenGL flip. If a normal map question describes Y-only or "vertical" artifacts, your answer is almost always "invert the green channel."

Question 4

On a model, the albedo's painted scratches follow the geometry correctly, but the corresponding roughness scratches are shifted and the normal details are rotated. All source images have the same dimensions and were exported together.

What should the artist verify first?

  1. That ambient occlusion is multiplied more strongly so the shifted scratches become visually concealed.
  2. That roughness and normal are changed to sRGB so their details match the albedo's color transform.
  3. That the metallic map is thresholded to pure black and white before any other maps are aligned.
  4. That all maps share the intended UV coordinates and use consistent mapping scale, rotation, and offset. (correct answer)
Explanation: When multiple texture maps describe the same surface detail but those details appear misaligned across maps, your first instinct should be to audit the UV mapping pipeline — not the maps' content or color settings. Texture maps are only meaningful relative to the UV coordinates that position them on the mesh. If roughness scratches are shifted and normal-map details are rotated compared to the albedo, the most likely culprit is that each map is being sampled with different UV transformations — different scale, rotation, or offset values in their respective texture nodes. This is exactly what D addresses. Before assuming anything is wrong with the maps themselves, you should confirm every map feeds from the same UV channel and that no node (such as a Mapping node or separate UV input) is applying an unintended transform to just one or two of them. A single misconnected Mapping node can shift one map independently while leaving others untouched, which matches the symptom described perfectly. A is a distractor that confuses visual masking with solving the root cause — boosting ambient occlusion doesn't fix misalignment, it just obscures it temporarily. B is a common misconception: roughness and normal maps should remain in Non-Color (linear) data space, not sRGB, so converting them to sRGB would corrupt the data rather than align details. C introduces an unrelated operation; thresholding the metallic map has no bearing on whether roughness or normal map UVs are correctly positioned. As a study tip, whenever texture maps share the same baked detail but appear offset on different channels, always trace the UV path first — one stray Mapping node is almost always the culprit.

Question 5

Two surfaces use the same neutral gray base color. One must read as polished gray plastic, and the other as brushed aluminum. An artist proposes using a very low roughness value for both because both materials can produce bright highlights.

Which response best explains why roughness alone is insufficient?

  1. Roughness controls how strongly reflected light is tinted, while metallic controls whether reflected details appear sharp or softened by the surface.
  2. Roughness controls reflection spread, while metallic changes the balance and color behavior of diffuse and specular response. (correct answer)
  3. Roughness controls the intensity of ambient occlusion in recesses, while metallic adjusts the direction encoded by the surface normal map.
  4. Roughness controls base color brightness at grazing angles, while metallic determines the UV scale and orientation used for texture sampling.
Explanation: When working with Blender's Principled BSDF shader, questions about material realism often test whether you understand what each parameter physically controls — not just what it visually affects at a glance. Polished plastic and brushed aluminum both produce highlights, but they belong to fundamentally different material categories, which is the core trap here. The Metallic parameter does far more than adjust shininess — it switches the entire lighting model. Non-metals (like plastic) have both a diffuse response (scattered, color-tinted light) and a weak specular response (reflections tinted by white). Metals have no diffuse response; instead, virtually all light reflects specularly, and those reflections are tinted by the base color itself. This means two surfaces with identical roughness values will still look completely different if one is metallic and one isn't — the balance of diffuse vs. specular and how color influences reflections changes fundamentally. That's exactly what B captures: roughness controls how spread out reflections are, while metallic governs the underlying diffuse/specular balance and color behavior. A is backwards — roughness spreads reflections while metallic (not roughness) affects color tinting of reflections. C fabricates a connection between roughness and ambient occlusion, and between metallic and normal map direction — neither relationship exists in the Principled BSDF. D is entirely invented; neither parameter has anything to do with UV scaling or grazing-angle brightness in the way described. As a study tip: whenever a question pairs two similar-looking materials, ask yourself whether the difference is physical category (metal vs. non-metal) rather than just surface smoothness — that distinction almost always points to the Metallic parameter.

Question 6

A painted steel panel has intact red paint over most of its surface and several chips that expose bare steel. The texture set uses a metallic-roughness workflow.

Which map interpretation is most physically consistent?

  1. Treat both paint and exposed steel as metallic, then use roughness to distinguish the two regions.
  2. Treat paint as metallic and steel as nonmetallic because only the paint has a visible color.
  3. Treat paint as nonmetallic and exposed steel as metallic, while roughness varies independently in each region. (correct answer)
  4. Treat both regions as nonmetallic, then place the steel response in the ambient occlusion map.
Explanation: When working with PBR (Physically Based Rendering) materials in Blender's metallic-roughness workflow, you need to think about what the metalness channel actually represents: it tells the renderer whether a surface behaves like a conductor (metal) or a dielectric (nonmetal). This distinction drives how light interacts with the surface at a fundamental level — metals reflect light differently and absorb color into their reflections, while nonmetals reflect at the surface and transmit color through diffuse response. Answer C is correct because it accurately maps real-world physics onto the PBR channels. Paint is a dielectric — it has no free electrons, so metalness = 0. Exposed steel is a conductor, so metalness = 1. Crucially, roughness operates independently in each region: the paint might be smooth and glossy while the chipped steel could be rough and oxidized, or vice versa. These two properties are genuinely orthogonal. Answer A fails because classifying paint as metallic is physically wrong. Paint has no metallic light response regardless of how shiny it appears — shininess in dielectrics is controlled by roughness alone, not metalness. Answer B reverses the logic in a subtle way. Paint having a "visible color" doesn't make it metallic — in fact, dielectrics are more associated with rich surface color. Metals derive their apparent color from specular tint, not diffuse. This answer exploits a common misconception about color and metallicity. Answer D is a fundamental category error. Ambient occlusion affects shadowing in crevices; it has no role in defining a material's conductive or dielectric properties. Remember: metalness answers "is this a conductor?" — roughness answers "how microscopically bumpy is it?" Keep those channels doing their separate jobs.

Question 7

An albedo texture was photographed under directional studio lighting. It contains a bright highlight on one side and a soft cast shadow on the other. After the texture is assigned to Base Color, the object is rotated under a new light, but the photographed highlight and shadow remain fixed to the object.

What is the best conceptual correction to the texture set?

  1. Move the fixed shading into the normal map so the new lighting can reinterpret its brightness.
  2. Remove the photographed illumination from albedo, retaining only the surface's intrinsic base color. (correct answer)
  3. Move the fixed highlight into metallic and the fixed shadow into ambient occlusion.
  4. Increase roughness until the photographed highlight and shadow become visually less noticeable.
Explanation: When working with PBR (Physically Based Rendering) texture sets in Blender, the most important principle to understand is channel purity: each texture map should contain only the data it's designed to carry. The albedo (Base Color) map has one job — store the object's raw, intrinsic surface color, completely free of any lighting information. The scenario describes a classic baked lighting artifact: a photograph taken under studio lights captures both the surface color and the lighting conditions of that moment. When you plug that image directly into Base Color, the highlight and shadow become permanently "glued" to the surface, because Blender's lighting system adds its own shading on top. The result is double-shading — your scene's lights interact with light that's already painted into the texture. Removing that photographed illumination and retaining only the true surface color, answer B, is exactly what restores correct PBR behavior. A is a tempting distraction, but the normal map encodes surface geometry — bumps and angles — not lighting removal. Transferring a photograph's highlight there doesn't fix the contamination; it just misuses another channel. C is similarly misguided: metallic and ambient occlusion serve specific physical roles (conductivity and micro-shadow occlusion, respectively) and cannot meaningfully absorb arbitrary photographic lighting data. D sidesteps the actual problem entirely — increasing roughness spreads specular response but cannot undo baked illumination already embedded in the texture. A useful rule of thumb: if rotating your object under a new light produces impossible shadows or highlights, suspect albedo contamination. Clean your Base Color first.

Question 8

A material set contains separate files for albedo, roughness, metallic, tangent-space normal, and ambient occlusion. All were authored for a standard color-managed PBR workflow.

Which color-space assignment is generally the correct starting point in Blender?

  1. Use sRGB for albedo and Non-Color for roughness, metallic, normal, and ambient occlusion. (correct answer)
  2. Use Non-Color for albedo and sRGB for roughness, metallic, normal, and ambient occlusion.
  3. Use sRGB for albedo and normal, but Non-Color for roughness, metallic, and ambient occlusion.
  4. Use sRGB for every map because all image textures require display-color correction before shading.
Explanation: When working with PBR texture maps in Blender, the key distinction is between maps that carry perceptual color data and maps that carry raw linear data. This determines which color space Blender should use to interpret each file before passing values to the shader. Albedo (diffuse color) is painted to look correct on a monitor, meaning it was encoded in sRGB gamma. Blender must therefore decode it using the sRGB color space so the internal linear math in the shader receives accurate linear light values. Roughness, metallic, ambient occlusion, and normal maps, however, store numerical data — surface properties, not colors for human eyes. These were authored as linear values and should be assigned Non-Color so Blender does not apply gamma correction, which would silently distort the data and break your physically based shading. Choice A is correct because it follows this exact logic: sRGB for albedo, Non-Color for all data maps. Choice B inverts the logic entirely — treating albedo as raw data and perceptual maps as sRGB — which would simultaneously wash out your diffuse color and corrupt every data channel. Choice C correctly handles roughness, metallic, and ambient occlusion, but mistakenly assigns sRGB to the normal map. Normal maps encode XYZ direction vectors as numerical data, not perceptual color, so applying gamma correction skews the decoded surface normals and produces incorrect lighting. Choice D reflects a common misconception that "images always need sRGB." sRGB correction is only appropriate for human-perceived color data, not numerical texture data. A reliable rule of thumb: if a texture is meant to be seen as color, use sRGB; if it stores numbers, use Non-Color.

Question 9

A supplied ambient occlusion map darkens seams and tight recesses. The material already receives direct illumination and indirect bounce lighting in the scene, and the Principled BSDF has no dedicated AO input.

Which use of the AO map best matches its intended role while minimizing unrealistic results?

  1. Use it as the metallic map so deeply occluded regions produce weaker dielectric reflections.
  2. Use it as roughness so recesses automatically become less reflective under direct illumination.
  3. Multiply it conservatively with base color or indirect shading, avoiding excessive double-darkening. (correct answer)
  4. Connect it through a Normal Map node so crevices alter their orientation toward incoming light.
Explanation: When working with texture maps in Blender, the key question to always ask is: what does this map actually represent, and where does that information belong in the shading pipeline? An ambient occlusion map encodes geometric accessibility — how much ambient light reaches each surface point. It's a contact-shadow and crevice-darkening tool, not a material property descriptor. With that framing, C is correct. Multiplying the AO map conservatively with base color or indirect lighting honors its actual meaning: regions that receive less ambient light appear subtly darker. The word "conservatively" matters here — since your scene already computes real indirect bounce lighting, feeding AO too aggressively will double-darken those areas, creating muddy, physically inaccurate results. A gentle multiply blend respects the map's role as a subtle detail enhancer rather than a lighting replacement. A is wrong because metallic values control whether a surface behaves as a conductor or dielectric — this is a material identity property, not a light-accessibility property. Darkening metallic values in crevices misrepresents the physics entirely. B is wrong for a similar reason: roughness describes microsurface scattering, not how much light reaches a point. Making recesses less reflective via roughness is a different (and incorrect) physical effect. D is wrong because a Normal Map node interprets its input as encoded surface orientation data (XYZ packed into RGB). Feeding an AO map — which contains grayscale proximity information — through a Normal Map node produces meaningless, corrupted normals. As a study habit, always match each texture map to its semantic meaning before deciding where to plug it in. If a map answers "how much light reaches here?" it belongs in the lighting path, not material properties.

Question 10

An RGB tangent-space normal texture is connected directly from an Image Texture node's Color output to the Principled BSDF Normal input. The texture is set to sRGB, and the result appears distorted rather than showing the intended fine relief.

Which node setup most appropriately corrects both conceptual errors?

  1. Use sRGB, pass the image through a Bump node's Height input, and connect Bump to Normal.
  2. Use Non-Color, pass the image through a Normal Map node, and connect its Normal output to the shader. (correct answer)
  3. Use Non-Color, connect the image directly to the shader's Normal input, and lower Metallic.
  4. Use sRGB, pass the image through a Color Ramp, and connect the result to shader Roughness.
Explanation: When working with normal maps in Blender, two things must always be correct simultaneously: the color space of the image and the node that interprets the data. Normal map textures encode directional vectors as RGB values — they are raw data, not visual color, so the pipeline must treat them accordingly. The fix requires both corrections at once. First, the Image Texture node must be set to Non-Color, because sRGB applies a gamma curve that distorts the linear vector data baked into the texture, producing those surface artifacts you see. Second, the image must pass through a Normal Map node before reaching the shader. This node decodes the tangent-space RGB values into actual surface normal vectors that the Principled BSDF can use correctly. Together, these two changes are exactly what option B describes — making it the right answer. Option A is wrong on two counts: it keeps the destructive sRGB color space, and it routes the image through a Bump node, which expects a grayscale height map, not an RGB normal map. These are entirely different texture types. Option C skips the Normal Map node entirely, so even with the correct Non-Color space, the shader receives raw RGB floats rather than properly decoded normals — and lowering Metallic has nothing to do with the problem. Option D wanders off completely, feeding a normal texture into Roughness via a Color Ramp, which neither fixes the color space problem nor uses the texture for its intended purpose. A reliable rule: normal map → Non-Color + Normal Map node; bump map → Non-Color + Bump node. Mixing these up is the most common normal-map mistake in Blender.