(edited by Zeffy.3984)
Game suddenly crashing when dying armor.
Bumping this because I’d like to know if anyone else is having problems with the dye remover.
Hi did you tried the new nvidia driver 306.23 WHQL
http://www.nvidia.com/Download/index.aspx?lang=en-us
Hi did you tried the new nvidia driver 306.23 WHQL
http://www.nvidia.com/Download/index.aspx?lang=en-us
I haven’t. I read something about Ambient Occlusion causing problems for GW2 in the latest driver, so I was hesitant to try it. I could always download it and see for myself though. :3
(edited by Zeffy.3984)
I have the exact same problem and i am using the newest drivers from nvidia. I dont think its related.
Im using amd drivers, and had not had this problem prior, but today it suddenly started up for me. Luckily I remembered this thread.. so its not isolated to just Nvidia it seems.
Had this exact same problem, only when dying the “Noble” Medium Armor Set, but I found a workaround. Just toggle dye mode off instead of closing down the character screen, it won’t crash.
Are you sure you don’t have a corrupted installation?
Maybe the problem is inside your downloaded GW2.dat that contains errors.
Windows 8 Professional
Same problem, its not a corrupted install. Have been fine till i updated to the new nvidia drivers, now random crashes and dye armor crashing.
EDIT – Yea, im still getting the issue every time i dye the armor, but if you get out of DYE MODE before you X out of the screen, it wont crash. It wont fix random crashes, obviously (im still getting some of those now) but the little work around thing, works.
(edited by Kahless.8965)
Game suddenly crashing when dying armor.
in Account & Technical Support
Posted by: Cpt Kamikaze.2506
I am also experiencing this issue, and can confirm exiting out of Dye Mode prior to closing the screen will not crash the game.
I just duplicated this about 20 times. I crash every single time I remove the dye from my armor and close the window. I can dye it fine, but removing it will result in a crash 100% of the time after closing the hero screen. The only way to fix it is like other suggested, exiting out of Dye Mode prior to closing the Hero screen. I have the latest AMD drivers. This definately did not happen last week because I’ve never exited out of dye mode before closing the hero screen. This is a new bug.