Jump to content
Sign in to follow this  
noubernou

Key In Use issue with Steam and D2D versions running at the same time.

Recommended Posts

I want to run two instances of ArmA 2 at the same time.

I been doing a lot of multiplayer scripting and figured instead of bugging people I know to get on and test stuff for me, which is sort of annoying for both parties I would get another copy of ArmA2.

I have the Steam version as my main copy and I bought another copy off of Direct2Drive and I figured running them in windowed mode would allow me to run one as a server/player and the other as a client.

When I connect though it complains that the CD key is already in use on the D2D version, even though I am running the Steam version. It then, as expected, boots me from connecting.

Does anyone have any ideas on how to fix this (besides running it on another computer)? I figured it would not be an issue with two separate CD keys... :confused:

Edited by NouberNou

Share this post


Link to post
Share on other sites

I think someone from BIS would have to provide more information on how their keys are checked, and since it's part of their copy protection system they're probably unlikely to.

My suspicion is that the key is stored in the registry and if so, it's likely that all versions of the game use the same registry key. Therefore, you could only have one key activated/in use at at time. That's just a guess though and I'm basing that almost entirely on the presence of a registry entry called "KEY" under "Bohemia Interactive Studio\ArmA 2".

If you're up for experimenting with it you might want to try backing up that registry entry, then going through the activation process on your other key and see if it gets changed. If so, you might be able to work around the system by importing the registry settings for one key, starting one copy of the game, then import the registry settings for the other key and starting that one.

To find the registry entries, just do a search for key names of "Arma 2". Mine lives under HKLM\Software\Wow6432Node\Bohemia Interactive Studio\ArmA 2. If you're running a 32-bit version of Windows, it'll probably be under HKLM\Software\Bohemia Interactive Studio\ArmA 2.

Also be aware that messing around with the activating/deactivating keys may eventually cause your key to be useless, and this tomfoolery may trigger all kinds of unwanted side-effects, so proceed with caution.

Share this post


Link to post
Share on other sites

I assumed that the steam version would use Steams normal copy protection methods to protect the install and the D2D would use the traditional methods. I'll have to look into it more. Just a pain the butt.

I tried running under two different windows accounts, like actually switching between the accounts and it still complained.

Share this post


Link to post
Share on other sites

Someone figured out a way to do it a while back but I can't remember how it was done. Search the forums and see what you can find.

Share this post


Link to post
Share on other sites

Try running a ded.server in persistent mode, then join and do some player inputs to be verified and then restart client and JIP to see that the MP things works correct.

Yes, kills the worst monster machine but thats how I do it testing and verifying edits in Warfare - total pain.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×