IS and DaoC

[JamieW]

Hey,

It appears that the latest DAOC (1.98) version and Inner Space do not work together.

I know that I asked about it in IRC last night, and you indicated that someone else was mentioning it caused a crash. But I thought I should make a post here, too.

Any ideas on whether you'll get it working again?

[Lax]

I set my DAOC to patch up overnight, so I should be able to take a look at this today

[JamieW]

Excellent!

As a side note. Mythic has unlocked all expansions for all accounts currently. They've also provided a single install download to install directly to the latest expansion/version.

[Lax]

Update: I've fixed the crash, but it turns out DAOC uses DirectInput 7 (or at least the client I have patched up does) which was never implemented for Inner Space. So there's more work to do before it's fully compatible with Inner Space, but I should be able to get it done this weekend.

[JamieW]

DirectInput 7 I'm guessing is earlier than the current support of IS.

I'm surprised it didn't get updated with the WAR release (they're supposedly based on the same engine).

[JamieW]

Oh, and thanks for the effort! I'll probably go ahead and start working on my ISBoxer config for DAOC. I've got Monday morning off of work, so I'm hoping to have something by then to play around with and start re-learning the game.

[Lax]

Yeah, IS was only supporting DirectInput 8. There is now a development build of Inner Space up, build 5027, that has DAOC support. Please try it out and let me know how it goes.

[JamieW]

Awesome. I'll take a look at this tomorrow and Monday.

I patched and got DAOC to startup without the crash and activated the console just fine. I'll need to re-activate more than just 1 account to test out ISBoxer and see how that is working.

[JamieW]

Okay, this is the experience with DAOC thus far:

I setup a character set with 4 characters in them. I setup a window layout to have the inactive screens displayed along the top. I played around with IS to get it to create a default DAOC profile. I turned windowed mode off in DAOC.

When I launch it this way, the first session comes up in full-screen mode. I have access to the console, and I see the text overlay indicating the character slot name.

I checked the "Forced Windowed" in Inner Space (I also tried windowed mode in DAOC, but was met with bad results which I expected from the old days of using WinEQ2)

I launch the character set and while the patcher for character 1 is running, I get pop-up errors indicating that there is a file being accessed that the patcher needs to access. I deduce from looking at the uplink console that IS is instantly trying to run the 2nd character in the character set. I think that it probably isn't following the launch order from camelot.exe to camelot.bin to login.dll to game.dll that appears in the uplink console at each step of the login process. Either reintroducing the old delay or special code will need to handle the launching of the individual characters.

So I let it timeout after the first character, and try to launch the 2nd character. I immediately notice that while IS has resized character 1's window initially to the 1st inactive spot, once I click on it, the window goes back to 640x480 and will not move position/resize when it's supposed to. Character #2's window appears in the same spot as the 1st one, and exhibits the same bad behavior.

When I do move from the character select screen (which is native 640x480 res), and login a character, the window stays the same size (640x480) and the game's graphics are scaled down to that resolution by IS. Again, the window doesn't resize/move dynamically as it should for the ISBoxer setup.

The good news is that if I entered in a windowsize -viewable 1680x1028 command into a logged in character's screen, the window DID re-size. I was able to move around, so input was being received okay. I didn't test out any of the commands that would send anything to alternate windows. I know DAOC has the issue where it doesn't process keypresses unless it thinks its the foreground window. I didn't see any difference thus far from having that option enabled/disabled, so I'll go by any guidance you can give on that.

[JamieW]

Also I thought it might be helpful to have the uplink console window text from when I was doing some of this. You'll see me login the 1st character, then it times out the other characters after trying to launch character #2. Then you'll see another entry where character #2 goes in, and it attempts to launch character #3 and times it out. What the windowsnapper messages are from exactly, I'm not sure:

Code: Select all

/====================================================
|
| 15:39:15 ISBoxer: Preparing to launch Character Set 'Necro_RvR'
| 15:39:15 ISBoxer: Settings imported from ISBoxerToolkit.GeneralSettings.XML
| 15:39:15 ISBoxer: Making sure Characters in Character Set 'Necro_RvR' are valid...
| 15:39:15 ISBoxer: Good!
| 15:39:16 ISBoxer: Initializing PiPSqueak
| 15:39:16 ISBoxer: WindowSnapper Options: -noalwaysontop -norollover -noignorekey
-nodragkey 
Slot 1 is now 0,262,1680,786
Slot 2 is now 0,0,560,262
Slot 3 is now 560,0,560,262
Slot 4 is now 1120,0,560,262
| 15:39:16 ISBoxer: Launching Character Set 'Necro_RvR' ...
| 15:39:16 ISBoxer: Launching Slot 1 Character 'Karley'
Session launched (is20): "D:/Mythic/LOTM/camelot.exe"
Session launched (is1): "D:/Mythic/LOTM/camelot.bin"
| 15:39:19 ISBoxer: Launching Slot 2 Character 'Murphie'
Window not available
Window not available
Session launched (is20): "D:/Mythic/LOTM/camelot.exe"
Session launched (is20): "D:/Mythic/LOTM/login.dll"
Window not available
Window not available
Session launched (is1): "D:/Mythic/LOTM/game.dll"
New window position: -3,239
New Window Size: 1686x812 (Viewable: 1680x786)
| 15:40:19 ISBoxer: Character Set 'Necro_RvR' not fully launched after 60 seconds. Select
again to continue launching additional slots.
| 15:40:19 ISBoxer: Instructions completed.
|
\====================================================

/====================================================
|
| 15:40:34 ISBoxer: Preparing to launch Character Set 'Necro_RvR'
| 15:40:34 ISBoxer: Settings imported from ISBoxerToolkit.GeneralSettings.XML
| 15:40:34 ISBoxer: Making sure Characters in Character Set 'Necro_RvR' are valid...
| 15:40:34 ISBoxer: Good!
| 15:40:34 ISBoxer: Initializing PiPSqueak
| 15:40:34 ISBoxer: WindowSnapper Options: -noalwaysontop -norollover -noignorekey
-nodragkey 
Slot 1 is now 0,262,1680,786
Slot 2 is now 0,0,560,262
Slot 2 is now 0,0,560,262
Slot 3 is now 560,0,560,262
Slot 4 is now 1120,0,560,262
| 15:40:35 ISBoxer: Launching Character Set 'Necro_RvR' ...
| 15:40:35 ISBoxer: Launching Slot 2 Character 'Murphie'
Session launched (is20): "D:/Mythic/LOTM/camelot.exe"
Session launched (is2): "D:/Mythic/LOTM/camelot.bin"
| 15:40:38 ISBoxer: Launching Slot 3 Character 'Jamiewolf'
Window not available
Window not available
Session launched (is20): "D:/Mythic/LOTM/camelot.exe"
Window not available
Window not available
Session launched (is20): "D:/Mythic/LOTM/login.dll"
Window not available
Window not available
Session launched (is2): "D:/Mythic/LOTM/game.dll"
New window position: -3,239
New Window Size: 1686x812 (Viewable: 1680x786)
WindowSnapper: Window will snap to 0,0 with size 560x262
WindowSnapper: Window will snap to 0,0 with size 560x262
WindowSnapper: Window will snap to 0,0 with size 560x262
WindowSnapper: Window will snap to 0,0 with size 560x262
WindowSnapper: Window will snap to 0,0 with size 560x262
| 15:41:38 ISBoxer: Character Set 'Necro_RvR' not fully launched after 60 seconds. Select
again to continue launching additional slots.
| 15:41:38 ISBoxer: Instructions completed.
|
\====================================================

[Lax]

Hi everyone, this thread is 2 years old and does not reflect the current state of DAOC support in Inner Space. There are no currently-known issues with DAOC. If you have a problem with DAOC in Inner Space, please report it as a new issue.

Thanks!