Strange behavior :)

Kaycee · Post by **Kaycee** » Fri Sep 09, 2005 4:50 pm

Since the mouse auto release thing was put in I've seen on a few occasions that when I switch sessions right after I hit the key to do so and type something to say to the group for instance that the session I changed from and the current session echo the same thing in the chat box.

IE.

PlayerA says to group Hello
PlayerB says to group Hello

When player B was the one who actually typed hello and A echo'd it. Just seems to do it right after a session change like within a second of the change.

I use Num1 thru 3 keys to change to each of my 3 sessions. No alt tab etc.

Also not sure if its my system in general and I'm assuming its another process doing it but in the mass clicking phase of the mouse sometimes I end up with the mouse arrow on my 2nd screen doing a right click on the desktop pulling up the menu. I'm only using 1 monitor for all 3 sessions currently when this happens. It acts like another process running in the background takes focus for a second and wineq releases the mouse to it then I have to move it back and click on the game session to get it back in control again.

Not sure if anyone else had that issue and if its Norton doing it I"m gonna torch it lol ;0

Thanks
kaycee

Kaycee · Post by **Kaycee** » Fri Sep 09, 2005 4:55 pm

Oh also on the process taking focus issue when the mouse is on the other screen temporarily, using the num1 thru 3 keys wont bring up the sessions it just makes the icons on the task bar blink until you click on a session to get control again then the hotkeys work

kaycee

Sorry not added to first post

Kaycee · Post by **Kaycee** » Fri Sep 09, 2005 4:58 pm

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 1592/2045MB
Page File: 3176/3432MB
Virtual Memory: 2015/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) 4 CPU 2.80GHz @ 2793MHz
CPU 2: Intel(R) Pentium(R) 4 CPU 2.80GHz @ 2793MHz
CPU Affinity Mask: 3
Video 1: \\.\DISPLAY1/NVIDIA GeForce FX 5900XT
Video 2: \\.\DISPLAY2/NVIDIA GeForce FX 5900XT
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Monitor 2: \\.\DISPLAY2 (1280,0,2560,1024) (1280x1024)
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.11

Loaded Modules:
-----------------------------------
Module 0: C:\Everquest I\everquest.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\WINDOWS\system32\WS2_32.dll
Module 4: C:\WINDOWS\system32\msvcrt.dll
Module 5: C:\WINDOWS\system32\WS2HELP.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\USER32.dll
Module 10: C:\WINDOWS\system32\GDI32.dll
Module 11: C:\WINDOWS\system32\WINMM.dll
Module 12: C:\WINDOWS\system32\WININET.dll
Module 13: C:\WINDOWS\system32\CRYPT32.dll
Module 14: C:\WINDOWS\system32\MSASN1.dll
Module 15: C:\WINDOWS\system32\OLEAUT32.dll
Module 16: C:\WINDOWS\system32\ole32.dll
Module 17: C:\WINDOWS\system32\SHLWAPI.dll
Module 18: C:\WINDOWS\system32\WSOCK32.dll
Module 19: C:\WINDOWS\system32\d3d8.dll
Module 20: C:\WINDOWS\system32\d3d8thk.dll
Module 21: C:\WINDOWS\system32\VERSION.dll
Module 22: C:\WINDOWS\system32\DSOUND.dll
Module 23: C:\WINDOWS\system32\COMCTL32.dll
Module 24: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 25: C:\Program Files\WinEQ2\WinEQ2.dll
Module 26: C:\WINDOWS\Lavish.dll
Module 27: C:\WINDOWS\system32\PSAPI.DLL
Module 28: C:\Program Files\WinEQ2\WinEQ2-EQ.dll
Module 29: C:\WINDOWS\system32\SHELL32.dll
Module 30: C:\WINDOWS\system32\MSIMG32.dll
Module 31: C:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 32: C:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 33: C:\Program Files\WinEQ2\WinEQ2-DI8.dll

Direct3D9:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
EQClient.ini: .\eqclient.ini
Patch: ON Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 29 (+145 min RAM)
Texture Compression: ON (+0 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: INVALID VALUE 3
Sky: COMPLEX (+10 min RAM)
Load Velious Armors with Luclin: ON (+51 min RAM)
Calculated minimum RAM: 489MB (BASE+206MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=1
Additional setting: 1xPixelShaders=TRUE

Post by **Lax** » Fri Sep 09, 2005 6:23 pm

I see your CPU Affinity mask is 3 (cpu 0 and 1 according to task manager), which as of a few builds of WinEQ ago should actually be set to 1 or 2. Are you manually setting it? or is WinEQ for some reason failing to set it? EQ has horrible problems with it like that, but I'm not sure if this is related or not. I'll have to disable the feature to see the issue is related.

Post by **Lax** » Fri Sep 09, 2005 8:04 pm

I think this other thread http://www.lavishsoft.com/forum/viewtopic.php?t=2067 is related, so keep an eye on that one too. I'm trying to reproduce the issue(s) described, and have yet to be able to duplicate keys for more than a fraction of a second. Maybe I need to disable EQPlayNice too

Kaycee · Post by **Kaycee** » Sat Sep 10, 2005 5:58 pm

Wasnt even aware that CPU Affinity could be changed or where to change it so WinEQ must have added that setting. I'll check out the other post and see whats up there

.

Kaycee

Kaycee · Post by **Kaycee** » Sat Sep 10, 2005 6:01 pm

AH read the other post I dont think I've had issues with movement just the auto release and the double talk issue but the time frames of it happening within a second does sound familiar so maybe we're in the same boat

. If I need to change that affinity issue manually can you tell me where at and what it should be set to ?

Thanks again for the hard work

kaycee

Post by **Lax** » Sat Sep 10, 2005 6:14 pm

Well, I was just asking because WinEQ should be setting it, and it apparently didnt for you.

However, as of WinEQ 2.12 you shouldn't experience t his issue anymore. If you are, and are running WinEQ 2.12, please let me know

Kaycee · Post by **Kaycee** » Sun Sep 11, 2005 1:38 pm

Looks like wineq set it back to affinity 1 instead of 3

Hopefully thats right

Thanks again
Kaycee

Post by **Lax** » Sun Sep 11, 2005 1:48 pm

Yep, it should ideally be 1 or 2, but not both (1+2=3)