New Purchase (Issue with steam)

Hi,

I just purchased an addon Hawk T.1A from the E-shop (email m70atkinson@gmail.com) Order#348240, I didn't notice until after the fact that it will not work with my steam version, I do have both versions of dcs running the 2.0 alpha with Las Vegas and steam version 1.5.4.

How can I get this to work with Steam as I would like to fly in both version.

Thanks in advance,

Mark

Hi it wont work on steam. You could download the 1.5 standalone version and move all you steam modules over.

Wasn't sure that would work, I would have to activate everything again I assume. Thanks for the tip..

Wasn't sure that would work, I would have to activate everything again I assume. Thanks for the tip..

There is a procedure to get the keys out if your steam account. You can register these with your ED account on http://www.digitalcombatsimulator.com

DELETED - Sorry, for the confusion, wrong memory on my side.

When the module keys are in the ED database, you can install the modules in the module manager as with DCS World 2.0

I made a how to video a while back. May need to turn the sound up tho my mic was pants hehe

After your modules are registered with your ED account, they won't activate on Steam anymore.

Where did you come up with that information??? Keys bought on Steam will always work on Steam, whether you use an ED standalone installation or not.

Please provide a reference for this information if you can, otherwise don't post something that just bubbled to the top of your head.

Steam Keys will activate Steam and ED Distribution,

As the modules arent activated via steam, they are still Activated via Starfoce Proactive.

The difference is Steam and ED Distributions have different Module Managment for Install and Update process.

Steam Keys will activate Steam and ED Distribution,

 

As the modules arent activated via steam, they are still Activated via Starfoce Proactive.

 

The difference is Steam and ED Distributions have different Module Managment for Install and Update process.

Sorry, my bad then. I had a memory, of a statement that the keys can't be validated in both databases... Guess that has changed with the module manager integration and the registration database, then.

Good to know, so Module Manager and Steam verify the Key through the same StarForce mechanism and the key is valid per machine?

Good to know, so Module Manager and Steam verify the Key through the same StarForce mechanism and the key is valid per machine?

Everything goes in the Windows Registry. You could have twenty different versions of the sim, including a Steam version, installed on the same machine and you would still only be using the single activation stored in the registry. I think my max was around eight different versions but I haven't done that in a while.

The testers, and serious modders, around here would be lost if that was not the case.

Guess that was the whole point of introducing the module manager, to fix the hassles with key activations.

Anyway, this makes it even more convenient for end users now.

Simply install DCS World in parallel. Test and check everything runs flawless and then remove the Steam version if you like, or keep it, if you want.

Another important point, to this discussion, is that by using the 'DCS_variant.txt' file, you can use separate Saved Games folders for any of your installations. This makes playing with configurations nearly painless.

EDIT: Aside from the DCS variant file, you could do this even before DCS World, or the module manager, existed. It is really just a side effect of the way Windows and Starforce work.

Guess that was the whole point of introducing the module manager, to fix the hassles with key activations.

 

Anyway, this makes it even more convenient for end users now.

 

Simply install DCS World in parallel. Test and check everything runs flawless and then remove the Steam version if you like, or keep it, if you want.

The Module Manager had nothing to do with it, Both Steam and ED Versions can run the "protect.exe" file to bring up the activate/deactivate dialog.

Both ED and Steam Use Starforce Proactive, and always have, from DCS:A-10C 1.1.1 to now.

The only difference is steam does the silent Starforce Prompt and auto fills the key into the dialog box.

Steam handles their own Update process and module management.

All you need to move from Steam to ED's Distribution is your starforce license key,

Nothing else.

In fact, if you have Steam's DCS World and Say, A-10C,

You can download EDs DCS World, Install A-10C and Fly without activating again as the Starforce License Key is already activated for that machine.

Ok, now you have me confused, Skate.

I really want to understand this in detail.

If the whole activation is handled completely in StarForce and has no additional checks versus a Steam or EDs key databases, why is it still necessary to bind the Steam keys into your account with ED?

This is only to handle installation?

If I understand that correct one could simply copy all his modules from the Steam install to your DCS install, right? It would seek the StarForce activation in the registry (bound to the PC config) and start any module.

Would online play just require the ED account, or is it necessary to bind the keys to your account?