WinEQ 2.02, EverQuest, 92%+ CPU Usage issue

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
Venthos
GamingTools Subscriber
Posts: 28
Joined: Wed Jul 14, 2004 7:21 am

WinEQ 2.02, EverQuest, 92%+ CPU Usage issue

Post by Venthos » Sat Nov 13, 2004 4:25 am

- Please explain which GAME you are having trouble with
EverQuest

Weird ass problem going on. With WinEQ 2.02 Pro running, one window of EQ open. If I just hover the mouse over any taskbar item to where a "tip" displays. For the length of time that displays (including the "Fade Up" time, visible time, and "Fade Down" time.) eqgame.exe's CPU Usage rockets to 92%+. When the tip goes away, it resumes back down to ~15% usage.

This ONLY occurs if WinEQ's window is "visible". It doesnt matter if it's in focus or not. Just if the window itself is visible.

Let me know what other information if any you need.

-Venthos
SysInfo.txt wrote:WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_rtm.040803-2158
System Physical RAM: 364/1023MB
Page File: 1710/2465MB
Virtual Memory: 1396/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 3000+ @ 2094MHz
Video 1: \\.\DISPLAY1/NVIDIA GeForce4 Ti 4600
Video 2: \\.\DISPLAY2/NVIDIA GeForce4 Ti 4600
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1024,768) (1024x768) PRIMARY
Monitor 2: \\.\DISPLAY2 (1024,0,1824,600) (800x600)
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.02

Direct3D9:
-----------------------------------
Adapter Display Mode: 1024x768 D3DFMT_X8R8G8B8
Game Display Mode: 1024x768 D3DFMT_X8R8G8B8
Current Adapter: 0

Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0

DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
Profile 1: WinEQ 2.0 Default Profile
EQ Path: C:\EverQuest-New
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Primary
Luclin models: 29 (+145 min RAM)
Texture Compression: ON (+0 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: LOW (+0 min RAM)
Calculated minimum RAM: 432MB (BASE+149MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=TRUE
Additional setting: 1xPixelShaders=TRUE

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Oct 11 2004 15:21:50
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 30
Rendering: 1/30

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

Post by Lax » Sat Nov 13, 2004 12:35 pm

This happens even without WinEQ. I'll see if I can figure out a way to prevent it, thanks for the report

Venthos
GamingTools Subscriber
Posts: 28
Joined: Wed Jul 14, 2004 7:21 am

Post by Venthos » Sat Nov 13, 2004 7:55 pm

Oh? I had just the other day (The day of that post) decided to switch from WinEQ 1 to WinEQ 2. Never had this issue prior. Assumed it was a WinEQ2 thing. My apologies.

-Venthos

Post Reply