> For the complete documentation index, see [llms.txt](https://docs.sollumz.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sollumz.org/documentation/texture-dictionaries.md).

# Texture Dictionaries (.ytd)

Texture dictionaries contain textures that can be used by drawables or fragments. Compared to embedded textures, texture dictionaries allows you to share textures between multiple models and reduce asset file sizes.

The `Sollumz Tools > Texture Dictionaries` panel in the sidebar lets you create dictionaries and add or remove textures manually, or add *source* mesh objects that automatically gather all images used by their Sollumz shaders, with a per-image toggle to control what gets included.

<figure><img src="/files/U2QZlCas002RRcUjfh2Y" alt="" width="521"><figcaption><p>Texture Dictionaries panel</p></figcaption></figure>

#### Sources

Sources let you reference Objects or Collections whose Sollumz shaders are scanned for textures, keeping the texture dictionary in sync with the textures actually used by your models.

The Images list shows every texture gathered from each source. Use the checkbox to control which of them are included in the texture dictionary. By default, embedded textures are excluded and non-embedded textures are included.

<figure><img src="/files/7haeqpu9Aj5w6Tf1wIhE" alt="" width="375"><figcaption><p>Texture dictionary sources list</p></figcaption></figure>

#### HD Texture Dictionaries

HD texture dictionaries (+hi) can also be managed using Sollumz. Next to each textures there is an "HD" toggle. On export, textures marked as HD are exported to a +hi.ytd at full resolution, while the base .ytd contains half-resolution versions. For this, it is necessary for the textures to have mipmaps.

This also works with embedded textures on drawables, fragments, and drawable dictionaries: when HD textures are present, a +hidr.ytd/+hifr.ytd/+hidd.ytd is exported alongside the main asset.

<figure><img src="/files/zoiTQB07lhK9zVtrmXpi" alt="" width="563"><figcaption><p>HD embedded textures</p></figcaption></figure>

{% hint style="info" %}
Remember, HD texture dictionaries must be defined in your `_manifest.ymf`, under `HDTxdBindingArray`. For example:

{% code lineNumbers="true" expandable="true" %}

```xml
<?xml version="1.0" encoding="UTF-8"?>
<CPackFileMetaData>
 <MapDataGroups itemType="CMapDataGroup" />
 <HDTxdBindingArray itemType="CHDTxdAssetBinding">
  <Item>
   <assetType>AT_DRB</assetType>
   <targetAsset>prop_bbq_2</targetAsset>
   <HDTxd>prop_bbq_2+hidr</HDTxd>
  </Item>
  <Item>
   <assetType>AT_FRG</assetType>
   <targetAsset>prop_flamingo</targetAsset>
   <HDTxd>prop_flamingo+hifr</HDTxd>
  </Item>
  <Item>
   <assetType>AT_TXD</assetType>
   <targetAsset>prop_mower</targetAsset>
   <HDTxd>prop_mower+hi</HDTxd>
  </Item>
 </HDTxdBindingArray>
 <imapDependencies itemType="CImapDependency" />
 <imapDependencies_2 itemType="CImapDependencies" />
 <itypDependencies_2 itemType="CItypDependencies" />
 <Interiors itemType="CInteriorBoundsFiles" />
</CPackFileMetaData>
```

{% endcode %}
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sollumz.org/documentation/texture-dictionaries.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.