Sov13t

Yep, we had to evacuate our building in Northern VA... cellphone network down... hanging out outside.... 5.9 magnitude.

Ah okay! Was this your first time ever up in the air like that? or done it before?

@Frazer, come on! Share some of the emotions/feelings... more detail :) Videos are great!

Both engines can definitely be started simultaneously (procedures outlined in 27 manual), of course in scramble type situations only. Otherwise left first - right second as it will be easier to pinpoint faults in systems should one of the engines throw a malfunction. Now, the exhausts on the 27 are located differently... so I could be wrong with the PAK-FA location... but they look rather convincing [to me at least].

АЛ-31 series engines use "turbostarters" to spool up the turbines, they are located on the engine itself and each engine has an independent turbostarter... It would be my guess that the АЛ-41 [117S] that is installed on the T-50 uses the same approach. Picture here: http://koavia.com/gtde.htm

APU exhausts

СУ-35:

Было ли принято решение над судьбой так называемого ГС3, или всё так и осталось в подвисшем состоянии?

Generally you want your curve at around 25-30 for rudder, with a dead-zone of 10 or so...

Thank you everyone for continued interest in this campaign, we are still waiting for responses from a few squadrons as well as evaluating those who have expressed interest in participating in this event. Please disregard the initial August 5th deadline for invites to go out, I fell behind schedule (also some forums are in foreign languages which makes it a little difficult to register and proceed) and thus some of the squads will continue to receive invitations. I have also received numerous private messages with various questions, so let me use this opportunity to answer some of the more frequent ones: Q: Has this event already started? A: No, the event has not been started, we are still in the process of reviewing all of the squads that expressed interest in this event, as well as inviting more squadrons to participate. Q: When is the start date? A: Once we feel that we have enough squadrons signed up we will schedule a meeting for senior officers to discuss the start date as well as any further questions. A rough guesstimate puts the campaign start date at end of August beginning of September. Q: Is the campaign players vs AI or players vs players? A: The campaign is definitely players vs. players! However, we utilize all of the available units that are controlled by AI to simulate the most realistic battlefield environment Flaming Cliffs 2 and DCS: KA-50 can offer. Generals will have the ability to assign waypoints, deploy reinforcements and carry out maneuvers with the AI units. Q: Can lone-wolfs (squad-less pilots) participate? A: Unfortunately, no. From our previous experience this event requires squadron-wide approach, as it is demanding and doesn't last one day. Q: What if some of our pilots will not be able to attend on one of the days? A: This is one of the "hidden" features of Georgian Incident, just like in real life situations you never know what may happen, one day red coalition may be outnumbered and may be forced to defend instead of attack, the other day blue coalition may be outnumbered and will be forced to do the same. However, we do advise squadrons to have back-up pilots for event days so that things remain as balanced as possible. We will do our best to assign squadrons to both coalitions such that the numbers of active pilots are balanced. Hope this answers some of the more frequent questions. Regards, -Soviet

That particular reason comes up a lot in military tech... thrust vectoring is definitely not an iWin button... but with proper use and knowledge base it can prove to be "needed". The Indians at Red Flag abused vectoring so much that it was detrimental to the performance of their birds in dog fights... but as I understand it the F-22 pilots with proper and more training are able to utilize it quite nicely now in CAC.

August 1st, 2011 - The most renowned dynamic multiplayer campaign, The Georgian Incident, is set to resume. Featuring multi-squadron operations, turn based strategic maneuvers, resource management and live ground controllers... The Georgian Incident utilizes every asset of the industry leading simulation platforms by Eagle Dynamics: the DCS:KA-50 and Flaming Cliffs 2, to push virtual immersion to it's limits. Each coalition will have the ability to manage resources, relocate and deploy units, draft and execute plans of action - which results in a fully dynamic front-line. For further details on rules and procedures please direct your attention to the attached SOPs. Starting August 1st, squadrons that have actively participated in the previous installment of the campaign, The Crimean Incident, as well as those squadrons that we see active in the community will begin to receive invitation letters for this event. We are also open to review applications from squadrons that wish to participate but did not receive the invitation by August 5th, please direct your attention to our forum(link below). Should Eagle Dynamics develop a compatibility patch for DCS:A-10C, the Georgian Incident campaign will expand to incorporate interested squadrons into the operations. Upon hearing back from all of the invited squadrons and reviewing potential interested squadrons a meeting with officers of each participating squadron will be scheduled to address any concerns and set the campaign start date. The Georgian Incident Website: http://www.georgian-incident.com The Georgian Incident Discussions: http://forum.51st.org/viewforum.php?f=45 (on the 51st 'Bisons' PVO Regiment board) The Georgian Incident - SOPs.pdf

Here is the stats link: http://www.51st.org/stats/battlestats.php?starttime=2011-07-30%2018:41:36&endtime=2011-07-30%2022:41:53

Thank you all for showing up today, hope it was fun for everyone and for those who missed today's GCI tomorrow is the final day!

This is definitely something everyone should try to attend regardless of their experience. Imagine flying with a live AWACS... as long as you can understand things like: "bandits 130 for 20 angels high hot" you should be just fine!

Ah, they just look so good, made me think it was A-10C engine... can't wait :pilotfly:

Grandsmurf, does this mean you are no longer developing the mod for FC2? but switched to A-10C?

And the more you get to modern day sensors the harder it is...

Nope... they are all the same... Having a realistic thermal model for each type of aircraft and engine... would be something out of this world... but ED has bigger things to work on... such as realistic missile physics etc. Plus, they have no interest in Russian craft at this moment.

Gentlemen, at that range it doesn't matter whether it is the missile or the EOS sensor. The reason there is such a limitation is due to the target aspect being 5-15 degrees which means that the heat source is obscured by the airframe thus no lock for either missile or EOS. The moment you are 15+ degrees the range shoots up almost exponentially. Now, this is 3 dimensional 5-15 degrees... ROE for 27T(E) state to always have +/- 1.5km altitude than the target. And of course, at such short ranges 27R(E) will do the job should the target prove to be stubborn.

Of course... the above should give only a general idea... thermal signatures of engines differ greatly. As well as the manual that this is quoted from is quite dated.

Distance of acquisition on a non-afterburning fighter SU-15 on the backdrop of clear sky in Rear Hemisphere (0/4 - 2/4) [six to eight/four o'clock] is about 50km, on cloudy/ground/water backdrop is about 20-35km. Distance of acquisition of targets such as MiG-25 on afterburners in Front Hemisphere with aspect of 1/4 (one/eleven o'clock) is about 90-100km. Distance of Lock is about 70% of the distance of acquisition. Lock distance on non-afterburning targets in Front Hemisphere with aspect of about 5-15 degrees is about 10km. Pardon the rushed translation... but this should give you an idea. Now, the SU-35 EOS is where it really gets interesting... some distances can rival that of radar... depending on conditions of course.

The WCS of the 27/29 is rather complicated for it to be summarized in two-three sentences. The manuals for both aircraft are rather confusing in their language as well as secondary documents (supplemental systems manuals) sometimes conflict the aircraft manuals... I can see how ED came to the conclusion of automatic radar acquisition and other simplifications, due to the various unclear statements in the manuals that can be interpreted as such. Regardless, the EOS is a rather complicated system that from my limited understanding is deeply integrated into the overall weapons management of the Flanker/Fulcrum. There are such things as Primary and Secondary channels for weapon control and depending on the setting one backs up the other, and so on. But, I do agree that having EOS change to radar on you just because target aspect changed by 10 degrees is a big gimp to some tactical situations... it is equal to that of the F-15s home on jam gimp.

Yep, I miss my 120 slaves I fetched back in the day. :megalol: 'em Georgian ones are the best... I tell ya... No wonder they went after them again.

Out of the 27 manual: 1. Accelerate to Vi=650-750 km/h till H=200m on Afterburner or Maximum setting. 2. Pitch up and maintain M0.8-M0.85 till 10,000-12,000m 3. At 10,000-12,000m accelerate to M1.6 on full afterburner and gain altitude until vertical speed +3-5m/s.