rTexPacker Tutorial: Create Optimized Texture Atlases in Minutes
Texture atlases reduce draw calls, save memory, and speed up rendering. This tutorial shows how to use rTexPacker to create optimized texture atlases quickly, with practical tips for best results.
What is rTexPacker?
rTexPacker is a texture atlas packing tool that automatically arranges images into a single atlas, generating metadata for coordinates and trimming transparent pixels. It’s aimed at game developers and graphics programmers who need fast, efficient atlas creation.
Prerequisites
- rTexPacker installed (binary or integrated into your build pipeline)
- A folder of source sprites or images (PNG preferred with alpha)
- Basic familiarity with texture atlases and your target engine’s sprite/UV handling
Step 1 — Prepare source images
- Consistent scale: Ensure sprites intended to be used together share the same scale and pixel density.
- Trim whitespace: Remove unnecessary transparent padding unless required for effects.
- Naming: Use descriptive filenames; include suffixes for states/variants (e.g., player_run01.png).
Step 2 — Choose settings for optimal packing
Use these default settings for a balance of speed and compactness:
- Max atlas size: 2048×2048 (adjust for target hardware)
- Padding: 2–4 px between sprites to prevent bleeding during texture filtering
- Trim: Enabled — removes fully transparent borders to save space
- Rotation: Allowed (90°) — increases packing efficiency but requires engine support for rotated UVs
- Algorithm: Guillotine or MaxRects (MaxRects usually yields tighter packs)
Command-line example (adjust flags to your build):
Code
rtexpacker -i ./sprites -o ./output/atlas.png -m ./output/atlas.json –max-size 2048 –padding 2 –trim –allow-rotate –alg maxrects
Step 3 — Run rTexPacker
- Point rTexPacker at your sprite folder and choose output paths for atlas images and metadata.
- Run with the chosen settings. For large sets, run in a background job or CI step.
- Inspect console output for warnings (e.g., images exceeding max size).
Step 4 — Verify atlas and metadata
- Open the atlas image to visually check packing and spacing.
- Inspect the metadata (JSON, XML, or custom format) for sprite coordinates, sizes, rotation flags, and trimming offsets.
- Confirm your engine’s importer reads rotation and trim offsets correctly; if not, disable rotation or apply trimming offsets at import.
Step 5 — Import into your engine
- Unity: Use a custom importer or runtime loader that reads rTexPacker metadata and creates Sprite objects with correct UVs and pivot/trim adjustments.
- Godot: Use an importer script to map regions to AtlasTexture or AtlasSprites.
- Custom engines: Parse the JSON/XML and adjust UVs, sprite bounds, and pivot based on trim/rotation info.
Example JSON fields to map:
- name
- x, y, width, height
- rotated (boolean)
- trimmed (boolean)
- sourceWidth, sourceHeight
- spriteSourceX, spriteSourceY (trim offsets)
Optimization tips
- Group sprites by usage frequency or shader/material to minimize wasted space and reduce texture switches.
- Use power-of-two atlas sizes for GPU compatibility and mipmapping.
- For animation frames, keep consistent frame sizes where possible to avoid complex trimming corrections.
- Consider multiple atlases for wildly different resolution assets (UI vs. large world textures).
Troubleshooting
- Artifacts at edges: increase padding or use clamp-to-edge sampling.
- Sprites missing/overlapping: ensure max atlas size is large enough or split into multiple atlases.
- Rotation mismatch: disable rotation if your import pipeline cannot handle rotated UVs.
Quick workflow (summary)
- Prepare and trim sprites.
- Run rTexPacker with MaxRects, trim enabled, padding 2–4 px, optional rotation.
- Inspect atlas and metadata.
- Import into engine with a parser that handles trim and rotation.
- Test in-game and adjust settings if needed.
Using rTexPacker you can turn a folder of images into an optimized texture atlas in minutes—saving memory, draw calls, and development time.
Leave a Reply