mmemory fps indicators

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
ScottAdams
Non-Subscriber
Posts: 44
Joined: Thu Dec 23, 2004 3:17 pm
Contact:

mmemory fps indicators

Post by ScottAdams » Wed Dec 29, 2004 4:24 pm

On one ssystem I running 2 copies of EQ2. Frequently the memory/fps indicators will not show up. When this occurs the game will not run very well.

Shutting of one load of the game and reloading it sometimes works and sometimes doesn't.

Can't seem to figure out what is the problem.

ti4600 with 66.93 nvidia drivers and a lcd DVI monitor
Scott Adams
Not Dilbert, Adventure!

ScottAdams
Non-Subscriber
Posts: 44
Joined: Thu Dec 23, 2004 3:17 pm
Contact:

Post by ScottAdams » Wed Dec 29, 2004 4:26 pm

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_rtm.040803-2158
System Physical RAM: 726/1023MB
Page File: 1503/1695MB
Virtual Memory: 2003/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 1900+ @ 1606MHz
Video 1: \\.\DISPLAY1/NVIDIA GeForce4 Ti 4400
Video 2: \\.\DISPLAY2/NVIDIA GeForce4 Ti 4400
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Sound: SB Live! Audio [E800]
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.07

Loaded Modules:
-----------------------------------
Module 0: C:\Everquest2\EverQuest2.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\WINDOWS\system32\WINMM.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\IMM32.dll
Module 9: C:\WINDOWS\system32\SHELL32.dll
Module 10: C:\WINDOWS\system32\msvcrt.dll
Module 11: C:\WINDOWS\system32\SHLWAPI.dll
Module 12: C:\Everquest2\mss32.dll
Module 13: C:\WINDOWS\system32\d3d9.dll
Module 14: C:\WINDOWS\system32\d3d8thk.dll
Module 15: C:\WINDOWS\system32\VERSION.dll
Module 16: C:\WINDOWS\system32\WSOCK32.dll
Module 17: C:\WINDOWS\system32\WS2_32.dll
Module 18: C:\WINDOWS\system32\WS2HELP.dll
Module 19: C:\WINDOWS\system32\ole32.dll
Module 20: C:\WINDOWS\system32\OLEAUT32.dll
Module 21: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 22: C:\WINDOWS\system32\comctl32.dll
Module 23: C:\Program Files\WinEQ2\WinEQ2.dll
Module 24: C:\WINDOWS\Lavish.dll
Module 25: C:\WINDOWS\system32\PSAPI.DLL
Module 26: C:\Program Files\WinEQ2\WinEQ2-EQII.dll
Module 27: C:\WINDOWS\system32\MSIMG32.dll
Module 28: C:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 29: C:\Program Files\WinEQ2\WinEQ2-HooksI.dll
Module 30: C:\WINDOWS\system32\mswsock.dll
Module 31: C:\WINDOWS\system32\hnetcfg.dll
Module 32: C:\WINDOWS\System32\wshtcpip.dll
Module 33: C:\WINDOWS\system32\DNSAPI.dll
Module 34: C:\WINDOWS\System32\winrnr.dll
Module 35: C:\WINDOWS\system32\WLDAP32.dll
Module 36: C:\WINDOWS\system32\rasadhlp.dll
Module 37: C:\Program Files\WinEQ2\EQPlayNice.dll
Module 38: c:\tempIadHide3.dll
Module 39: C:\Program Files\Logitech\MouseWare\System\LgWndHk.dll
Module 40: C:\WINDOWS\system32\MSCTF.dll

Direct3D9:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
Windows Hooks Input:
-----------------------------------

EverQuest II:
-----------------------------------
Profile 1: WinEQ 2.0 Default Profile
EQII Path: C:\Everquest2
EQIIClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Scott Adams
Not Dilbert, Adventure!

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

Post by Lax » Thu Dec 30, 2004 12:02 pm

Hi Mr Adams, glad to see you again :)

This may sound weird, but this problem is actually solved by uninstalling, and then re-installing your video card drivers. Something in this process fixes some corrupt files or something, I'm not entirely sure... but every instance of this problem has been solved this way, regardless of the driver version (same version works fine).

It's odd that it shows up sometimes for you. Most reports have said that when this problem exists on their system, they will *never* see the indicator.

ScottAdams
Non-Subscriber
Posts: 44
Joined: Thu Dec 23, 2004 3:17 pm
Contact:

Post by ScottAdams » Thu Dec 30, 2004 2:03 pm

I saw the faq on version one about installingthe drivers again and that did not work.

BUT I think I may have stumbled on a solution. I created another profile and specifically changed it to using the primary display. I think the program was getting confused about which display to use. Note I have only one display but it has both vga and dvi outputs and I them both connected. this makes it look like 2 displays. this may have been the problem with others not seeing the indicator. I suspect they also had more that one display to choose from.

BTW I am anxiously awaiting fury as I am running a hydra in EQ2, and also please call me Scott :)

Great utilities!
Scott Adams
Not Dilbert, Adventure!

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

Post by Lax » Thu Dec 30, 2004 2:56 pm

That makes sense. Using both dvi and vga outputs (some have dual vga or dual dvi also) is how dual monitor systems are usually achieved. I suspect most of the others weren't using dual outputs.

I'll have a chance to get Fury alpha going pretty soon. I put it off to begin working on Inner Space, since it has further reach and I intend for it to actually replace WinEQ 2 (certain flaws in WinEQ 2 are the primary reason for Inner Space). I was planning on having Fury Alpha out earlier this month, but I need to redesign parts of it to bring it up to date.

Post Reply