Application error with globalbind
Moderators: Lavish Software Team, Moderators
Application error with globalbind
Running Everquest 2..
Ok i set up a global bind on my 2nd session, i.e
GlobalBind Test ctrl+1 "press 1"
when i press ctrl+1 on my 1st session, i get an application error.
The instruction at blah blah referenced memory at blah blah. The memory could not be "read"
and consequently my 2nd session closes
Hmm am I doing something wrong? do i need to set something up prior.
What is strange tho, if i had the consol up on the 2nd session, the number 1 gets sent to the console and doesnt crash:)
Ok i set up a global bind on my 2nd session, i.e
GlobalBind Test ctrl+1 "press 1"
when i press ctrl+1 on my 1st session, i get an application error.
The instruction at blah blah referenced memory at blah blah. The memory could not be "read"
and consequently my 2nd session closes
Hmm am I doing something wrong? do i need to set something up prior.
What is strange tho, if i had the consol up on the 2nd session, the number 1 gets sent to the console and doesnt crash:)
Globalbind with EQ2
Was this fixed or are there still issues?
Globalbind
Hrmm, well I am at work atm so cant test it out, but i tried yesterday, and it was not working. Even though it did not crash anymore, the bound key would do nothing. If you had the session with which you bound the key via the console in the forground, it would not do anything either.
I thought this was broken, because of the problems with win32i.
I thought this was broken, because of the problems with win32i.
Still doesnt work for me:(
It just doesnt trigger the key in the other window.
Tried to play with it a bit more, so maybe you can tell me why its not working. I did a Globalbind Test 1 "press 7" on my session #3
If i tried pressing the '1' key on session #2 , it does absolutely nothing, on either sessions. If i pressed '1' key on session #3, then it actually presses the 7 instead.
What am i doing wrong?:(
It just doesnt trigger the key in the other window.
Tried to play with it a bit more, so maybe you can tell me why its not working. I did a Globalbind Test 1 "press 7" on my session #3
If i tried pressing the '1' key on session #2 , it does absolutely nothing, on either sessions. If i pressed '1' key on session #3, then it actually presses the 7 instead.
What am i doing wrong?:(
Well, nothing particularly. EQ2 itself is programmed to ignore any keys if it's not foreground (which is kind of dumb since it wont get non-emulated keys unless it is foreground). You can get around this in IS 0.83 -- in the "Games and Profiles" window, under EverQuest II, Window System, set "Lock Foreground" to ON. Apply changes, and restart EQ2 (or launch it the first time). It should work then 

Actually its not even from the press command. I havnt done enough tests. It seems it happened because of the locked foreground.
When im switching between sessions, ill just notice the ctrl, alt and shift keys were held down, without me doing anything. This happens without using the globalbound keys i set. It happens all the time.
When im switching between sessions, ill just notice the ctrl, alt and shift keys were held down, without me doing anything. This happens without using the globalbound keys i set. It happens all the time.
They shouldnt stick anymore.
I'm slaving away at this trying to get certain things to work with EQ2's input system. For example, correctly binding "alt+1" when you press "ctrl+1". It may work for hotkeys in the game, but it wont correctly work in the chatbox (if you press alt+1 or ctrl+1 in the chatbox manually, it will put a "1". If you press ctrl+alt+1, it puts nothing).
Anyway, for the most part you should be able to use it fine now. Let me know
I'm slaving away at this trying to get certain things to work with EQ2's input system. For example, correctly binding "alt+1" when you press "ctrl+1". It may work for hotkeys in the game, but it wont correctly work in the chatbox (if you press alt+1 or ctrl+1 in the chatbox manually, it will put a "1". If you press ctrl+alt+1, it puts nothing).
Anyway, for the most part you should be able to use it fine now. Let me know