• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

The Official Guild Wars 2 thread

log in....NOW. GO GO GO GO GO....

/bah working
//maybe able to log in for a couple hours later
 
I am interested in seeing if they've come up with a solution for parties being split into overflow queues. That was one of my only frustrations with the last BWE.
 
I am interested in seeing if they've come up with a solution for parties being split into overflow queues. That was one of my only frustrations with the last BWE.

They said that instance switching was off.
But yeah, it was really annoying.
 
Sorry if already posted, I thought it was this game but can someone confirm there's a known bug with the menu/character creation screen and not limiting fps?

I was making a new character and man, my gpu fan started to get REALLY loud and i alt tabbed to look at evga precision and saw the temp at 93!

I get into the game and play and the temp hovers around mid 50'sih. Seems like I remember reading in this thread (but cna't remember if it was this or another game) about the menu screen having a bug that doesn't limit the frames drawn and it goes extremely high.

One thing that really bugs me is the fact that for some strange reason you can't use the mouse wheel to zoom in/out if you are moving seems rather weird. My mouse cursor in game keeps disappearing too.
 
Sorry if already posted, I thought it was this game but can someone confirm there's a known bug with the menu/character creation screen and not limiting fps?

I was making a new character and man, my gpu fan started to get REALLY loud and i alt tabbed to look at evga precision and saw the temp at 93!

I get into the game and play and the temp hovers around mid 50'sih. Seems like I remember reading in this thread (but cna't remember if it was this or another game) about the menu screen having a bug that doesn't limit the frames drawn and it goes extremely high.

One thing that really bugs me is the fact that for some strange reason you can't use the mouse wheel to zoom in/out if you are moving seems rather weird. My mouse cursor in game keeps disappearing too.

Pretty sure that was a Starcraft 2 error. Might affect other games. It was fixed in a nvidia driver I thought? It literally caused some GPU's to fry at the time.
 
Pretty sure that was a Starcraft 2 error. Might affect other games. It was fixed in a nvidia driver I thought? It literally caused some GPU's to fry at the time.

FFXIV had a small "patching content" window that was Direct X and would render at multiple thousands of FPS on some systems. This was a good cause of GPU squealing, good times :D
 
Last edited:
They must have turned on graphics optimization because the game is silky smooth now even at full graphics settings. Wonderful.
 
They must have turned on graphics optimization because the game is silky smooth now even at full graphics settings. Wonderful.

Plays the same for me as the last client/beta. Run into Divinities reach, super CPU limited.

On another note, had to stop playing early for work Arg! This game is awesome. I cannot decide which profession to play lol. I like that you can play short or closs range on all of them, makes it very interesting.

Can't wit until the next beta!
 
Plays the same for me as the last client/beta. Run into Divinities reach, super CPU limited.

Interesting. Maybe it's the drivers? I think I've installed Catalyst 12.4 since the last beta weekend. I'm running a 7970 with a i5-2500k at 2560x1600 resolution, nothing overclocked. It was stuttering for me last time but now, even in battles, it's smooth like Guild Wars 1. I'm happy!
 
Just crashed out of the game and couldn't log back in. Went to the beta forums and it says the stress test is over. Thought it ended at 9 pm PST but it was EST. Oh well it was fun.
 
I got it to work with my 20/30/20 setup with SoftTH it was freaking awesome!!! I still had major server lag but fps was a lot better then the last beta.
 
Interesting. Maybe it's the drivers? I think I've installed Catalyst 12.4 since the last beta weekend. I'm running a 7970 with a i5-2500k at 2560x1600 resolution, nothing overclocked. It was stuttering for me last time but now, even in battles, it's smooth like Guild Wars 1. I'm happy!

I haven't updated my drivers since the last one. Performance seemed smoother, but there were also a lot less people around... so much for a 'stress test'.
 
I haven't updated my drivers since the last one. Performance seemed smoother, but there were also a lot less people around... so much for a 'stress test'.

Running a "stress" test on a weekday afternoon was just about stupid. I got to play for about 30 min and there wasn't nearly as many people playing as the last beta weekend. While lag was better this time, the framerates weren't better. At the default midrange settings on a i5 2500K Sandy @ 3.8GHz and a 7950 @ 1GHz, I was seeing 60fps V-sync capped, but when I moved the slider to the right for maximum graphic detail, frames would drop to high 20's and low 30's just like it did in the last beta weekend. The game looks decent but not good enough for those kind of framerates. There's no excuse for that.
 
sweet pics!

Anyone else already figured out their classes?

Think this is mine:

Warrior ---> Human
Mesmer --->Asura
Norm --> Guardian
Charr ---> Ranger
Sylvari --> Necromancer
Asura --> Engineer (Buy a slot? lol)
 

Herp derp....

2iifom1.jpg
 
this is the same old build.

Why do you think it's the same? Because they didn't release a new client executable? But that's unnecessary since the game patches itself upon launch. Maybe our definitions of "build" differs but files were downloaded and the client patched when I launched the beta the night before the stress test. I don't know what changed but something did change. It wasn't the same build used during the beta weekend.

Running a "stress" test on a weekday afternoon was just about stupid. I got to play for about 30 min and there wasn't nearly as many people playing as the last beta weekend. While lag was better this time, the framerates weren't better. At the default midrange settings on a i5 2500K Sandy @ 3.8GHz and a 7950 @ 1GHz, I was seeing 60fps V-sync capped, but when I moved the slider to the right for maximum graphic detail, frames would drop to high 20's and low 30's just like it did in the last beta weekend. The game looks decent but not good enough for those kind of framerates. There's no excuse for that.

I'd give the developers the benefit of the doubt. If all they wanted to do was try to break their servers, they could have announced the test with more advance notice or sent out emails to every beta participant notifying them of the stress test or held it on weekend, all steps they took with the last beta event that was labeled a "stress test" (the last stress test was on a Friday). It seems to me that not doing these things was very deliberate, perhaps because they had other technical goals in mind other than simply trying to overload everything. Or maybe they had lots of people logged on but their tinkering really did the job and we didn't notice.

It's interesting, I've seen other people on other sites say that framerate was better but others like you say there was no difference. I still think it's too early to condemn the developers for the framerate - it sounds like you think the level of performance you saw will be the same at launch but I think that's premature. It's still a beta and there may be months of development still to go.
 
Last edited:
The NDA was lifted, what is he going to get banned for?

//Update: Looks like there is a private beta, the shot is from the private beta.

Yeah, I believe the NDA was lifted for those in the beta weekends. I imagine that is not the case for closed beta testers.
 
The filepath seems unusually precise for a regular Joe who got invited into the beta. Who creates a folder labeled "Guild Wars 2 Gw2Dev"? Makes me think he may be an Arenanet employee.
 
Last edited:
The filepath seems unusually precise for a regular Joe who got invited into the beta. Who creates a folder labeled "Guild Wars 2 Gw2Dev"? Makes me think he may be an Arenanet employee.

It's probably a folder created by the build of the game and not manually created by the person.

If he is an employee then being banned is the least of his concerns.
 
It's probably a folder created by the build of the game and not manually created by the person.

Ah could be. I guess I was thinking about the instructions for the beta events where participants had to manually create their own folders. But the closed betas could very well be using a different, automated installer.
 
Why do you think it's the same? Because they didn't release a new client executable? But that's unnecessary since the game patches itself upon launch. Maybe our definitions of "build" differs but files were downloaded and the client patched when I launched the beta the night before the stress test. I don't know what changed but something did change. It wasn't the same build used during the beta weekend.

ArenaNet specifically stated (was a twitter post iirc) that the stress test would be using the same build of the game as the BWE, so they could hold it as a control to test the backend changes that they made on their netcode.
 
I haven't played the first one yet but i have herd great things. The second one looks fantastic. But the question is, is their a story line to it?
 
Back
Top