Sticky keys fix?

WinEQ 2.0 Lite discussion

Moderators: Lavish Software Team, Moderators

Post Reply
nuceman
Non-Subscriber
Posts: 3
Joined: Tue Jul 19, 2005 1:44 am

Sticky keys fix?

Post by nuceman » Wed Aug 31, 2005 3:50 am

Today's update to WinEQ 2.10 eradicates the old "Sticky key" issue which plagued everyone who used Global Activation hotkeys, but wouldnt have bothered anyone else.

This bug was fixed as a result of a customer who provided an easy way to reproduce the problem, and should be a lesson to those who do not report their problems or never bother to answer my questions about the problem Smile
I'm having some problems with my looting macros now after todays WinEQ2 Lite update. I have a character that follows me around and loots corpses for me while I kill stuff that runs in the background. I've made no changes to the macros and my internet connection was stable as usual. For some reason my looting character was having trouble looting corpses constantly. He would get stuck in the loot window and the macro would stop. I would have to switch back and end the macro and start it over again.

I noticed that sometimes instead of looting the items it would open the item stats window of the item or sometimes nothing would happen. I've tried using both alt+tab and ctrl+alt+z/c to switch between windows but I still get the same problem. My only guess is the keys were getting stuck when I switched between the windows which is kind of strange since today you updated WinEQ2 to prevent the keys from sticking :\

The only way I could prevent this was to use scroll lock and move my windows so they weren't overlapping each other, which causes some bad lag for me. Any ideas on what to do?

Code: Select all

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows 2000/Service Pack 4/
System Physical RAM: 1043/1535MB
Page File: 1792/2153MB
Virtual Memory: 1284/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 2200+ @ 1804MHz
Video 1: \\.\DISPLAY1/ALL-IN-WONDER 9600 SERIES   
Video 2: \\.\DISPLAY2/ALL-IN-WONDER 9600 SERIES - Secondary 
Video 3: \\.\DISPLAY4/NetMeeting driver
Monitor 1: \\.\DISPLAY1 (0,0,1152,864) (1152x864) PRIMARY
Monitor 2: \\.\DISPLAY2 (1152,0,2304,864) (1152x864)
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2800.1106
WinEQ: 2.10

Loaded Modules:
-----------------------------------
Module 0: C:\Everquest\eqgame.exe
Module 1: C:\WINNT\system32\ntdll.dll
Module 2: C:\Everquest\mss32.dll
Module 3: C:\WINNT\system32\KERNEL32.dll
Module 4: C:\WINNT\system32\USER32.dll
Module 5: C:\WINNT\system32\GDI32.dll
Module 6: C:\WINNT\system32\WINMM.dll
Module 7: C:\WINNT\system32\ADVAPI32.DLL
Module 8: C:\WINNT\system32\RPCRT4.dll
Module 9: C:\WINNT\system32\WSOCK32.dll
Module 10: C:\WINNT\system32\WS2_32.DLL
Module 11: C:\WINNT\system32\MSVCRT.DLL
Module 12: C:\WINNT\system32\WS2HELP.DLL
Module 13: C:\WINNT\system32\DINPUT8.dll
Module 14: C:\WINNT\system32\IMM32.dll
Module 15: C:\Everquest\DSETUP.dll
Module 16: C:\WINNT\system32\VERSION.dll
Module 17: C:\WINNT\system32\LZ32.DLL
Module 18: C:\WINNT\system32\ole32.dll
Module 19: C:\WINNT\system32\SHELL32.dll
Module 20: C:\WINNT\system32\COMCTL32.dll
Module 21: C:\WINNT\system32\SHLWAPI.dll
Module 22: D:\Everquest\WinEQ2\WinEQ2.dll
Module 23: C:\WINNT\Lavish.dll
Module 24: C:\WINNT\system32\PSAPI.DLL
Module 25: D:\Everquest\WinEQ2\WinEQ2-EQ.dll
Module 26: C:\WINNT\system32\MSIMG32.dll
Module 27: D:\Everquest\WinEQ2\WinEQ2-D3D9.dll
Module 28: D:\Everquest\WinEQ2\WinEQ2-D3D8.dll
Module 29: D:\Everquest\WinEQ2\WinEQ2-DI8.dll
Module 30: C:\WINNT\system32\msafd.dll
Module 31: C:\WINNT\System32\wshtcpip.dll
Module 32: C:\WINNT\System32\rnr20.dll
Module 33: C:\WINNT\system32\DNSAPI.DLL
Module 34: C:\WINNT\system32\iphlpapi.dll
Module 35: C:\WINNT\system32\ICMP.DLL
Module 36: C:\WINNT\system32\MPRAPI.DLL
Module 37: C:\WINNT\system32\SAMLIB.DLL
Module 38: C:\WINNT\system32\NETAPI32.DLL
Module 39: C:\WINNT\system32\NETRAP.dll
Module 40: C:\WINNT\system32\NTDSAPI.dll
Module 41: C:\WINNT\system32\WLDAP32.DLL
Module 42: C:\WINNT\system32\SECUR32.DLL
Module 43: C:\WINNT\system32\OLEAUT32.DLL
Module 44: C:\WINNT\system32\ACTIVEDS.DLL
Module 45: C:\WINNT\system32\ADSLDPC.DLL
Module 46: C:\WINNT\system32\RTUTILS.DLL
Module 47: C:\WINNT\system32\SETUPAPI.DLL
Module 48: C:\WINNT\system32\USERENV.DLL
Module 49: C:\WINNT\system32\RASAPI32.DLL
Module 50: C:\WINNT\system32\rasman.dll
Module 51: C:\WINNT\system32\TAPI32.dll
Module 52: C:\WINNT\system32\DHCPCSVC.DLL
Module 53: C:\WINNT\System32\winrnr.dll
Module 54: C:\WINNT\system32\rasadhlp.dll
Module 55: D:\Everquest\WinEQ2\EQPlayNice.dll
Module 56: D:\mq2\3\MacroQuest2\MQ2Main.dll
Module 57: C:\Program Files\Winamp\Plugins\gen_wkc4.dll
Module 58: C:\WINNT\system32\comdlg32.dll
Module 59: C:\WINNT\system32\NTMARTA.DLL
Module 60: C:\WINNT\system32\WINSPOOL.DRV
Module 61: C:\WINNT\system32\MPR.DLL
Module 62: C:\Everquest\EQGraphicsDX9.DLL
Module 63: C:\WINNT\system32\d3d9.dll
Module 64: C:\WINNT\system32\d3d8thk.dll
Module 65: C:\Everquest\dpvs.dll
Module 66: D:\mq2\3\MacroQuest2\mq2itemdisplay.dll
Module 67: D:\mq2\3\MacroQuest2\mq2custombinds.dll
Module 68: D:\mq2\3\MacroQuest2\mq2map.dll
Module 69: D:\mq2\3\MacroQuest2\mq2chatwnd.dll
Module 70: D:\mq2\3\MacroQuest2\mq2eqbugfix.dll
Module 71: D:\mq2\3\MacroQuest2\mq2nokosgscrack.dll
Module 72: D:\mq2\3\MacroQuest2\mq2nostun.dll
Module 73: D:\mq2\3\MacroQuest2\mq2size.dll
Module 74: D:\mq2\3\MacroQuest2\mq2docrack.dll
Module 75: D:\mq2\3\MacroQuest2\mq2zonelag.dll
Module 76: D:\mq2\3\MacroQuest2\mq2wpwarp.dll
Module 77: D:\mq2\3\MacroQuest2\mq2dps.dll
Module 78: D:\mq2\3\MacroQuest2\mq2sumcorpse.dll
Module 79: D:\mq2\3\MacroQuest2\mq2twist.dll
Module 80: D:\mq2\3\MacroQuest2\mq2gank.dll
Module 81: D:\mq2\3\MacroQuest2\mq2exchange.dll
Module 82: D:\mq2\3\MacroQuest2\mq2move.dll
Module 83: C:\Program Files\AIM95\idlemon.dll
Module 84: C:\WINNT\system32\HID.DLL

Direct3D9:
-----------------------------------
Driver: ALL-IN-WONDER 9600 SERIES   /ati2dvag.dll/6/14/10/6497
Adapter Display Mode: 1152x864 D3DFMT_R5G6B5
Game Display Mode: 1024x768 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: 365MB
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: The Thing
EQ Path: C:\Everquest
EQClient.ini: .\eqclient.ini
Patch: OFF  Test Server: OFF  Locale: us
Video Adapter: Application Controlled
Luclin models: 5 (+25 min RAM)
Texture Quality: MEDIUM (+30 min RAM)
Calculated minimum RAM: 338MB (BASE+55MB)
Level of Detail: 0
MaxFPS: 100
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=1
Additional setting: 20PixelShaders=1
Additional setting: 1xPixelShaders=1

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Aug  4 2005 15:40:59
Foreground
Mode: FPS Limiter
Max FPS: 100
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 60
Rendering: 1/1

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

Post by Lax » Wed Aug 31, 2005 8:52 am

You can tell if keys are sticking by having the memory indicator visible. Theyre not ;)

I might be able to help you if you PM me your loot macro, but I have no idea why it would be affected.

nuceman
Non-Subscriber
Posts: 3
Joined: Tue Jul 19, 2005 1:44 am

Post by nuceman » Wed Aug 31, 2005 2:45 pm

I'm pretty sure the keys are sticking. I can see the spell names on the buff names and durations on my background window when I switch with alt+tab or any of the ctrl+alt hotkeys, which only show up when I hold alt, also if I alt+left click any items it opens up the item stats window. Which is what the macro keeps doing. I also tried to type something and closed a bunch of my windows on accident cause control was stuck and I didn't notice.

I'm not sure which memory indicator you're talking about for EQ? I checked under WinEQ, Everquest, and PlayNice preferences and I only see hide memory warnings, which I have set to off. I only see memory indicator options under Warcraft III.

I have no problem with sending you my loot macro, but seeing as it has been working fine the last 2 months with no changes and the day WinEQ has an update regarding sticky keys and all of a sudden sticky key symptoms start showing up, well I just find it hard to put any blame on the macro :\

I know this isn't the MQ2 boards or anything but it's a rather short section of the macro that does the looting. The delays were not originally there, I added them thinking maybe it was some sort of lag issue, but I tested it without the delays under maybe 10-15 fps and it was still looting fine as long as I switched out using scroll lock (mouse release).

Code: Select all

Sub LootMob
/declare LootSlot    int inner  0
/declare LootCheck   int inner  0
/declare LootTotal   int inner  0
   /keypress forward
   /keypress back
   /if (!${Me.Buff["Miraculous Visions"].Duration}) /call Cast "Kizrak's Gauntlets of Battle" item
   /loot
   /delay 1s
   /if (!${Corpse.Items}) {
      /echo NO LOOT! Cheap Bastard!
      /return
   }
   /varset LootTotal ${Corpse.Items}
   /for LootSlot 1 to ${LootTotal}
      /delay 2
      /itemnotify loot${LootSlot} leftmouseup
      /delay 8
      /if (${RV_LootAllItems}) {
         /echo Keeping a ${Cursor.Name}... WOOT!
	/delay 2
         /autoinventory
         /delay 8
      } else {
         /for LootCheck 1 to ${RV_LootArray.Size}
            /if (${Cursor.Name.Find[${RV_LootArray[${LootCheck}]}]}) {
               /echo Keeping a ${Cursor.Name}... WOOT!
               /varcalc RV_LootStats[${LootCheck}] ${RV_LootStats[${LootCheck}]}+1
		/delay 2
               /autoinventory
               /delay 8
            }
         /next LootCheck
      }
      /if (${Cursor.ID}) {
         /echo Destroying a ${Cursor.Name}...
         /delay 2
         /destroy
         /delay 8
      }
   /next LootSlot
   /notify LootWnd DoneButton leftmouseup
/return

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

Post by Lax » Wed Aug 31, 2005 3:00 pm

WinEQ has never reset the status of Alt when you alt+tab out of the window, thats pretty normal behavior. It resets it when you switch back IN though (note that most people dont macro, so it isnt an issue when the window is in the background!). MQ2FPS has a feature in it that resets the modifier keys if you switch away from the window. Did you recently stop using that maybe?

Nevermind about the memory indicator, it's a Pro feature. My bad ;)

Post Reply