GW2-Addon-Manager
GW2-Addon-Manager copied to clipboard
Says invalid directory when installed on D drive.
I have Guild Wars 2 installed in D:\Guild Wars 2\bin64. When I click "Update" I get "Unable to locate the Guild Wars 2 /bin/ or /bin644/ folder. Please verify Game Path is correct." It is correct, tried forward and back slashes, even added a forward and a back slash at the end of the bin64.
Can you post your acctuall game path and config.xml
file please? Without that, im afraid we cant do anything to fix the issue.
Path is "D:\Guild Wars 2\Gw2-64.exe" Tried with and without the bin64
Can't attach the .xml, but here are the contents (assuming you want from your addon, I do not see one in GW2):
-<UserConfig xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<LaunchGame>false</LaunchGame>
<GamePath>D:\Guild Wars 2\bin64</GamePath>
Hmm the config you posted seems broken, there are many things missing. I will look futher into this. Meanwhile you can manually edit the config file, heres how it should look like:
<?xml version="1.0"?>
<UserConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<LoaderVersion>v0.3</LoaderVersion>
<BinFolder>bin64</BinFolder>
<LaunchGame>false</LaunchGame>
<GamePath>D:\Guild Wars 2</GamePath>
<ExeName>Gw2-64.exe</ExeName>
<AddonsList Hash="f1395110af4a91a0fe352b944db75e78cc1eb6af">
<AddonData>
<Name>d3d9_wrapper</Name>
<Version>v1.2</Version>
<Installed>true</Installed>
<Disabled>false</Disabled>
</AddonData>
</AddonsList>
</UserConfig>
If this wont work, maybe try clean install? Prefably on the same drive that your game is installed.
@Draeggiar I had the same problem, looking on my config and comparing it with the one you posted, mine was missing <LoaderVersion>v0.3</LoaderVersion>
property
I did a clean install of both GW2 and the Addon Manager and I'm having the same issue as above :/
Adding <LoaderVersion>v0.3</LoaderVersion>
to the config fixed it for me.
Adding
<LoaderVersion>v0.3</LoaderVersion>
to the config fixed it for me.
same
I confirm this, the config file default seem broken, this produce an completely strange error message instead of LoaderVersion
is missing or something like that.
I think the newest version fixes this . I didn't realize the release at the top of the releases page was old and that one had the issue you mentioned but the one below I've had no issues with
just to confirm please indicated what version you are talking about. the 1.3.0 have this bug
oh strange, the one that works for me is 1.3.0 and alpha 1.3.0.3 was the one giving me this problem