Problem with Vista and WoW: limiter not working

[madman]

Apologies if this has been asked before, I tried searching the forum but haven't found anything to help with my problem.

Using WoW+WinEQ2 with Vista Business, I have installed WinEQ as administrator and am running it as administrator. WoW starts normally, it's just that none of the limiter options (CPU, FPS) work. The game constantly uses full CPU (well, 50% on a dual core system) and draws full frames, no matter what I set it at. That makes dual boxing impossible because the second session is starved.

I can run WoW in the WinEQ window fine other than that, it's just the limiters that are not working at all. I also cannot get the memory/FPS display to show, no matter what I try to set the hotkeys for it to. The other hotkeys (for example for resizing from regular size to tiny) work.

Here's my Sysinfo:

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Windows Vista (TM) Business//6000.vista_rtm.061101-2205
System Physical RAM: 2370/3581MB
Page File: 5966/7348MB
Virtual Memory: 1972/2047MB (Extended: 0MB)
CPU 1: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz @ 2666MHz
CPU 2: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz @ 2666MHz
CPU Affinity Mask: 1
Video 1: \\.\DISPLAY1/NVIDIA GeForce 7900 GTX
Video 2: \\.\DISPLAY2/NVIDIA GeForce 7900 GTX
Video 3: \\.\DISPLAYV1/RDPDD Chained DD
Video 4: \\.\DISPLAYV2/RDP Encoder Mirror Driver
Monitor 1: \\.\DISPLAY1 (1680,0,3280,1200) (1600x1200)
Monitor 2: \\.\DISPLAY2 (0,0,1680,1050) (1680x1050) PRIMARY
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 7.0.6000.16512
WinEQ: 2.15

Loaded Modules:
-----------------------------------
Module 0: d:\games\wow\wow.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\msvcrt.dll
Module 5: C:\Windows\system32\USER32.dll
Module 6: C:\Windows\system32\GDI32.dll
Module 7: C:\Windows\system32\ADVAPI32.dll
Module 8: C:\Windows\system32\RPCRT4.dll
Module 9: C:\Windows\system32\ole32.dll
Module 10: C:\Windows\system32\OLEAUT32.dll
Module 11: C:\Windows\system32\OLEACC.dll
Module 12: C:\Windows\system32\WSOCK32.dll
Module 13: C:\Windows\system32\WS2_32.dll
Module 14: C:\Windows\system32\NSI.dll
Module 15: C:\Windows\system32\OPENGL32.dll
Module 16: C:\Windows\system32\GLU32.dll
Module 17: C:\Windows\system32\DDRAW.dll
Module 18: C:\Windows\system32\DCIMAN32.dll
Module 19: C:\Windows\system32\SETUPAPI.dll
Module 20: C:\Windows\system32\dwmapi.dll
Module 21: C:\Windows\system32\VERSION.dll
Module 22: C:\Windows\system32\IMM32.dll
Module 23: C:\Windows\system32\MSCTF.dll
Module 24: d:\games\wow\fmod.dll
Module 25: C:\Windows\system32\MSACM32.dll
Module 26: C:\Windows\system32\WININET.dll
Module 27: C:\Windows\system32\SHLWAPI.dll
Module 28: C:\Windows\system32\Normaliz.dll
Module 29: C:\Windows\system32\iertutil.dll
Module 30: C:\Windows\system32\SHELL32.dll
Module 31: d:\games\wow\DivxDecoder.dll
Module 32: C:\Windows\system32\ShimEng.dll
Module 33: C:\Windows\system32\apphelp.dll
Module 34: C:\Windows\AppPatch\AcGenral.DLL
Module 35: C:\Windows\system32\UxTheme.dll
Module 36: C:\Windows\system32\NETAPI32.dll
Module 37: C:\Windows\system32\PSAPI.DLL
Module 38: C:\Windows\system32\sfc.dll
Module 39: C:\Windows\system32\sfc_os.DLL
Module 40: C:\Windows\system32\USERENV.dll
Module 41: C:\Windows\system32\Secur32.dll
Module 42: C:\Windows\system32\urlmon.dll
Module 43: C:\Windows\system32\MPR.dll
Module 44: C:\Windows\AppPatch\AcSpecfc.DLL
Module 45: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.6000.16386_none_87e0cb09378714f1\COMCTL32.dll
Module 46: C:\Windows\system32\mscms.dll
Module 47: C:\Windows\system32\WINSPOOL.DRV
Module 48: C:\Windows\system32\COMDLG32.dll
Module 49: C:\Windows\system32\LPK.DLL
Module 50: C:\Windows\system32\USP10.dll
Module 51: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6000.16386_none_5d07289e07e1d100\comctl32.dll
Module 52: D:\programs\WinEQ2\WinEQ2.dll
Module 53: D:\programs\WinEQ2\Lavish.dll
Module 54: C:\Windows\system32\iphlpapi.dll
Module 55: C:\Windows\system32\dhcpcsvc.DLL
Module 56: C:\Windows\system32\DNSAPI.dll
Module 57: C:\Windows\system32\WINNSI.DLL
Module 58: C:\Windows\system32\dhcpcsvc6.DLL
Module 59: C:\Windows\system32\mswsock.dll
Module 60: C:\Windows\System32\wshtcpip.dll
Module 61: C:\Windows\system32\NLAapi.dll
Module 62: C:\Windows\System32\winrnr.dll
Module 63: C:\Windows\system32\WLDAP32.dll
Module 64: C:\Windows\system32\napinsp.dll
Module 65: C:\Windows\system32\pnrpnsp.dll
Module 66: C:\Windows\system32\rasadhlp.dll
Module 67: D:\programs\WinEQ2\WinEQ2-WOW.dll
Module 68: C:\Windows\system32\MSIMG32.dll
Module 69: D:\programs\WinEQ2\WinEQ2-D3D9.dll
Module 70: C:\Windows\system32\d3dx9_30.dll
Module 71: D:\programs\WinEQ2\WinEQ2-Win32I.dll
Module 72: D:\programs\WinEQ2\EQPlayNice.dll

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

World of Warcraft:
-----------------------------------
Profile 1: WinEQ 2.0 Default Profile
WoW Path: d:\games\wow\
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled

[eqjoe]

Try setting your game client process to have affinity with just one of your processor cores.

-j

[madman]

Tried that, j, have set it both via WinEQ preferences (by setting CPU affinity to ON) and via Vista task manager to CPU 0, both together and alternatively, no difference. Game still runs with 100+ FPS in spite of the limiter being ON and set to 40.

Still can't get the framerate/memory indicator to display either.

Now, I've done some digging around on my backup drive and found my old sysinfo.txt from when I was running Win XP, and here's what it says at the end:

Code: Select all

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce 7900 GTX/nv4_disp.dll/6/14/11/6250
Adapter Display Mode: 1680x1050 D3DFMT_X8R8G8B8
Game Display Mode: 1674x1023 D3DFMT_UNKNOWN (Windowed)
Current Adapter: 0
Available Texture Memory: 663MB
Win32 Input:
-----------------------------------

Compared to Vista, where it reads:

Code: Select all

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

Not being familiar with sysinfo output (and just getting started with Vista), is that maybe an indication of the graphics driver not being installed correctly?

I'm grateful for any hints or pointers, thanks.

[Lax]

Actually that last post shows the problem. You're playing in opengl mode, and WinEQ doesnt know how to frame limit in that mode Open up World of Warcraft\WTF\config.wtf and delete the line that says something about opengl. There should only be one

[madman]

Still no luck.

Checked the config.wtf, the renderer variable was not set, I set it explicitly to "d3d" still not working.

I'm starting to get frustrated, although I don't think it is a WinEQ issue and am more inclined to blame it on the crap drivers that NVidia has for Vista. So far I've learned that installing newer drivers makes my performance go down, so I'm running on some 97.51 that came with Windows Update and is dated January instead of the current 16x.xx ones.

[eqjoe]

Change SET gxApi "opengl" to SET gxApi "direct3d" in config.wtf.


-j

[madman]

There's no OGL option set anywhere in my Config.wtf though, j. I tried setting both

Code: Select all

SET renderer "d3d"
SET gxApi "direct3d"

as well, doesn't help either . I'm still getting that weird

Code: Select all

Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN (Windowed)
Current Adapter: 0
Available Texture Memory: (not currently available)

line in sysinfo.txt too. The graphics driver seems to be installed okay otherwise, it is reported by vista with no problems whatsoever in both the display and device manager and the d3d performance is pretty good otherwise too.

I'm grateful for any additional input on the matter.

[eqjoe]

Thats just wierd. If it where me, I would back rev my video driver and see if that makes a difference.

-j

[madman]

Went back through a couple revisions starting from 163.44 and picked a select few out until 97.52 (Nvidia Forceware), no luck. Still the same issue, nothing gets limited, and the overlay information is not displayed either. Card still

Is anyone here running WinEQ ( forWOW) + Vista on an NVidia GPU (I got a 7900 GTX) and could point me to a specific working driver? If it works, what does it say under "Adapter" in Sysinfo.txt? Mine keeps stating "D3DFMT_UNKNOWN".