> 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/useful-to-know/logs.md).

# Logs

Learn about our Logs

## Introduction

The **Logs Window** in Durty Cloth Tool is a vital feature that provides detailed tracking of all actions taken within a cloth project. It helps you monitor the internal processes, changes, and events during your workflow, offering a comprehensive view of every step made throughout your modding process. The logs are automatically persisted and saved through sessions for each cloth project, ensuring no information is lost between sessions.

<figure><img src="https://2130288373-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRsXe3tqSiAvM8iKYjngE%2Fuploads%2Fgit-blob-23c414f116361bd7141e2fc505470311196d4dd9%2Flogs.png?alt=media" alt="The Project logs pane with 0 Errors, 2 Warnings, 12 Information and 0 Verbose, Follow latest, the log search and Export, listing saves of the test project with the folder shown as a path placeholder."><figcaption><p>Durty Cloth Tool Logs Window example</p></figcaption></figure>

## Accessing the Logs Window

There are two ways to access the **Logs Window** in Durty Cloth Tool:

1. **Top Navigation Menu**:\
   Navigate to **"View > Logs Output"** in the application's top menu (or press **Ctrl+K** and paste `>Logs Output`) to open the logs window at any time.
2. **Bottom Log Preview Click**:\
   The most recent log entry is always displayed at the bottom of the application. Clicking on this entry will also bring up the complete **Logs Window**.

When a build fails, the Build window offers **Open project log**. When adding from a built resource, from another DCT project, or a tattoo or overlay fails, the message offers **Open log** beside **OK**.

## Logs Window Overview

When opened, the **Logs Window** displays a **scrollable list** of all log entries, providing insights into every action taken in the project. This window includes:

* **Log Entries**:\
  Each log entry contains detailed information about an action or event that occurred in the project. These logs help you track everything from changes made to the project, file operations, optimizations, and other significant actions.
* **Scroll Functionality**:\
  The window is fully scrollable, allowing you to browse through extensive logs efficiently. This feature is particularly useful when working on large projects where many actions are logged over time.
* **Persisted Logs**:\
  Log entries are persisted across project sessions, meaning that if you close and reopen the project later, the logs from the previous sessions will still be available for review. This persistence ensures a complete history of all modifications and actions taken in the project.
* **Related Items**:\
  When an entry refers to an item or texture that still exists, click its linked name, double-click the entry, press **Enter**, or use **Go to** to select it in the project. Entries whose target was removed remain available as history but cannot be opened.

## Types of Information Logged

The **Logs Window** provides detailed insights into various types of actions and events. Some of the key log categories include:

* **File Operations**:\
  Every time a file is added, replaced, renamed, or deleted within the project, a corresponding log entry is generated. This includes actions on both cloth drawable models and textures.
* **Project Changes**:\
  All changes made to the project, such as modifications to appearance items, texture optimizations, or configuration adjustments, are logged.
* **Optimization & Build**:\
  When optimizing cloth resources or building projects using the dynamic config builders, logs are generated to document the processes and any outcomes or errors.
* **Warnings & Errors**:\
  Any warnings or errors encountered during project handling will be logged, helping you identify potential issues or areas that require attention.
* **Project Sync**:\
  Uploads, commits, changes that arrived from other people, finished downloads and sync problems of a synced project. See below.

## Filtering and exporting

* **Severity filters** narrow the view to the levels you care about.
* **Follow latest** starts on when you open Project Logs, with the newest entry in view. Scroll away or begin a search to pause it while you read.
* **Export** writes the visible entries as TXT or CSV.
* **Support log export** writes a complete log in **English**, whatever interface language you use, so it is readable by whoever helps you.

{% hint style="info" %}
Project Logs and the status bar show outcomes. More detailed diagnostic entries are kept at **Debug** level for support.
{% endhint %}

Entries that relate to a specific item can jump back to that drawable or texture.

## Project sync entries

When the project syncs with DCT Cloud or Git, Logs record what happened:

* each save that was uploaded to the cloud or committed and pushed to Git, with a short summary of what changed
* changes that arrived from other people, with who made them and what changed, or a note that your own changes from another PC arrived
* each clothing item someone else updated, linked so you can jump to it
* when all clothing of a newly downloaded cloud project has arrived
* sync problems in plain words, such as a needed sign-in or changes that need your review

The **Show** button of the **Changes arrived** notice opens Logs when several items changed. See [Project Sync](https://docs.gta.clothing/share-and-sync/project-sync.md).

<figure><img src="https://2130288373-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRsXe3tqSiAvM8iKYjngE%2Fuploads%2Fgit-blob-452e271882fb4aea048bc2147e5fb0333d5eb5c5%2Fproject-logs-sync-entries.png?alt=media" alt="Project Logs searched for the test project Forge Studio Test, with four Information entries: All clothing in Forge Studio Test has downloaded., Uploaded Forge Studio Test to the cloud: Female 2 Female 35 blouse changed, the collaborator updated Forge Studio Test: 2 items changed, and the collaborator updated Female 0 Female 6 top in Forge Studio Test with the item&#x27;s picture and a link to it. The collaborator&#x27;s name is blurred."><figcaption><p>Sync entries of a test project: the finished download, an upload, and changes that arrived from a collaborator. The entry for a single item links to it.</p></figcaption></figure>

## Send feedback

**Help > Send feedback** (or press **Ctrl+K** and paste `>Send feedback`), **Send feedback** beside the version at the top of the editor, or **Send feedback** at the bottom left of Home, sends a message straight to the Durty Cloth Tool developers at any time: what works, what does not, or what you are missing. It is free on every license. See [Usage Data & Feedback](https://docs.gta.clothing/basics/good-to-know/usage-data-and-feedback.md#where-feedback-goes) for what happens to it.

1. Write your **Message**, up to 4,000 characters.
2. If you would like an answer, enter your e-mail address or Discord name under **Contact (optional)**. When you are signed in, your Discord name is already there; change or clear it as you like. It is sent as shown.
3. Tick **Attach my recent log** to add up to the last 200 lines of the Project Logs from this session. It is off by default. The window shows the attached text below it exactly as it will be sent, so you can read it first.
4. Choose **Send feedback**. Without an internet connection, the feedback is kept on this PC and sent later.

What is sent:

* your message;
* the contact, only if you entered one;
* the log, only if you ticked **Attach my recent log**, in English;
* the same anonymous technical details an automatic error report carries, such as the Durty Cloth Tool version and update channel, basic facts about Windows and the computer without its name, and a few counts and settings of the open project, such as how many items it holds and its build target.

Before sending, the folder names in file paths, your Windows user name, the name of this PC, e-mail addresses other than your contact, network addresses, IDs and keys are removed from your message and from the log. Only a file name such as `model.ydd` stays, so the developers can tell which file a line is about. When this changes your message, the text that is sent appears under it. Detailed license checks never go into the attached log, and no project files are sent.

The same applies to what you type in **Add details…** when Durty Cloth Tool reports an error, except that every e-mail address is removed there, because it has no contact field.

{% hint style="info" %}
Feedback is sent only while **Send anonymous error reports automatically** is on in **Options > Privacy** (or press **Ctrl+K** and paste `@Send anonymous`). While it is off, Durty Cloth Tool sends nothing, feedback included: the window says so and offers **Open Options**. If error reports were off when Durty Cloth Tool started, restart it after turning them on, then send. After several messages in one session, the window asks you to share anything else on our [Discord](https://discord.plebmasters.de/).
{% endhint %}

<figure><img src="https://2130288373-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRsXe3tqSiAvM8iKYjngE%2Fuploads%2Fgit-blob-2771d2e151a15673768b45bda942a28700af87b0%2Fsend-feedback.png?alt=media" alt="The Send feedback window with a short message about the texture list, the Discord name forge_studio_test under Contact (optional), and Attach my recent log ticked. Below it, three attached log lines in which the project folder reads <path>. The Send feedback and Close buttons are at the bottom."><figcaption><p>Send feedback, ready to send: the attached log shows exactly what goes with the message, with the folder path already removed.</p></figcaption></figure>

## Using the Logs to Troubleshoot and Understand Project Actions

The logs can serve as a useful tool for troubleshooting and understanding what is happening behind the scenes during your work on a project. You can use the logs to:

* **Review Past Actions**:\
  Go back through previous sessions and see what actions were taken, such as file operations or optimizations, allowing you to track and understand changes made to the project over time.
* **Identify Errors or Issues**:\
  Logs provide detailed information on any warnings or errors that may occur during your workflow. This can help pinpoint the cause of a problem and guide you toward a solution.
* **Audit Changes**:\
  The logs serve as a complete audit trail of the project. Whether working alone or as part of a team, the logs can help keep track of what has been done, what needs to be revised, and the order in which actions were taken.

## Summary

The **Logs Window** in Durty Cloth Tool is a powerful feature for monitoring all actions taken in your cloth projects. Accessible from the top navigation menu or by clicking the most recent log entry at the bottom of the app, this window provides a comprehensive, persistent record of every change or event. By offering detailed insight into file operations, project changes, optimizations, and more, the **Logs Window** allows users to track progress, troubleshoot issues, and better understand their projects.
