Curiously poor performance...

Cofcos · Post by **Cofcos** » Mon Jun 20, 2005 5:28 pm

In WoW, without WinEQ, I can run 2 instances perfectly at maxed settings for both windows... It just has the slight problem of rebooting my computer every 5 minutes. So, I turned to WinEQ, and it works(no crashes or anything). But has a terrible framerate, even with everything turned down...

Why might this be?

I've a 3ghz P4 /w ~1.5gb memory and an ATI x800pro(256mb vram).

Thanks[/i]

Post by **Lax** » Mon Jun 20, 2005 8:20 pm

How "terrible" is the framerate? Playing the game in a window drops your framerate as it is, which you can do without WinEQ by switching the game to windowed mode.

If your computer reboots every 5 minutes, you should probably try to find out why (it's most likely a BSOD and you're simply not seeing the blue screen because of Windows XP settings)-- I would be inclined to install new video drivers, check the video card fan, etc.

Cofcos · Post by **Cofcos** » Mon Jun 20, 2005 11:27 pm

Well... I suppose terrible as compared to without WinEQ.

I tried using 2 accounts, but had the afore mentioned crash problem. However, during the short time it does work, I have performance similar to WoW without a second copy running. And this is in windowed mode...

With WinEQ, I don't crash, but have less than a quarter my normal framerate.

...Hm. I did use 'maximized' window mode which I had never noticed before(one of WoW's innate options that removes the window border and makes it appear to be full screen). Maybe I'll try turning that off.

Cofcos · Post by **Cofcos** » Mon Jun 20, 2005 11:59 pm

I updated my driver and disabled 'maxmimized window' and tried running two copies of WoW without WinEQ and it crashed again. Framerate was still about 1/4th with WinEQ as compared to without.

I should note that using only one windowed instance of WoW without WinEQ is not noticblely different, performace-wise, than full screen. One copy of WoW with WinEQ shows the same performance hit as running two copies with WinEQ, while running two copies without WinEQ shows the same performance as one copy alone...

I think I've confused you enough for now.

Cofcos · Post by **Cofcos** » Tue Jun 21, 2005 12:03 am

...Yikes. I really must explaing that more clearly.

Without WinEQ, regardless of video mode and the presence of a second instance, WoW performs about the same.

With WinEQ, even running only one instance, performance is degraded to about a quarter.

Post by **Lax** » Tue Jun 21, 2005 12:10 am

Not quite enough, need to throw another dose at me.

Post SysInfo.txt for me, which can be found in the WinEQ 2 folder or can be opened by right clicking on an open WinEQ 2 game window's title bar and selecting Generate System Info.

Cofcos · Post by **Cofcos** » Tue Jun 21, 2005 12:22 am

I notice a few things that seem odd, but that's probably due to my lack of knowlage about it all.

Hope there's nothing embarassing in it...

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_rtm.040803-2158
System Physical RAM: 1093/1534MB
Page File: 3143/3434MB
Virtual Memory: 1687/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) 4 CPU 3.06GHz @ 3059MHz
CPU 2: Intel(R) Pentium(R) 4 CPU 3.06GHz @ 3059MHz
Video 1: \\.\DISPLAY1/RADEON X800 PRO
Video 2: \\.\DISPLAY2/RADEON X800 PRO Secondary
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1024,768) (1024x768) PRIMARY
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.08

Loaded Modules:
-----------------------------------
Module 0: I:\World of Warcraft Beta\wow.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\WINDOWS\system32\MSVCRT.dll
Module 4: C:\WINDOWS\system32\COMCTL32.dll
Module 5: C:\WINDOWS\system32\ADVAPI32.dll
Module 6: C:\WINDOWS\system32\RPCRT4.dll
Module 7: C:\WINDOWS\system32\GDI32.dll
Module 8: C:\WINDOWS\system32\USER32.dll
Module 9: C:\WINDOWS\system32\SHELL32.dll
Module 10: C:\WINDOWS\system32\SHLWAPI.dll
Module 11: C:\WINDOWS\system32\WSOCK32.dll
Module 12: C:\WINDOWS\system32\WS2_32.dll
Module 13: C:\WINDOWS\system32\WS2HELP.dll
Module 14: C:\WINDOWS\system32\OPENGL32.dll
Module 15: C:\WINDOWS\system32\GLU32.dll
Module 16: C:\WINDOWS\system32\DDRAW.dll
Module 17: C:\WINDOWS\system32\DCIMAN32.dll
Module 18: C:\WINDOWS\system32\IMM32.dll
Module 19: I:\World of Warcraft Beta\DivxDecoder.dll
Module 20: C:\WINDOWS\system32\WINMM.dll
Module 21: I:\World of Warcraft Beta\fmod.dll
Module 22: C:\WINDOWS\system32\ole32.dll
Module 23: C:\WINDOWS\system32\MSACM32.dll
Module 24: C:\WINDOWS\system32\WININET.dll
Module 25: C:\WINDOWS\system32\CRYPT32.dll
Module 26: C:\WINDOWS\system32\MSASN1.dll
Module 27: C:\WINDOWS\system32\OLEAUT32.dll
Module 28: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 29: C:\WINDOWS\system32\serwvdrv.dll
Module 30: C:\WINDOWS\system32\umdmxfrm.dll
Module 31: F:\Programs\WinEQ2\WinEQ2.dll
Module 32: C:\WINDOWS\Lavish.dll
Module 33: C:\WINDOWS\system32\PSAPI.DLL
Module 34: F:\Programs\WinEQ2\WinEQ2-WOW.dll
Module 35: C:\WINDOWS\system32\MSIMG32.dll
Module 36: F:\Programs\WinEQ2\WinEQ2-D3D9.dll
Module 37: F:\Programs\WinEQ2\WinEQ2-Win32I.dll
Module 38: C:\WINDOWS\system32\mswsock.dll
Module 39: C:\WINDOWS\system32\hnetcfg.dll
Module 40: C:\WINDOWS\System32\wshtcpip.dll
Module 41: C:\WINDOWS\system32\DNSAPI.dll
Module 42: C:\WINDOWS\System32\winrnr.dll
Module 43: C:\WINDOWS\system32\WLDAP32.dll
Module 44: C:\WINDOWS\system32\rasadhlp.dll
Module 45: C:\WINDOWS\system32\uxtheme.dll
Module 46: F:\Programs\WinEQ2\EQPlayNice.dll
Module 47: C:\WINDOWS\system32\NTMARTA.DLL
Module 48: C:\WINDOWS\system32\SAMLIB.dll
Module 49: C:\WINDOWS\system32\d3d9.dll
Module 50: C:\WINDOWS\system32\d3d8thk.dll
Module 51: C:\WINDOWS\system32\VERSION.dll
Module 52: C:\WINDOWS\system32\ctagent.dll
Module 53: C:\WINDOWS\system32\dsound.dll
Module 54: C:\WINDOWS\system32\WINTRUST.dll
Module 55: C:\WINDOWS\system32\IMAGEHLP.dll
Module 56: C:\WINDOWS\system32\wdmaud.drv
Module 57: C:\WINDOWS\system32\msacm32.drv
Module 58: C:\WINDOWS\system32\midimap.dll
Module 59: C:\WINDOWS\system32\KsUser.dll
Module 60: C:\WINDOWS\system32\Secur32.dll
Module 61: C:\WINDOWS\system32\urlmon.dll
Module 62: C:\WINDOWS\system32\RASAPI32.DLL
Module 63: C:\WINDOWS\system32\rasman.dll
Module 64: C:\WINDOWS\system32\NETAPI32.dll
Module 65: C:\WINDOWS\system32\TAPI32.dll
Module 66: C:\WINDOWS\system32\rtutils.dll
Module 67: C:\WINDOWS\system32\msv1_0.dll
Module 68: C:\WINDOWS\system32\iphlpapi.dll
Module 69: C:\WINDOWS\system32\sensapi.dll
Module 70: C:\WINDOWS\system32\USERENV.dll

Direct3D9:
-----------------------------------
Driver: RADEON X800 PRO/ati2dvag.dll/6/14/10/6542
Adapter Display Mode: 1024x768 D3DFMT_R5G6B5
Game Display Mode: 1026x748 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: 295MB
Win32 Input:
-----------------------------------

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

Post by **Lax** » Tue Jun 21, 2005 12:39 am

Looks fairly normal, the only thing that actually sticks out is the install directory says Beta

When WoW Beta ended we installed clean from retail, I'm not sure if that would make any difference or not though. We are talking about retail WoW not beta right? If we're talking about beta, then I cant really guarantee anything at all, but assuming not.

Another thing to try is I see you're running 16-bit color. You could definitely pop that up to 32-bit color. If the game itself wants to do 32-bit color and you have your windows desktop at 16-bit (as you do), then that could contribute to problems as well (and has caused BSODs with EQ too). WinEQ will force the game to use the same color depth as Windows, which could be why it works with WinEQ without crashing but not without.

After the previous suggestions, I would check stuff like
1) Motherboard drivers (e.g. IDE, SATA, AGP chipset, etc)
2) Motherboard BIOS
3) Virus and Spyware scans

Cofcos · Post by **Cofcos** » Tue Jun 21, 2005 12:55 am

Oh, beta is because I was too lazy to reinstall it after the beta. It's never given my any problems, and I have multiboxed before without these problems.

I actually changed the color resolution to 16 bit to test something-- thanks for reminding me.

I did reinstall Windows a little while ago, so I'll check on the chipset driver. The BIOS is the most recent as is the soundcard driver.

It'd be much easier if I could just get over the poor framerate. But it drives me crazy-- I had to give up EQ2 almost solely because the crappy performance got to me... And if I do fix it, it'll probably be just before this morning's 12 hour affair/"maintenance".

...One thing comes to mind: Would APG apurture have any affect? Though, even if it did I don't remember how to change it. I did once years ago, through the BIOS(I thought), but when I've looked there recently there was no option to change it.

Post by **Lax** » Tue Jun 21, 2005 9:45 am

AGP Aperture Size won't change anything, and here's why:

Available Texture Memory: 295MB

Your X800 probably has 256MB on it, and it would take several sessions of WoW to tear through that

I was about to test this but the servers are down. Bah. The only other framerate issue that comes to mind is with dual monitors. I see your system is only set up with 1 according to Windows, but if you're using some sort of desktop manager to use 2 there could be issues with that.

Cofcos · Post by **Cofcos** » Mon Jul 11, 2005 4:12 pm

I thought I'd note that this issue, and another I came upon when running 2 EQ2s was solved when I updated my video driver from the May release to the latest July release; which wasn't available at the time I had this problem...

There must've been some reason that version of the video driver didn't like WinEQ2.

Oh, the issue I had with EQ2 was that it would freeze the background window for 2 seconds before giving control. But this too was fixed...

(incase anyone else appears with this problem)