DAoC Direct Input 7 fix

ingo · Post by **ingo** » Fri Jul 01, 2011 1:09 am

So I had some trouble with Innerspace sending random keys when I played two copies of daoc with it. It really bugged me. Apparently a few others are having trouble with it too. So I thought I'd let you all know how I fixed it.

Easy enough, just right click on camelot.exe (not the shortcut the real app), and go to compatibility. Select run in compatibility mode and use WinXP SP2.

TaDa! No more random hotbar switching, or weird bugs with keys other than what your pressing being activated on key down.

In case you were wondering why I though of that, it's because Lax posted that innerspace only supports direct input 8, and daoc uses 7. Thus using compatibility mode windows 7 seems to translate the commands for you.

Cheers,
-ingo

ingo · Post by **ingo** » Fri Jul 01, 2011 11:45 am

Sorry, I'm too stupid to know how to edit.

Anyway, as I said the fix gets rid of the random key presses, but it still has issues with two key downs at once not working quite right (forward/straif) and keyboard turning/straifing well in auto run or stuck to a object will break auto run/stick.

None the less, if you can live with that it works well enough to be playable.

Also if you can't seem to change settings/key-bindings. Turn off file visualization for that toon, change it, delete the virtualized file, and turn visualization on again. This will save your changes. Seems to be a problem with the virtual file code for daoc.

ingo · Post by **ingo** » Sat Jul 02, 2011 9:50 am

So I believe I've found what the problem is. So long as daoc is selected as being in WinXP SP2 compatibility mode the only error seems to be that for ANY key held event (meaning the event after a key is pressed down and stays down), InnerSpace also sends the Down Arrow Key. Removing down arrow from any key-bindings, /qbinds, seems to fix the problems I've been having at least. However, I'd like to actually be able to use that key so is it possible this is just an error in IS? Maybe a simple 30 minute fix or something? If so, that would be epic, if not, I'll live.

Thanks,
-ingo

Post by **Lax** » Sat Jul 02, 2011 10:14 am

I'll have to take another look

Post by **Lax** » Sat Jul 02, 2011 11:10 am

The post you found about Direct Input 7 is from 2009 and does not reflect the current state of Inner Space. Direct Input 7 is supported and appears to be working.

You should avoid using compatibility mode.

If you can provide me your ISBoxer config I will take a look and see if I can duplicate whatever issues you are having

Post by **Lax** » Sat Jul 02, 2011 11:26 am

I have duplicated the extra keypresses issue you've described, working on it now.

Post by **Lax** » Sat Jul 02, 2011 12:51 pm

This issue is corrected by Inner Space build 5453.

Please DISABLE any compatibility mode settings on IS or the game

I have zero current reports of issues regarding DAOC, if you have a problem report it as new. Thanks!

ingo · Post by **ingo** » Sat Jul 02, 2011 2:32 pm

Nice, even with compatibility disabled your new patch makes it work fine. The only other bug with daoc is more isboxer virtual file related (daoc can't seem to write to the virtual files), but I'll post that in isboxer forums.

Thanks so much for the quick fix!
-ingo

Post by **Lax** » Sat Jul 02, 2011 2:39 pm

Yeah, I am currently working on the issue with virtual files

Agree with taking this to isboxer.com. Thanks!

Post by **Lax** » Sat Jul 02, 2011 3:41 pm

ingo wrote:The only other bug with daoc is more isboxer virtual file related (daoc can't seem to write to the virtual files), but I'll post that in isboxer forums.

Also fixed as of now! Inner Space build 5454 solves this issue.