Guild Wars 2

As title. It isn’t working, I cannot stay connected, I cannot switch chars or open the trade post without DC. I get DC’d from WvW constantly.

None of this was happening prior to todays patch. I am used to having a choice between 32 or 64 on most of my downloaded programs. 32 is most stable, 64 works on a very few.

I particularly do not like the idea of any program deciding on it’s own to change my settings.

Taking a clue from Microsoft re unwanted “upgrades” isn’t a great Idea. Consumers should have a choice. The 32 bit was working fine for me.

from the 64-bit faq:
https://forum-en.gw2archive.eu/forum/support/support/64-BIT-CLIENT-FAQ

My computer satisfies the requirements for automatic switching to the 64-bit client, but I want to remain on the 32-bit client.

If you want to remain on the 32-bit client, you may add -32 to the command line used to launch the game client. Please refer to the wiki for instructions on how to modify your command line.

link to wiki on adding command lines
https://wiki.guildwars2.com/wiki/Command_line_arguments

nottsgman.8206:

from the 64-bit faq:
https://forum-en.gw2archive.eu/forum/support/support/64-BIT-CLIENT-FAQ

My computer satisfies the requirements for automatic switching to the 64-bit client, but I want to remain on the 32-bit client.

If you want to remain on the 32-bit client, you may add -32 to the command line used to launch the game client. Please refer to the wiki for instructions on how to modify your command line.

link to wiki on adding command lines
https://wiki.guildwars2.com/wiki/Command_line_arguments

So apparently the game autoupdates itself to 64? After the patch, I can’t even run the launcher, I keep on getting the Gw2-64.exe error, probably because I can’t run on 64.

Anyway I tried adding -32 to the command line for the shortcut. It launched, but it looks like it’s downloading another client. Really need help

Teofa Tsavo.9863:

I particularly do not like the idea of any program deciding on it’s own to change my settings.

Taking a clue from Microsoft re unwanted “upgrades” isn’t a great Idea. Consumers should have a choice. The 32 bit was working fine for me.

I can’t agree more. Even though I liked they made a 64 bits version and it has been running well for me, I’m still all up for having choices (looking at you Win 10 o.~). Don’t force stuff on us. Also, why defaulting to 64 bits? If someone has been using the 32 bits client on a 64 bits system it’s most likely they must have a very valid reason for that. Why not doing the opposite where a param would be required to run the 64 bits version and it defaulting to 32?

Also, I haven’t tested it myself as I had already been using the 64 bits client, but as far as I know an executable cannot contain both 32 and 64 bits code in it, what leads me to think that the command line switch causes it to rebuild/replace itself. If so, why that? Isn’t it easier to have two clients as we already had if, technically, this way they are also two different clients?

Well, after the “awesome” NPE that they seem to be stubborn about revising, I’m not going to hold my breath neither surprises me such kind of decision :/

Well, forcing the 32 helped, but I still have a char in Hoelbrek, and no matter how I try to log onto that character, I get a hard disconnect that closes the game.

shadow.6174:

Also, I haven’t tested it myself as I had already been using the 64 bits client, but as far as I know an executable cannot contain both 32 and 64 bits code in it, what leads me to think that the command line switch causes it to rebuild/replace itself. If so, why that? Isn’t it easier to have two clients as we already had if, technically, this way they are also two different clients?

There are two executables (clients) in your GW2 folder, Gw2.exe and Gw2-64.exe. The shortcut to start GW2 links to the first one. That exe checks to see if you can run the 64 bit client and if so closes itself and starts the 64 bit client. If it can’t run the 64 bit client or if you have the -32 command line option it will run the 32 bit client. So you have two clients.

Also, why defaulting to 64 bits? If someone has been using the 32 bits client on a 64 bits system it’s most likely they must have a very valid reason for that. Why not doing the opposite where a param would be required to run the 64 bits version and it defaulting to 32?

As there was no 64 bit client when GW2 releases you didn’t have a choice of running the 64 bit client on a 64 bit system. Now that client is there it makes sense to use the 64 bit client for 64 bit systems as default. So making running the 32 bit client on a 64 bit system optional is the logical choice. Why should you run the 32 bit client on a 64 bit system in the first place? The 64 bit client should run better. If it is not then there is something going on on your system.
As with every PC game how the game runs can be totally different between two almost identical systems. So having an option to fall-back to a 32 bit client is a good idea. Another reason to run the 32 bit client is because you use a 3rd party tool that needs Gw2.exe to run and not the 64 bit client. For example SweetFX and other injectors. And then there are those cases where an anti-virus program or an anti-malware program decides that Gw2-64.exe is a threat and blocks access to the game and Gw2.exe is fine. Something that should be solved by unblocking Gw2-64.exe and not choosing the less optimal executable.

Teofa Tsavo.9863:

Well, forcing the 32 helped, but I still have a char in Hoelbrek, and no matter how I try to log onto that character, I get a hard disconnect that closes the game.

Try guesting to another server and log in to that character. I know that tends to help when a map instance glitches and a character refuses to load a different instance.