Chat windows strobing while tabbed out in EQ1

WinEQ 2.0 Lite discussion

Moderators: Lavish Software Team, Moderators

Post Reply
Barraind
Non-Subscriber
Posts: 1
Joined: Tue Sep 14, 2004 1:42 pm

Chat windows strobing while tabbed out in EQ1

Post by Barraind » Wed Jul 06, 2005 1:04 pm

While alt tabbing out from EQ1 (only while using wineq2.0), my chat windows begin pulsing dark black to my normal settings, constantly.

This doesnt happen in normal EQ windowed mode, and I havent had that problem before with Wineq2.7, but it is rather annoying, as I tab out quite often, and strobe lighting is not something I enjoy all that well.




WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP//2600.xpclnt_qfe.021108-2107
System Physical RAM: 607/1023MB
Page File: 1880/2462MB
Virtual Memory: 1947/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 2200+ @ 1792MHz
Video 1: \\.\DISPLAY1/NVIDIA GeForce FX 5200
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2600.0000
WinEQ: 2.08

Loaded Modules:
-----------------------------------
Module 0: c:\program files\everquest\eqgame.exe
Module 1: C:\WINDOWS\System32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: c:\program files\everquest\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\ADVAPI32.dll
Module 7: C:\WINDOWS\system32\RPCRT4.dll
Module 8: C:\WINDOWS\System32\WINMM.dll
Module 9: C:\WINDOWS\System32\WSOCK32.dll
Module 10: C:\WINDOWS\System32\WS2_32.dll
Module 11: C:\WINDOWS\system32\msvcrt.dll
Module 12: C:\WINDOWS\System32\WS2HELP.dll
Module 13: C:\WINDOWS\System32\DINPUT8.dll
Module 14: C:\WINDOWS\System32\IMM32.dll
Module 15: c:\program files\everquest\DSETUP.dll
Module 16: C:\WINDOWS\system32\VERSION.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\SHELL32.dll
Module 19: C:\WINDOWS\system32\SHLWAPI.dll
Module 20: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a\comctl32.dll
Module 21: C:\WINDOWS\system32\comctl32.dll
Module 22: C:\Program Files\WinEQ2\WinEQ2.dll
Module 23: C:\WINDOWS\Lavish.dll
Module 24: C:\WINDOWS\System32\PSAPI.DLL
Module 25: C:\Program Files\WinEQ2\WinEQ2-EQ.dll
Module 26: C:\WINDOWS\System32\MSIMG32.dll
Module 27: C:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 28: C:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 29: C:\Program Files\WinEQ2\WinEQ2-DI8.dll
Module 30: C:\WINDOWS\system32\mswsock.dll
Module 31: C:\WINDOWS\System32\wshtcpip.dll
Module 32: C:\WINDOWS\System32\DNSAPI.dll
Module 33: C:\WINDOWS\System32\winrnr.dll
Module 34: C:\WINDOWS\system32\WLDAP32.dll
Module 35: C:\WINDOWS\System32\rasadhlp.dll
Module 36: C:\WINDOWS\system32\uxtheme.dll
Module 37: C:\WINDOWS\System32\MSCTF.dll
Module 38: C:\Program Files\Logitech\MouseWare\System\LgWndHk.dll
Module 39: C:\WINDOWS\System32\NTMARTA.DLL
Module 40: c:\program files\everquest\EQGraphicsDX9.DLL
Module 41: C:\WINDOWS\System32\d3d9.dll
Module 42: C:\WINDOWS\System32\d3d8thk.dll
Module 43: c:\program files\everquest\dpvs.dll
Module 44: C:\Program Files\Logitech\iTouch\iTchHk.dll
Module 45: C:\WINDOWS\System32\usp10.dll
Module 46: C:\WINDOWS\System32\HID.DLL
Module 47: C:\WINDOWS\System32\SETUPAPI.DLL
Module 48: C:\Program Files\Common Files\Logitech\Scrolling\LgMsgHk.dll
Module 49: C:\WINDOWS\System32\MSVCP60.dll
Module 50: C:\WINDOWS\System32\mslbui.dll
Module 51: C:\WINDOWS\system32\OLEAUT32.DLL
Module 52: C:\Program Files\Trillian\events.dll
Module 53: C:\WINDOWS\system32\comdlg32.dll
Module 54: C:\Program Files\Trillian\MSVCR71.dll
Module 55: C:\Program Files\Logitech\iTouch\kbdhook.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce FX 5200 /nv4_disp.dll/6/14/10/6703
Adapter Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Game Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Current Adapter: 0
Available Texture Memory: 355MB
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
Profile 2: Barraind
EQ Path: c:\program files\everquest
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 12 (+60 min RAM)
Texture Quality: INVALID VALUE -1
Velious Textures #17: ON (+7 min RAM)
Velious Textures #18: ON (+7 min RAM)
Velious Textures #19: ON (+7 min RAM)
Velious Textures #20: ON (+7 min RAM)
Velious Textures #21: ON (+7 min RAM)
Velious Textures #22: ON (+7 min RAM)
Velious Textures #23: ON (+7 min RAM)
Calculated minimum RAM: 392MB (BASE+109MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=0
Additional setting: 1xPixelShaders=0

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Jul 06, 2005 1:12 pm

1) Update your Windows to SP2 (or at the very LEAST, SP1 with all windows updates other than SP2 itself). Even MS wont really support Windows XP without at least SP1
2) Your video card driver is out of date, update that to the latest driver from nvidia.com

One or both of the above should solve your issue. The only thing associated with WinEQ 2 that would give a strobe sort of appearance is EQPlayNice Pro with Rendering Limiting enabled, and you dont have that loaded nor would you be able to enable rendering limiting.

Cofcos
Non-Subscriber
Posts: 14
Joined: Wed Aug 11, 2004 11:09 pm

Post by Cofcos » Mon Jul 11, 2005 4:54 pm

Actually, in reading posts from the developers, I think your problem may have to wait for the next patch(july 13th, I think).

They're having trouble with alpha channels in EQL at the moment. And some interface issues have resulted, especially for Nvidia users.

...Note that just because something happens with WinEQ and not without doesn't absolutely mean its WinEQs fault. :)

Post Reply