Guild Wars 2

After the new patch, whenever i open the BLTC everything on the screen freezes for about half a second, then everything resumes as normal. Checked on every other window, the BLTC is the only one that does it.

Same here, although it freezes for 2 or 3 seconds for me

Same as well. Doesn’t really bother me.

Same here. 2 to 3 seconds freeze.

~Also of note is that you cannot move when you click on something to sell/buy.~

CC Danicia.1394:

Here’s an update: https://forum-en.gw2archive.eu/forum/info/updates/Game-Update-Notes-January-21-2014/first#post3530674

just applied the most recent update…still getting that second of freeze

From what I recall it has always happened to me every time I open TP. It always have frozen game for 1 or 2 secs so I even have thought it’s a “normal” behavior (given that TP uses a external application to work [awesomium.exe]).

When I access BL from any direction, I first get a black screen, then it appears I leave the game for my desk top for a few seconds, then the bl opens. This has been going on for a few days now.

With the lastest trips to Lornar Pass— and trying to kill the watchwork puppet, I keep getting booted from the game and game freezing.

shadow.6174:

From what I recall it has always happened to me every time I open TP. It always have frozen game for 1 or 2 secs so I even have thought it’s a “normal” behavior (given that TP uses a external application to work [awesomium.exe]).

I know for a fact that it hasn’t always done this, I run the champ trains a lot and sell stuff on the run/jump and ive never had it freeze like that each time.

It only started with the patch today for me, never used to freeze at all. Latest update didn’t fix

I’m glad this issue was jumped on and fixed right away, and not bugs that actually affect the game, especially ones that affect the core of the game like combat.

Even a red banner post for such a non issue thread, its outstanding.

Even after the 3rd build today.. still doing it. But like I said, doesn’t bother me.

UPDATE TO THE ISSUE: After all the patches yesterday this is still happening, i also noticed if you are moving and trying to sell something the second you click “Match lowest seller” it stops your movement. Really frustrating when trying to sell stuff on the run.

UrMom.4205:

UPDATE TO THE ISSUE: After all the patches yesterday this is still happening, i also noticed if you are moving and trying to sell something the second you click “Match lowest seller” it stops your movement. Really frustrating when trying to sell stuff on the run.

Hey, came here to post about this issue. Previous to this update I was always able to buy/sell in the TP window while on the move, especially useful during wvw but post update it is like you said, freezes player movement the second you click on anything in the window. Very frustrating. It is not fixed even after these numerous updates. There was just one a few minutes ago and this issue still persists.

Just to inform the team that this is happening still.
Upon rightclicking an item and select the option ‘Sell on TP’ your computer will freeze.

To add my problem – when I try to open the TP my game crashes.

Mine crashes the game as well, now, frequently, since the madness update.

UrMom.4205:

CC Danicia.1394:

Here’s an update: https://forum-en.gw2archive.eu/forum/info/updates/Game-Update-Notes-January-21-2014/first#post3530674

just applied the most recent update…still getting that second of freeze

same here.

Opening the TP had always caused a little bit of a lockup as the running awesomium_process.exe accessed the TP server and loaded graphics, which also used CPU, but it was not really all that bad, but noticeable.

However, the reason for the recent increase in very noticeable lag/lockup/delay when opening the TP is because the awesomium_process.exe used to launch upon opening the TP for the first time upon entering the game and stay running the entire time you played and then be closed upon exiting the game. Apparently, in addition to the serious issue of the BLTP interface disabling keyboard (chat/movement) binds when being interacted with, the awesomium_process.exe is launching when you open the TP and then being closed once you exit the TP…having to relaunch the process every single time you open your TP up during gameplay. This will cause a second or three of locking up while the process is executed and accesses the TP server. I think they made this change so the process doesn’t eat resources for the entire time you are playing just because you used the TP once. I think they tried to improve performance by closing the process when not in use, but underestimated the frequency at which players access the TP…leading to constant relaunching of the program.

StinVec.3621:

Opening the TP had always caused a little bit of a lockup as the running awesomium_process.exe accessed the TP server and loaded graphics, which also used CPU, but it was not really all that bad, but noticeable.

However, the reason for the recent increase in very noticeable lag/lockup/delay when opening the TP is because the awesomium_process.exe used to launch upon opening the TP for the first time upon entering the game and stay running the entire time you played and then be closed upon exiting the game. Apparently, in addition to the serious issue of the BLTP interface disabling keyboard (chat/movement) binds when being interacted with, the awesomium_process.exe is launching when you open the TP and then being closed once you exit the TP…having to relaunch the process every single time you open your TP up during gameplay. This will cause a second or three of locking up while the process is executed and accesses the TP server. I think they made this change so the process doesn’t eat resources for the entire time you are playing just because you used the TP once. I think they tried to improve performance by closing the process when not in use, but underestimated the frequency at which players access the TP…leading to constant relaunching of the program.

interesting….if that’s the case…looks like were stuck with it like this…bummer….