Technical Artist Workflow
Unity Prefab and Material Review for Technical Artists
Technical artists should review prefab and material changes as connected Unity data. For prefabs, inspect hierarchy, components, nested sources, overrides, and references. For materials, inspect shader identity, keywords, textures, saved properties, and render flags. Validate representative instances and renderers before approval.
Build the dependency scope
Start with the changed asset list, then include the dependencies that explain the change:
- Prefab sources, variants, nested prefabs, and scene instances.
- Scripts attached to changed components.
- Materials, shaders, textures, meshes, and importer meta files.
- ScriptableObjects or data assets referenced by the prefab.
- Meta files for every added, moved, renamed, or replaced asset.
A material diff without its shader change, or a prefab diff without its nested source, can lead to the wrong conclusion.
Prefab review checklist
- GameObject hierarchy, names, parents, sibling order, and active state.
- Added and removed components and their owning GameObjects.
- Script GUIDs and serialized component property changes.
- Nested prefab source GUIDs and source object fileIDs.
- Instance override targets, property paths, and values.
- Added or removed objects/components represented as overrides.
- Local and cross-asset references.
Material review checklist
- Shader GUID and expected render pipeline compatibility.
- Enabled keywords and stale keyword cleanup.
- Texture GUIDs, scale, offset, and importer assumptions.
- Saved float, integer, color, and vector properties.
- Render queue, instancing, GI, culling, and other flags.
- Properties removed, renamed, or reset after a shader update.
Review through Unity concepts
MergeSight technical-art asset review can compare working tree, branches, commits, or supported VCS revisions and show prefab objects, components, properties, overrides, material keywords, saved property paths, GUIDs, fileIDs, and references. Filters can isolate only materials, prefabs, references, overrides, or a specific change kind.
Export Markdown or JSON when the change crosses team boundaries and needs a durable review artifact.
Technical-art risk table
| Change | Primary risk | Validation |
|---|---|---|
| Shader replacement | Lost properties or incompatible render state | Open representative materials and renderers. |
| Nested prefab source | Propagation to many scenes and variants | Inspect affected sources and representative instances. |
| Override path change | Stale or retargeted local customization | Open Prefab Mode and inspect overrides. |
| Script/meta GUID change | Missing component type | Import and check missing scripts. |
| Texture/import setting | Visual, memory, or platform regression | Inspect meta diff and target-platform import. |
| Large reserialization | Real change hidden by YAML churn | Separate or filter semantic changes. |
Approval workflow
- Confirm the comparison range and intended visual or pipeline change.
- Review semantic prefab and material changes.
- Resolve important GUID/fileID targets to named assets and objects.
- Open representative prefab instances and renderers in Unity.
- Check platform-specific import, shader compilation, and material behavior where relevant.
- Run missing-script/reference checks and project-specific validation.
- Approve only after unrelated reserialization is explained or removed.
When a prefab or material conflict appears
Preserve Base / Ours / Theirs. For a prefab, classify hierarchy, source, override, component, and reference decisions. For a material, compare shader identity and each saved property path. Preview the result and validate representative consumers before writing or marking the conflict resolved.
FAQ
What should a technical artist review in a Unity prefab?
Review hierarchy, components, script identity, nested prefab sources, overrides, added or removed objects, and resolved local or cross-asset references.
What should a technical artist review in a Unity material?
Review shader identity, keywords, textures, saved properties, render flags, importer changes, and representative renderer output.
Can Unity material changes be reviewed in Git?
Yes, text-serialized .mat files can be diffed. A semantic view makes shader, keyword, texture, and saved-property changes easier to understand.
Can MergeSight filter prefab and material changes?
Yes. MergeSight can filter changed assets by type, path, name, and status, and filter semantic rows by query, change kind, and item type.
Summary
Review dependencies
Prefab sources, shaders, textures, scripts, data assets, and meta files explain the visible diff.
Inspect semantic paths
Ownership, overrides, keywords, saved properties, GUIDs, and fileIDs carry technical-art meaning.
Validate representative use
Open real instances and renderers, then check imports, scripts, references, and target platforms.
Technical-art review connects serialized asset changes to the prefab, shader, material, import, and runtime systems they can affect.
Next step
For focused property analysis, use How to Diff Unity Materials and ScriptableObject Assets.