XivAlexander with ReShade and GShade: Chain-Loading Guide
ReShade and GShade are visual overlay tools that, like XivAlexander’s autoload mode, can be loaded through a DLL placed in the game folder and named d3d11.dll or dxgi.dll. When two tools both want the same file name, only one can occupy it, and the other must be chain-loaded through the first. If you simply copy both tools’ DLLs into the game folder with the same name, one will overwrite the other, and you will end up with either a missing tool or a crash. This guide explains chain-loading, the correct order to test, and how to isolate a crash.
How chain-loading works
Chain-loading means one DLL, when loaded by the game, loads the next DLL in the chain, which loads the next, and so on. The game itself only loads the first file, named d3d11.dll or dxgi.dll. That first file is responsible for passing control onward. XivAlexander, ReShade, and GShade all support chain-loading arrangements, but the exact configuration depends on which tool occupies the first file name and which tool is configured to load next. Do not assume that copying files in any order will chain correctly; an unconfigured chain is just a missing tool.
Recommended approach: portable mode first
The simplest way to avoid the entire DLL conflict is to use XivAlexander in portable mode while ReShade or GShade handles the visual layer through its own autoload file. In portable mode, XivAlexander does not need a DLL in the game folder, so there is no file-name collision at all. Start the game with your visual tool active, then attach XivAlexander with the portable loader, as described in How to Install XivAlexander on Windows. Test that both tools work together in this arrangement before attempting a full autoload chain. If portable mode works, you have a working setup, and you do not need to solve the chain-loading puzzle at all.
If you need full autoload chain-loading
- Back up your game folder’s DLL files and your visual tool’s presets before changing anything. A preset you lose to a careless overwrite is difficult to reconstruct.
- Decide which tool occupies the game’s d3d11.dll or dxgi.dll name, and configure that tool to chain-load the other, following the documentation of the tool that occupies the first name. Do not configure both tools to chain-load each other in a loop.
- Test with the game alone, then with the visual tool alone, then with the chain. If the chain crashes but each tool works alone, the fault is in the chain configuration, not in either tool by itself.
- If you use GShade, remember that GShade is a community fork with its own update history. Do not apply ReShade instructions to GShade blindly, and do not assume a GShade preset will behave identically under ReShade.
Isolating a crash
If the game crashes with both tools active, remove the chain and test each tool alone, in the same way you would isolate a Dalamud conflict in XivAlexander and Dalamud Conflict. If XivAlexander alone crashes, check patch compatibility in XivAlexander Not Working After a Patch. If the visual tool alone crashes, check its own compatibility with the current game version and graphics driver. Only when both work alone should you rebuild the chain, one link at a time, testing after each link. A chain that is built all at once and crashes tells you nothing about which link failed.
Frequently asked questions
Can I use XivAlexander autoload and ReShade at the same time?
Yes, with chain-loading, but portable mode for XivAlexander is the simpler and more reliable arrangement for most players.
Which file name should I use, d3d11 or dxgi?
Use the name your visual tool already uses, and chain the other tool through it, unless that tool’s documentation directs otherwise. Consistency matters more than the specific name.
Do visual presets affect latency?
No. A preset changes rendering, not network timing. A heavy preset can affect frame rate, which can feel like lag, but that is a graphics problem, not a network or animation-lock problem.
Visual tools and latency tools can coexist, but only if you respect the file-name collision that autoload creates. Portable mode sidesteps it entirely. Full chain-loading requires a deliberate order, a backup, and one-link-at-a-time testing. Either path works; the one that fails is the one where both DLLs are copied in with the same name and nobody checks the chain.
Important: Final Fantasy XIV prohibits third-party tools that inject code into the game client or alter its network behaviour. XivAlexander is an unofficial, community tool, not affiliated with Square Enix. Using it carries a risk of account restriction. This guide is for information only; decide for yourself whether that risk is acceptable, and never use a third-party tool on an account you are unwilling to risk.
