Error Message Guide

This page will describe errors and warnings in more detail, which show up in the PGPatcher confirmation dialog. Warnings should be reviewed but often can be ignored, errors should always be addressed.

Warnings

NOTE In the confirmation dialog you can right click any warning and click on Ignore - this will hide it for all future runs unless you check the Show Ignored Warnings box. This is useful to clear warnings you know are to be ignored to avoid additional clutter when reviewing the results of a run.

Texture {} contains non-ascii characters which are not allowed

NIFs in Skyrim do not support non-ASCII characters, therefore PGPatcher will ignore these textures and will not apply them to any meshes/texture sets. The mod author would need to resolve this.

BSA is in INI but does not exist: {}

This message indicates that a BSA was indicated to load in an INI file, but it does not exist. It is generally safe to ignore unless you know that BSA should be loading.

File {} in BSA {} contains non-ascii characters

BSA files, while on their own can support non-ASCII characters, are problematic in-game as the Skyrim engine has a bug where file hashes are not calculated properly for non-ASCII filenames in BSAs. Therefore, non-ASCII characters should not be used for files in BSAs at all. This is safe to ignore, though it may be good to fix to avoid issues with the game reading this file.

BSA file {} not loaded by any active plugin or INI.

This warnings indicates that a BSA file exists in the data folder but is not being loaded by either INI or a plugin. These are safe to ignore unless you know the BSA should be being loaded.

Output directory is empty. No files were generated.

If PGPatcher did nothing, you will get an empty output and this message. Usually, this is because your settings are wrong. Verify your game path, game type, and conflict mod manager settings.

Unable to read model path: {}

This warning will occur when model paths in plugins are not readable (wrong syntax). This record is skipped by PGPatcher for the run.

Unable to read texture set: {}

This warning will occur when texture paths in plugin TXST records are not readable (wrong syntax). This record is skipped by PGPatcher for the run.

Weight slider enabled but mesh name doesn't end with _0.nif or _1.nif: {}

There is no case where a weight slider should be enabled but the mesh is not named properly. This record is skipped by PGPatcher for the run. This should be reported to the original author of the mod in question.

Errors

ERRORS NEED TO ALWAYS BE ADDRESSED not just for PGPatcher, all errors represent a fundamental issue with your load order that will cause problems.

Unable to process texture: {}

This indicates PGPatcher was unable to read a texture. This means the texture is corrupt and should be fixed.

Unable to save texture {}: {}

This error indices PGPatcher was unable to save a texture because it was blocked somehow by your system.

Unable to process mesh: {}

This indicates PGPatcher was unable to read a mesh. This means the mesh is corrupt and should be fixed.

Failed to read file: {}

This is a more generic error message indicating that PGPatcher sought to read this specific file but was unable to because of something on your system blocking it.

Failed to get file pointer from BSA: {}

This indicates the BSA is somehow corrupt as PGPatcher cannot get file pointers from it.

Failed to parse JSON: {}

If a JSON file was invalid json or otherwise corrupt, PGPatcher will issue this error. This is a mod author issue.

Mesh {} has texture slot(s) with invalid non-ASCII chars

As addressed above, NIF files cannot have non-ASCII characters. This will cause issues in-game and this mesh should be fixed.

Error reading mod directory {}: {}

This will occur when something on your system is preventing PGPatcher from reading a MO2 mod folder. This could be an open file handle from another application, for example. You should address this then rerun PGPatcher.

Weighted mesh variant for '{}' not created. Weight variants (_0 and _1) do not match. or Weighted mesh variants '{}' and '{}' do not match.

Weighted meshes refer to meshes where weight sliders are enabled in ARMA (Armor Addon) records. These meshes usually end in _0.nif or _1.nif. PGPatcher patches them independently. If it turns out that only one of them was outputted and not the other (first message), or the 2 outputted variants do not match in terms of block types and IDs (second message), it means the original _0 and _1 variants are somehow different (in either meshes or plugins), which is not allowed and will cause issues in-game. This can happen in plugins if the weight slider is enabled on one use of the mesh but disabled on a different use of the mesh. This should be fixed by the mod author of these meshes.

Failed to read plugin: {}

This indicates that a plugin is likely corrupt as PGPatcher was unable to read it. PGPatcher will skip this plugin for the processing run.

Plugin has missing masters: {}

This indicates that a plugin in your load order has missing masters. Usually this means some parent mod is not present that is required. PGPatcher will skip this plugin for the processing run.

Failed to resolve model record: {}

This is always because you have some plugin that overrides another plugin but the formids do not match by type. This can often happen in cases where a base mod is updated, but a patch plugin is not updated yet, for example. You need to fix this, this is not a suggestion, this will cause CTDs in-game.

Failed to copy model record: {}

This will happen when PGPatcher is unable to copy a record to its own output plugin. This is because the original record/plugin is corrupt.