Second account LDs at frontier keeps.

[Margaret]

I have two fairly good spec computers that I switch between when running two accounts at once, and usually have no problems with it - I'm on a DSL connection, so bandwidth is not a problem.

However, lately I've discovered an odd bug whenever I enter one of the frontier keeps - Svasud Faste or Vindsaul Faste - with the second character running behind me: the moment I enter the Svasud or Vindsaul 'zone', the second character stops following me and runs in a straight line through the wall, and then proceeds to linkdie.

Or at least, that's what it seems like from the main character's point of view.

The really odd thing is that when I switch to the second computer, I'm still following the main character. I can see chat messages, I change direction when the main character changes direction, and everything seems normal, but if I try to interact with anything non-chat related - opening a door with the lever, talking to an NPC, interacting with a merchant - nothing happens. From my second computer's end, I can even chat in main or /gu. But when my main computer sees the secondary 'linkdie', my secondary computer gets the LD screen and the message, "An error has occurred. The server closed the connection."

Anyone have any ideas what could cause this?

 

[Elendar]

I have two fairly good spec computers that I switch between when running two accounts at once, and usually have no problems with it - I'm on a DSL connection, so bandwidth is not a problem.

However, lately I've discovered an odd bug whenever I enter one of the frontier keeps - Svasud Faste or Vindsaul Faste - with the second character running behind me: the moment I enter the Svasud or Vindsaul 'zone', the second character stops following me and runs in a straight line through the wall, and then proceeds to linkdie.

Or at least, that's what it seems like from the main character's point of view.

The really odd thing is that when I switch to the second computer, I'm still following the main character. I can see chat messages, I change direction when the main character changes direction, and everything seems normal, but if I try to interact with anything non-chat related - opening a door with the lever, talking to an NPC, interacting with a merchant - nothing happens. From my second computer's end, I can even chat in main or /gu. But when my main computer sees the secondary 'linkdie', my secondary computer gets the LD screen and the message, "An error has occurred. The server closed the connection."

Anyone have any ideas what could cause this?

this is what i am getting when playing on my main pc, happens almost every time i use the toa or nf porting system, can't interact but can see whats happening for a while

 

[Boni]

Or at least, that's what it seems like from the main character's point of view.

The really odd thing is that when I switch to the second computer, I'm still following the main character. I can see chat messages, I change direction when the main character changes direction, and everything seems normal, but if I try to interact with anything non-chat related - opening a door with the lever, talking to an NPC, interacting with a merchant - nothing happens. From my second computer's end, I can even chat in main or /gu. But when my main computer sees the secondary 'linkdie', my secondary computer gets the LD screen and the message, "An error has occurred. The server closed the connection."

Anyone have any ideas what could cause this?

This is a standard LD nothing odd at all.

Your 2nd account is linkdead, its client is recieving no new info from the server and will do its best to show you what it thinks you are doing by *predicting* your new position, of course with no communication from the server you cant see the result of any actions like pulling levers or even going into sit down mode and everyone else will be still (or continusouly moving). To speedup the linkdead message just sit down or try and cast, your client will realise youve gone LD a lot quicker then...

The other PC that isnt linkdead is just extrapolating the position of your 2nd account, last thing it saw was that person moving forward, itll continue to update its local 'picture' from the main server and watch that character run off into the sunset.

Why your 2nd accounts is going LD isnt clear, but running into complex areas with lots of stuff going on (like the border keeps) will tip a machine over the edge and make it LD if its already having problems...

It sounds like you have 2 different machines? If they where both on the same PC I would have a few ideas..., but it sounds like that machine thats going LD (or do they both depending on whos stuck to who?) is running to slowly for whatever reason (bad connection, virus, low spec, disk space, memory, video card drivers etc are things to check for).

 

[Chilly]

no its a different type of LD, id say wait til new patch and see if its still broken then, if not rightnow it, iv no idea what could be causing that.

 

[Boni]

no its a different type of LD, id say wait til new patch and see if its still broken then, if not rightnow it, iv no idea what could be causing that.

Its a standard LD imo, just a client machine being a little slow about noticing. If you think this is different or weird perhaps you could tell us what happens when you linkdie normally and how that difffers?

The only strange thing here is that its taking a while before the client notices, but that can happen, the client is trying to recieve enough info to not resort to linkdying, depending on a lot of factors it can giveup realy quickly or take upwards of 30seconds.

 

[raid]

I have exactly same problem. When entering the border keeps, I get something which is a bit like LD, cant do anything but can see chat for a while. Later on it usually says "You have left castle sauvage" and "You have entered (null)" or some other weird area and after a while "error has occured, server has closed your connection blahblah"

This happened sometimes with old client when going to portal keep in emain for rebuff or whatever (never after porting, only when approaching the PK from outside), but now with NF it happens every time after releasing.