Guild Wars 2

Recently decided to try out windows 10 tech preview, I noticed an issue after the 11/4 update, may be unrelated, but don’t remember if it happened before or after I installed Windows 10.

So, the game opens up audio plays, I’ll be in the game and the picture freezes, it acts like it’s still playing though, I can run around, use skills and can hear stuff like the game is still running, but the screen is frozen in place.

I’m currently running a R9 290x stock speeds, with the newest drivers, (updated to beta 14.9.2). Still freezing, I figure it’s just a bug that needs to be worked out so I thought I would give you guys a heads up

hummm .. start and force the game to run in windowed mode and see what happen

edit your shortcut :

…\Guild Wars 2\Gw2.exe" -windowed

Well, Windows 10 is a very brand new system and it’s not even officially released yet then I think it will take a while until games are adapted to the new platform. Also, as it’s still in preview state bugs can occur, either with the system itself and with any software running under it. I don’t think GW2 or any graphic cards vendors have official support for Windows 10 yet.

Hey thought I’d post my issue here too as it’s almost exactly the same,

I started getting this issue while previewing Windows 10 so I rolled back to my Win8 install but it’s still happening.

The glitch is as you describe, the game will freeze but you can still move your cursor and hear the sound in the background still rolling. It’s very frustrating so I’d like to get some sort of fix for this.

My specs:

Windows 8.1 x64
Intel 4790k
nVidia 780ti

All running stock speeds too.

Gw2 crashes for me right before the game even renders anything (I go from the launcher, to a black screen, maybe a millisecond of audio, and then the error report).

Using a 7850 with Catalyst 14.11.2 Beta; Windows 10 TP 9879.

Edit: Only occurs when GW2 tries to start or be switched to fullscreen mode. Windowed and Fullscreen Window modes work fine.

Friend said GW2 fullscreens fine for him on NVIDIA, so maybe this is just a case of driver incompatibility with AMD currently. Can’t really place fault on AMD too harshly though considering they don’t even support the OS yet.