Question regarding Cycling Sessions - EQ1

uevrwndry · Post by **uevrwndry** » Sun Oct 30, 2005 9:25 pm

Ever since the last EQ patch (aka the patch from Hell) when I am running two sessions of WinEQ, I am getting booted to the secondary session (i.e. the one I am not actively focused on) if it performs an action such as loading, camping, etc. This did not happen prior to the last patch. Previously, I could start the second session, load my toon and switch back to my main while it was loading and zoning with no interruption. The only reason I am curious about this is becuase it has cause me some problems while playing due to the unwanted session cycling to active while I am trying to heal or something. Is there some setting that I missed that would block the program from doing this?

On another note, I have also noticed that since the new 'System Mouse' thing, I can click on the PiP of my second session and it will cycle to it for me. It this permanent? I used to hide stuff behind the PiP screen and now I cannot click on it and drag it out anymore.

I have attached my Sysinfo, although I am not sure if these questions have anything to do with that is contained there...

Any comments would be welcome.

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 1827/2558MB
Page File: 4264/4903MB
Virtual Memory: 1019/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) 4 CPU 3.20GHz @ 3192MHz
CPU 2: Intel(R) Pentium(R) 4 CPU 3.20GHz @ 3192MHz
CPU Affinity Mask: 1
Video 1: \\.\DISPLAY1/NVIDIA GeForce 6800
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\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.12

Loaded Modules:
-----------------------------------
Module 0: C:\Program Files\Sony\EverQuest\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\Program Files\Sony\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: C:\Program Files\Sony\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\system32\LPK.DLL
Module 21: C:\WINDOWS\system32\USP10.dll
Module 22: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 23: C:\WINDOWS\system32\comctl32.dll
Module 24: C:\Program Files\WinEQ2\WinEQ2.dll
Module 25: C:\WINDOWS\Lavish.dll
Module 26: C:\WINDOWS\system32\PSAPI.DLL
Module 27: C:\Program Files\WinEQ2\WinEQ2-EQ.dll
Module 28: C:\WINDOWS\system32\MSIMG32.dll
Module 29: C:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 30: C:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 31: C:\Program Files\WinEQ2\WinEQ2-DI8.dll
Module 32: C:\WINDOWS\system32\mclsp.dll
Module 33: C:\WINDOWS\system32\SPORDER.dll
Module 34: C:\Program Files\WinEQ2\EQPlayNice.dll
Module 35: C:\PROGRA~1\McAfee\SPAMKI~1\mskoeplg.dll
Module 36: C:\WINDOWS\system32\OLEAUT32.dll
Module 37: C:\WINDOWS\system32\msctfime.ime
Module 38: C:\WINDOWS\system32\mclsphlr\gdlsphlr.dll
Module 39: C:\WINDOWS\system32\McRtl32.dll
Module 40: C:\WINDOWS\system32\mswsock.dll
Module 41: C:\WINDOWS\system32\hnetcfg.dll
Module 42: C:\WINDOWS\System32\wshtcpip.dll
Module 43: C:\WINDOWS\system32\DNSAPI.dll
Module 44: C:\WINDOWS\System32\winrnr.dll
Module 45: C:\WINDOWS\system32\WLDAP32.dll
Module 46: C:\WINDOWS\system32\rasadhlp.dll
Module 47: c:\progra~1\mcafee.com\vso\McVSSkt.dll
Module 48: C:\WINDOWS\system32\NTMARTA.DLL
Module 49: C:\WINDOWS\system32\SAMLIB.dll
Module 50: C:\Program Files\Sony\EverQuest\EQGraphicsDX9.DLL
Module 51: C:\WINDOWS\system32\d3d9.dll
Module 52: C:\WINDOWS\system32\d3d8thk.dll
Module 53: C:\Program Files\Sony\EverQuest\dpvs.dll
Module 54: C:\WINDOWS\system32\HID.DLL
Module 55: C:\WINDOWS\system32\SETUPAPI.DLL
Module 56: C:\WINDOWS\system32\WINTRUST.dll
Module 57: C:\WINDOWS\system32\CRYPT32.dll
Module 58: C:\WINDOWS\system32\MSASN1.dll
Module 59: C:\WINDOWS\system32\IMAGEHLP.dll
Module 60: C:\WINDOWS\system32\MSACM32.dll
Module 61: C:\WINDOWS\system32\wdmaud.drv
Module 62: C:\WINDOWS\system32\msacm32.drv
Module 63: C:\WINDOWS\system32\midimap.dll
Module 64: C:\WINDOWS\system32\DSOUND.DLL
Module 65: C:\WINDOWS\system32\KsUser.dll
Module 66: C:\Program Files\MUSICMATCH\Musicmatch Jukebox\KeyboardHookDll.dll
Module 67: C:\WINDOWS\system32\MSVCR71.dll
Module 68: C:\Program Files\Sony\EverQuest\eqmain.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce 6800 /nv4_disp.dll/6/14/10/8185
Adapter Display Mode: 1024x768 D3DFMT_X8R8G8B8
Game Display Mode: 1280x1024 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: 487MB
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 2: Illiaria
EQ Path: C:\Program Files\Sony\EverQuest
EQClient.ini: .\eqclient.ini
Patch: ON Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 29 (+145 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: 494MB (BASE+211MB)
Level of Detail: 0
MaxFPS: 100
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=TRUE
Additional setting: 1xPixelShaders=TRUE

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Oct 25 2005 17:13:06
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: FPS Limiter
Max FPS: 30
Rendering: 1/30

Post by **Lax** » Sun Oct 30, 2005 9:38 pm

I have attached my Sysinfo, although I am not sure if these questions have anything to do with that is contained there...

Never hurts, usually I prefer to have it handy when answering questions anyway

Ever since the last EQ patch (aka the patch from Hell) when I am running two sessions of WinEQ, I am getting booted to the secondary session (i.e. the one I am not actively focused on) if it performs an action such as loading, camping, etc. This did not happen prior to the last patch. Previously, I could start the second session, load my toon and switch back to my main while it was loading and zoning with no interruption. The only reason I am curious about this is becuase it has cause me some problems while playing due to the unwanted session cycling to active while I am trying to heal or something. Is there some setting that I missed that would block the program from doing this?

Unfortunately, I'm not sure why this would happen for you, and havent heard reports of this from others at this point, so it's a mystery to both of us

On another note, I have also noticed that since the new 'System Mouse' thing, I can click on the PiP of my second session and it will cycle to it for me. It this permanent? I used to hide stuff behind the PiP screen and now I cannot click on it and drag it out anymore.

This has actually been how it always worked -- if it worked differently for you, it was probably just a fluke. However, you can (temporarily) enable PIP Lock to prevent it from cycling. The default hotkey to toggle PIP Lock is CTRL+ALT+O, but as with all hotkeys, this is configurable if you want

uevrwndry · Post by **uevrwndry** » Mon Oct 31, 2005 10:27 am

Thank you Lax. I will look at the PiP Lock. Now that you mention it, I remember fiddling around with those settings when I was initially trying to figure out how to get the PiP to work and that sort of sounds familiar. It is possible that I had it locked without even realizing it.

On the other issue, I guess since this is not happening to anyone else and you yourself have not experienced it, it is possible that it is something on my end. Although what I haven't a clue... If anyone else has this issue or if you are able to duplicate it I would be interested in knowing, if only to reassure myself that I have not *completely* lost it.