Troubleshooting

Most problems with Nexus come down to a single addon, a leftover file from another tool, or an addon waiting for an update after a game patch. This guide helps you narrow down the cause quickly, explains the most common symptoms, and shows how to collect the information developers need when you report a problem.

First steps

Work through these in order. Each one rules out a whole group of causes.

1. Check whether a game update just happened. After a patch, addons marked as volatile are disabled until they are updated, and Nexus shows a notification for each of them. That is expected and resolves itself once the developers release fixes.
2. Start the game with -ggvanilla. This launch option starts the game with Nexus inactive and no addons loaded. If the problem persists, it is not caused by Nexus or your addons. Check your graphics drivers, overlays and other tools instead.
3. Disable addons one at a time. If the game works with -ggvanilla, the cause is most likely an addon. Disable half of your addons on the Addons page, restart, and keep halving until you have found the one that causes it.
4. Read the log. Open Log in the Nexus menu, or addons\Nexus\Nexus.log after closing the game. Warnings and errors usually name the file that caused them.

The game does not start or crashes on startup

• Start once with -ggvanilla. If that works, start normally again and check addons\Nexus\Nexus.log after the crash. The last entries show which addon was being loaded.
• Look for duplicates. Two copies of the same addon, for example ArcDPS both in the addons folder and as d3d11_chainload.dll, frequently cause crashes. Remove one of them.
• Check the chainload. A broken or outdated d3d11_chainload.dll can prevent the game from starting. Move it out of the game folder temporarily.
• Check other proxy DLLs. Files such as dxgi.dll in the game folder or in bin64 belong to other tools, typically ReShade. Move them out temporarily to see if they are involved.
• Check your antivirus. Some antivirus software quarantines or blocks DLL files it does not know. If d3d11.dll disappears or the game fails to load it, add an exception for your game folder.

An addon does not load

The Addons page and the log tell you why. Common reasons:

Updates do not install

• Updates need internet access to api.raidcore.gg and, for most addons, api.github.com and github.com. Firewalls, VPNs or DNS filters can block them. The log shows the failing address.
• Addons that cannot be unloaded while the game is running only switch to their new version after a restart.
• Check that automatic updates are not turned off for the addon. Right-click it on the Addons page to see.
• Some addons only publish their updates as pre-releases. If the developer asks you to test one, enable pre-release updates for that addon in the right-click menu.
• Nexus needs write access to the game folder. If the game is installed in a protected location and updates fail with access errors, make sure your Windows user can write to the game folder.

The Nexus interface does not show

• Press Ctrl+H. This keybind hides all Nexus and addon interfaces, and it is easy to press by accident.
• Press Ctrl+O to open the menu directly. If the Quick Access bar is set to show only in or out of combat, or never, it is hidden on purpose. See Customizing Nexus.
• If the license agreement never appeared and nothing shows, check whether Nexus was loaded at all: addons\Nexus\Nexus.log exists and has been written to recently if it was.
• If the interface is far too large or too small, toggle DPI Scaling in the options and check the game's own interface size setting.

Keybinds or the mouse behave strangely

• If a key no longer works in the game, a Nexus or addon keybind probably uses it. Find it on the Keybinds page, then change it, remove it, or allow the key to pass through to the game.
• Addons that press game keys need to know your game keybinds. Import them on the Guild Wars 2 tab of the keybinds page.
• If the cursor jumps around while you rotate the camera, enable the cursor options under Options.
• If you click through addon windows into the game or the other way round, check whether Clicking requires modifiers is enabled.

Performance problems

Nexus itself has very little overhead, since it draws into the game's existing frame. Noticeable frame drops almost always come from individual addons, especially ones that draw many elements or process a lot of combat data in large fights. Disable addons one at a time to find the expensive ones, and check their options for features you do not need.

Reporting a problem

If you have found a bug, report it to the developer of the addon involved, or to Raidcore if it is about Nexus itself, on the Raidcore Discord. A good report includes:

• What you did, what you expected and what happened instead.
• Your Nexus.log from the session where the problem happened, found in addons\Nexus. It is overwritten on the next start, so copy it before starting the game again. If you multibox, the log is called Nexus_.log.
• If the game crashed, the crash report Guild Wars 2 created, ArenaNet.log in %AppData%\Guild Wars 2.
• Which addons you have enabled, and whether the problem also happens with only the suspected addon enabled.

The log contains your game command line and folder paths, which can include your Windows user name. Look through it before posting it publicly.