> For the complete documentation index, see [llms.txt](https://docs.gta.clothing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gta.clothing/basics/essential-knowledge/cloth-analysis-report.md).
# Cloth Analysis Report
Learn about our Information, Warnings and Errors
## Introduction
The **Cloth Analysis Report** in Durty Cloth Tool (DCT) is an essential feature designed to help developers analyze their clothing resources for potential issues, optimizations, and overall quality. The tool automatically generates error, warning, and informational messages to assist users in maintaining high standards of quality and compatibility for their clothing assets.
This documentation will cover:
* **Cloth Analysis Report** overview and purpose
* The **Error List** window and how it works
* Explanation of the different types of messages: **Errors**, **Warnings**, and **Information**
* How these messages are integrated into the tool’s **drawables list**
Durty Cloth Tool Errors, Warnings and Information in Appearance List
## Purpose
The **Cloth Analysis Report** ensures that all clothing resources are thoroughly reviewed and optimized before being finalized and used in the game. This analysis helps identify:
* **Potential Issues**: Such as missing or conflicting data in the drawable models or textures.
* **Performance Optimizations**: Opportunities to reduce texture sizes or fix polygon counts.
* **Warnings**: Areas where improvements are suggested, even if they aren’t critical issues.
This reporting system allows modders, developers and content creators to ensure their clothing resources are not only functional but also optimized for the best possible performance, especially in multiplayer environments where efficiency is key.
## The Error List Window
The **Error List Window** is where users can view and manage all the reported issues and suggestions from the Cloth Analysis. It offers a centralized view of all **Errors**, **Warnings**, and **Information** messages across the current project.
Durty Cloth Tool Error List Window demo
### Key Features of the Error List Window:
* **Type**: Each message is categorized by its severity with clear icons to distinguish between **Errors**, **Warnings**, and **Informational** messages.
* **Filtering**: Users can filter the messages based on type, such as viewing only Errors or only Warnings by clicking on the related type icon in the top section.
* **Sorting:** Easily sort messages by their severity (Level), Code, Description and more
* **Search:** Quickly search thru all messages to find issues of a specific item by using the upper right search input.
* **Grouping:** Appearance items with two or more findings have an expandable header. A single finding stays on its own labeled row.
* **Details**: Each row holds all related details about the issue, often with specific references to the problematic cloth drawable or texture.
* **Jump to Location**: By double clicking you can simply jump to the related item to take further actions.
* **Thumbnails**: Findings can show the related cloth or texture thumbnail, so you recognise the item without opening it.
* **Quick actions**: Use the action beside a finding to open the relevant optimizer, replace a source or companion file, add a texture, or review the related settings. Review and inspection actions help you investigate; they do not automatically change the item.
* **Copy and export**: Copied and exported findings keep the item they belong to.
* **Ignore reviewed findings**: Ignore one finding for an item or texture variation, or ignore that rule for the same target. The choice is saved with the project. Ignored rows are hidden by default and can be revealed and restored from the Error List.
### Understanding groups
An appearance item with two or more findings has a header showing its name, finding count and severity summary. A right-pointing arrow means collapsed; a down-pointing arrow means expanded. Click the header to toggle it. A single finding stays on its own labeled row, and filtered groups show visible/total counts.
Use **Expand all** or **Collapse all** from the Error List actions menu. Changing the search expands matching groups temporarily; clearing it restores your previous expansion choices. Copying or exporting filtered findings includes findings inside collapsed groups.
## Error Types
* :exclamation: **Errors**: These are critical issues that prevent a drawable or resource from functioning properly. Errors often result from missing files, broken links between models and textures, or invalid file formats. Errors **must** be resolved before the cloth resource can be build and used correctly in the game.
* :warning: **Warnings**: Warnings are less severe than errors but indicate potential problems that could lead to suboptimal performance or unintended behavior. For example, a drawable may have an excessively high polygon count, or a texture may not be optimized. While the resource may still function, addressing warnings can improve the quality and performance of your cloth resource.
* :bulb: **Information**: These are general messages that provide useful insights about your resources but don’t require immediate action. For example, a message might inform you that a drawable has an unused material that could be cleaned up. Information helps keep your project organized and clean but does not impact functionality.
## Error List Integration with Drawables List
In addition to the **Error List Window**, DCT provides real-time feedback directly within the **Drawables List** itself. This means that when a drawable (such as a piece of clothing) has an issue, it will be flagged in the drawables list with a corresponding icon to indicate whether it has errors, warnings, or informational messages.
Durty Cloth Tool Errors, Warnings and Information in Appearance List
Click an item’s error, warning or information indicator to filter the Error List to that drawable and its texture variations. Clicking a variation’s indicator shows only that variation’s findings. The scope above the list names the item; choose **Show all items** to return to the full list. Severity controls and search continue to work within that scope.
### Error Reporting in Drawables List
Each item in DCT is monitored for various issues and possible improvements, here are just some examples:
1. **Missing Data**: If a drawable is missing essential elements like textures or models, it will trigger an error.
2. **High Polygon Counts**: DCT warns when a level reaches its configured triangle budget. New projects use 30,000 High, 15,000 Medium and 7,500 Low triangles by default; existing project settings stay unchanged. These are adjustable performance guidelines, not hard game-format limits. The Model Optimizer uses the same budgets in Automatic mode.
3. **Texture Issues**: If a texture is too large or in an incompatible format, this will be flagged as a warning or error.
4. **LOD Mismatch**: If there is an inconsistency in the levels of detail (LOD) between the different levels of the model, it could generate a warning.
5. **Naming Conflicts**: Duplicate names for drawables of the same type or category can result in conflicts. The tool will warn you when multiple items share the same name or identifier.
A **Wasted UV space** finding shows how much of the texture the UV bounds use and how much space the UV optimizer can reclaim after padding and size constraints. **Fix** opens the Texture Optimizer for that drawable. After a crop or island re-pack, the finding clears when there is no further worthwhile saving, even if the finished texture still contains some empty space.
By providing real-time feedback in the **Drawables List**, users can immediately identify where an issue exists and begin fixing it without needing to manually review each drawable. The icons next to each item will indicate its status, allowing users to prioritize their work.
### Clothing compatibility findings
Alongside the size and quality checks above, DCT reports compatibility findings and points to the relevant repair or review tools:
* **Invalid freemode rig**: rendered vertices are checked across every LOD for definite skin weight and bone mapping defects.
* **High heel support to review**: with **Is High Heels** enabled, an incomplete heel-bone signature produces an informational review note by default. Newly imported shoes with the complete signature enable the option automatically, without changing the heel height.
* **Hair without colour support**: hair drawables warn when their recognized materials do not support in-game hair colour rendering.
* **Wasted UV space**: meshes sample only a small part of a large texture. Fix it with the UV crop in [Texture Optimizer](/basics/essential-knowledge/texture-optimizer.md).
* **Missing normal or specular map**: fix it with [Normal & Specular Maps](/basics/good-to-know/normal-and-specular-maps.md).
* **Shop apparel entry budget**: the pack is approaching the shared entry list capacity. See [Game Limits and Crashes](/game-mechanics/game-limits-and-crashes.md).
* **Drawable and prop limits**: each affected item is named with its index and the runtime consequence. Where DCT can repair the project, the finding can move high heels before flat shoes or restore automatic resource splitting after you confirm the change.
{% hint style="info" %}
**Did you know?** You can fine tune and adjust each threshold in the Project Settings window. See [App & Project Settings](/basics/good-to-know/app-and-project-settings.md) for more details.
{% endhint %}
## Error Fixing Workflow
When using the **Error List Window** and **Drawables List**, it’s recommended to follow a simple workflow for addressing issues:
1. **Review Errors First**: Always resolve critical errors first, as they will prevent the project from functioning properly.\
In many cases these can be issues like clothes that miss textures and similar, in such cases read the error carefully and follow given steps to resolve it.
2. **Address Warnings**: Warnings should be resolved next, as they may affect performance or cause issues down the line, particularly in multiplayer environments.\
In many cases using our inbuilt Optimization Feature might help but not be taken as the ultimate solution for everything. See [Optimizing Clothes](/basics/essential-knowledge/optimizing-clothes.md) for more details.
3. **(optional) Handle Information Last**: Informational messages should be addressed at your discretion, particularly if you’re aiming for maximum optimization and cleanliness in your project. **In most cases they require extensive cloth modding knowledge.**
By working in this structured manner, you can ensure that your project is not only functional but also optimized and clean.
## Understanding Quality Advice
Cloth Analysis checks rendered geometry, shader requirements, distance detail levels (LODs), texture dictionaries and mipmaps, and the structure of attached cloth physics files. Polygon totals include every part of each LOD. Missing or barely simplified distance levels can point to useful performance improvements, particularly for detailed ports. These budgets are guidance, not universal GTA V format limits.
A valid freemode rig can use rounded byte weights, rigid attachments or cloth simulation bindings. High heels without the complete heel-bone signature receive an informational visual-review note, not a claim that the shoes are broken. Check the heel height and animations in preview and in game before changing **Is High Heels**.
Tattoo checks distinguish fully transparent artwork from a fully opaque background. Size advice suggests reducing larger textures when their visible detail permits; it does not ask you to enlarge smaller tattoos. Validation settings control the rules and their severity.
Cloth physics findings cover missing companion files and structural inconsistencies. Wind, pins, collisions and motion quality still need the 3D preview and an in-game check. A simulated-vertex budget refers to the physics mesh, not the polygons of the visible garment.
## Handling Duplicate Clothing Automatically
In addition to detecting potential issues and optimizations, Durty Cloth Tool also has an advanced system for identifying and managing duplicate clothing items to maintain a clean and efficient project.
### **Automatic Duplicate Detection**
When adding new clothing to a project, the tool automatically checks for duplicates by comparing:
* File content data
* Assigned gender
* Drawable type
If a duplicate is detected, a prompt will appear, giving the option to either proceed with adding the duplicate or skip it. Users can also select a session-specific setting to **Always Import** or **Always Skip** duplicates during the active session. This choice is reset upon restarting the tool, ensuring full control and flexibility each time the tool is used.
All duplicate handling actions are logged, providing a transparent view of how decisions on duplicates are made and allowing users to review these actions at any time.
### **Project-Wide Duplicate Analysis**
DCT also offers a **Find duplicates...** action under **Project > Project Actions**. It scans the whole project for drawables and texture variations with identical file content and lists every group it finds: the copy that stays and its duplicates, with thumbnails when thumbnails are enabled for the project. Filter the result to one drawable type when reviewing a large project. Every duplicate is ticked for removal; untick what you want to keep, use **Keep this instead** to keep another copy, and use **3D preview** on any entry to compare copies in the 3D preview while the window stays open. By default the same drawable in the other gender and the same texture on another drawable do not count as duplicates, since packs often do that on purpose; two options extend the scan across genders and across drawables. Unique texture variations of a removed drawable move to the kept one, and removal happens only after a confirmation, streamlining the project’s clothing assets for optimal organization and performance.
With these features, DCT ensures users can maintain clean, organized clothing resources and avoid unnecessary redundancies, supporting high standards of quality and project management.
## Summary
The **Cloth Analysis Report** is a powerful tool in the Durty Cloth Tool, offering detailed feedback on the quality and functionality of clothing resources. By leveraging the **Error List Window**, real-time feedback in the **Drawables List**, and a structured approach to resolving issues, developers can ensure their clothing mods are not only functional but also optimized for performance and compatibility.
Understanding and addressing the different levels of **Errors**, **Warnings**, and **Information** will lead to higher-quality results, whether you are working on Singleplayer DLC or multiplayer cloth resources for FiveM.
