![]() |
|
|
|
#1
|
|||
|
You have to mash the key a dozen times for the auto run function to work in Everquest.
Tried three different keyboards. Blacks will pay for this. | ||
|
#2
|
|||
|
Autorun using forward and the enter key.
__________________
"Pleasure writes fewer good songs..."
Red99 | ||
|
#3
|
|||
|
That's neat. Thanks
Anyhow, I rebound the function to a key other than numlock and it works just fine. This is not ideal however, as I've grown accustomed to numlock being my auto run key for over a decade. I've decided not to install windows 8 on my main machine. I guess. | ||
|
#4
|
||||
|
Quote:
http://www.autohotkey.com/ Make a new script and tell your desired key to emulate your destination function key. i.e. numlock :: insert (assuming you've bound auto run to Insert) | |||
|
#6
|
|||
|
Hmm... my Win8 didn't have this problem.
But I ended up changing from numlock anyway, because I hate it. | ||
|
#7
|
|||
|
I will never upgrade to Win8..Vista was bad enough..but I never thought once about running games on it.
Win98/Xp FTW
__________________
~~
Lylith - High Elf Cleric P99 Skelatoria - Dark Elf Necro P99 PortStar - Human Druid P99 Sinfuly - Dark Elf Rogue (MIA 2010) P99 ~~ | ||
|
#8
|
|||
|
This is more than likely because you either have a bad serial connector (or USB connector) or you have numlock mapped to a special function in another program.
For keyboard input, you are actually using a HID driver (human interface device). Every time you press and depress a key there is a HID report being sent to the kernel that processes I/O. In most cases, this would be a report that contains what key, and what it did. In that aspect, pressing 'Num lock' is no different than any other letter or combination thereof. This could be caused by software you have installed alongside EQ. More than likely, something is intercepting this report - as it's not making it to the EQ Client. What kind of keyboard(s) did you use? Are they programmable? Did you have specific drivers downloaded for your keyboard? | ||
|
#9
|
|||
|
I tested it with a Logitech G19, Logitech G15, Razer Arctosa, and a shitty Wal-Mart keyboard. Driver software was installed for the Logitech devices but I could never get them to establish a connection with the Logitech keyboard software, the other two just use windows default drivers.
| ||
|
Last edited by Casey II; 05-28-2013 at 07:58 PM..
| |||
|
#10
|
|||
|
I use Win8 and NumLock works for me.
| ||
![]() |
|
|