Blink and crash

[Demitre]

i've been in and out of the emu for a while now just decided to start playing again and have gotten everything set up and working correctly...
so far

1. fresh titanium edition installed (no patches)
2. fixed mouse bug stuck in top left corner
3. get all the way to login everything works great
4. login and see the public server list
5. 3-5 seconds later the game just ends, no errors or anything


i am running windows xp home, all drivers and everything are up to date, my roommate on him comp had gotten an uable to connect to server error.

any help would be more than appreciated and i appologize in advance if this is already a thread but after 5 hours of searching and fixing both computers i figured asking couldn't hurt...:D :D

[Sakrateri]

sorry cant help you there , I just saw the title and thought this was some kind of a new game, sounds like a cool name for one anyway!

[Theeper]

Have you ever been able to log into the server ?

What do the logs say ?

Are you using minilogin or the LS ?

[EyyySvenne]

I also got this just now. I was logged in on a server and was just gonna relog and the same thing started, except for it's 3-5 tenths of a second, but that's more likely to me having a fast computer. Rebooting didn't help.

On the loginscreen, hitting Alt+Enter to get windowed mode before logging in helped me get past it.

I'm using LS.

Logs/dbg.txt for a crash with full screen:
2007-07-29 20:47:17 Starting EverQuest (Build Oct 31 2005 10:33:37)
2007-07-29 20:47:17 Timezone: UTC+1h00m
2007-07-29 20:47:17 Loading graphics DLL.
2007-07-29 20:47:17 Parsing INI file .\eqclient.ini
2007-07-29 20:47:17 INI file .\eqclient.ini loaded.
2007-07-29 20:47:18 Initializing timers.
2007-07-29 20:47:21 Checking critical files.
2007-07-29 20:47:21 Initializing WinSock.
2007-07-29 20:47:21 Enumerating 3D devices.
2007-07-29 20:47:21 Found adapter #0 - NVIDIA GeForce 8800 GTX (6.14.11.6201)
2007-07-29 20:47:21 Adapter #0 - NVIDIA GeForce 8800 GTX :
2007-07-29 20:47:21 32Bit = 1, D32 = 0, D24 = 1, D16 = 1
2007-07-29 20:47:21 16Bit(565) = 1, D32 = 0, D24 = 1, D16 = 1
2007-07-29 20:47:21 16Bit(1555) = 0, D32 = 0, D24 = 0, D16 = 0
2007-07-29 20:47:21 Initializing keypress handler.
2007-07-29 20:47:21 Parsing INI file .\defaults.ini
2007-07-29 20:47:21 INI file .\defaults.ini loaded.
2007-07-29 20:47:21 Loading keyboard tables.
2007-07-29 20:47:21 Creating window.
2007-07-29 20:47:21 Checking display driver version.
2007-07-29 20:47:24 Activating window.
2007-07-29 20:47:24 Picking a default resolution, desktop is 1680 x 1050, 32 bits
2007-07-29 20:47:24 Ratio is 1.60
2007-07-29 20:47:24 Resolution was capped at 1280 x 720
2007-07-29 20:47:24 Resolution verified 1280 x 720, 32 bits ... diff was 1000 from 0 modes
2007-07-29 20:47:24 Resolution selected 1280 x 720, 32 bits
2007-07-29 20:47:24 CRender::InitDevice: Using 32bit mode.
2007-07-29 20:47:24 CRender::InitDevice: Using vsync 0.
2007-07-29 20:47:24 CRender::InitDevice: Using 24bit depth buffer with 8 bit stencil.
2007-07-29 20:47:24 CRender::InitDevice: HardwareTnL Enabled.
2007-07-29 20:47:24 Using hardware vertex shaders.
2007-07-29 20:47:24 Initializing render system.
2007-07-29 20:47:24 Trilinear Mipmapping available.
2007-07-29 20:47:24 Vertex Shader Version: 3.0
2007-07-29 20:47:24 Pixel Shader Version: 3.0
2007-07-29 20:47:24 Initializing engine internals.
2007-07-29 20:47:24 CRender::InitDevice completed successfully.
2007-07-29 20:47:24 Parsing INI file ./eqlsUIConfig.ini
2007-07-29 20:47:24 INI file ./eqlsUIConfig.ini loaded.

[techguy84]

Try to delete your eqconfig.ini file, or whatever that file was named. The one that stores all the settings for the client. It will rebuild a fresh one from scratch so it may fix your error.

Assuming this since you mentioned that going into windowed mode makes it work, proabably a resolution issue, which has been talked about in more than 50 posts on the boards.

[EyyySvenne]

Correction: Windowed mode only made the crash occur much later, i.e. 20ish seconds. Noticed this when i made something else for a few moments after logging in.

Thanks for the tip about the ini-file, makes sense thou since windowed mode uses other ini-settings than fullscreen. I'll think i'll wont just delete it thou, but instead try to figure out whats causing this by testing different settings.

[John Adams]

It's a safe file to delete, since the client builds it from a fresh install upon running anyway. But I agree, root cause is my sole purpose in life. ;)