BUG: Zone Loading Screen Hang = "failed teleport"?!

[Bjond]

Tried to zone into e.star cavern and got this.

(Dungeon Master): This small cavern near Eveningstar conceals an entrance to the depths of the Underdark. Once held by the Drow, the cave is now guarded by the Purple Dragon Knights.
(Error): Recovering from failed teleport...

Turns out if you type /quit at the loading screen, the yes/no kills the loading screen and shows the UI again. That in turn permits you to read chat and otherwise interact with the UI .. and to see just what is causing the loading screen hang itself.

I've never noticed the message from an actual failed scroll/spell teleport, but I'm wondering if that isn't exactly the same thing going on here (ie. failure by design, applied a bit broader than intended) .. yet it doesn't punt you into the sky above market, perhaps because it's not a scroll/spell teleport.

Anyway, once you see the "failed teleport..." bit after trying to zone, it won't ever come back. It's permanently hung -- time to kill the client.

[adamkatt]

Yeah ive known about this for years.

[YUTANG75]

Yup. Whenever you get stuck on a loading screen for a while its worth doing /quit to check for the message, if its not there you will zone in eventually, otherwise it's dead.
I find it amusing the message is "Recovering from failed teleport..." because I don't think I've *ever* seen it actually recover... I almost wish instead of printing an error to the chat that you'll never see (without doing the trick) it instead just killed the client with a suitable critical error message.

[kmoustakas]

And once you kill the client and restart usually the chat isn't working for quite a while. I wonder how those are related

[LightBear]

And once you kill the client and restart usually the chat isn't working for quite a while. I wonder how those are related

I wonder if it would help if I kill some service besides the DDO process tree.

I have no idea which service that would be then.

[drex81]

And once you kill the client and restart usually the chat isn't working for quite a while. I wonder how those are related

The zone transition failure probably prevents a clean log out from the chat server. So you are left with some type of dangling session. Which probably interferes with the non-tell channels. Eventually the dangling session information clears and the local client is able to reestablish a clean connection. Not sure if the session would have a time out on it or if they have process that runs every ## minutes to clean things up.