Changelog
All notable changes to Kit Optimizer are documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[1.0.0] - 2026-10-07
First public release. Requires Unity 2022.3 LTS or Unity 6, with the Built-in Render Pipeline, URP or HDRP. Written entirely in C#, with no native plugins.
Added
- One dockable window (Tools > Kit Optimizer) with Home, Library, Atlases, Merge Groups and Build Check tabs, plus a Help menu with this manual, a quick start, third-party notices, Report a Problem (a report of versions, settings and recent messages to send to support) and an About box. An Advanced tickbox shows the settings most projects never need.
- Home tab: checks the render pipeline, a third-party lightmapper integration when one is installed, and the library folder; task cards for the main jobs; the open scenes' before and after numbers; Suggestions, which proposes atlases and merge groups for the open scenes (planned like real ones, nothing changes until you create one; atlas proposals use the smallest page that keeps the detail Unity shows now, and merge proposals keep each prop whole and are named after it); links to the manual and quick start; and Show sample, which highlights the Collector's Study sample's scene (the sample ships in the tool's
Samplesfolder; the Atlases tab lists its atlas only while its scene is open). - Before and after cards in the Atlases, Merge Groups, Build Check and Home tabs: materials, textures, texture memory, renderers and draw calls, originals against the result, with the assumptions behind each estimate. A result that is not better is shown, not hidden. An atlas whose members already share one material says so and suggests a merge group instead; one that costs texture memory says so, with a button to its Memory view.
- Memory view for each atlas: every generated map's size, format and texture memory for the active build target, what a smaller Max Size, compression or mip map streaming would save, and the atlas's Texture Import preset for setting them.
- Shared asset library, one folder per computer used by all your projects:
- Import project assets with everything they depend on. Shaders and Shader Graphs are stored with the files they include; scripts and package files are recorded as requirements, not copied.
- Import files and folders from outside the project, by file picker or by dragging from your file browser.
- Adobe Substance 3D Painter exports become a model with a material for the project's render pipeline (Standard, URP Lit or HDRP Lit), metallic or specular. ORM maps are converted exactly into MetallicSmoothness and Occlusion maps (a mask map in HDRP), and the normal-map direction is measured from the map itself. PNG, TGA, JPG, TIFF, PSD, BMP and GIF maps are read exactly.
- PBR downloads with the common map naming (diff, nor_gl, arm, rough, metal, alpha and so on, with a resolution suffix) are recognised. ARM maps and separate roughness and metallic maps are converted exactly into MetallicSmoothness (and Occlusion) maps, and an alpha map is combined with the base colour, giving a Cutout material when at least 97% of its texels are fully transparent or fully opaque (soft edges allowed), otherwise Fade.
- Capture configured scene objects; prefab instances become variants that keep their overrides.
- Placement keeps Unity GUIDs, so references survive. Identical files are reused, collisions are refused, and each project stays on its revision until you update it.
- Prepared versions: the same source files imported with smaller textures, switchable per project without loss.
- Thumbnails, packs, My assets and External filters, filters by kind, tags, search and drag into the scene.
- Several projects can use one library at once without overwriting each other's imports; a pack file that cannot be read hides only that pack, and an unavailable folder is reported as such.
- Placed assets can be edited and imported back into their pack. Scripts and plugins in imported folders are skipped and listed, and references to files outside an import are reported.
- Reversible texture atlasing:
- Intentional UV sharing is kept: stacked, partially overlapping, mirrored and cross-asset islands keep sharing their texels. Texels are copied exactly unless the content must be scaled to fit its page or you choose a reduction; islands are moved, never scaled on their own.
- Apply, Restore originals and Disable at any time, with Undo. Original textures, meshes and materials are never modified.
- Pack modes per texture set (Repack Islands, Keep Layout, Keep Whole Texture, Keep Whole Texture Cropped, Original) and a layout comparison.
- Generate & Apply in one click, with Generate, Apply and Restore originals as separate steps below it.
- A member list with each member's state and original material, a remove button per row, and a filter.
- Delete an atlas (asks first): members go back to their originals and the definition goes to the Recycle Bin.
- Islands view: see how islands are grouped and keep chosen islands together or apart.
- Fit to page (default): the atlas is packed on the page size you choose. When the content does not fit, every texture set is scaled by the same factor, resampled once from the originals, and this is reported, with the page size that keeps every texel exact and a button to use it.
- Full (exact texels): content that does not fit is never shrunk: choose a larger page, a split into several atlases, or a detail reduction for the whole atlas or one texture set.
- Optional resampling of maps whose size differs from the rest of their set, from the originals.
- Tiled textures (optional): members whose UVs repeat the texture, like a tiled floor, are copied tile by tile, exactly, up to 8 repeats.
- Maps keep their sources' precision: EXR and HDR sources give an EXR atlas map (values above 1 kept), 16-bit data maps a 16-bit PNG.
- Atlases are built from what Unity shows: Flip Green Channel, normal maps created from greyscale, alpha from greyscale or none and channel swizzles are applied to the atlas texels.
- Outputs are tracked and reported as stale when any input changes, including those import settings.
- Generation shows its progress and can be cancelled; a cancelled generation changes nothing.
- Packing uses a built-in managed packer (see Third Party Notices), so atlases are generated in every editor and come out the same on every computer.
- Rotate regions to fit (optional, built-in shader profiles): the packer may flip a region across its diagonal to fit it tighter. Texels are still copied exactly and normal maps read the same.
- Skinned mesh renderers and submeshes that share vertices are supported.
- Baked lighting is kept: atlas meshes keep their lightmap UVs, and a mesh without them keeps its original UVs as lightmap UVs. Emissive members still light bakes after atlasing.
- Atlas textures follow the members' import settings, including mipmap coverage for cutout maps and per-platform overrides.
- Texture import (advanced): a Texture Import preset sets the generated textures' import settings (size, compression, format, mip maps, filtering and per-platform overrides), for the whole atlas or per map. New from output makes one from a generated texture to edit in the Inspector. Colour space, texture type and readability stay as the atlas needs them.
- Mask (advanced, off by default): a flat colour (ID map) or grey step per unique mesh, in a texture lined up with the atlas and/or in the generated meshes (a UV channel or vertex colour). Each mesh's value is stable across generations and can be set by hand; Copy legend gives the values and a shader test for each. Existing mesh data is never overwritten unless you ask.
- Texel density (advanced): keep each texture set's detail (exact), even it out across sets, or cap it at a number of texels per metre.
- Gallery view: compare originals with the result in a temporary preview that never touches your scene. Each distinct look is shown once, in a grid by size however far apart the members are, with In a line and As placed layouts, spacing and Frame all.
- Shader profiles:
- Built-in profiles for the common shaders of each pipeline: Standard (metallic and specular), Autodesk Interactive, the Legacy and Mobile shaders and Unlit; URP Lit (metallic and specular, Complex Lit), Simple Lit, Baked Lit and Unlit; HDRP Lit (every material type, tessellation) and Unlit. Any other shader works through an editable generic profile. A new atlas picks the profile that matches its members; other pipelines' profiles are greyed out.
- Detail maps on the second UV set, HDR emission, textures stored inside models and
.assetfiles, and members with different anisotropy or mip bias are atlased. - Output to any installed shader through a template material edited with that shader's own inspector, with draggable generated textures, auto-fill and packed textures (roughness, smoothness, metallic, ORM, mask map or custom).
- Save profiles to the library as versions and reuse them in other projects.
- Optional baking of tints and strengths into texels, so members that differ only in those values can share one material. The atlas material is checked with its shader's own inspector rules, so it draws as generated.
- Members lit with MonoSH directional lightmaps are never moved to a shader that does not decode MonoSH without your explicit acceptance.
- Reversible mesh batching with merge groups:
- Combine nearby static objects into one renderer, one submesh per material. Members stay in the scene with their renderers hidden and their colliders and scripts intact; separate again at any time.
- Lightmaps are kept: each member's lightmap scale and offset are folded into the combined mesh, with Unity's built-in lightmapper and with third-party lightmappers that keep their own per-scene lightmap storage (including MonoSH).
- Groups are separated when a bake starts and combined again afterwards, automatically. This covers full bakes; Unity's Auto Generate previews and bakes of selected objects only are left alone.
- Members may use different materials; members lit by light probes are combined whenever their probe light stays the same (no baked probes, a shared Anchor Override, or probes holding the same light).
- Split by lightmap makes one group per lightmap when a bake spread the members over several; Make settings match gives members the renderer settings most of them have.
- A combined object lit by more realtime lights than one object receives is flagged; NavMesh areas are carried over.
- Members lit by the third-party lightmapper's SH and RNM modes, or by its vertex lighting, combine with their lighting carried over.
- Every refusal comes with a reason. With Unity 6's GPU Resident Drawer on, a group that repeats one mesh and material says the drawer already draws those together.
- The Collector's Study sample: a tea corner built from CC0 props and materials, with an atlas and a merge group declared but not generated, and a two-minute walkthrough in its README.
- Scene modes: add or remove atlas and merge members by clicking in the Scene view, with reasons shown on hover and an Isolate option.
- Safe by default: the window is read-only in Play mode, atlases and scenes saved by a newer version of the package are shown but not changed, and a tab that hits an error shows a notice with Report a problem instead of breaking.
- Build check: everything that differs from your declared atlas and merge state, with fixes and Fix all. Player builds stop (after asking, in the editor) when the open scenes have a blocker: a build that would miss objects, materials or lighting; content builds made with the Scriptable Build Pipeline (Addressables) stop too. Editor-only data and previews are kept out of builds, as are originals that only that data refers to, and nothing from Kit Optimizer runs in your built game. The check also runs from the command line for build machines (
KitOptimizer.Editor.Build.CommandLine.Checkand.FixAll, with exit codes).
Upgrading from 0.x development versions
- Atlas definitions and saved profiles from 0.x load and keep their settings.
- Atlases generated by 0.x are reported as stale after updating, because each atlas's input fingerprint includes the package version. Nothing changes in your scenes until you regenerate: members that show 0.x output keep showing it.
- To regenerate every atlas at once, open the Build Check tab and click Fix all. To regenerate one atlas, select it in the Atlases tab and click Generate. Generation always reads your original files, so the result is the same as a fresh generation, and members that showed the old output switch to the new one.