[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMFF27Q72VE7RH35KKKX67":3,"skill-same:01M7CMFF27Q72VE7RH35KKKX67":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CMFF27Q72VE7RH35KKKX67","unity-2d-pixel-perfect",null,"Blurry, shimmering or seamed pixel art in Unity: Pixel Perfect Camera, import settings, snapping.","tipoLi5890\u002Funity-dev-skills","tipoLi5890","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F177803612?v=4","01M7CMD7DHGZ09CB53CRFHAA34","Li, ching yu","01M7CMD7E70K5RAHWWZVYX9YMG",2,"MIT","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unity-2d-pixel-perfect\ndescription: >-\n  Blurry, shimmering or seamed pixel art in Unity: Pixel Perfect Camera,\n  import settings, snapping.\n---\n\n# unity-2d-pixel-perfect — two components with the same name, and only one of them is yours\n\n> **Pixel perfect is not one Unity feature, it is two incompatible implementations of one name.**\n> URP ships `UnityEngine.Rendering.Universal.PixelPerfectCamera`, driven by enums. The\n> standalone `com.unity.2d.pixel-perfect` package ships `UnityEngine.U2D.PixelPerfectCamera`,\n> driven by booleans. Adding the wrong one costs you nothing at compile time and everything at\n> runtime, so **the pipeline in force decides the component, and you resolve it first.**\n\n## Start here — symptom → where to look\n\n| Symptom | Go to |\n|---|---|\n| \"Which `PixelPerfectCamera` do I add\"; the pipeline in force decides which same-named component | §1 |\n| The component is on the camera and nothing snaps; it compiles but does nothing after a render-pipeline change | §1, §9 — wrong implementation for the pipeline |\n| `PixelPerfectCamera` will not resolve in an Editor script | §1 — assembly names |\n| Sprites are soft or washed out at every zoom | §2 |\n| Sprites sharp at one zoom, soft at another; choosing a reference resolution | §3 — non-integer scale factor |\n| Hairline gaps between tilemap tiles | §5 |\n| Pixels crawl or shimmer while the camera pans | §4 `gridSnapping`, then §8 |\n| The camera jitters and framing pops between shots; Cinemachine and the pixel camera fight over orthographic size | §6 — Cinemachine |\n| UI text went soft; the scene did not | §7 |\n| Post-processing blurs the entire frame | §7 |\n| A physics-driven sprite stutters while everything else is smooth | §8 |\n| Black bars, or the scene stretched to a wrong aspect | §4 `cropFrame`, §3 |\n| Compiler errors naming `UnityEngine.Experimental.Rendering.Universal` | §9 |\n| Property tables, enum values, old-bool mapping | `reference\u002Fapi-and-enums.md` |\n\n## 1. Resolve the pipeline, then pick the component\n\n> **Read `GraphicsSettings.currentRenderPipeline`, not `RenderPipelineManager.currentPipeline`.**\n> The second holds the pipeline *instance*, which does not exist until a frame has rendered, so\n> it reports \"built-in\" on startup paths and on headless checks. On a project running URP,\n> `RenderPipelineManager.currentPipeline` can be **null** while\n> `GraphicsSettings.currentRenderPipeline` names the URP asset. Two APIs, opposite answers, same\n> instant.\n\n| | URP | Standalone built-in |\n|---|---|---|\n| Type | `UnityEngine.Rendering.Universal.PixelPerfectCamera` | `UnityEngine.U2D.PixelPerfectCamera` |\n| Assembly | `Unity.RenderPipelines.Universal.2D.Runtime` | `Unity.2D.PixelPerfect` (confirm by reflection) |\n| Comes from | URP itself — nothing to install | `com.unity.2d.pixel-perfect` |\n| API shape | Enums: `gridSnapping`, `cropFrame` | Booleans: `pixelSnapping`, `upscaleRT`, `cropFrameX\u002FY`, `stretchFill` |\n\nConfirm the standalone assembly name by reflection on a project that has the package —\n`reference\u002Fpipeline-and-migration.md` §2, with why a guessed `Runtime` suffix breaks `Type.GetType`\nand the lockfile check.\n\n> **Do not add `com.unity.2d.pixel-perfect` to a URP project.** It installs and compiles without\n> complaint, and leaves the project carrying two different components under one name — remove the\n> package rather than working out which one wins. On a URP project the type you want is already\n> there; a project that arrived with the package already on a camera is §9.\n\n**A null default pipeline does not mean built-in.** A project can have an empty default with\nevery quality tier overriding it; `currentRenderPipeline` folds the tier in and is the one to\ntrust. The six reads and the grep trap: `reference\u002Fpipeline-and-migration.md` §1; the full\nprocedure: `unity-render-urp` → `reference\u002Fresolve-active-pipeline.md`.\n\nCode: `resources\u002FPipelineDetection.cs` — pipeline probe,\ncomponent-type lookup for either pipeline, and the mismatch check §9 uses.\n\n> **Report, then wait.** Fixing import settings reimports textures and rewrites `.meta` files\n> across the art folder; adding or swapping a camera component changes a scene. Survey first,\n> list what you would change with before\u002Fafter values, and wait for confirmation. Default to the\n> open scene — sweep the whole project only when asked for it.\n\nReaching a live Editor for any of these reads: `unity-debug` → `reference\u002Feditor-control.md`.\n\n## 2. The four import settings that decide sharpness\n\nBilinear filtering is the import default and the most common cause of soft pixel art. Set\n`filterMode = Point`, mipmaps off, `Uncompressed`, one `spritePixelsPerUnit` project-wide; AA 0 in\nthe **active** quality level, MSAA 1 on the URP asset, and `allowHDR`\u002F`allowMSAA`\u002F\n`allowDynamicResolution` off on the camera. A centre pivot on an odd-sized sprite lands on half a\npixel (\"only this one sprite is blurry\"). Editor grid snapping: `1 \u002F assetsPPU`. The table, the\nwhy and the snapping steps: `reference\u002Fsharpness.md` §2. Code:\n`resources\u002FSpriteImportFix.cs`. Frames shipped upscaled by F (`frames.json` `pixel.block_px`)\nimport at F × the art-pixel PPU; `assetsPPU` is their PPU ÷ F (`codex-visual` →\n`reference\u002Fpixel-grid.md`).\n\n## 3. Reference resolution, chosen once\n\nPick it before art production: 320×180 fits 1080p, 1440p and 2160p at whole numbers (6×, 8×,\n12×), which is why it is the safe default; a fractional factor ribs the art, and a screen with no\ninteger fit gets `cropFrame = Windowbox`, not a stretch. `Camera.orthographicSize =\n(refResolutionY \u002F 2f) \u002F assetsPPU` (320×180 at PPU 16 → 5.625), separate from the component's own\nread-only value. The table: `reference\u002Fsharpness.md` §3.\n\n## 4. `gridSnapping` and `cropFrame`\n\n`GridSnapping` is `None`, `PixelSnapping`, `UpscaleRenderTexture`; `CropFrame` is `None`,\n`Pillarbox`, `Letterbox`, `Windowbox`, `StretchFill`; `PixelPerfectFilterMode` is `RetroAA`,\n`Point` — all enumerated from the assembly. `PixelSnapping` + `Windowbox` is the default worth\nreaching for: it snaps sprite renderers at render time, leaves transforms at float precision, and\nstays compatible with post-processing and with UI. `UpscaleRenderTexture` renders the frame at\nreference resolution and scales the whole buffer up — the authentic look, and the source of both\nproblems in §7.\n\n> **`PixelPerfectFilterMode` has no public property on the URP component.** Only the serialized\n> private `m_FilterMode`, so the Inspector can set it and script cannot — author it in a prefab or\n> scene. It is documented to apply only under `cropFrame = StretchFill`, and it is unrelated to\n> per-texture `filterMode` (§2).\n\nProperty tables for both components, the old-bool mapping, recommended combinations and the\n`pixelSnapSpacing` formula: `reference\u002Fapi-and-enums.md`.\n\n## 5. Tilemap seams — work the ladder in order\n\nHairline gaps have six ordinary causes and one that appears only in motion; work them top to\nbottom, never a negative cell gap or PPU 31.99: atlas Tight Packing off and Padding ≥ 4 → mipmaps\noff on tileset and atlas → AA and MSAA off → `Uncompressed` → even pixel dimensions → `assetsPPU`\nequal to the tile's width → gaps only while the camera moves: `gridSnapping = PixelSnapping`. The\nladder with each failure: `reference\u002Fsharpness.md` §5. Rows 1 and 2 are `unity-sprite-atlas`;\nauthoring the tilemap is `unity-tilemap`.\n\n## 6. Cinemachine writes orthographic size too\n\nThe pixel camera owns orthographic size, and Cinemachine writes it every frame too: jitter, plus\nframing that pops between shots. Put the **`CinemachinePixelPerfect` extension** on every camera\nrig, through its Add Extension dropdown. Follow, dead zones, confiners, blends and the component\nnames for each Cinemachine major: `unity-camera` → `reference\u002Fpixel-perfect-follow.md`.\n\n## 7. `UpscaleRenderTexture` versus UI text and post-processing\n\nOne cause, two symptoms: the scene is rendered small and then scaled up, and anything that runs\nafter that scale-up — or gets caught inside it — is working at the wrong resolution.\n**Post-processing** then filters an enlarged image: leave `gridSnapping = PixelSnapping`, or inject a\n2D renderer feature after post-processing, since a plain `ScriptableRendererFeature` on a URP 2D\nrenderer is **ignored without an error**. **UI text** on a Screen Space – Camera canvas softens with\nthe scene: set the canvas to **Screen Space – Overlay**, the route that holds. The ranked\nalternatives and where canvas and font work goes: `reference\u002Fmotion-and-upscale.md` §2. Confirm\neither fix in a windowed run with the canvas and a volume in the scene — a headless check shows\nneither symptom.\n\n## 8. Micro-stutter is physics, not rendering\n\nA sprite driven by `Rigidbody2D` stutters while everything else is smooth: physics advances on a\nfixed timestep and rendering does not, and snapping makes the sub-pixel error visible. The fix is\n`Rigidbody2D.interpolation = RigidbodyInterpolation2D.Interpolate` on every physics-driven sprite;\na matched fixed timestep and camera follow in `LateUpdate` tighten it —\n`reference\u002Fmotion-and-upscale.md` §3. Confirm it in play mode with a moving rigidbody. The\nmovement code itself is `unity-2d-controller`.\n\n## 9. Migration\n\n**Wrong component for the pipeline** — URP in force, `UnityEngine.U2D.PixelPerfectCamera` on the\ncamera: remove the package and the component, add the URP one, re-enter the settings (booleans do\nnot migrate into enums). `PipelineDetection.HasWrongComponent` finds it. **Deprecated booleans on\nthe right component** still compile, as a **warning, not an error** — so bool-style code compiling\nproves nothing about which component you are on. Read the type, not the property names.\n\n**Old URP namespace** (`UnityEngine.Experimental.Rendering.Universal`), **no 2D renderer under\nURP**, and **HDRP**, which has no Pixel Perfect Camera at all: steps for all five cases, and the\nbool → enum mapping, via `reference\u002Fpipeline-and-migration.md` §3.\n\n## Scope — what this skill does NOT do\n\nSlicing sheets, pivots, rects, 9-slice borders and outlines are `unity-2d-sprites` — this skill\nonly says which pivot values keep a sprite on the grid. Atlas packing, padding, packer mode and\natlas memory are `unity-sprite-atlas`, which rows 1 and 2 of §5 hand off to. Tilemaps, palettes\nand rule tiles are `unity-tilemap`; §5 ends at \"the seam is not the tilemap's fault\". Parallax\nand sorting are `unity-2d-rendering`.\n\nResolving the active render pipeline, URP asset and renderer configuration, Volumes and Render\nGraph passes are `unity-render-urp` — §1 reads the pipeline, it does not set it. The canvas itself\n— render mode, scaler, layout — is `unity-ui-ugui`, and font assets and CJK glyph coverage are\n`unity-game-ui`; §7 only says which canvas mode escapes the upscale. Before\u002Fafter screenshots and\nconnecting to a live Editor at all are `unity-debug`.\n\nArt direction is out of scope in both directions: this skill will not tell you a resolution is\ntoo low for your art, and it does not apply to high-resolution or hand-painted 2D, where point\nfiltering and snapping make smooth art look wrong.\n\n## Reference\n\n- `reference\u002Fapi-and-enums.md` — both components member by member,\n  enums with old-bool equivalents, combinations, `pixelSnapSpacing`.\n- `reference\u002Fsharpness.md` — the import settings table, reference\n  resolutions, the tilemap seam ladder.\n- `reference\u002Fpipeline-and-migration.md` — pipeline reads,\n  assembly names, migration steps.\n- `reference\u002Fmotion-and-upscale.md` — the Cinemachine rule, the\n  upscale's side effects, physics stutter.\n- Code: `PipelineDetection.cs` (resolve the pipeline, pick the\n  type, detect a mismatch), `CameraSetupURP.cs` (enum-style),\n  `CameraSetupBuiltIn.cs` (bool-style, standalone package),\n  `SpriteImportFix.cs` (the four import settings from §2).\n","# unity-2d-pixel-perfect — two components with the same name, and only one of them is yours\n\n> **Pixel perfect is not one Unity feature, it is two incompatible implementations of one name.**\n> URP ships `UnityEngine.Rendering.Universal.PixelPerfectCamera`, driven by enums. The\n> standalone `com.unity.2d.pixel-perfect` package ships `UnityEngine.U2D.PixelPerfectCamera`,\n> driven by booleans. Adding the wrong one costs you nothing at compile time and everything at\n> runtime, so **the pipeline in force decides the component, and you resolve it first.**\n\n## Start here — symptom → where to look\n\n| Symptom | Go to |\n|---|---|\n| \"Which `PixelPerfectCamera` do I add\"; the pipeline in force decides which same-named component | §1 |\n| The component is on the camera and nothing snaps; it compiles but does nothing after a render-pipeline change | §1, §9 — wrong implementation for the pipeline |\n| `PixelPerfectCamera` will not resolve in an Editor script | §1 — assembly names |\n| Sprites are soft or washed out at every zoom | §2 |\n| Sprites sharp at one zoom, soft at another; choosing a reference resolution | §3 — non-integer scale factor |\n| Hairline gaps between tilemap tiles | §5 |\n| Pixels crawl or shimmer while the camera pans | §4 `gridSnapping`, then §8 |\n| The camera jitters and framing pops between shots; Cinemachine and the pixel camera fight over orthographic size | §6 — Cinemachine |\n| UI text went soft; the scene did not | §7 |\n| Post-processing blurs the entire frame | §7 |\n| A physics-driven sprite stutters while everything else is smooth | §8 |\n| Black bars, or the scene stretched to a wrong aspect | §4 `cropFrame`, §3 |\n| Compiler errors naming `UnityEngine.Experimental.Rendering.Universal` | §9 |\n| Property tables, enum values, old-bool mapping | `reference\u002Fapi-and-enums.md` |\n\n## 1. Resolve the pipeline, then pick the component\n\n> **Read `GraphicsSettings.currentRenderPipeline`, not `RenderPipelineManager.currentPipeline`.**\n> The second holds the pipeline *instance*, which does not exist until a frame has rendered, so\n> it reports \"built-in\" on startup paths and on headless checks. On a project running URP,\n> `RenderPipelineManager.currentPipeline` can be **null** while\n> `GraphicsSettings.currentRenderPipeline` names the URP asset. Two APIs, opposite answers, same\n> instant.\n\n| | URP | Standalone built-in |\n|---|---|---|\n| Type | `UnityEngine.Rendering.Universal.PixelPerfectCamera` | `UnityEngine.U2D.PixelPerfectCamera` |\n| Assembly | `Unity.RenderPipelines.Universal.2D.Runtime` | `Unity.2D.PixelPerfect` (confirm by reflection) |\n| Comes from | URP itself — nothing to install | `com.unity.2d.pixel-perfect` |\n| API shape | Enums: `gridSnapping`, `cropFrame` | Booleans: `pixelSnapping`, `upscaleRT`, `cropFrameX\u002FY`, `stretchFill` |\n\nConfirm the standalone assembly name by reflection on a project that has the package —\n`reference\u002Fpipeline-and-migration.md` §2, with why a guessed `Runtime` suffix breaks `Type.GetType`\nand the lockfile check.\n\n> **Do not add `com.unity.2d.pixel-perfect` to a URP project.** It installs and compiles without\n> complaint, and leaves the project carrying two different components under one name — remove the\n> package rather than working out which one wins. On a URP project the type you want is already\n> there; a project that arrived with the package already on a camera is §9.\n\n**A null default pipeline does not mean built-in.** A project can have an empty default with\nevery quality tier overriding it; `currentRenderPipeline` folds the tier in and is the one to\ntrust. The six reads and the grep trap: `reference\u002Fpipeline-and-migration.md` §1; the full\nprocedure: `unity-render-urp` → `reference\u002Fresolve-active-pipeline.md`.\n\nCode: `resources\u002FPipelineDetection.cs` — pipeline probe,\ncomponent-type lookup for either pipeline, and the mismatch check §9 uses.\n\n> **Report, then wait.** Fixing import settings reimports textures and rewrites `.meta` files\n> across the art folder; adding or swapping a camera component changes a scene. Survey first,\n> list what you would change with before\u002Fafter values, and wait for confirmation. Default to the\n> open scene — sweep the whole project only when asked for it.\n\nReaching a live Editor for any of these reads: `unity-debug` → `reference\u002Feditor-control.md`.\n\n## 2. The four import settings that decide sharpness\n\nBilinear filtering is the import default and the most common cause of soft pixel art. Set\n`filterMode = Point`, mipmaps off, `Uncompressed`, one `spritePixelsPerUnit` project-wide; AA 0 in\nthe **active** quality level, MSAA 1 on the URP asset, and `allowHDR`\u002F`allowMSAA`\u002F\n`allowDynamicResolution` off on the camera. A centre pivot on an odd-sized sprite lands on half a\npixel (\"only this one sprite is blurry\"). Editor grid snapping: `1 \u002F assetsPPU`. The table, the\nwhy and the snapping steps: `reference\u002Fsharpness.md` §2. Code:\n`resources\u002FSpriteImportFix.cs`. Frames shipped upscaled by F (`frames.json` `pixel.block_px`)\nimport at F × the art-pixel PPU; `assetsPPU` is their PPU ÷ F (`codex-visual` →\n`reference\u002Fpixel-grid.md`).\n\n## 3. Reference resolution, chosen once\n\nPick it before art production: 320×180 fits 1080p, 1440p and 2160p at whole numbers (6×, 8×,\n12×), which is why it is the safe default; a fractional factor ribs the art, and a screen with no\ninteger fit gets `cropFrame = Windowbox`, not a stretch. `Camera.orthographicSize =\n(refResolutionY \u002F 2f) \u002F assetsPPU` (320×180 at PPU 16 → 5.625), separate from the component's own\nread-only value. The table: `reference\u002Fsharpness.md` §3.\n\n## 4. `gridSnapping` and `cropFrame`\n\n`GridSnapping` is `None`, `PixelSnapping`, `UpscaleRenderTexture`; `CropFrame` is `None`,\n`Pillarbox`, `Letterbox`, `Windowbox`, `StretchFill`; `PixelPerfectFilterMode` is `RetroAA`,\n`Point` — all enumerated from the assembly. `PixelSnapping` + `Windowbox` is the default worth\nreaching for: it snaps sprite renderers at render time, leaves transforms at float precision, and\nstays compatible with post-processing and with UI. `UpscaleRenderTexture` renders the frame at\nreference resolution and scales the whole buffer up — the authentic look, and the source of both\nproblems in §7.\n\n> **`PixelPerfectFilterMode` has no public property on the URP component.** Only the serialized\n> private `m_FilterMode`, so the Inspector can set it and script cannot — author it in a prefab or\n> scene. It is documented to apply only under `cropFrame = StretchFill`, and it is unrelated to\n> per-texture `filterMode` (§2).\n\nProperty tables for both components, the old-bool mapping, recommended combinations and the\n`pixelSnapSpacing` formula: `reference\u002Fapi-and-enums.md`.\n\n## 5. Tilemap seams — work the ladder in order\n\nHairline gaps have six ordinary causes and one that appears only in motion; work them top to\nbottom, never a negative cell gap or PPU 31.99: atlas Tight Packing off and Padding ≥ 4 → mipmaps\noff on tileset and atlas → AA and MSAA off → `Uncompressed` → even pixel dimensions → `assetsPPU`\nequal to the tile's width → gaps only while the camera moves: `gridSnapping = PixelSnapping`. The\nladder with each failure: `reference\u002Fsharpness.md` §5. Rows 1 and 2 are `unity-sprite-atlas`;\nauthoring the tilemap is `unity-tilemap`.\n\n## 6. Cinemachine writes orthographic size too\n\nThe pixel camera owns orthographic size, and Cinemachine writes it every frame too: jitter, plus\nframing that pops between shots. Put the **`CinemachinePixelPerfect` extension** on every camera\nrig, through its Add Extension dropdown. Follow, dead zones, confiners, blends and the component\nnames for each Cinemachine major: `unity-camera` → `reference\u002Fpixel-perfect-follow.md`.\n\n## 7. `UpscaleRenderTexture` versus UI text and post-processing\n\nOne cause, two symptoms: the scene is rendered small and then scaled up, and anything that runs\nafter that scale-up — or gets caught inside it — is working at the wrong resolution.\n**Post-processing** then filters an enlarged image: leave `gridSnapping = PixelSnapping`, or inject a\n2D renderer feature after post-processing, since a plain `ScriptableRendererFeature` on a URP 2D\nrenderer is **ignored without an error**. **UI text** on a Screen Space – Camera canvas softens with\nthe scene: set the canvas to **Screen Space – Overlay**, the route that holds. The ranked\nalternatives and where canvas and font work goes: `reference\u002Fmotion-and-upscale.md` §2. Confirm\neither fix in a windowed run with the canvas and a volume in the scene — a headless check shows\nneither symptom.\n\n## 8. Micro-stutter is physics, not rendering\n\nA sprite driven by `Rigidbody2D` stutters while everything else is smooth: physics advances on a\nfixed timestep and rendering does not, and snapping makes the sub-pixel error visible. The fix is\n`Rigidbody2D.interpolation = RigidbodyInterpolation2D.Interpolate` on every physics-driven sprite;\na matched fixed timestep and camera follow in `LateUpdate` tighten it —\n`reference\u002Fmotion-and-upscale.md` §3. Confirm it in play mode with a moving rigidbody. The\nmovement code itself is `unity-2d-controller`.\n\n## 9. Migration\n\n**Wrong component for the pipeline** — URP in force, `UnityEngine.U2D.PixelPerfectCamera` on the\ncamera: remove the package and the component, add the URP one, re-enter the settings (booleans do\nnot migrate into enums). `PipelineDetection.HasWrongComponent` finds it. **Deprecated booleans on\nthe right component** still compile, as a **warning, not an error** — so bool-style code compiling\nproves nothing about which component you are on. Read the type, not the property names.\n\n**Old URP namespace** (`UnityEngine.Experimental.Rendering.Universal`), **no 2D renderer under\nURP**, and **HDRP**, which has no Pixel Perfect Camera at all: steps for all five cases, and the\nbool → enum mapping, via `reference\u002Fpipeline-and-migration.md` §3.\n\n## Scope — what this skill does NOT do\n\nSlicing sheets, pivots, rects, 9-slice borders and outlines are `unity-2d-sprites` — this skill\nonly says which pivot values keep a sprite on the grid. Atlas packing, padding, packer mode and\natlas memory are `unity-sprite-atlas`, which rows 1 and 2 of §5 hand off to. Tilemaps, palettes\nand rule tiles are `unity-tilemap`; §5 ends at \"the seam is not the tilemap's fault\". Parallax\nand sorting are `unity-2d-rendering`.\n\nResolving the active render pipeline, URP asset and renderer configuration, Volumes and Render\nGraph passes are `unity-render-urp` — §1 reads the pipeline, it does not set it. The canvas itself\n— render mode, scaler, layout — is `unity-ui-ugui`, and font assets and CJK glyph coverage are\n`unity-game-ui`; §7 only says which canvas mode escapes the upscale. Before\u002Fafter screenshots and\nconnecting to a live Editor at all are `unity-debug`.\n\nArt direction is out of scope in both directions: this skill will not tell you a resolution is\ntoo low for your art, and it does not apply to high-resolution or hand-painted 2D, where point\nfiltering and snapping make smooth art look wrong.\n\n## Reference\n\n- `reference\u002Fapi-and-enums.md` — both components member by member,\n  enums with old-bool equivalents, combinations, `pixelSnapSpacing`.\n- `reference\u002Fsharpness.md` — the import settings table, reference\n  resolutions, the tilemap seam ladder.\n- `reference\u002Fpipeline-and-migration.md` — pipeline reads,\n  assembly names, migration steps.\n- `reference\u002Fmotion-and-upscale.md` — the Cinemachine rule, the\n  upscale's side effects, physics stutter.\n- Code: `PipelineDetection.cs` (resolve the pipeline, pick the\n  type, detect a mismatch), `CameraSetupURP.cs` (enum-style),\n  `CameraSetupBuiltIn.cs` (bool-style, standalone package),\n  `SpriteImportFix.cs` (the four import settings from §2).\n",{"name":5,"description":7},"main","b7459aa49fb881c5abb764223674ec8f397a02b1","skills\u002Funity-2d-pixel-perfect",0,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills","https:\u002F\u002Fgithub.com\u002FtipoLi5890","https:\u002F\u002Ftipoli5890.github.io\u002F","2026-11-10 09:16:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tipoLi5890\u002Funity-dev-skills --skill unity-2d-pixel-perfect",{"tool":38,"command":39},"bunx","bunx skills add tipoLi5890\u002Funity-dev-skills --skill unity-2d-pixel-perfect",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tipoLi5890\u002Funity-dev-skills --skill unity-2d-pixel-perfect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002FSKILL.md",true,[46,52,56,60,64,70,74,78],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Fapi-and-enums.md","REFERENCE","参考文档",8879,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002Freference\u002Fapi-and-enums.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fmotion-and-upscale.md",4340,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002Freference\u002Fmotion-and-upscale.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"reference\u002Fpipeline-and-migration.md",5584,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002Freference\u002Fpipeline-and-migration.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"reference\u002Fsharpness.md",4392,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002Freference\u002Fsharpness.md",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"resources\u002FCameraSetupBuiltIn.cs","OTHER","其他",3889,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002Fresources\u002FCameraSetupBuiltIn.cs",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"resources\u002FCameraSetupURP.cs",4358,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002Fresources\u002FCameraSetupURP.cs",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"resources\u002FPipelineDetection.cs",4739,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002Fresources\u002FPipelineDetection.cs",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"resources\u002FSpriteImportFix.cs",4837,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-2d-pixel-perfect\u002Fresources\u002FSpriteImportFix.cs",[83,90,97,104,111,118],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CMNYXQNW14ST64EYEEZ5V5","unity-web-release","Ship a WebGL\u002FWebGPU build: shrink the download, Brotli server headers, Safari and iPhone memory.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-web-release\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CMNTHD1EA70CCJ2F9FN3HT","unity-vivox","Vivox voice and text chat: channels, positional voice, mute and push-to-talk, mic permission.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-vivox\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7CMNPHPRQZ7K1FES2953DRQ","unity-urp-migration","Migrate a Built-in project to URP, or fix a half-moved one: pink materials, PPv2, old shaders.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-urp-migration\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7CMNJ756DK4V0D50HMAZYQW","unity-ui-ugui","Canvas UI (uGUI): CanvasScaler, RectTransform anchors, Layout Groups, ScrollView, UI built from C#.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-ugui\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7CMNDESZN79EK5FRDXCA2WA","unity-ui-toolkit","UI Toolkit (UXML, USS, UIDocument): flex layout, binding, custom elements, editor windows.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-toolkit\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7CMN8GBV07K0YCY07BJ6A1W","unity-ugs","Unity Gaming Services API: which package, init and sign-in order, Cloud Save, Cloud Code, Remote Config.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ugs\u002FSKILL.md",[],[]]