session console keyboard input

Discussion of Inner Space

Moderators: Lavish Software Team, Moderators

Post Reply
qinen
GamingTools Subscriber
Posts: 7
Joined: Sun Sep 26, 2004 2:27 pm

session console keyboard input

Post by qinen » Tue Jul 04, 2006 5:02 pm

I am using IS and trying to run two sessions of EQ1 on one computer. I load one session and all is well. The "`" key brings up the console, I can load extensions and run scripts.

If I load the 1st session w/o loading any extensions or run any scripts and then load the 2nd session, it seems key bindings go nutz. I can't bring up the session console with the "`" key. The "f" key starts toggling the FPS indicator on and off (ctrl-alt-f or whatever that combo is also still toggles FPS).

I'm wanting to use the teamspeak HUD. Related question, can I run an instance of the teamspeak HUD in each session ?

qinen
GamingTools Subscriber
Posts: 7
Joined: Sun Sep 26, 2004 2:27 pm

Post by qinen » Tue Jul 04, 2006 5:50 pm

update...

several hotkeys change like the f key I mentioned above. "F, M, X" I know for sure. I can't type anything in EQ1 because they seem to get bound by IS. I can type a capitol F, M, X. I can't type the lower case because f toggles the fps indicator, m toggles the memory indicator, and x toggles me between the sessions.

I have limited it down to: if I run two sessions I'm fine. I can ext isxteamspeak. Once I runscript teamspeakhud, it all goes downhill.

qinen
GamingTools Subscriber
Posts: 7
Joined: Sun Sep 26, 2004 2:27 pm

Post by qinen » Tue Jul 04, 2006 7:03 pm

final update and I give up for a while.

If I run more than one session, the above mentioned hotkeys screw up as described above. I am at a loss as what to try next. As soon as the 2nd character goes past the character select screen and logs into EQ, the above keys mess up.

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

Post by Lax » Wed Jul 05, 2006 10:01 am

Go into the IS configuration window, under Game Configuration, pull down EverQuest. Check the "Virtual Input" box in the middle at the top, and click Apply. Then launch again.

From your description it sounds like a bug with ctrl/alt sticking, which should not be a problem with the new input system (Virtual Input)

qinen
GamingTools Subscriber
Posts: 7
Joined: Sun Sep 26, 2004 2:27 pm

Post by qinen » Wed Jul 05, 2006 11:18 am

Well Hell, that was easy! That fixed it Lax !

Thanks, after struggling with it for hours, its funny in a twisted way how easy the fix was, haha.

Post Reply