PLAYTEX Guides for Texture Tools, PBR Maps, HDRI, and Game Material Workflows

Choose the guide by asset state

If you have only an idea, start with AI Texture Generator. It explains presets, game type, style, pattern scale, seamless output, model choice, and when to generate matching material variants.

If you already have a photo, scan, artwork crop, or AI image, start with Image to Texture. It explains Region Select, Surface Extraction, crop control, surface type, lighting removal, preserve-wear behavior, seamless strength, frequency, seed lock, and tile preview.

If the image itself needs repair before it becomes a texture source, use Image Editor. It covers transform, background matte, brush/object/color-key cleanup, color and tone, creative effects, region selection, feathering, region lock, and save/download handoff.

If the base texture is ready and needs real material behavior, use the web-based PBR mapping tool. It covers image, procedural, and hybrid source modes; material intent; procedural surfaces and presets; pattern, art-direction, color, wear, simple settings, advanced channel controls, quality review, and engine export.

Use settings in the right order

The fastest path through PLAYTEX is usually source selection first, cleanup second, material conversion third, export or project handoff fourth. Skipping the order creates avoidable problems: noisy sources produce noisy maps, unchecked seams show up in repeated surfaces, and unreviewed roughness or metallic channels break once lighting changes.

In every guide, the settings reference is written as a decision aid. Use it when you are about to touch a control and need to know what it changes, when to adjust it, and what mistake it can create if pushed too far.

Treat visual review as part of the workflow. AI textures need tile inspection. Image-to-texture outputs need repeated preview and seam metrics. PBR materials need per-channel inspection, not only beauty preview. HDRIs need 360 seam and orientation checks. Asset Binder needs slot-level review before bindings are saved.

Where each product fits

AI Texture Generator is the ideation surface. Its most important controls are material preset, game type or art target, visual style, seamless toggle, pattern scale, prompt, palette, model, and matching-set generation.

Image to Texture is the source conversion surface. Region Select gives manual crop control. Surface Extraction gives automated surface interpretation with auto-detect and explicit surface categories. The Seamless Creator workspace adds local repair tools such as mask, gradient, histogram, blend, graphcut, overlays, brush modes, and 3x3 or 5x5 tile preview.

PBR Map Generator is the technical material surface and PBR mapping tool for game materials. It turns a viable texture or procedural source into albedo, normal, roughness, metallic, ambient occlusion, height, and emission outputs. The advanced rail exposes the actual channel math users care about: normal format and strength, roughness response, metallic source channel, emission mode, height parallax safety, AO behavior, seam-aware processing, map consistency, and power-of-two handling.

HDRI Sphere Generator is the lighting environment surface. It uses text-to-HDRI or image-to-HDRI, environment option, environment style, time of day, cloud density, sun position, stars, resolution, model, preserve-original-look, seam fix, yaw rotation, and HDR/PNG export paths.

When the workflow becomes team work

Library saves are the first handoff point. Save outputs when they have passed the relevant review step: tile preview for seamless textures, channel review for map stacks, and visual or orientation review for HDRIs.

Projects become useful when a material belongs to a workspace instead of a single session. Project context keeps assets, versions, activity, and collaboration closer to the actual production decision.

Asset Binder is for mesh-level handoff. Import or select a mesh, parse slots, bind specific material versions, inspect slot focus, compare states, use Show Me Why when a slot result needs explanation, and save only after the binding state is coherent.

Builder Trainer supports onboarding and UI explanation. Upload a clear screenshot, let the analyzer detect controls, review hotspots, then use Build Helper when the question is broader than one visible control.

Use the guide cards as the product manual for the current toolset

Each guide explains the controls users actually touch, the order to use them, and the review step that should happen before a result moves downstream.

• Start with AI Texture or Image to Texture when the base surface does not exist yet.
• Move to PBR Map Generator only after the tile or source image is clean enough to review.
• Use Library, Projects, HDRI, Asset Binder, and Builder Trainer when the asset needs context beyond one generated file.

Engine-focused pages are also available for Unity Texture Generator and Unreal Texture Generator workflows.