Troubleshooting

Table of Contents

• Disclaimer
• Basic Troubleshooting
• Resetting the tool/settings
• Accessing log files for issue reporting
• Anamnesis cannot find the ffxiv_dx11.exe process
• Anamnesis silently fails to launch
• Poses are deleted when the tool is updated
• The tool asks you to install .NET despite there being a compatible runtime installed
• Anamnesis.exe is deleted when the tool is extracted
• A 'Screenshot Failed' error appears when using Anamnesis in conjunction with a post-processing tool such as ReShade or GShade
• Multiple Anamnesis processes found
• My issue isn't here!

Disclaimer

Anamnesis is still in a beta state, and the tool should not be used under the assumption that it works perfectly. Bugs can and will occur during development, and the team have gone to great lengths to make troubleshooting and error reporting as simple as possible for end users. With that in mind, it is highly recommended that you do not use the tool unless you are prepared to treat it as a tool in beta, and follow proper troubleshooting and issue reporting guidelines, including using the reporting templates provided when opening tickets.

Basic Troubleshooting

It is good practice to ensure you have adhered to the following basic rules while using Anamnesis. Failure to do so will result in most of, if not all issues, crashes, etc. you may encounter.

• Make sure you're running the latest version of the tool.
• Make sure the folder you have extracted the program to is owned by an Administrator.
• Make sure you have either turned off your Antivirus program, or at the very least made an exception for the Anamnesis executable in your Antivirus program and Windows Firewall.
• Make sure you have launched Final Fantasy XIV and logged into a character before launching Anamnesis.
• Make sure you are running the International client of the game (JP/NA/EU). Note that the Chinese and Korean clients are not fully supported at this time, so you may have limited use of the tool with these clients.
• If you did not previously have .NET Desktop Runtime 6.0.6 x64 installed on your system and have installed it for the purpose of using Anamnesis, make sure you reboot your PC after installing it to ensure it's installed completely.

      ^{↑ back to top}

Resetting the tool/settings

In the event that a setting has not saved correctly, the settings file has corrupted, or you simply wish to reset the tool to its default settings, press and hold the Shift button while launching the tool, and continue holding until you are presented with the message seen to the right.

* This dialogue window will be in English regardless of any language settings previously used.

      ^{↑ back to top}

Accessing log files for issue reporting

Anamnesis provides easy access to logs via the About menu, so please use those instead of taking screenshots of an error message, as images of error messages will not give the developers enough information to work with. Anamnesis will retain the last fifteen instance logs for your convenience.

You can also manually access these logs if you don't have the tool open:

1. Press the Windows key on your keyboard and enter %appdata%, then hit the Enter key- this will take you to the Roaming folder
2. Double-click on the Anamnesis folder
3. Double-click on the Logs folder

From there you can drag and drop your log files into a Github Issue text box or Discord channel, which will upload it for the developers to read.

No identifying information is kept in these log files- they are completely anonymous, and are only used for the express purpose of troubleshooting and issue resolution only.

      ^{↑ back to top}

Anamnesis cannot find the ffxiv_dx11.exe process

Anamnesis only supports the DX11 version of the game, as Square Enix will be dropping support for the DX9 version as technology evolves. Please ensure you are running the DX11 version of the game before running Anamnesis.

If, for whatever reason, you cannot use the DX11 version of the game, then you will not be able to use Anamnesis. We apologise for this inconvenience.

Additionally, Anamnesis currently only works with the international (JP/NA/EU) client; while some support exists for CN and KR clients, it is provided as-is, as the developers do not have access to these clients to test compatibility.

      ^{↑ back to top}

Anamnesis silently fails to launch

Some versions of the .NET Desktop Runtime have issues with backwards compatibility; if you have recently installed .NET Desktop Runtime 6.0.6 x64 or newer but Anamnesis fails to open, please do a fresh install of the .NET Desktop Runtime, restart your computer, then try launching the tool again.

      ^{↑ back to top}

Poses are deleted when the tool is updated

This occurs when poses are saved into the tool's Build-In Poses folder. You should never place custom pose files in this folder. Please ensure you are using the default Poses folder in the Documents directory, or loading from a different folder.

      ^{↑ back to top}

The tool asks you to install .NET despite there being a compatible runtime installed

Older installations of .NET Framework/Core can occasionally interfere with newer installations, including .NET Desktop Runtime 6.0.6 (used by Anamnesis). This is caused by newer versions of .NET failing to correctly update its Host Version on installation, and not something caused or remedied by Anamnesis.

To check if this is affecting you, please follow these instructions:

1. Open a Command Prompt window by typing cmd into the search bar of the Start menu and pressing Enter
2. Type (or copy and paste) dotnet --info and press Enter
3. Scroll down until you see Host- check to see if the Version below it is 6.0.6

If the version is not correct/up to date, please note down which version it was, as you will need to uninstall it to prevent Windows from silently failing to read the correct version.

      ^{↑ back to top}

Anamnesis.exe is deleted when the tool is extracted

Occasionally your Anti-virus software will delete the executable when the archive is extracted, and/or flag the tool as a false positive. To circumvent this:

1. Right-click the archive and select Properties
2. Press the Unblock button at the bottom
3. Press Apply and Okay
4. Extract the archive either on top of the existing installation and overwrite the files when prompted, or extract the archive to your folder of choice.)

If this alone does not resolve the issue, then you will need to whitelist the tool and its related folders in your Anti-virus software. The method for whitelisting applications varies from program to program. Below is a list of popular antivirus programs and links to their documentation.

• Avast
• AVG
• BitDefender
• ESET NOD32
• McAfee
• Windows Defender (preferred by the developers)

The folders that will need to be whitelisted include:

• The folder you extracted the tool to
• %appdata%\Anamnesis
• Documents\Anamnesis

      ^{↑ back to top}

A 'Screenshot Failed' error appears when using Anamnesis in conjunction with a post-processing tool such as ReShade or GShade

This is due to a Windows Security feature, and usually only appears when the user is trying to take a screenshot when Anamnesis has window focus. To remedy this, try the following fixes in order until the issue is resolved:

• Click anywhere in the game window to ensure it has focus before pressing the Print Screen button
• Ensure GShade/ReShade has been added to the Windows Firewall
• Check your keybinds in-game and in GShade/ReShade to ensure they aren't conflicting
• Roll back any recent Windows Updates

If none of these options resolve the issue, then you may not be able to use Anamnesis until a workaround is found. As such, please wait for an update on our Discord. We apologise for this inconvenience.

This is a feature of Windows Security, and not a bug with either Anamnesis or your chosen post-processing injector. As this isn't an Anamnesis or program problem, the developers will not be able to assist you with questions about this.

An alternative to using your set Screenshot button is to utilise the Snipping Tool, which is a stock Windows tool, and is covered in detail by Microsoft.

      ^{↑ back to top}

Multiple Anamnesis processes found

There can only ever be one instance of Anamnesis open at any given time. If you receive an error stating that you have multiple instances of the tool open, please follow these steps to close all instances so you can start over:

1. Press Ctrl + Alt + Delete
2. Select Task Manager
3. Select any instances of Anamnesis.exe in the Apps list or in the Details tab
4. Click End task
5. Repeat 1-4 for any additional instances in the list.

From there you can simply relaunch the tool as normal.

      ^{↑ back to top}

My issue isn't here!

If you have checked ensured that your issue is not caused by failing to adhere to the above practices, then you have likely encountered a bug that has been missed during our extensive testing phases.

If this happens, please open a ticket in the Issues tab, ensuring you have included as much detail as possible, and have attached any relevant logs. The information we require to fully act on a bug report has been clearly outlined with the Bug Report template. Any ticket opened that does not follow this template, or requests for basic help with anything that has already been covered extensively elsewhere in this wiki will be closed. Please note that reporting issues requires an email verified Github account.

You should always check both opened and closed tickets, as it's possible that your issue has been encountered, reported, and resolved already. Duplicate issues impede development, and are a waste of not only the developers' time, but also your own.

Please make the effort to read all documentation and complete your issue reports as robustly as possible, including following the provided templates. Anamnesis is created and maintained by volunteers in their spare time, and responding to poor bug reports or reports based on user-made errors or misuse is time-consuming.

Support channels on Discord are covered mainly by server moderators and the original alpha testing team, and are best used for "how can I do [task]?"-like queries and general tool issues that aren't already covered in this wiki, not bug reports or technical issues. If the tool is not working for you, please open a ticket on Github instead of using Discord, as bug reports on Discord will likely end up with you being pointed back to the Github repo anyway. Most top level/generic error messages are meaningless when provided without context, and as such what is far more valuable to the developers are the steps taken to produce that error, as well as the potential error(s) caused by repeating said steps. As such, your error message will fall into one of two categories, with differing levels of severity

1. Error message received → No tool or game crash, and/or you can click the error away and continue using the tool → You can upload log to the #log-file-upload channel on the XIV Tools Discord server with a rundown of what you did to encounter it. From there the developers can investigate, or a volunteer may provide insight. You may be asked to report the issue on Github depending on the severity.
2. Error message received → Either the tool or game crashed → Report the issue directly on Github, ensuring you've followed the reporting template provided. Do not post these logs to Discord.

      ^{↑ back to top}