Single Character won't load in specific zone....

[Jalico]

so it seems with a naked body i got further but here is the output from zoning over:


Requesting initialization data.
2016-08-14 12:25:47 DoMainLoop: just before first while(!ReadyEnterWorld).
2016-08-14 12:25:48 Networking: connection terminated [client[You must be logged in to view images. Log in or Register.]isconnectReasonOtherSideTerminated,server: DisconnectReasonNone]
2016-08-14 12:25:48 disconnected at C:\EQ\EverQuest\EverQuest.cpp:17973 (char. select) DisconnectReasonOtherSideTerminated,DisconnectReas onNone
2016-08-14 12:25:48
2016-08-14 12:25:48 Character is Chalica.
2016-08-14 12:25:48
2016-08-14 12:25:48 YOU HAVE BEEN DISCONNECTED.
2016-08-14 12:25:48
2016-08-14 12:25:48 end of DisplayScreen
2016-08-14 12:25:48
2016-08-14 12:25:51 Cleaning up groups.
2016-08-14 12:25:51 Failed to send message 3702: connection lost.
2016-08-14 12:25:51 Connection status 2/1 [DisconnectReasonOtherSideTerminated,DisconnectReas onNone] before teardown.
2016-08-14 12:26:01 Networking: Connection Closed [0] with 23 pending bytes.
2016-08-14 12:26:01 Stopping world display.
2016-08-14 12:26:01 Attempt to send message 30546 on a void connection.
2016-08-14 12:26:01 Exiting normally.
2016-08-14 12:26:01 Cleanup 1
2016-08-14 12:26:01
2016-08-14 12:26:01 Cleanup 4
2016-08-14 12:26:01
2016-08-14 12:26:01 Cleanup 5
2016-08-14 12:26:01
2016-08-14 12:26:01 Cleanup 6
2016-08-14 12:26:01
2016-08-14 12:26:01 Cleanup 7
2016-08-14 12:26:01
2016-08-14 12:26:01 Cleanup 8
2016-08-14 12:26:01
2016-08-14 12:26:01 Cleanup 9
2016-08-14 12:26:01
2016-08-14 12:26:01 Cleanup 10
2016-08-14 12:26:01
2016-08-14 12:26:01 Resetting UI.
2016-08-14 12:26:01 Resetting character select UI.
2016-08-14 12:26:01 Resetting game UI.
2016-08-14 12:26:01 UI Reset.
2016-08-14 12:26:02 Cleanup 11
2016-08-14 12:26:02
2016-08-14 12:26:02 Picking a default resolution, desktop is 1920 x 1080, 32 bits
2016-08-14 12:26:02 Ratio is 1.78
2016-08-14 12:26:02 Resolution was capped at 1280 x 720
2016-08-14 12:26:02 Resolution verified 1280 x 720, 32 bits ... diff was 1000 from 0 modes
2016-08-14 12:26:02 Resolution selected 1280 x 720, 32 bits
2016-08-14 12:26:02 CRender::InitDevice: Using 32bit mode.
2016-08-14 12:26:02 CRender::InitDevice: Using vsync 0.
2016-08-14 12:26:02 CRender::InitDevice: Using 24bit depth buffer with 8 bit stencil.
2016-08-14 12:26:02 CRender::InitDevice: HardwareTnL Enabled.
2016-08-14 12:26:02 Using hardware vertex shaders.
2016-08-14 12:26:02 Initializing render system.
2016-08-14 12:26:02 Trilinear Mipmapping available.
2016-08-14 12:26:02 Vertex Shader Version: 3.0
2016-08-14 12:26:02 Pixel Shader Version: 3.0
2016-08-14 12:26:02 Initializing engine internals.
2016-08-14 12:26:02 CRender::InitDevice completed successfully.
2016-08-14 12:26:02 Parsing INI file ./eqlsUIConfig.ini
2016-08-14 12:26:02 INI file ./eqlsUIConfig.ini loaded.


sold a bunch of stuff, deleted others, put all my high ticket items and wearables in bank...... booted but looks like its further than last time

gonna keep playing with it, wonder if the devs know about this issue.

[paulgiamatti]

The thought occurred to me that it might have something to do with something in your bank. Felwithe and Greater Faydark both have bank vendors - as I understand it, all of your banked item data is attached to those vendor NPCs.

It's a long shot, but maybe for some weird reason it's okay with you zoning *into* a zone with a bank vendor (Felwithe), and then glitches out when you try to zone out of the zone containing the bank vendor and puts your character in a bugged state.

I guess a way you could try to verify this is get moved to a different zone other than Felwithe or Greater Faydark with a bank, like North Freeport, and then try to zone over to West Freeport.

[Jalico]

i had the same thing happen from lfay and butcher too..... I think i'm going to try and see about transferring all my items to a newbie char and then moving around..... it may not be items at all but instead character files on server...... hopefully this will be fact finding.... i'll let you know what happens

[joppykid]

This is a crazy bug! I hope you're able to get it corrected.

[Tupakk]

It really sounds like file corruption.

Honestly I would look for another source of Titianium.

Maybe try making a whole new account and see if that has anything to do with it.

[urbanbo]

I am having this EXACT same issue and it just started last night. I camped in GFAY and am now unable to log back in. The same thing happens to me, it will pause and then kick me back to the login screen (with the occasional "you have been disconnected"). I can log into all other characters in other zones. There is something with GFAY only. I have tried all the old fixes posted for this issue like turning loading art off and turning cached mode off. I guess I will need to petition to get moved into Felwithe tonight.

[joppykid]

Originally Posted by Tupakk [You must be logged in to view images. Log in or Register.]

It really sounds like file corruption.

Honestly I would look for another source of Titianium.

Maybe try making a whole new account and see if that has anything to do with it.

I think it is but I think Paul hit it on the head with being a server-side corruption. A good way to test this would be to try logging in on another computer with a different install and seeing if the result is different. If it was local file corruption, clearing out the characters .ini/config file would/should fix the issue.

[joppykid]

Woot, Post #1000 ^ lol

[urbanbo]

Originally Posted by joppykid [You must be logged in to view images. Log in or Register.]

I think it is but I think Paul hit it on the head with being a server-side corruption. A good way to test this would be to try logging in on another computer with a different install and seeing if the result is different. If it was local file corruption, clearing out the characters .ini/config file would/should fix the issue.

I have not deleted the .ini/config file. Will try this tonight after work.

[Tupakk]

I think if it was server side everyone would have issues. I think it might be a mix of bad ini and server side.

@sirken ( if this works)