Forcing 64 Bit Client is Hasty
I’ve had to add in the -32 myself. I initially had no problems with the 64 bit client until an AB meta when I ended up in single digit FPS. I do feel it should have been an optional thing.
“Even if we find a way to save the world from the
dragons, I sometimes wonder if we’ll ever find a way to save us from ourselves.”
dragons, I sometimes wonder if we’ll ever find a way to save us from ourselves.”
The 64 bit client isn’t forced. You can still choose between 32 and 64 bit. It’s just that the 64 bit client is now the default one. I think for most people the 64 bit client is an improvement. Multiple monitor setups and SLI are not as common and people who set up such systems should be able to add the -32 switch just fine.
Since you’re apparently using the 32 bit client: Are the memory issues fixed or does the client still crash after half an hour of playing HoT? I’ve been using the 64 bit client since the start of it’s beta because of these issues.
I have never had a crash using the 32 bit client, except for maybe a couple of times during meta events with hundreds of other players around me.
ANet,
A while back I posted a bug with the 64 bit client and multiple monitors in SLI (black screen, I need to reboot the PC to restart). Nobody answered. Now that it is forced, I have the same bug. I will go in and add the -32 switch to the command line to force it back to 32 bit, but a lot of people won’t know how to do that. I’ve seen many people posting problems with the 64 bit client. It just seems like the client really is not ready for mass (default) release. Just my opinion.
Hi
The black screen bug is not GW2. It happens in many games, I’ve had it happen also on Skyrim, Witcher 3 and Battlefront. There is also a White Screen equivalent for people using AMD cards. All these bugs started happening when graphics manufacturers started developing single suite drivers for regular monitors and VR, they are nasty and hard to get rid of.
I highly recommend visiting your graphics card tech support for it. I had to update my vid card Bios to get rid of mine, that is something that hardly anyone needs to do, ever.
You may even have more success if you switch this thread to the tech support section. Believe me, that if you have a 64 bit system, it is well worth to run the 64 bit client once you work out the kinks out of it, runs much faster, better, more stable. In the meanwhile, you can continue using the 32 bit client as posted above.
Heavy Deedz – COSA – SF
I’ve had to add in the -32 myself. I initially had no problems with the 64 bit client until an AB meta when I ended up in single digit FPS. I do feel it should have been an optional thing.
If you are using a laptop read this
https://forum-en.gw2archive.eu/forum/support/support/64bit-8fps-with-right-GPU-setting
ANet,
A while back I posted a bug with the 64 bit client and multiple monitors in SLI (black screen, I need to reboot the PC to restart). Nobody answered. Now that it is forced, I have the same bug. I will go in and add the -32 switch to the command line to force it back to 32 bit, but a lot of people won’t know how to do that. I’ve seen many people posting problems with the 64 bit client. It just seems like the client really is not ready for mass (default) release. Just my opinion.
Hi
The black screen bug is not GW2. It happens in many games, I’ve had it happen also on Skyrim, Witcher 3 and Battlefront. There is also a White Screen equivalent for people using AMD cards. All these bugs started happening when graphics manufacturers started developing single suite drivers for regular monitors and VR, they are nasty and hard to get rid of.
I highly recommend visiting your graphics card tech support for it. I had to update my vid card Bios to get rid of mine, that is something that hardly anyone needs to do, ever.
You may even have more success if you switch this thread to the tech support section. Believe me, that if you have a 64 bit system, it is well worth to run the 64 bit client once you work out the kinks out of it, runs much faster, better, more stable. In the meanwhile, you can continue using the 32 bit client as posted above.
I have Skyrim and do not have this problem when running 3 monitor SLI. This is the only program I have that has this problem.
It just seems like the client really is not ready for mass (default) release. Just my opinion.
Correct sentence is : It just seems like the SLI multi monitor is not ready for mass.
I’ve had to add in the -32 myself. I initially had no problems with the 64 bit client until an AB meta when I ended up in single digit FPS. I do feel it should have been an optional thing.
If you are using a laptop read this
https://forum-en.gw2archive.eu/forum/support/support/64bit-8fps-with-right-GPU-setting
I’m not. I currently have an AMD Radeon HD 5670. I currently have 4 GB RAM which is most likely where the problem lies. However, with the 32 bit client I wasn’t running into any issues, including DCs etc that other people were experiencing. For now I’ve swapped back to that and I’ll be upgrading my RAM in a couple of weeks when I can afford to as I’m not funded by the bank of mum and dad like a lot of people are. The issue I have is that ANet assumed the ‘conditions were favourable’ for the 64 bit client when in actual fact, they weren’t. I would have preferred a prompt that I could have cancelled, not a decision automatically made for me which turned out to be the wrong one.
“Even if we find a way to save the world from the
dragons, I sometimes wonder if we’ll ever find a way to save us from ourselves.”
dragons, I sometimes wonder if we’ll ever find a way to save us from ourselves.”
The game shouldn’t be out of beta, because some people have issues with it still.
Out of beta doesn’t mean it will work flawlessly with every system and every setup. That’s not what out of beta means. It means the basic function for most people will work and the basic function for most people does.
Providing an option to switch it off is a reasonable alternative.
If Anet, or any software company, waits until every single bug or compatibility issue is fixed, nothing would ever get out of beta.