CPU affinity not being set after a while

anonguy · Post by **anonguy** » Thu Oct 06, 2005 11:49 pm

I think cpu affinity is not being set correctly all the time. I have a X2 cpu. Load 2 instances, first one loads on first core, 2nd one loads on the 2nd core. Play for a while then camp the 2nd instance (/camp desk), so only first instance on first core running. A while later I load a second instance, but it seems to be putting it on the first core along with the first instance. I tried camping and restarting the 2nd instance a few times, but it kept putting it on the first core. So, with first instance still running on first core, i went into options and set cup affin/pip/tiling to ON/OFF/ON then reloaded 2nd instance. This time it loaded onto the 2nd core.

Btw, im still getting the bug where the affin/pip/tiling aren't displaying any values each time i load wineq.

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 810/2046MB
Page File: 2864/3939MB
Virtual Memory: 1915/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ @ 2009MHz
CPU 2: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ @ 2009MHz
CPU Affinity Mask: 2
Video 1: \\.\DISPLAY1/NVIDIA GeForce 7800 GTX
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.2900.2180
WinEQ: 2.12

Loaded Modules:
-----------------------------------
Module 0: d:\program files\everquest\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: d:\program files\everquest\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\WINMM.dll
Module 7: C:\WINDOWS\system32\ADVAPI32.dll
Module 8: C:\WINDOWS\system32\RPCRT4.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: d:\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.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 21: C:\WINDOWS\system32\comctl32.dll
Module 22: D:\Program Files\WinEQ2\WinEQ2.dll
Module 23: C:\WINDOWS\Lavish.dll
Module 24: C:\WINDOWS\system32\PSAPI.DLL
Module 25: D:\Program Files\WinEQ2\WinEQ2-EQ.dll
Module 26: C:\WINDOWS\system32\MSIMG32.dll
Module 27: D:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 28: D:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 29: D:\Program Files\WinEQ2\WinEQ2-DI8.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: D:\Program Files\MQ\MQ2Main.dll
Module 38: C:\WINDOWS\system32\NTMARTA.DLL
Module 39: C:\WINDOWS\system32\SAMLIB.dll
Module 40: d:\program files\everquest\EQGraphicsDX9.DLL
Module 41: C:\WINDOWS\system32\d3d9.dll
Module 42: C:\WINDOWS\system32\d3d8thk.dll
Module 43: d:\program files\everquest\dpvs.dll
Module 44: D:\Program Files\MQ\mq2labels.dll
Module 45: D:\Program Files\MQ\mq2itemdisplay.dll
Module 46: C:\WINDOWS\system32\ctagent.dll
Module 47: D:\Program Files\MQ\mq2custombinds.dll
Module 48: D:\Program Files\MQ\mq2hud.dll
Module 49: C:\WINDOWS\system32\usp10.dll
Module 50: D:\Program Files\MQ\mq2map.dll
Module 51: D:\Program Files\MQ\mq2bzsrch.dll
Module 52: D:\Program Files\MQ\mq2chatwnd.dll
Module 53: D:\Program Files\MQ\mq2eqbugfix.dll
Module 54: D:\Program Files\MQ\mq2autoskills.dll
Module 55: D:\Program Files\MQ\mq2exchange.dll
Module 56: D:\Program Files\MQ\mq2moveutils.dll
Module 57: D:\Program Files\MQ\mq2gmcheck.dll
Module 58: D:\Program Files\MQ\mq2fps.dll
Module 59: D:\Program Files\MQ\mq2autodestroy.dll
Module 60: D:\Program Files\MQ\mq2feedme.dll
Module 61: C:\WINDOWS\system32\HID.DLL
Module 62: C:\WINDOWS\system32\SETUPAPI.DLL
Module 63: C:\WINDOWS\system32\WINTRUST.dll
Module 64: C:\WINDOWS\system32\CRYPT32.dll
Module 65: C:\WINDOWS\system32\MSASN1.dll
Module 66: C:\WINDOWS\system32\IMAGEHLP.dll
Module 67: d:\program files\everquest\mssmp3.asi
Module 68: d:\program files\everquest\mssvoice.asi
Module 69: d:\program files\everquest\mssa3d.m3d
Module 70: d:\program files\everquest\mssds3d.m3d
Module 71: d:\program files\everquest\mssdx7.m3d
Module 72: d:\program files\everquest\msseax.m3d
Module 73: d:\program files\everquest\mssrsx.m3d
Module 74: C:\WINDOWS\system32\MSACM32.dll
Module 75: d:\program files\everquest\msssoft.m3d
Module 76: d:\program files\everquest\mssdsp.flt
Module 77: C:\WINDOWS\system32\wdmaud.drv
Module 78: C:\WINDOWS\system32\msacm32.drv
Module 79: C:\WINDOWS\system32\midimap.dll
Module 80: C:\WINDOWS\system32\DSOUND.DLL
Module 81: C:\WINDOWS\system32\KsUser.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce 7800 GTX/nv4_disp.dll/6/14/10/8182
Adapter Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Game Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Current Adapter: 0
Available Texture Memory: 297MB
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 1: WinEQ 2.0 Default Profile
EQ Path: d:\program files\everquest
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 6 (+30 min RAM)
MipMapping: ON (+4 min RAM)
Sound: ON (+22 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Quality: MEDIUM (+30 min RAM)
Sky: COMPLEX (+10 min RAM)
Calculated minimum RAM: 383MB (BASE+100MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: HardwareTnL=TRUE
Additional setting: VSync=1
Additional setting: VertexShaders=1
Additional setting: 20PixelShaders=1
Additional setting: 1xPixelShaders=1

anonguy · Post by **anonguy** » Fri Oct 07, 2005 9:11 am

On a related subject, where are affin/pip/tiling values being stored? I toggled them in options/preferences and have seen no change in any of the files in the WinEQ directory.

Post by **Lax** » Fri Oct 07, 2005 11:18 am

They are actually supposed to be stored in WinEQ2.ini, which due to a bug isnt being created at the moment.

I'll be working on these issues shortly.

Post by **Lax** » Sun Oct 09, 2005 12:57 am

Apparently it was being created in c:\windows

These issues should be fixed as of today's WinEQ 2 patch.

anonguy · Post by **anonguy** » Tue Oct 11, 2005 5:55 pm

I think i still have the problem with both instances being loaded on the the first core. If i follow the procedure in my original post (setting cpu affin off before loading 2nd instance) i can get the 2nd instance on the 2nd core. Im assuming this is the normal windows task allocation putting it there.

anonguy · Post by **anonguy** » Wed Oct 12, 2005 11:30 pm

Ok. What exactly is the cpu affinity option supposed to do? Right now it just assigns all wineq instances to the first processor and ignores the 2nd. If you disable it windows assigns stuff to the 2nd but you get that performance bug in eq. Is there some way in wineq to assign the 2nd window to the 2nd processor?

Post by **Lax** » Thu Oct 13, 2005 7:43 pm

This should be fixed as of today's patch. It was incorrectly counting your number of CPUs, and will now correctly rotate between the two. I will add in-game CPU affinity selection in a near-future update.

anonguy · Post by **anonguy** » Mon Oct 17, 2005 6:10 pm

Still a minor issue, not sure if worth fixing. When i have 2 instances up and camp the 2nd (on 2nd core) then reload the 2nd one later, its back on the first core. Im using sysinternals process explorer to see where it's being assigned and changing it. It's pretty obvious from game play though. I play 1280x1024 with a decent amount of graphics on.

Post by **Lax** » Mon Oct 17, 2005 9:25 pm

Yeah, I'm aware of this and it wasnt really feasible for me to fix this in the amount of time that I hto spend on it. I'll probably have the main program automatically re-distribute the CPU affinity of all sessions when a new one starts or ends, and have cpu affinity on the right click menu in game.