Quick answer: Set Texture Type explicitly — Normal Map for normals, Default with sRGB unchecked for data textures. Add an AssetPostprocessor that enforces the type based on file name suffixes.

After a team member checked in updated normal maps, the next person to reimport noticed their normals had subtle wrong lighting. The .meta file said sRGB was checked. They unchecked it, the lighting looked right, they committed, and a week later it happened again to someone else.

How Unity Decides sRGB

The Texture Importer’s Texture Type dropdown sets a category that determines how Unity treats the texture data:

If a normal map is set to Default, sRGB can be toggled by hand but Unity may flip it back during reimport — particularly if the source file changes dimensions or channel count. The fix is to set Texture Type to Normal Map, which removes the toggle entirely and locks the linear interpretation.

The AssetPostprocessor Solution

For project-wide enforcement, add an Editor-only script that classifies textures by filename suffix:

using UnityEditor;
using UnityEngine;

public class TextureImportRules : AssetPostprocessor
{
    void OnPreprocessTexture()
    {
        var importer = (TextureImporter)assetImporter;
        string path = assetPath.ToLower();

        if (path.Contains("_n.") || path.Contains("_normal."))
        {
            importer.textureType = TextureImporterType.NormalMap;
        }
        else if (path.Contains("_d.") || path.Contains("_data.") ||
                 path.Contains("_mask.") || path.Contains("_rough."))
        {
            importer.textureType = TextureImporterType.Default;
            importer.sRGBTexture = false;
        }
        else if (path.Contains("_ui."))
        {
            importer.textureType = TextureImporterType.Sprite;
        }
    }
}

Place in Assets/Editor/. The script runs every time Unity imports or reimports a texture. Filename conventions become the source of truth, and individual .meta tweaks no longer drift.

Force a Project-Wide Reimport

To apply the new rules to existing textures, reimport them:

// Editor menu: Tools → Reimport All Textures
[MenuItem("Tools/Reimport All Textures")]
static void ReimportAll()
{
    var guids = AssetDatabase.FindAssets("t:Texture2D");
    foreach (var guid in guids)
    {
        var path = AssetDatabase.GUIDToAssetPath(guid);
        AssetDatabase.ImportAsset(path, ImportAssetOptions.ForceUpdate);
    }
}

Run after committing the AssetPostprocessor. Commit the resulting .meta changes — they encode the corrected import settings.

Verifying

Pick a known normal map. Open the Inspector. Texture Type should read “Normal Map”. Open the .meta file in a text editor (it’s YAML); look for sRGBTexture: 0. If it says 1, the rule didn’t match the filename pattern — check the suffix convention.

Compare a material with the normal map before and after the fix. Subtle but distinct: post-fix normals show crisper micro-lighting, especially on metallics where the energy conservation depends on accurate normal data.

What About Existing Misnamed Files?

If your project has normal maps named rock_bump.png instead of rock_n.png, either rename them (Unity rewrites references on rename), or add label-based classification:

AssetDatabase.SetLabels(asset, new[] { "NormalMap" });
// then in the importer:
if (AssetDatabase.GetLabels(importer.GetAsset()).Contains("NormalMap")) ...

Labels survive renames and are project-wide visible.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Manual sRGB toggles drift. AssetPostprocessor rules don’t. Encode the convention once; let the importer enforce it forever.”

Lock the Texture Type, not the sRGB toggle. Type is the durable setting; sRGB is its consequence.