[Patrick Proctor]

And I am sorry to hear you are having problems.

The ATF Scenario Pack is built for ATF. In otherwords, you must have ATF for the Scneario Pack to work. It relies on database elements, vehicle icons, and other assets that only ship with ATF.

By backwards compatibility, we DO mean that you can run scenarios from earlier versions of the ATF Engine in later ATF Engine games. But you must have the complete scenarios in order to play the scenario. And, unless an industrious scenario designer starts from scratch, creating all new maps, databases, and vehicle icons, this probably means that each scenario is dependent on the version of the ATF Engine with which it was made.

What you CAN do with backwards compatibility is the following. If, for example, you own ATF, Raging Tiger, and The Star and the Crescent, you can install them in this order:

ATF -> RT -> TSATC

The game will then be upgraded to the latest version of the ATF Engine (The Star and the Crescent), but allow you to run scenarios from ATF and RT (including user scenarios made with those games) in TSATC. However, for instance, if you got a user made scenario made with The Falklands War 1982, it probably will not run in your "uber-TSATC" install, since that scenario will rely on assets found in TFW, that you don't have.

In your situation, you COULD use assets from the ATF Scenario Pack (such as the all new maps and graphics in those scenarios) in your own user-made scenarios. But, as you found, you cannot load the scenarios themselves, because they rely on database files only found in ATF.

Please let us know if we can clear up our marketing in any way to make this clearer. I hate for someone to by one of our games thinking it can do something it can't. And, again, sorry for the confusion.