FSDT module and C9

[Dimon]

I'm planning to buy C9 ENBR and just wondering whether I should manually replace purchasing C9 modules to new ones from FSDT (since I have already purchased KORD and LSZH from FSDT).

Thanks
Dmirtiy

[virtuali]

There's no need to do anything special: our module is backward compatibile with Cloud9 products as well, so a single version of the Addon Manager will work at any time, handling all products together.

It's handled by the installers, because there's both version and date/time check so, an older installer will never overwrite new files already on the system.

In case of ENBR, just be sure to update it to the latest SP2-compatible version, found here:

http://forum.fscloud9.it/viewtopic.php?t=5007

[Dimon]

Thanks fo response

Why do I need SP-2 verion if I'm going to use it for FS2004 only?

[virtuali]

Why do I need SP-2 verion if I'm going to use it for FS2004 only?

Well, of course you don't need that one in FS9 but, since you haven't specified which version you were interested into, I simply advised of the only possible issue to be aware of.

[Dimon]

Purchased 3-5 minutes ago. However, AES doesn't allow me to assign credits to ENBR, because AES needs version 1.01 or higher. I DO have version 1.01. What should I do in this situation?

[virtuali]

This is probably a question for the Aerosoft forum, are you using the latest version of AES ?

If you downloaded Bergen recently, surely you have 1.01. But, if you downloaded a while ago, and decided to buy only now, it might be you still have an older version.

However, if you are using the latest Addon Manager and Bergen works and you haven't got any warning about being an older version, your Bergen is updated.


EDIT:
Found a thread on Aerosoft's forum that might be useful:

http://www.forum.aerosoft.com/index.php?showtopic=17477

[Dimon]

Thank again for your help, Virtualli. What I did (before I saw your posting) is disable ALL of AES airports, closed AES, then run it again and checked all the airports again. This time Bergen was checked in Full Mode.

Now seems like everything is fine - perhaps some type of minore technical error in AES.