When a mod does not draw right

Most problems end at the first or second check of their symptom. Find yours, and work down its list:

You see	Go to
The overlay does not open in game	The overlay does not open
No trace of the mod	The mod does not show at all
The mod broke after a game update	It worked before a game update
Some parts are the game's own	Part of the mod shows as the game's own
Wrong colours, plain or missing textures	Wrong or missing textures
A saved change does not show	A change to a description does not show
Flicker, stretching, parts vanishing	Parts flicker, stretch or vanish
A mod's key does nothing	A key does nothing
A crash or a hang	The game crashes or hangs

Where	What it tells you
Timbre's Health	Each mod Timbre could not describe, make native or draw, under its cause, such as Files missing or Made by a newer Overtone, with what to do.
The overlay's Wardrobe (Home in game)	Every mod Overtone loaded, by character, on or off. A green dot means it is on screen.
The overlay's Tools → Report	Whether mods are drawing at all, from a few seconds after the game starts.
Timbre's In game panel (press In game or On screen, where Play is, while the game runs)	What is on screen, and each enabled mod that is Not on screen, Drawn as the game's or Passed over for another.
Timbre's Settings → Help	How the last time you played went: The last run went fine, The last run had complaints or Something failed last time you played.
The log	%LOCALAPPDATA%\Overtone\wuwa\overtone.log; paste the path into Explorer. Each game start adds a run beginning === run started. Search it for the mod's name: no mention means Overtone never loaded it.

Is it the mod or Overtone? If you have the XXMI Launcher, install the mod's archive into XXMI's own Mods folder (not your Overtone library) and look at it there. A mod that looks wrong in XXMI too is broken: tell its author.

The overlay's key (Home unless you changed it) opens nothing, so Overtone is not running.

1. The game must run on DirectX 12. If the log's last run says the game was started on DirectX 11, set the game's launcher, or the XXMI Launcher, to DirectX 12.
2. In Timbre, Settings → Play must say Overtone is installed. If not, press Play once.
3. If the log's last run holds a swap chain was made on a device that is not DirectX 12, the game drew with DirectX 11 even though its launcher says DirectX 12. Start it with Play in Timbre instead, which asks for DirectX 12, and not from the game's own launcher.
4. If the log's last run holds no DirectX 12 device had been made through Overtone and a minute of play passed, the game may have loaded Overtone's file but draw through another one. In Timbre, open Settings → Help, press Save beside Save diagnostics, and send the file to whoever helps you: it names the program and each DirectX file it loaded.

1. Mods on? F8 turns every mod off and on.
2. Ray tracing off? With ray tracing on, reflections, ray-traced shadows and far-away characters show the game's outfit. If no mod draws at all, Tools → Report says Ray tracing is on: turn ray tracing off in the game's graphics settings, and start the game again.
3. Is the mod in the Wardrobe?
   • It says No described mods in the library: Timbre describes a mod when it adds it. Add your mods through Timbre (Add your mods), or open Health and press Describe under New mods.
   • Listed but off: turn it on with its switch, there or in Timbre.
   • Not listed: Timbre has not described it yet. Open Health and press Describe under New mods; the game shows it a moment later, or at F10.
   • Health lists it under Files missing or Can't read its files: install it again through Timbre. Under Made by a newer Overtone, a newer Timbre described it: update Timbre, then press Play. Under Not moved to this version, an update could not bring it along: close any other Overtone tool, then press Try again.
   • Marked Not read: Timbre and Overtone in the game are of different versions. The notice above the list says which to update.
   • Health lists it under Draws nothing, naming a file that ends in .INI: rename the file so it ends in .ini, in lower case. The game reads no other spelling, with Overtone or without it.
   • Not listed, and it sits in a folder another mod manager made (IMM_TEMP_ and a number, IMM_INI_BACKUP, or a restore point named RESTORE- and a date): those folders are ignored. Add the mod again in Timbre from its download. Health → Tidy up → Leftover files offers to send their files to the Recycle Bin, under Other managers' files.
4. Is it on screen? Listed, but never with a green dot:
   • A mod for a skin draws only while the character wears that skin.
   • Of two mods for the same outfit, only one draws. Timbre's In game panel marks the other Passed over for the one drawn, and the log says <mod> is passed over for <other>. Turn one off, or mix them.
   • Tools → Report says No mod matched: after a game update, see the next section.
5. Still nothing? Search the log for the mod's name. A line ending in not drawn says why.

An update can change the character's model so a mod no longer fits it, and the mod draws nothing. Overtone cannot repair this yet. The log may say on screen and never drawn: and the mod's mesh.

Install the author's updated version through Timbre (Update a mod).

A file of the mod is missing. Timbre's In game panel marks the mod Drawn as the game's, and the log says mesh <name> claims nothing, and the game draws its own: <file> cannot be read. Install the mod again through Timbre.

1. Replace textures must be on (the default), in Timbre's Settings → Developer or the overlay's Tools → Debug.
2. Textures that start blurred and sharpen are still loading.
3. Some textures get their role, the job they do (colour, bumps), only the first time the mod is played. If one is still wrong, open the mod in Timbre (In game → Model), click a part's colour swatch, and give each texture under Swapped here, no role yet a role. Use, with the number of suggestions, takes Timbre's guesses. A texture in the slot its ini names (ps-t3) that has no role yet is listed under On this part, and pointing at it says Drawn in game, no role yet · ps-t3.
4. A tattoo or lace part shows as a solid panel: Cut parts by their masks must be on (the default), in the same place.
5. Glow maps are not drawn yet, so glowing parts look plain.

1. Reload when files change must be on, as it is unless you turned it off (Play with Overtone); otherwise press F10 after each save.
2. A piece's material, a choice's wear table or a rule covers what [part.<n>] says (Which texture wins).
3. Search the log for the mod's name. line <n>: ...; it is passed over names a line Overtone ignored, such as a misspelt role or a part that names no mesh; would not read: says why the whole file was refused.

Check the mod in XXMI first (see Where to look). Each setting below is on by default: under Look in the overlay's Settings or Timbre's Settings → In game, and See-through parts under Timbre's Settings → Developer or the overlay's Tools → Debug.

You see	Check
The mod turns into the game's model from far away	Keep mods at a distance is on
A see-through part, such as sheer cloth, is missing	See-through parts is on
The character fades out when the camera is close	That is the game. F7 stops it, but may show what the game hides on purpose.
A few vertices stretch for one frame, a clone takes another's pose, or the face does not move	Send a report (below)

1. A mod's keys work only while it is on screen, with a green dot in the Wardrobe.
2. While the overlay is open, it keeps the keys it uses itself: arrows, Enter, Space, Esc, Tab, PgUp, PgDn, Delete, Q, E and /, any key with Ctrl, and every key while you type in a search box.
3. Two mods on screen with the same key: mods one character wears, such as an outfit, a face and her weapon, all take the press, as in WWMI. Between two characters on screen at once, such as in the character menu, it goes to the one drawn most, and does nothing where they are drawn alike.
4. Use the Wardrobe instead: its arrows step a switch and Wear puts on a look, without any key.
5. To change a mod's key, open the mod in Timbre and click the key in its Variants list. The game uses this marks a key the game already needs.
6. Still nothing: report it. The log says what each press moved, or why it moved nothing.

1. Before starting the game again, report it. The report file holds the log, any crash report, your settings and your mod list.
2. Press F8 to turn mods off. If the crash stops, press F8 again, turn your newest mods off in Timbre, and turn them back on one at a time to find the one.
3. If it crashes at start, under Settings → Play try Skip the game's launcher, and switch off ReShade or any other tool listed there.

1. In Timbre, press Report a problem, the speech bubble near the foot of the left bar. When the game closes after a problem, Timbre also offers Report it in a banner, which opens the page with Game crashed picked.
2. Pick what went wrong, from Game crashed, Mod looks wrong, Timbre misbehaves or Something else, and say what happened.
3. Under Which mod, tick the mods from your last session that are involved. Overtone notes each mod the first time it shows in a game session, so the tiles are what was on screen.
4. Press 4 attachments · 3 MB (the count and size are your own) to see what the report carries. Logs and Your setup always go, and pressing one shows its files. Switch Hang dump on only if the game froze, as it may hold your user name.
5. Press Send report. Timbre saves the report file beside its logs, shows it in its folder, and opens GitHub with your note filled in. You need a free GitHub account.
6. Drag the file onto the page on GitHub, then submit the issue.

Your report stays on the page under its day, marked Waiting for you until its issue is on GitHub. Its Add the file on GitHub button opens the page and shows the file again. What you write is kept until you send it.

Timbre then follows each report on GitHub while the page is open, at most every ten minutes, without signing in:

The card says	What it means	What you can do
Waiting for you	No issue holds your report yet.	Add the file on GitHub and submit it.
On GitHub	Your issue is open, with how many others said they have it.	Nothing: it is in the queue.
Fixed	A release fixes it, and you don't have that release yet.	Update Timbre.
You have the fix	You have every release that fixes it.	If it still happens, press Still happening.
Closed, Not planned or Duplicate	GitHub closed it without a release naming it.	Still happening opens the issue to say so.

Open a card to see its steps, or press Remove to take it off the page with its file. Known problems opens the issues others have already reported.

Without Timbre, attach overtone.log, and overtone-native-crash.txt or an overtone-hang- dump if there is one, from %LOCALAPPDATA%\Overtone\wuwa. Copy them before starting the game again.

• Play with Overtone: every key and setting named here.
• Coming from WWMI: what works differently from WWMI.
• Add your mods: add a mod again, or its update.

A mesh here is one model of a mod; sheets are its textures; a palette is the bones a mesh draws with.

• Tools → Report → Mods on screen has an entry per mesh of each mod. waiting means its files are still loading. refused or no palette with no drawn count means Overtone found the mod and gave its draws back to the game: send a report.
• No sheets placed count under a mesh with Replace textures on means the description gives those parts no role.
• The log's line per mesh, sheets N placed (N no-role: N abstained, N wrong-kind; N no-view), says why textures were left out. Tools → Debug → Survey game textures logs what the game bound at each slot.
• Under Tools → Report → Counters, toggles → ambiguous counts key presses two characters' mods tied over. The log's <key> pressed: line names the mods a press went to and what each moved, or why it moved nothing: a tie, no mod binding it drawn, its keys waiting for parts not drawn, or its conditions.
• The log's N mods read from <folder> line, or N mods drawn from <folder>, chosen by … where a profile chose them, says how many mods were read, and from where.
• Settings → Help → Log detail keeps more in the log; raise it only when asked for a bug report.