coalquay404

I'd really just like to try Flaming Cliffs. Come on guys. I have no issue with purchasing software that has DRM as long as prompt support is available when that DRM gives me problems. It's now been ten days and not only has my problem not been solved but I actually have no idea when it's likely to be solved. This is terribly poor service and is preventing me from splashing out on BS and A10.

Okay, it's been a week now since I entered the ticket and still no response. Can anybody here give me an indication of when I might even hear from support?

Thanks for the reply. I'll give it a while so you guys can get around to it. By the way, I don't think it's a StarForce issue since I installed the updated drivers before attempting to activate it.

Hi, I originally purchased LOMAC years ago and used to run it on an ancient Pentium 4. I loved it so much that I later went ahead and purchased the first Flaming Cliffs online. Years have since passed and I'd like to play it again. I've just tried to install Flaming Cliffs 1.1b on a new computer (Windows 7 64bit) but I'm running into problems regarding activation. Specifically, when I use the activation key I have for Flaming Cliffs, I receive the following: "Activation failed. You have exceeded the number of activations allowed for the given Serial Number..." My copy may have been reinstalled a few times over the years (primarily due to having to reinstall Windows itself) but I've never given the activation key to anybody else. I've attempted to file a support ticket (ticket ID: 14443) for this but it's been several days now and I've had no response. Can somebody here let me know how I might go about resolving the issue?

The point is though that the strike package almost always gets shot down. I *can* see a group of four F15s on the apron but the AWACS don't appear anywhere at the airbase. Looking at the map in the mission editor the AWACS are supposed to be about 100m due East of the F15s, but they don't show up. A truly bizarre thing about this is that if the strike package doesn't get shot down, they actually attack the spot where the AWACS are supposed to be. I've seen them launch Vikhrs at the apron until they run out, but the mission is never completed. Again, the problem seems to be that the AWACS never show up in the mission, although the computer-controlled strike package does seem to think that they're there.

Has anyone noticed a bug in Mission 11 of the Su-25T Flaming Cliffs campaign? The victory conditions for this mission involve destroying two Awacs aircraft that are parked on the apron at an enemy airbase, as well as taking out Patriot and Hawk missile defense with Kh-58 missiles and an ETS pod. I can take out the missile defenses quite easily, but there are never any Awacs aircraft on the tarmac to destroy! This is in spite of the fact that their icons show up quite clearly on the preflight mission map. Anyone have any ideas about this?

I've spent some considerable time looking at payload issues and there are several things that, from a usability standpoint, deserve to be classed as major design flaws. 1) The whole Classify/Declassify idea is badly implemented. It adds unneccessary complexity to what was an already well-designed mission editor. 2) When at the loadout screen before a mission the Classify/Declassify options in the Edit menu are often greyed out, meaning that you can't click on them. This suggests that the options are unavailable to the user. However, one can always press Ctrl-Shift-C or Ctrl-Shift-D to access these features. From a usability standpoint this is terribly bad design: why suggest to the user that an option isn't available when a secret keypress will actually enable access? 3) Maximum weight: Suppose you load an aircraft with weapons such that it's at 99% of maximum takeoff weight. Now increase the quantity of fuel using the slider and a warning message pops up to tell you that you're over max weight. Clicking on OK removes the message but trying to decrease the quantity of fuel results in a new warning message each time the fuel slider is moved down a notch. Again, bad from a design standpoint. 4) Weapon loadout profiles. Suppose you're flying the "Nighty Night" mission in the Su-33 campaign and want to change your loadout. After jumping through hoops to solve the Classify/Declassify issue you'll eventually get to the loadout screen. A default weapon loadout is selected that corresponds to a preset weapon profile. If you want to change even a single weapon you need to define an entirely new loadout profile. This was handled much better in Lock On 1.0x. I think FC is a great sim, but many of these niggling flaws are reducing my enjoyment of the game significantly.

I've figured out how to do it. When you load up a campaign you can press Ctrl-Shift-C to Classify it. Enter a password. Then press Ctrl-Shift-D to declassify it. You'll need to enter the password you just gave. You can then reconfigure the mission all you want. Oh Eagle Dynamics, why did you bother with such a stupid way of dealing with campaigns. It's counter-intuitive, undocumented, and a pain in the ass. Shame on you for trying to fix a system that wasn't broken in the first place.

Is there any way to forcefully declassify all the singleplayer campaigns in Flaming Cliffs? I *really* enjoy this sim, but not being able to to choose my own loadout on most of the missions is actually ruining my impression of the game. As far as I'm aware, the only new campaign that I can declassify is the Su-25T Flaming Cliffs one. All of the others have the "Declassify" option greyed out so that you can't click on it. Some help with this would be hugely appreciated.

Cool. Thanks for the info. That'll teach me not to pay attention to the manual. :icon_redf

I'm not sure if these are bugs or "features," but I find them pretty annoying. 1) The AI seems to be pretty brain-dead. I refer specifically to the performance of your wingman in the SU-25T flaming cliffs campagin. Time and again I've told my wingman to engage ground targets but he just keeps flying on my wing. 2) I can't seem to change the default loadout of planes in campaign missions. In Lomac 1.0 I could edit the payload quite simply but since I upgraded to FC I can no longer select my weapons before takeoff. It's *very* annoying since I generally don't like the default payload. I can't change the aircraft skins either. 3) If I select Invulnerability On in the global options screen, it is always Off when I get to a campaign mission and there's no way to override it. I'd really appreciate some advice on problems 2 and 3.