WinEQ + Vista + EQ2 Mouse bug

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
blakhart66
GamingTools Subscriber
Posts: 44
Joined: Wed Jul 14, 2004 8:55 am

WinEQ + Vista + EQ2 Mouse bug

Post by blakhart66 » Sat Mar 08, 2008 12:28 pm

Discovered an interesting new bug today - In EQ2, under Vista Home Premium 64bit, I'm having issues with the camera swinging up so that I'm looking up from beneath my character whenever I click right or left mouse buttons. If I enable mouselook in game, it swings the camera up like that without touching anything... This is only happening when I'm running the game through WinEQ though - after multiple attempts to tweak settings in game to fix it, I tried running EQ2 directly, without WinEQ, and the mouse worked normally... I just built a new system, the same mouse worked just fine under Vista HP 32bit on my old system, so I'm not sure if this is an issue with Vista HP 64bit, or an issue with the latest game update not being fully compatible with current WinEQ, or possibly an issue tied to my new hardware+WinEQ, as there was a new game update several days ago while I was rebuilding the computer.


----------------------------------
WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Windows (TM) Vista Home Premium//6000.vista_gdr.071023-1545
System Physical RAM: 1504/4093MB
Page File: 5668/8344MB
Virtual Memory: 1748/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ @ 2411MHz
CPU 2: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ @ 2411MHz
CPU Affinity Mask: 1
Video 1: \\.\DISPLAY1/NVIDIA GeForce 9600 GT
Video 2: \\.\DISPLAY2/NVIDIA GeForce 9600 GT
Video 3: \\.\DISPLAYV1/RDPDD Chained DD
Video 4: \\.\DISPLAYV2/RDP Encoder Mirror Driver
Monitor 1: \\.\DISPLAY1 (0,0,1680,1050) (1680x1050) PRIMARY
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 7.0.6000.16609
WinEQ: 2.15

Loaded Modules:
-----------------------------------
Module 0: D:\EQ2\EverQuest2.exe
Module 1: C:\Windows\SysWOW64\ntdll.dll
Module 2: C:\Windows\syswow64\kernel32.dll
Module 3: C:\Windows\system32\VERSION.dll
Module 4: C:\Windows\syswow64\msvcrt.dll
Module 5: C:\Windows\syswow64\USER32.dll
Module 6: C:\Windows\syswow64\GDI32.dll
Module 7: C:\Windows\syswow64\ADVAPI32.dll
Module 8: C:\Windows\syswow64\RPCRT4.dll
Module 9: C:\Windows\syswow64\Secur32.dll
Module 10: C:\Windows\syswow64\SHELL32.dll
Module 11: C:\Windows\syswow64\SHLWAPI.dll
Module 12: D:\EQ2\xul.dll
Module 13: D:\EQ2\js3250.dll
Module 14: D:\EQ2\nspr4.dll
Module 15: C:\Windows\system32\WSOCK32.dll
Module 16: C:\Windows\syswow64\WS2_32.dll
Module 17: C:\Windows\syswow64\NSI.dll
Module 18: C:\Windows\system32\WINMM.dll
Module 19: C:\Windows\syswow64\ole32.dll
Module 20: C:\Windows\syswow64\OLEAUT32.dll
Module 21: C:\Windows\system32\OLEACC.dll
Module 22: D:\EQ2\MSVCR71.dll
Module 23: D:\EQ2\plc4.dll
Module 24: D:\EQ2\plds4.dll
Module 25: C:\Windows\system32\WINSPOOL.DRV
Module 26: C:\Windows\syswow64\comdlg32.dll
Module 27: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.6000.16386_none_87e0cb09378714f1\COMCTL32.dll
Module 28: D:\EQ2\mss32.dll
Module 29: C:\Windows\system32\d3d9.dll
Module 30: C:\Windows\system32\d3d8thk.dll
Module 31: C:\Windows\system32\dwmapi.dll
Module 32: C:\Windows\syswow64\IMM32.dll
Module 33: C:\Windows\syswow64\MSCTF.dll
Module 34: C:\Windows\system32\ShimEng.dll
Module 35: C:\Windows\system32\apphelp.dll
Module 36: C:\Windows\AppPatch\AcGenral.DLL
Module 37: C:\Windows\system32\UxTheme.dll
Module 38: C:\Windows\system32\NETAPI32.dll
Module 39: C:\Windows\syswow64\PSAPI.DLL
Module 40: C:\Windows\system32\MSACM32.dll
Module 41: C:\Windows\system32\sfc.dll
Module 42: C:\Windows\system32\sfc_os.DLL
Module 43: C:\Windows\syswow64\SETUPAPI.dll
Module 44: C:\Windows\system32\USERENV.dll
Module 45: C:\Windows\syswow64\urlmon.dll
Module 46: C:\Windows\syswow64\iertutil.dll
Module 47: C:\Windows\system32\MPR.dll
Module 48: C:\Windows\AppPatch\AcLayers.DLL
Module 49: C:\Windows\syswow64\LPK.DLL
Module 50: C:\Windows\syswow64\USP10.dll
Module 51: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6000.16386_none_5d07289e07e1d100\comctl32.dll
Module 52: C:\Windows\system32\mswsock.dll
Module 53: C:\Windows\System32\wship6.dll
Module 54: C:\Program Files (x86)\WinEQ2\WinEQ2.dll
Module 55: C:\Program Files (x86)\WinEQ2\Lavish.dll
Module 56: C:\Windows\system32\iphlpapi.dll
Module 57: C:\Windows\system32\dhcpcsvc.DLL
Module 58: C:\Windows\system32\DNSAPI.dll
Module 59: C:\Windows\system32\WINNSI.DLL
Module 60: C:\Windows\system32\dhcpcsvc6.DLL
Module 61: C:\Windows\system32\wshtcpip.dll
Module 62: C:\Windows\System32\winrnr.dll
Module 63: C:\Windows\syswow64\WLDAP32.dll
Module 64: C:\Windows\system32\NLAapi.dll
Module 65: C:\Windows\system32\napinsp.dll
Module 66: C:\Windows\system32\pnrpnsp.dll
Module 67: C:\Windows\system32\rasadhlp.dll
Module 68: C:\Program Files (x86)\WinEQ2\WinEQ2-EQII.dll
Module 69: C:\Windows\system32\MSIMG32.dll
Module 70: C:\Program Files (x86)\WinEQ2\WinEQ2-D3D9.dll
Module 71: C:\Windows\system32\d3dx9_30.dll
Module 72: C:\Program Files (x86)\WinEQ2\WinEQ2-HooksI.dll
Module 73: D:\EQ2\DbgHelp.dll
Module 74: C:\Windows\syswow64\CLBCatQ.DLL
Module 75: C:\Windows\SysWOW64\dxdiagn.dll
Module 76: C:\Windows\SysWOW64\dxgi.dll
Module 77: C:\Windows\system32\wbem\wbemprox.dll
Module 78: C:\Windows\system32\wbem\wbemcomn.dll
Module 79: C:\Windows\system32\rsaenh.dll
Module 80: C:\Windows\system32\wbem\wbemsvc.dll
Module 81: C:\Windows\system32\wbem\fastprox.dll
Module 82: C:\Windows\system32\NTDSAPI.dll
Module 83: C:\Windows\system32\winbrand.dll
Module 84: C:\Windows\system32\dsound.dll
Module 85: C:\Windows\system32\POWRPROF.dll
Module 86: C:\Windows\system32\nvd3dum.dll
Module 87: D:\EQ2\Miles\mssmp3.asi
Module 88: D:\EQ2\Miles\mssogg.asi
Module 89: D:\EQ2\Miles\mssvoice.asi
Module 90: D:\EQ2\Miles\mssdolby.flt
Module 91: D:\EQ2\Miles\mssds3d.flt
Module 92: D:\EQ2\Miles\mssdsp.flt
Module 93: D:\EQ2\Miles\msseax.flt
Module 94: D:\EQ2\Miles\msssrs.flt
Module 95: C:\Windows\System32\MMDevApi.dll
Module 96: C:\Windows\system32\WINTRUST.dll
Module 97: C:\Windows\system32\CRYPT32.dll
Module 98: C:\Windows\system32\MSASN1.dll
Module 99: C:\Windows\syswow64\imagehlp.dll
Module 100: C:\Windows\System32\audioses.dll
Module 101: C:\Windows\System32\audioeng.dll
Module 102: C:\Windows\System32\AVRT.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce 9600 GT/nvd3dum.dll/7/15/11/7416
Adapter Display Mode: 1680x1050 D3DFMT_X8R8G8B8
Game Display Mode: 1664x1014 D3DFMT_UNKNOWN (Windowed)
Current Adapter: 0
Available Texture Memory: 2268MB
Windows Hooks Input:
-----------------------------------

EverQuest II:
-----------------------------------
Profile 2: Old Drive
EQII Path: D:\EQ2
EQIIClient.ini: .\eqclient.ini
Patch: ON Test Server: OFF Locale: us
Video Adapter: Application Controlled

blakhart66
GamingTools Subscriber
Posts: 44
Joined: Wed Jul 14, 2004 8:55 am

Post by blakhart66 » Mon Mar 24, 2008 12:40 pm

This issue is now fixed =)

blakhart66
GamingTools Subscriber
Posts: 44
Joined: Wed Jul 14, 2004 8:55 am

Post by blakhart66 » Thu Apr 24, 2008 10:54 pm

And the mouse bug is back.... =(

feinam1
GamingTools Subscriber
Posts: 5
Joined: Wed May 14, 2008 4:23 pm

Post by feinam1 » Wed May 14, 2008 6:14 pm

I'm browsing for an answer to my problem, but I'm having a similar issue.. for some reason the keys I had on when switching windows get stuck (i/e CTRL will stick on the window I just left) and the only way to turn them back off again is to go to the window its stuck on and hitting the key again. Your mouse issue might be the system remembering your last movement as you switched windows.

blakhart66
GamingTools Subscriber
Posts: 44
Joined: Wed Jul 14, 2004 8:55 am

Post by blakhart66 » Sun Jun 08, 2008 2:40 am

Still no update from Lax on if there's any word on a solution... haven't used WinEQ in quite a while now since its impossible to play with this bug in effect.. went back to running EQ2 directly and gave up on running 2 accts at once - too bad subscriptions are annual instead of monthly around here =(

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sun Jun 08, 2008 12:48 pm

3 months or a year actually.

I apologize, I've unfortunately been held up by unrelated problems (which I'm not going to go into detail but things keep piling on) for several months now and have had little time to work on fixing WinEQ-specific bugs.

The good news is as follows:
1. This bug does not exist with Inner Space, which has a much more robust and stable input system than WinEQ ever did (I'm not telling you to use Inner Space, though you could if you wanted to; this just helps explain the points below)
2. The Inner Space 2 engine is the next generation of Inner Space technology, and this bug will certainly not exist in the engine
3. WinEQ 3 (which has tentatively been named Cerberus) will be built using the Inner Space 2 engine. Cerberus has been due for a while, but as I have just recently begun to get time to work on Lavish, the Inner Space 2 engine has been the main focus. Cerberus was originally going to be built on Inner Space 1 technology, but IS1 was not built for making applications out of, just in, and therefore the process was cumbersome and would have been hard to maintain. However, the IS2 engine is designed such that the next WinEQ will be the first application built, and this is planned to be available in beta within the next 2 months or so.
4. WinEQ 3 will have new features and should be much easier to use advanced features than with WinEQ 2. For example, there will be an in-game user interface that CAN be used instead of the external interface or having to use hotkeys for everything. I've got lots of other plans too, but that may be one of the most obvious and important. The UI will be a lot easier to use than what is currently in WinEQ 2, and certainly not as complicated as Inner Space's. It'll be cool, kind of just have to see it (and right now the UI is in my head).

So in summary I apologize and I hope you don't get too discouraged; some of these issues are more difficult to fix than they should be (or sound like) due to the design of WinEQ 2. Those design issues are several years old now and (to reiterate) have been solved in newer generations. I am trying to get the new WinEQ out as soon as possible because WinEQ users have been waiting too long for some fixes, and although there has been some setbacks, I should have something to show within a month or two, and I think everyone will be happy with it.

blakhart66
GamingTools Subscriber
Posts: 44
Joined: Wed Jul 14, 2004 8:55 am

Post by blakhart66 » Sun Jun 08, 2008 3:35 pm

Thanks for the update =) I've been using WinEQ since the early days when InnerSpace was in the 'coming soon' stages, was starting to wonder if you were still actively working on WinEQ2 issues.. looking forward to the new version =)

Post Reply