Documentation

Sidebar

The sidebar contains navigation buttons for the five main sections:

Below the main nav buttons, the sidebar shows open tabs:

• Validation tabs — one per active validation session. The icon reflects the session status (pass, fail, warning, or idle). Click to switch between them; click the X to close.
• Create tabs — one per active submission session. Click to switch; click X to close.

Content Area

The content area renders the active view. In the Validate view, the layout splits into:

• Config panel (left, fixed 72px) — preset selector, asset name input, folder picker, and run button.
• Results / Viewport area (right, resizable) — validation report or 3D/2D viewer.
• 3D/Texture sidebar (optional, resizable) — drag the divider between the results and the sidebar to resize. Default width is 40% of the content area (min 20%, max 80%).

Projects

A Project is a named container that groups related Presets together. For example, you might have a “Characters” project holding presets for Hero, NPC, and Creature asset types.

• Projects are sorted by creation date by default.
• You can drag to reorder them in the library.
• Each project can be exported as a .json file and shared with teammates.
• Projects can be imported from a .json file. When importing a preset file, you choose whether to add it to an existing project or keep it as a standalone preset.

Presets

A Preset defines the validation rules for a specific asset type. It specifies:

• The expected root folder name (supports template variables like {AssetName}).
• The expected folder structure (sub-folders, with optional required/optional flags).
• The expected files inside each folder (name patterns, types, and technical constraints).

Presets can exist inside a Project or as standalone presets (not grouped in any project).

• Click a preset card to open a new Validation tab for that preset.
• Presets can be exported as individual .json files.
• Presets can be marked as favorites (star icon on hover) for quick access.

Custom Tags

Custom Tags are reusable, named variables you define once and reference across any preset. They let you express variability in filenames and folder structures — for example, a {Part} tag representing different body parts of a character.

There are three check types:

Custom Tags are managed in Settings > Custom Tags.

Template Variables

Template variables are placeholders used in preset folder paths and file name patterns. They are resolved at validation or submission time.

See the full Template Variables Reference for details.

Creating a Validation Tab

1. Navigate to Validate (the FT1F icon in the sidebar). This opens the Presets & Projects library.
2. Click a preset card inside a project, or click a standalone preset. A new validation tab opens and you are taken to it automatically.
3. Each tab is fully isolated — you can run different presets or different folders simultaneously in separate tabs.

Running Validation

The left config panel contains:

Once both fields are filled, click Run Validation (or press Enter while the asset name input is focused). A spinner shows while the scan runs.

Clicking Re-run after results are shown repeats the validation against the same folder.

Reading the Report

The report is organized into sections, each representing a category of checks:

• Naming — file and folder name convention checks.
• Folder Structure — expected folders present/missing.
• Textures — resolution, power-of-two, required suffixes.
• Meshes — polycount limits, expected scale and rotation.

Each section has an overall status badge:

Each item within a section shows:

• A label — the name of the specific check.
• A status indicator — colored dot (green/yellow/red/blue).
• A message — human-readable explanation of the result.
• Optional details — extended technical information.
• Optional fix suggestion — if a file or folder has a naming issue, a suggested rename (oldPath → newPath) is shown.

3D Viewport

When a validation report is available, you can load a 3D model from the scan results into the built-in viewer.

Display modes:

Additional controls:

• Materials panel — toggle individual material visibility. A legend lists all materials in the loaded model.
• Pivot point — toggle display of the model's pivot/origin point.
• UV channel selector — switch between UV channels when multiple are present.
• Grid Y position — adjust the ground plane height for accurate ground-contact visualization.

Supported model formats: FBX, GLTF, GLB, OBJ, USD.

Texture Viewer

Toggle the 2D Viewer button in the sidebar (or click a texture entry in the validation report) to open the texture sidebar. It displays the selected texture file as a 2D image. Textures are auto-mapped from the scan results by filename.

Picking a Preset

The Create section opens to a preset picker — the same library layout as the Validate section. Click a preset card to start a submission session for that preset.

• Use Import, New Preset, and New Project buttons at the top to manage presets without leaving the Create section.
• To return to the picker from an active session, click ← All Presets in the left config panel.

Tag Values

When a preset references Custom Tags, the Tag Values panel appears in the config panel. For each tag referenced in the preset, you provide the actual values to use.

For example, if the preset has a {Part} tag:

1. Type a value (e.g., Head) in the input and press Enter or click Add.
2. The value appears as a chip. Add as many values as needed.
3. To remove a value, click the X on its chip.

The file slots panel on the right automatically expands to show one slot for every combination of tag values (cartesian product). For instance, if {Part} has values [Head, Torso] and {LOD} has values [LOD0, LOD1], the result is 4 file slots.

File Slots

The File Slots panel (right side) shows every expected file defined by the preset, grouped by folder.

Each row (slot) represents one expected file and shows:

Auto-Detection: When you set a destination folder, FT1F automatically scans it and matches existing files to slots by filename (case-insensitive). Auto-detected files are marked accordingly. Re-click Re-check in the panel header to rescan at any time.

The header also shows a summary: X assigned · X pending · X/Y required.

Submitting Files

Configure the destination in the config panel:

Click Submit to start the operation. Progress is shown with a spinner. After completion:

• Success — a confirmation message appears with an optional Show in Folder button to open the destination in your system file explorer.
• Errors — a list of files that failed to copy or delete is shown. Partial successes are reported; no files are silently skipped.

General Settings

Root-Level Files

Defines files expected directly in the root folder (not inside any subfolder). Click Add File to add a file rule. Each rule is configured in the File Rules editor.

Folder Rules

The folder list defines the expected sub-folder structure inside the root. Each folder rule has:

• Click Add Folder to append a new folder rule.
• Drag the grip handle to reorder folders.
• Click the folder row to expand/collapse its file list.
• Click Delete (trash icon) to remove a folder and all its file rules.

File Rules

Each file rule defines one expected file (or a pattern matching a group of files):

Click the expand toggle on a file rule to access its constraints.

Constraints

Constraints are optional technical validation rules applied to a matched file.

General

License

Shows your current license status:

• License key — displayed in masked format (****-XXXX).
• Tier — your license tier (indie, pro, or studio).
• Deactivate — removes the license from this device, freeing the activation for use elsewhere. The app restarts and shows the license gate again.

Custom Tags

Lists all defined Custom Tags with:

• Tag name, check type, and description.
• Allowed values (for Enumerated tags) — visible on hover.
• Edit button to open the Custom Tag Editor.
• Delete button (two-step confirmation).

App Info

Displays the application version number and build date.

Structure Validation

Structure validation checks whether the scanned folder matches the hierarchy and naming patterns defined in the preset.

How filename matching works: Filenames are tokenized by splitting on _ and . characters. Each token in the filename is compared against the corresponding token in the preset pattern.

Example: SM_HeroCharacter_LOD0.fbx — Tokens: SM, HeroCharacter, LOD0, fbx

The pattern SM_{AssetName}_{LOD}.{ext} is compiled into a schema that matches those tokens positionally.

Rules:

• Static tokens must match exactly (case-sensitive by default).
• Variable tokens ({AssetName}, {CustomTag}, etc.) match the value provided or any value (for wildcards).
• Wildcards (*) match any single token.
• Required folders: If a required folder is absent, the section item fails.
• Required files: If a required file is absent (no file in the folder matches the pattern), the section item fails.
• Extra files: Files present in the folder but not matching any rule are flagged as informational or warnings depending on preset settings.

Fix suggestions: When a file's name is close to a valid pattern (measured by Levenshtein edit distance), the validator proposes a corrected filename.

Content Validation

Content validation reads the actual file data to check technical properties.

Validation Report

After validation completes, a ValidationReport is returned containing:

Each ValidationSection contains:

Each ValidationItem contains:

Activation

1. Launch the app. The license gate appears.
2. Enter your key (XXXX-XXXX-XXXX-XXXX) and click Activate.
3. On success, the app loads. Your license is saved encrypted to disk.

Validation

Each time the app starts, your stored license is validated silently. If validation fails (e.g., the key was revoked), the license gate reappears.

Deactivation

Go to Settings > License and click Deactivate. This removes the license from your device and frees the activation slot so you can use the key on another machine. The app restarts immediately after deactivation.

License Tiers

Error Messages