berkoutskaia

In FC, Georgian pilots are also able to fly the -25T ;)

You must be talking about the ZSU-23-4 Shilka actually (AAA), since the Strela is an IR-homing SAM launcher, and does not have a radar. And yes, I think the AI of Shilkas is definitely smarter. The Shilka can only fire at a range where the enemy aircraft is visible, so the radar is just there to help ith accuracy, not to detect the targets. And because the Shilka commander doesn't want you to spot him from 10 miles away, he just switches the radar when he wants to soot at you ! Anyway, IMO short range SAMs and AAA (Shilkas, Vlcans, Avengers, Strelas, etc...) is to be taken out with short-range weapon systems (Vikhr, KH-25ML, S-25L...). You need to look more carefully to the vehicles on the ground, but with a magnification of x23, I assure you it's not that difficult to distinguish a Strela from a UAZ ;)

Problem Solved ! I spent the afternoon doing a complete system re-install (disk format etc...) And it worked, I can eventually enjoy Flamming Cliffs. There's just another problem to solve now : but I'm pretty sure ED will answer that next week :D Thanks all for your support !

I got to look somewhere else then :( I played FC a bit this morning (I took a loooonnng breakfast to let it start :D), it's really great, but not easy to enjoy in these conditions :x

Well, could be that this synchronisation driver is for CD games only (STEFOSTEF was talking about SHIII) "Starforce (1.x) and Starforce (2.x) on my rig." Same. Crap, I'm stuck again :p

I just discovered (thanks to STEFOSTEF) that I have only 2 Starforce related drivers in my non plug&play drivers. Looks like "starforce protection synchronisation drivers" are missing... does anyone have an idea how to fix this ???

I already tried this one... doesn't help Thanks anyway, it feels better when you know some people are concerned about your problem ;)

You just have to be patient. This afternoon, I started FC, had lunch, then a small walk downtown, and when I came back I only had to wait to minutes left to fly... It's just a matter of time planning...

Well, I actually used manual activation, and followed Dmut instructions. However, I need to wait approximately 1 hour each time I start FC, and that's not what I call comfortable. I've restarted my computer, de-activatid antivirus software, disabled Virual CD-ROM drives, but it doesn't help. My HDD has 60% of its capacity left (wich means 25Go left)... I'm beginning to think I made a huge mistake yesterday...

WELCOME !!!! go here -> http://forum.lockon.ru/showthread.php?t=7373 , and join the club

Well, problem solved... It's just a matter of how patient you are. I had to wat 50 minutes for LO to start, but it looks really great now. Tnanks to you all !

Thx for answers ! I re-installed twice (by the way, I've got just 2 activations left :x). System specs: Asus A7V8X (VIA KT400) Athlon XP 2600+ (thouroughbred B) 1Go DDR-RAM GeForce Fx5200 SoundBlaster PCI128 Win XP Pro SP2

Hi all, Like many of you here, I've just installed Flaming Cliffs ( No need to notice that I followed Wags' notice carefully ). After Install, I double-click on Lockon 1.1 icon with a lot of excitement, enter my activation key in the Starforce window, clicks on OK, and........ Nothing. The LO icon appears on the taskbar, I can hear the sound of the loading screen, the mouse pointer turns into the grey-yellow LO hourglass when in the middle of the screen (returns to normal windows pointer on the outer). And nothing more. I've waited quite long, but nothing goes forward... I defragged my disk, changed my GPU drivers, restarted many times and so on, I'm still stuck. If any of you has any suggestion (and I really mean ANY ! ), please tell me, I ain't got any idea left :D Thanks

OOPPPSSS ! You're right :oops: I just watched a few video closer, and in fact, the Su-27 has no ailerons. Since the Su-33 has some, it seemed weird that the Su-27 has none. Well , that's one "bug" less to care about :D

Hi all :) Just a few bugs I spotted in LO version 1.02: The roll movement on the Su-27 is being controled by the flaps, not by the ailerons. Although this is only a visual matter, I wanted to report this. A locked target can be tracked with Helmet designator in EOS Mode even though the target is lower than the aircraft's nose. I have no knowledge about this stuff in real life, but as it is specified that the EOS Sensor cannot "see" targets at an angle higher than -15°, it doesn't seem to be realistic. Here's a screenshot: When an engine has been hit by a SAM or AAA, I usually trim the rudder, in order to make it easier while RTB. The problem is that the "trim rudder" command is also associated with a "trim" for nose wheel steering, thus resulting in a very chaotic landing. I hope I'm not too late to let you know of these bugs, since there a rumors speaking of an approaching release of "Flamming Cliffs" :D Perhaps some of those bugs are already known by the devs, and have been corrected, in this case, I'm just a bit more impatien about 1.1 version.