Stabalize Wentworths


Adam_Alpha

 

Posted

Quote:
Originally Posted by Eiko-chan View Post
Factually incorrect. I have over 3 Gigs of RAM - the most 32-bit OSes can address - and I still have this problem. This is not an issue I can fix by installing more RAM.
Quote:
Originally Posted by Bud View Post
Im in the same boat here, my computer isnt bad but it isnt a NASA comp either. I have over 3 gigs also and yet, sometimes i have time to bio while waiting for the Market to open, particularly on DXP weekends.

I also get the "greyed out" bug(?) with some items, where you have to click the item and then it finally shows.
I too have 3GB, and get the issue every time I play very nearly.


"Null is as much an argument "for removing the cottage rule" as the moon being round is for buying tennis shoes." -Memphis Bill

 

Posted

I have played CoH with a full out 4 gigs of RAM gaming system with completely stripped down apps running. I have also played it on a system that choked to play CoH at all.

What I have found is this.
1)No MATTER what your computer, assuming standard residential high speed internet connection, you will ALWAYS have a chance to get kicked upon opening WW/BM.
2)This chance is significantly higher if you are using your swap file at ALL in ANY way as of opening it, and also higher if your computer struggles with the game.

Now, from a tech perspective, here is why:
Connection 1:mapserver
You click on WW rep
Connection 2IFFERENT server with auction info. This DIFFERENT server sends a raw data dump, as evidenced by the net stats filling to the top with green (or not green if packets are lost, usually green for me)
Connection 1:mapserver tries to keep communicating during this time. As the connection is being flooded, there is an appreciable chance it will fail to do so.

Sorry, NCSoft, it is NOT inadequate hardware nor poor configuration (while these factors make it worse, they are NOT the cause).

Now... There are three ways I propose this could be resolved.
1)throttle the speed at which WW/BM sends data. Configuration for this could be added to the game options.
If this were added to the game, it would allow ANYONE to access wentworth's and have settings where they would almost never be D/C

2)send a code to the mapserver stating that the client does not wish to talk to it until further notice when about to access the BM/WW. This means your view freezes until the data is sent.

3)A hybrid of these two solutions would be the throttle as well as the client informing the mapserver that it should use significantly more lenient timeouts.

Now... as far as not showing everything on initial opening of WW/BM, you CAN do so by leaving a search term in when you close it, BUT... the server will STILL send the data on all items because the filter/search is performed client side.


 

Posted

well, could make it easy and just type /unloadgfx or set up a macro for it. i know it is bugged right now but it still works somewhat and i have no prblem ever using the markets. i may get slow loads, but i never dc. all from just that silly little slash command. and i am running 2 gig of ram.


 

Posted

Quote:
Originally Posted by Nobylis View Post
Now, from a tech perspective, here is why:
Connection 1:mapserver
You click on WW rep
Connection 2IFFERENT server with auction info. This DIFFERENT server sends a raw data dump, as evidenced by the net stats filling to the top with green (or not green if packets are lost, usually green for me)
Connection 1:mapserver tries to keep communicating during this time. As the connection is being flooded, there is an appreciable chance it will fail to do so.
Except that it's not an issue of the connection being overloaded. It's an issue of your RAM being overloaded because it's getting a single huge data dump. Would you like to know how I know this? Because if it were an issue of connection instability, you would be logged off rather than simply having the game crash because it used up all of the available memory for it to run on so that the underlying processes no longer had space to run in. I've yet to meet anyone that hasn't solved whatever WW woes they've had (including my own) by just getting more RAM.

By the way, necroposting is against the forum rules. Please try to refrain from doing so in the future.