Guild Wars 2

forum bug /15char

Johan Skold.4708:

Raven Lord.3407:

For the first time ever today after launching the 64-bit my security software flagged some guild wars 2 files for keylogging. It happened to be during a gem purchase through paypal. I blocked the function through the securities software but I thought it was odd since it has never happened before.

Interesting. What security software is that? Could you ensure that the executable is signed by us?

1. Right click the “Gw2-64.exe” file. If you don’t see the “.exe” part, that’s fine. It’s the file with the GW2 icon.
2. Click the “Digital Signatures” tab.
3. “ArenaNet Inc.” should be in the list of that tab.
4. If you select “ArenaNet Inc.” and click “Details”, it should say “This digital signature is OK.”

If all of the above is true, you can rest assure that it’s a false positive.

I use “360 Total Security”
I checked the certificate as directed and it says that the “This digital signature is OK” thanks.

BlankHearts.8216:

Not sure I correctly followed the instructions. I downloaded the GW2 64 bit beta client and dropped it into my GW2 data folder and started the application. But its downloading the entire game again. I’m not sure how to ‘’Update any shortcuts to the game to point to the new file instead.’’

More than 1 ways to do it but I suggest this.
Copy the GW2-64.exe file you downloaded in the GW2 folder.
Then proceed to delete any previous GW2 shortcuts you are
using(Desktop and Taskbar).Then right click on GW2-64.exe
in the GW2 game folder and select ‘send to desktop(create shortcut)’.

Sadly its still asking me to redownload the game, I guess I’m gonna have to.

No framerate issues here, seems the same as the 32bit client. Noticed client using up to 4.9GB of RAM in Tarir. Also seems a good chunk of RAM gets cleared on map change, so it seems good.

Posting the system specs to help you exclude and narrow down the problem.

i7 4790k
GTX 980
16GB DDR3
Sabertooth Z97 Mark 2
850 EVO SSD
Win 10 x64
Latest BIOS, non-beta drivers and updates.
KIS 2016 running in the background.

Keep the good work from a fellow dev

Has the 32-bit client and OOM been linked to the nVidia driver crash or will the new client not help with that?

*Display driver nvlddmkm stopped responding and has successfully recovered.

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. *

How would you like testing to be done? Max out the settings as they should be, if one has a card that will do it, and see what happens?

I’m having a problem with text and graphics overall becoming blurry when playing on 64bit client. Anyone got a clue what would fix this?

My framerate with the 64bit client is terrible. It’s around 10fps in LA, whereas it’s ~40 with the 32bit client.

Well I downloaded the client and put it in the GW2 directory and ran it…

I have no idea what to do now. There isn’t any error code or anything, windows just says no

ZudetGambeous.9573:

Well I downloaded the client and put it in the GW2 directory and ran it…

I have no idea what to do now. There isn’t any error code or anything, windows just says no

Your download looks incomplete, try redownloading the file. The 64-bit version is about 4m larger than the 32-bit one. Should be about 28M as opposed to 24M.

I’d like very much to try and use the new 64-bit client.

BUT, big but for me, without SweetFX my eyes just bleed in front of the screen. Are there 64-bit SweetFX dlls to use with the new client?

I just can’t play without the higher sharpness given by SweetFX, to me it feels like I’m seeing the monitor behind huge cataracts.

So far it seems to have fixed the oom crashes for me. Played through multiple wvw fights no problem.

Will this still support the -useOldFoV switch for those of us who still like/need to use it?

I don’t know like you guys said 64bit systems will have more access well more like complete access to all there ram so technically there should be a good chunk of performance improvement if you guys do the 64bit client correct.

Windows 8.1
Core i7 3630 QM
Radeon 7970M
16 GB of RAM

First difference is faster loading screens.
The performance seems the same when the game is loaded.

It may be causing some lagspikes (network, not fps ones) to me occasionally. I need to do firther testing to confirm it’s related to 64-bit client.

I want to really thank all the developers who created this 64beta. For me the differences are night and day with max settings.
Thank you so much!
i7 + 980gtx + HD resolution Windows 10 64 bit..

Didn’t have any issues with the 64bit-client so far. Just the overwolf-plugin for teamspeak doesn’t seem to work with it for some reason. As in, it doesn’t show me anymore who’s talking when I’m ingame.

Will this 64-bit client executable be updated with the updater when a new version is available?

Another slightly related question… Why is there no Linux client since you have Mac version and those two are really similar?

If you’re getting nvlddmkm.sys crashes, try downgrading to 347.88 (980 and older) or 353.49 (980ti). That’s caused by something else so I doubt switching to x64 would help.

GM Kveldulf.4790:

@Beldin.5498.

Exception: c0000005 is a fun one, and there are a lot of possible root causes unrelated to the 64-bit client. I recommend submitting a support ticket about it, and we’ll run through some troubleshooting with you.

Like i said .. it was TS3Overlay i think.

I tried now Overwolf .. however for Overwolf to stay in front i first had to rename
gw2-64.exe to gw2.exe

I wonder what happens on the next patch, will the patcher detect the x64 or
will it be overwritten with the x32 because of the name ?

Those are interesting news!

And to all guys around with something not working: Do you know why it is called “Beta”? Cos it is beta then nothing.

Good step in the right direction, will check on my PC later, though my bottlecneck seems to be CPU.

Saturn.6591:

Just the overwolf-plugin for teamspeak doesn’t seem to work with it for some reason.

I’d expect this is not only about overwolf, but about many (if not all) overlay plugins. There seems to be technical problems with it, don’t remember the details.

Finally some usefull Gratz for ANET, and I hope next big surprise is dx11/12 game client.

People know what beta is. I see very few people complaining. Most people are either praising the client, or posting encountered bugs so ANet can fix them before the client moves out of beta stage. If they don’t, ANet won’t know what to fix. Overall the discussion in the thread is polite, helpful and informative.

ZudetGambeous.9573:

Well I downloaded the client and put it in the GW2 directory and ran it…

I have no idea what to do now. There isn’t any error code or anything, windows just says no

You most likely use 32 bit Windows version. It can’t run 64 bit software.

Predator.1398:

ZudetGambeous.9573:

Well I downloaded the client and put it in the GW2 directory and ran it…

I have no idea what to do now. There isn’t any error code or anything, windows just says no

You most likely use 32 bit Windows version. It can’t run 64 bit software.

Nope, he’s just trying to run a 2kb file that isn’t the full client. He might have moved it without the download finishing or the download got cut off for some Internet reason.

Just placed the 64bit in the root directory, but when I press PLAY in the launcher, it crashes just when it should show the character screen (although the music is playing).
No issues with 32bit, opens up nicely as usual.

On my machine, memory usage is the only noticeable difference.
Around 900 000 k for the 32 bits version and around 1 285 000 k for the 64 bits version (standing idle in metrica province).

deltaconnected.4859:

If you’re getting nvlddmkm.sys crashes, try downgrading to 347.88 (980 and older) or 353.49 (980ti). That’s caused by something else so I doubt switching to x64 would help.

Ya, nothing helps much and no one has ever been able to pinpoint what that “something else” is or why the driver works fine for graphically heavy games like Watchdogs or Dishonored, but GW2 runs like a dog. It has been a persistent problem with nVidia hardware for over 10 years and it’s a friggin’ joke. It’s like a curse, once you have it, you never get rid of it.

This is something that the regular testing tools and benchmark tools do not touch. No problems indicated with Furmark or the eVGA stress tester, Intel CPU health check is clean, had the PSU checked twice at a computer shop, memtest86 is clean. It points to GW2 using some nVidia driver function that few other games use that is using some resource on the affected person’s machine that is broken, faulty or not there, again, that is not being used by most other games. 200+ games in my Steam library and this is the only one this happens to.

Still, I’m hoping the x64 client will help at least some.

This client works nice. Still have dips to 26 in full dragons stand but at least they are smooth 26 fps. I was maxing almost 7gb of ram there on the gw2-64.exe client. Now can we also please have a decent ui?

hope a developer can answer this when are you going to turn on high res character textures for the 64-bit client cause currently its not activated or turned on.

@danizmax

According to this topic
https://forum-en.gw2archive.eu/forum/support/support/Can-we-please-get-a-working-Mac-Client
i really don’t want to use the same client.

And by the way, Linux and Mac aren’t really similar.

I will try it when I get home, thanks Anet.
Info for trying it: backup your gw2 folder, for safety reasons, if something bad happens you will have a backup.
DirectX 11/12 will be improbable, as for DirectX 10 is possible, I remember in closed beta (or open beta) there was DirectX 10, but due to the checking software runing in the background to check for problems, it was unplayable.

This wont fix the crushses from people who don’t have a based x64 Computer, my computer is 32bit based, i can’t run x64 SO on my machine… and i have been constant crashes all day since Hot….

The “something” is just “attempted NVidia optimizations” lol. Nothing to do with GW itself. I’d list how painful surround has been as an experience (start menu far left on win10 since TPs, can’t disable surround to try non-surround without reinstalling, TW3 more broken with no fix in sight that makes the GW experience a pleasure, which says quite a bit given SLI+surround is broken for the newer drivers for it, among other less noticeable things) but it’d take up more than this page sooo…

Whatever you do just avoid the r355 branch and newer. Doubly so if you’re on SLI (it’s completely broken for it). Ideally 347.88 as that was the last time I had no NVidia-related crashes, and 353.49 if you’re on 980ti’s because it’s the newest driver that doesn’t suck for performance.

For Laptop users with multiple GPUs (Enduro/Optimus). You need to add the new executable file target to the HIGH Performance graphics mode otherwise you will be running on the Intel integrated cpu graphics as there are no games listed on the drivers known as GW2-64.exe.

That should be pretty obvious when your fps drops from 60 to 10.
Don’t know the exact method for Nvidia users but for AMD its as simple as going into the Switchable Graphics menu.

Btw for reference comparison im running an 7970m 2gb with 16gb of ram on W10 and I didn’t crash once since expansion release. I did have some 3s freezes from time to time which I guess is what was crashing some people.

PS:Also please give me Quaggan Freedom pls. :’(

So our group had the same problem as Honeymonster.7154 we crashed everytime we tried to load into fractals. We went back on the 32bit version and it worked again

That fix for FPS issues worked! Thanks Johan!

deltaconnected.4859:

The “something” is just “attempted NVidia optimizations” lol. Nothing to do with GW itself. I’d list how painful surround has been as an experience (start menu far left on win10 since TPs, can’t disable surround to try non-surround without reinstalling, TW3 more broken with no fix in sight that makes the GW experience a pleasure, which says quite a bit given SLI+surround is broken for the newer drivers for it, among other less noticeable things) but it’d take up more than this page sooo…

Nahh, attempted NVidia optimizations is not it…the driver crash issue has been a problem with GW2 since at least driver version 306.97 and January of 2013, then it would get worse with newer drivers so I stuch with 306.97 for a LONG time, periodically trying newer ones, then it seemed to stabilize a bit with driver 332.xx I believe, but you can’t stay on ancient driver versions for the sake of a single application. GW2 is literally the ONLY game I have that I’ve ever seen this type of crash in. Ultimately I was forced to upgrade my driver again because ESO would not work on on the older driver and flip-flopping drivers is a PITA.

The game crashes immediately when I click on gw2-64.exe. Here is the error. Happens every time. the 32 bit exe is fine.

• Crash <—*
  Exception: c000001d
  App: Gw2-64.exe
  Pid: 11616
  Cmdline:
  BaseAddr: 000000013F760000
  ProgramId: 101
  Build: 54655
  When: 2015-11-04T22:34:20Z
  Uptime: 0 days 0:00:00
  Flags: 0

• System <—*

This is really great gang. Keep up the god work! threatens whip

Can’t say I experienced any problem with 780 SLI for over two years, I actually don’t remember a single crash that wasn’t an unstable OC til r355 (and couldn’t downgrade low enough after upgrading to the 980ti’s). I do agree on staying on old drivers though… not looking forward to doing some minor ‘changes’ to SWBF’s client to skip the forced driver check when it launches…

Anyway, outside of a 1second hiccup every now and then, so far so good on the x64 client.

joaosequeira.2184:

This wont fix the crushses from people who don’t have a based x64 Computer, my computer is 32bit based, i can’t run x64 SO on my machine… and i have been constant crashes all day since Hot….

Try dissabling some graphic effects on the game, the new maps are a heavy load on graphic assets and are big than usual. This is also a problem due to the fact that some calculations that can be done on GPU are beeing done on on the CPU. CPU is a huge bottleneck on gw2, even if you have a top of the line GPU, if your CPU is weak, you will have problems(this is my problemas, I have an i3).
When the 64bit client is out, I would like Anet to adress this issue.

About 10 – 20 FPS decrease with the 64 bit client on a dual SLI 780 rog tytan.

Hope attachment helps

Just tried this, seems to be working well. Noticing a small performance increase as well as big performance increase when I come across zergs of players. Normally if I turn my camera really fast the game will shudder hard for a second while it loads all of the new models but that seems to be significantly improved now.

Johan Skold.4708:

SirJack.4760:

Going back to the 32-bit client doesn’t seem to be an option, as the client now states it can no longer detect a valid .dat file in the directory. Guess I’ll have to look up my backup and redownload the past few months…

Sorry that happened to you. We’ve tested going back and forth internally and never encountered that issue. Could you try repairing your files?

I used a previous dat-file and downloaded the last few patches. That seems to have fixed it, so I guess it was an issue with the .dat. 64-bit version still ruins my framerate though.

deltaconnected.4859:

Whatever you do just avoid the r355 branch and newer. Doubly so if you’re on SLI (it’s completely broken for it). Ideally 347.88 as that was the last time I had no NVidia-related crashes, and 353.49 if you’re on 980ti’s because it’s the newest driver that doesn’t suck for performance.

Why though? What is the instability? What typically causes it? Why does it work fine for some and not for others? These are question that no one EVER seems to be able to answer. ANet blames the hardware, nVidia/eVGA blames the software or other non-GPU hardware, the techs where I bought the computer blames ANet because all their test show the hardware is clean…it’s a vicious circle while my computer continues to crash along.

The biggest question is Will the x64 version of the client help? You say, “no”, but what does ANet say? Can’t make it much worse I guess since I typically crash every 15 minutes or so.

Would it be possible for the client to tell us that it is the 64bit client in game? Say in the F11 options? Thanks.

This is absolutely fantastic! Thank you so much engineers!
With the 32x client, I was getting 6-10 FPS in HoT areas and LA, 11-17 FPS elsewhere. With the 64x client, using the same graphics settings, I’m getting 26-30 FPS in HoT & LA, solid 30 FPS elsewhere. I’m using an Alienware M14x laptop running 64x Win7.

Again, this is amazing! Thank you!