Guild Wars 2

Good morning all,

I am trying to use DXTory to record my adventures. It’s working great in every game except this one.

Whenever I press the record button (currently F12) it causes either my video driver to crash and fail, forcing me to kill the GW2 process, or it immediately reboots my computer. I’ve tried different versions of the software, different codecs, and different drives to record to, none of which solves the problem. I heard somewhere that something that hooks graphically into GW2 can cause problems, but I recorded before using MSI afterburner with no problems, so I’m wondering what’s changed.

If anyone is using DXTory successfully, can you post your settings and version to help me out? If anyone has any other ideas on why it would be crashing like this, I’m all ears.

Thanks in advance.

What veideo drivers u have installed?

13.2 Beta’s from AMD.

7970 Video Card.

That is the problem. I allready submited a formal survey form explaining the issue to AMd support. Rollback drivers if u want to record untill they fix that. I also tryed every single screen capture sofware, none worked

Oh wow really? The rest of the games I tried record just fine. How far back did you need to go to record? 13.1’s? 12.12s?

Let me know, thanks.

http://www.guildwars2guru.com/topic/79950-catalyst-132-beta-driver-and-bandicam-issues/

Apparently this is reported here as well for Bandicam. I’ll have to let the dxtory developer know as well, see if there’s a fix on his end.

i had 12.11 before and recording worked just fine, cannot really tell u if 13.1 will work but i would say there is a 95% chance 13.1 drivers work properlly.

None of them works for some reasson (recording programs) i tryed them all with no luck i didn’t really wanted to roll back the drivers since they perform flawleslly :S

Yeah I agree, the new drivers are awesome. I’ll probably try the 13.2 leaked betas i had on there a week or so ago (which had the GW2 improvements) and see how that goes, then try backwards from there. I don’t NEED to record right now, but I’d like to be able to point AMD in the right direction as far as when it was last functioning as intended.

Thanks for the heads up.

Yeah, make sure u fill a formal bug report at the AMD drivers troubleshooting section, it would be pretty bad if the don’t fix when the drivers go live.

It works perfectly in the 13.1 WHQL drivers. So it’s definitely a 13.2 issue.

Where is the bug submission section? On AMD’s site?

Yeah at the drivers section on AMD site