FW190 for Steam DcS 1.5.6 & ED DCS 2.0.5

[jpbordi]

Hello,

 

Question from newbie, i was long time under steam, but lot of module are not yet in sale because in test, alpha, bugs. i use Steam DCS 1.5.6 and i bought all modules available

 

since the presale of normandy map, I take DCS 2.0.5 open alpha, because it is a logic upgrade, for buy M2000, Spitfire, map Nevada and later harrier,F18,F14

 

The good surprise, ED DCS 2.0 found all existing modules bought for steam DCS 1.5.6 steam and i was very happy, but except one.

 

the FW 190 Dora, it was not detected by DCS 2.0.5, i dont see in module manager, is that two specific version for DCS 1.5 / DCS 2.0 ? and must be buy twice ? or is a bug ?

 

i doesnt have issue widh DCS 1.5.6 for FW190

 

Some idea ?

 

Thanks for your help and your feed back

 

KR

JP

Edited May 8, 2017 by jpbordi

[jpbordi]

is the FW190 module compatible for DCS 2.0.5 ?

 

edit

ok after search, seem at last parch DCS 2.0.5, seem major issue with fw190 and doesnt work anymore

 

not good news

Edited May 8, 2017 by jpbordi

[antagonist]

is the FW190 module compatible for DCS 2.0.5 ?

 

edit

ok after search, seem at last parch DCS 2.0.5, seem major issue with fw190 and doesnt work anymore

 

not good news

 

Which were all fixed in subsequent patches.

 

My Dora module was affected with the engine unable to produce any power for some reason. Now it's fixed.

[jpbordi]

thanks for your answer

 

seem not, because module manager dont see it, seem disable or ignored, i miss only this one

[antagonist]

thanks for your answer

 

seem not, because module manager dont see it, seem disable or ignored, i miss only this one

 

It is compatible with 2.0.

 

If you bought the module on Steam, you need to copy the product key and redeem it for your profile on the website.

 

Only then will the 2.0 client ask you to download the module files.

[jpbordi]

thanks for your answer, you give me idea, i check my activation product key steam in profile, i check all information product key, it is valid for starforce, and i compare it with other module product key. i found difference.

 

the fw190 module was unbind with my user, and all other module are bind with my user, it exist an option in the profile information for bind the product key with user current.

 

I set it, and now the module manager can see the fw190. logic behaviours.

 

For me, each upgrade dcs world must save backward compatibility old module, each new module made with using new feature of the upgrade must be buy (like nevada, normandy map). it is logic behaviours.

 

Issue solved, everthing working fine. my modules migration steam 1.5.6 -> dcs 2.0 standalone is done.

 

i am happy :) :) ;)

Edited May 8, 2017 by jpbordi

[antagonist]

You are very welcome. =)