IS and DaoC Problems

JamieW · Post by **JamieW** » Sat Apr 29, 2006 4:29 pm

Lax:

A couple of things:

1) I seem to be getting the same issue when running DaoC through IS as I was through WinEQ2 on startup (where after typing in login information, and the client actually loading, it crashing). It's not as frequent as it had gotten in WinEQ2, yet, but it's there.

2) I chatted w/ you on IRC a bit, and you gave me some script commands to try. After playing around with them and talking to some others in IRC, it seem that some of the interface might be broken to DaoC? I cannot get a console window to appear in any daoc session, and the relay all press 1 command, for instance, appears to do nothing to either of my local sessions nor my networked/uplinked session on another computer. Although relay all echo hi will return 3 "hi" statements back on the uplink console window, which I'm guessing is expected and indicates that a command for each session is going out.

Post by **Lax** » Sun Apr 30, 2006 11:04 am

I'll look into it, thanks for letting me know

JamieW · Post by **JamieW** » Fri May 12, 2006 5:21 pm

Lax wrote:I'll look into it, thanks for letting me know

Any update on this? Just a friendly reminder in case you haven't gotten around to it.

Post by **Lax** » Fri May 12, 2006 11:53 pm

I haven't specifically tested DAOC, but I have been making changes that may apply to it. Try enabling the Virtual Input system and use the latest development build of Inner Space (check "Use development patches" and restart IS. The refresh/patch now buttons have some bugginess that confuses the hell out of people and makes them whine a lot, so dont use those)

JamieW · Post by **JamieW** » Sun May 14, 2006 9:54 pm

Lax wrote:I haven't specifically tested DAOC, but I have been making changes that may apply to it. Try enabling the Virtual Input system and use the latest development build of Inner Space (check "Use development patches" and restart IS. The refresh/patch now buttons have some bugginess that confuses the hell out of people and makes them whine a lot, so dont use those)

Cool, I'll give it a try here in the next few days, and let you know what I find.

JamieW · Post by **JamieW** » Sun May 14, 2006 10:46 pm

Okay, this is the behavior I'm getting now in Daoc:

I do a:

bind keyone 1 relay all press 1

I have 2 sessions:

is2
REMOTEHOST.is2

thus 2 copies of Daoc are running, one on the computer I'm working on, and one on a seperate computer

If the Inner Sphere Uplink window is active, and I press '1' then it's relayed properly to both sessions (both DaoC instances act as though I'd pressed the 1 key)

However, when I task-switch back to DaoC being the active window, it no longer relays the '1' to the remotehost session... it's almost as though DaoC picks up the keypress and processes it before Inner Sphere sees it.

Is this working as intended for Inner Sphere? If so, it seems like using binds to relays like this won't work for what I'm hoping to do (run 1 remote session on a 2nd computer, and 2 local sessions, and be able to duplicate or translate keypresses to all three sessions simultaneously).

Post by **Lax** » Sun May 14, 2006 11:34 pm

The issue is that binds are a per-session thing. If you create a bind in the Inner Space Uplink, that bind is only going to work in the uplink. If you create a bind on is2, it's only going to work on is2. A global bind (with the globalbind command) will apply to all of windows -- this may not be preferable particularly with a key like 1, since it would stop you from ever pressing 1. Also, even a local bind would stop you from typing 1 in that window except for using the IS bind (e.g. typing in a chat box, you couldnt type 1 without first disabling the bind).

Instead of making the bind in the uplink, make it in the console in the game. Hit ` in the game (by default) to open the console