EQInterface Forums - Possible EQW-specific UI conflict :\

01-29-2003, 10:42 PM	#1
Thossy A Bat Join Date: Oct 2002 Posts: 1	Possible EQW-specific UI conflict :\ While this isn't an EQW help board, I figured a post here may be in order since my problem seems to be UI-related. With any luck someone on the multiple boards I've posted on may have an answer for me. Anyway, on to the problem.. I'm using Vert 2.2, fully patched with everything and these boards, and edited using Cairenn's fixes. In fullscreen/SoEwindows my ui checks out fine, I get no error messages saying that it is not compatable. However, when I try to load the UI in EQW, I get a clean boot to desktop, with no error message at all. When this happens my UIErrors.txt file gets updated, but all it contains is the time/date stamp of the latest attempt to load (in EQW), there are no details about specific errors. I get the same results using both 16 bit and 32 bit color depths. Color depths always match in eqw.ini and eq.ini, and in-game resolution is the same as desktop resolution. I've spent hours searching the boards for another poster with this problem, but with no luck. So forgive me if I missed something in my search. Any help with this problem would be appreciated, and thanks for tolerating the (possible) off topic post.

01-29-2003, 11:05 PM

kitsinu

A Shissar Defiler

Join Date: Dec 2002

Server: Xegony

Posts: 179

I have troubles with the Vert 2.2 on SidlWidl and found how to fix it so I don't have the trouble. It might be the same issue, so try this out. The only change I made was to put the comment down a few lines. Sounds iffy for your problem, but who knows.

Attached Files

equi_playerwindow.zip (2.1 KB, 5 views)

01-30-2003, 10:11 AM	#3
Yelara A Shissar Defiler Join Date: Aug 2002 Server: ayonae ro Posts: 198	I have the exact same problem, only I'm using Sars version 4.0 (with his 1/20/03 patch installed) If I log using a totally default UI I can use EQW fine now, as long as I have no extra windows created etc. As soon as I attempt to load any skin other than default I crash to desktop. Does anyone have any suggestions regarding what changes, if any, can be made to the UI to make it EQW compliant? I'd love to be able to go back to using EQW but not at the expense of my UI. I can't play in default UI __________________ Je t'aime encore, Roguette

01-30-2003, 09:13 PM	#4
kitsinu A Shissar Defiler Join Date: Dec 2002 Server: Xegony Posts: 179	Some people were mentioning that they were having crash problems and were able to solve them by deleting the UI_character_##.ini file. Setting up your windows again is always a pain though, so you might want to back the .ini file up before doing anything.

02-10-2003, 05:23 PM	#5
ethion A Gray Wolf Join Date: Nov 2002 Posts: 5	eqw I'm also having the same problem. if i run default ui eqw works fine. if i load my modified nightelf it crashes to the desktop when i load my character. my ui is clean with no errors. i scaned my UI*.INI file to makesure i had no neg numbers... the end of my dbg.txt file shows the following... [Mon Feb 10 14:02:02 2003]00559:ProcessGame. Beginning main loop. [Mon Feb 10 14:02:04 2003]00560:Fatal Error Occurred in mainthread Code = c0000005 Addr = 00404158 [Mon Feb 10 14:02:04 2003]00561:Process was trying to READ invalid data. [Mon Feb 10 14:02:04 2003]00562:Invalid access occurred at virtual address 0x0023000b. [Mon Feb 10 14:02:04 2003]00563:Fatal error occurred in mainthread! (#629) [Mon Feb 10 14:02:04 2003]00564:Graphics DLL Loaded: Version 1.1.47 (DX8) Last Build Date: Jan 29 2003 11:39:32 [Mon Feb 10 14:02:04 2003]00565:Crash (char = Ethion, zone = poknowledge) [Mon Feb 10 14:02:04 2003]00566:Local Player's World location at time of crash: 63.000000, 982.000000, 4.300000. [Mon Feb 10 14:02:04 2003]00567:Gamestate at crash = 253 [Mon Feb 10 14:02:04 2003]00568:1 processor(s) of type 586. Physical memory = 1024 Megs. [Mon Feb 10 14:02:04 2003]00569: AMD 2191 I've read that it is a UI problem probably related to some minor xml error. I've also read that lots of trial and error loading xml files one at a time can isolate the problem file. has anyone done this? perhaps if it is know which file is a problem the error might be identified. Ethion