Вы находитесь на странице: 1из 31

(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Eurofighter Typhoon Package


Manual

1
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Table Of Contents

Introduction : 3

Special Thanks to : 3

About the Eurofighter Typhoon Package : 3

Features of the EFTP : 4

Notes : 6

Appendix A – The Eurofighter Typhoon aircraft:


Introduction : 6

A brief history : 6

Operators : 7

The aircraft : 11

Appendix B – Eurofighter Typhoon Flight Manual:


Introduction : 15

Aircraft versions : 15

3-D Model and Skins : 15

Basic aircraft data : 15

Flight Model : 15

Signature : 19

Various : 19

Cockpits : 19

Avionics : 20

Weapons : 22

How to fly and fight 25

Appendix C – The How to section

Introduction : 27

How to use Aeyes EF2000 Superpit : 27

How to add/change weapon loads : 28

How to add new squadrons : 30

2
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Introduction:
The Eurofighter Typhoon Package (EFTP) as an integral part of Open Falcon 4.7 represents the
pinnacle of an almost 5 years long development effort which started in autum 2003 with the aim to
increase the realism and improve the in simulation experience when flying the Eurofighter Typhoon
aircraft in Falcon 4.0. Not less than 14 versions of the initial EF2000Patch series were released
between November 2003 and April 2005 for various versions of Free Falcon 2, Free Falcon 3 and
Super Pak 4. The EF2000Patch series was eventually succeeded by the more comprehensive EFTP
series, 6 versions of which were released between April 2006 and May 2008 for the final versions of
Free Falcon 3 and Super Pak 4, various versions of Free Falcon4/Red Viper 1 and Open Falon 4.5. A
first attempt to integrate the EFTP into a Falcon 4 patch standard was initiated in late September
2007. It was planned to integrate it into OF 4.6 which was under development at that time.
Unfortunately OF 4.6 was finally cancelled, but in May 2008 the Global Falcon team released the so
called “4.6 get you started files” which were nothing else than the unfinished OF 4.6 beta files. In late
May 2008 members of the OF community started the OF 4.6 OCI project (One Click Installer) with the
aim to integrate the 4.6 beta files and various community mods, released since OF 4.5, into a single
package with a simple to use one click installer. As more and more stuff was added the project was
renamed to OF 4.7. Though large parts of the EFTP were already incorporated into the OF 4.6 beta,
development was just completed as part of OF 4.7. OF 4.7 is therefore the first Falcon 4 patch
standard to include the complete EFTP in the default install.
This manual describes the features of the EFTP as part of OF 4.7, gives credit to its contributors and
includes some useful information and tips about the Eurofighter Typhoon aircaft in OF 4.7 as well as
some support.

Special thanks to:


Over the years a couple of people contributed to the EFTP, though not all were directly involved into
this version their work was adopted. I want to thank all who helped me and the F4 community which
made this simulation to what it is today.

Development responsibilities:

Scorpion82 (author):
- Project management, features integration, data edits, flight model, 3-D cockpit modifications,
Lw skin modifications, RAF, AMI and BH skins, campaign modifications, UI work
(redesignations, icons…)
Mapi:
- 3-D cockpit, highres GAF skins and basic work on the chaff/flare dispensers

Selot:
- EdA skins

Joelhume:
- original FM though not much is left of it now

[BR][Raptor]:
- Additional Eurofighter Typhoon aircraft for OF 4.7 (lods, ct entries…)

About the Eurofighter Typhoon Package:


Super Pak 3 was the first Falcon 4 patch standard to include the Eurofighter Typhoon aircraft, but it
was neither fully developed, nor fully integrated at that time. In February 2003 I had the opportunity to
test a Typhoon beta package in SP3 developed by Joelhume. This package contained a new 3-D
model and skin from Ripper87th and a new flight model, modified rolling fire campaign, Eurofighter
specific entries for hardpoints and the radar and some data edits developed by Joelhume. I evaluated
the FM and reported my feedback to Joelhume who further adjusted it. We were hoping that the work
would make it into SP4, but that wasn’t going to happen. It was in fact Free Falcon 2 which became
the first F4 patch standard to feature a fully developed and integrated Eurofighter Typhoon. I
evaluated the FF2’s EF2000 but was a little bit disappointed so that I started to mod FF2 on my own
using TacEdit and F4Browse and adopting Joelhume’s FM. This was done for personal use only. To
avoid doing all the work again when I had to make a fresh install, I started to search for all the files
being affected by the modifications and backed them up. At that point I thought why not sharing this
achievement with the community as a small free mod. After receiving permission from Joelhume to

3
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

use his FM for the project the first mod was quickly released. Designated EF2000Patch v3 it was the
first publically released version. As all F4 patch standards since FF2 featured the Eurofighter Typhoon
aircraft I subsequently developed new versions of the EF2000Patch and with my growing experience
they became more and more comprehensive. Between November 2003 and April 2005 14 versions of
the EF2000Patch series were released for various versions of FF2, FF3 and SP4. From then on the
EF2000Patch series was ultimately replaced by the more comprehensive Eurofighter Typhoon
Package series (EFTP). Additional features such as 2-D and 3-D cockpits as well as new skins were
planned and people like Eole2 and Mapi supported me to achieve this goal. Unfortunately the 2-D
cockpit never went beyond an early beta status and couldn’t be adopted. The first EFTP versions
(v.0.9FF & SP) were finally released in April 2006 for SP4.2+BMS 2.0 and FF3.11+CobraOne
(optionally). 2 Additional versions followed for FF4/RV in February and March 2007 and another
update in November that year. An OF compatible version was initially skipped, but I eventually decided
to develop one for OF 4.5 back in August 2007. The EFTP v1.0OF was finally cancelled in late
September 2007 in favour for direct integration into the upcoming OF 4.6, whose release was soon
expected at that time. As 4.6 was delayed and eventually cancelled, I finally resurrected the EFTP
v1.0OF for OF4.5 on May 1st 2008 and released it the same month. As the global falcon team
abandoned any further development work on OF, just a kind of unfinished 4.6 was released
incorporating some of the work. When the community decided to develop the version 4.7 adding new
features and realising an one click installer the work could be completed and directly integrated. OF
4.7 is therefore the first Falcon 4 patch standard ever including the full EFTP features by default,
without the need to install it separately.

Features of the Eurofighter Typhoon Package:

The Eurofighter Typhoon Package introduces changes and additions to the Eurofighter Typhoon
combat aircraft and some of its associated weapon systems. Some changes/additions for the UI were
introduced as well.

All the modifications done will be described below under “UI”, “Aircraft”, “Weapons” and “new
Weapons”.

UI

- EF2000 Typhoon GE & UK renamed to Eurofighter and Typhoon FGR.4. These are the
designations used by the Luftwaffe and Royal Air Force
- Eurofighter Typhoon specific icons added for the UI (mission rooster, planning map etc.)
- JG 74, No.3F and 11F squadron patches added to the database (selectable from the logbook)
- Eurofighter added to the dogfight mode

Aircraft Modifications

- Austrian, Italian and Spanish Eurofighter Typhoons added


- 2 hires skins for each Eurofighter Typhoon representing series production aircraft as they are
in service with the Jagdgeschwader 73 & 74 (Luftwaffe), No.3(F) & 11(F) squadrons (RAF), 4°
& 36° Stormos (AMI), Ala 11 (EdA) and Luftraumüberwachungsgeschwader (Bundesheer)
- Simple 3-D cockpit
- Dimensions corrected according to data published by reliable sources like the manufacturer
(Length: 52.40 ft/15,96 m; Height: 7.40 ft/5,28 m; Span: 35.11 ft/10,95 m)
- Weights corrected (empty: 24250 lb/11000 kg; MTOW: 51700 lb/23500 kg) according to
current data published by reliable sources like the manufacturer
- Internal fuel load corrected to 11440 lb (5200 kg) according to current data published by
reliable sources like the manufacturer
- Flaps deleted in the takeoff/landing configuration as for the real aircraft
- More effective airbrake with increased deflection angle
- Symmetrical canard operations only as for the real EF2000
- Gear position modified, looks more realistic now
- More realistic leading edge slat behaviour
- Slightly modified pitch/roll/yaw momentum
- More realistic engine nozzle behaviour related to engine thrust

4
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

- Completely new flight model which brings the flight characteristics & performance closer to the
real EF2000
- Realistic chaff/flare dispensers (number, locations, deployment vectors and load of 320 Chaff
& 32 Flares)
- ECM strength increased
- Modified radar with greater range, coverage, sweep speed, ECCM and look down range
- New more realistic IRST (used by AI controlled aircraft only)
- Increased range for RWR
- Slightly reduced RCS
- Corrected and changed weapon load configurations reflecting the expected weapon options
for block 8 aircraft which will be delivered around 2012+ (except for Austria)
- Modified ATO-Tasking to suit the changed weapon load configurations.
- Modified squadron stores indexes making all integrated weapons available in the campaign
- Increased engagement envelope and changed AG weapon release altitude for AI controlled
aircraft
- Partially changed performance/behaviour parameters for AI controlled EF2000

Weapon Modifications

Mauser Bk27 gun:


- Renamed from 27 mm-1 to Mauser Bk27
- Is now shown as GUN in the SMS MFD page
- higher accuracy and effectiveness
- corrected v0 and firing rate
- corrected gun location

Meteor:
- weight corrected to 407 lb
- Flight time increased to 150 seconds
- Flight range increased to 80 NM
- CM resistance and range of the radar seeker increased
- New rocket motor enabling a more realistic flight profile and increasing range and endurance
- New DLZ timer which better suits the increased range
- Pickle delay and INS support added

ASRAAM:
- Modified rocket motor burning profile

IRIS-T:
- Modified rocket motor burning profile
- Max. g-load increased to 60 g

Storm Shadow:
- Increased maximum flight time and range
- Improved warhead effectiveness
- New propulsion data

1000 l AMX drop tank:


- Reduced drag

New Weapons

EGBU-16:
- Based on the GBU-16 LGB but with GPS-guidance+TGP support

GBU-54:
- Renamed copy of the GBU-38 with TGP support

5
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Enhanced Paveway IV (EPW IV):


- Renamed copy of the GBU-12 with GPS guidance and TGP support

Litening LDP:
- CAT III limited
- Selectable from the “other” section in the weapon load screen
- Activates TGP function

Notes:

- The modifications are based on information/data officially published by the manufactures,


militaries and other serious sources
- There is still no guarantee that the information/data which were used are fully correct
- Some weapons available in reality aren't included into Falcon 4.0 and can't be used.
- All data changes were realized by edits primarily done with F4Browse 2.31 and TacEdit 2.48,
except for the flight models, skins and cockpit
- It is not necessary to load the Litening LDP, as the TGP function will be automatically
available as soon as LGBs are loaded

Appendix A:

The Eurofighter Typhoon aircraft

Introduction:
The Eurofighter Typhoon is a 4th generation multirole combat aircraft jointly developed by Germany,
Italy, Spain and the United Kingdom. Designed as a singleseat, twin engined delta/canard fighter, the
Eurofighter Typhoon was optimised for the airdefence/air superiority role, with a secondary ground
attack role.

A brief History:
Back in the 1970s a number of western European airforces were looking for the procurement of new
generation fighters to replace a number of ageing types in a varity of roles. Especially the UK,
Germany and France were looking for joint development of a 4th generation fighter. Initial efforts ended
without any results due to different requirements of the participating airforces. In 1981 the cooperation
between the 3 partners ended temporarily. At that time Italy and Spain started to show an increased
interest in a multinational cooperation on the development of a new multirole combat aircraft.
Following national and multinational concept studies the Eurofighter project was finally started on 16
December 1983 under the designation FEFA (Future European Fighter Aircraft), which was soon
changed to EFA (European Fighter Aircraft). Though some basic agreements were achieved, the
partner nations were not able to come to a common solution however. In 1985 France finally left the
project and decided to go ahead alone and eventually developed the Rafale. The remaining partners
decided to go ahead and the development phase was finally started on 23 November 1988. The end
of the cold war and the German re-unification eventually led to political changes and a reorientation
phase was eventually established in 1992. In January 1994 the re-orientation phase was finally
completed, followed by the first flight of prototype DA1 on March 27 1994. A total of 7 prototypes were
built for the flight test program. On December 22 1997 the four partner nations finally agreed on the
production phase. The umbrella production contract was signed January 29 1998 and a first
production tranche was ordered on September 18 1998. Following the 4 national type acceptance on
June 30 2003, deliveries started and the type was eventually introduced into service throughout 2004.
The second out of the 3 planned Tranches was ordered on December 14 2004, with negotiations for
the third tranche being well underway. All customer nations have agreed to purchase a total of 620
aircraft.

6
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Operators:

Royal Air Force:

No.11(F) squadron Typhoon FGR.4 with 2 x ASRAAM, 4 x AIM-120C, 6 x Brimstone, 2 x EGBU-16, 2


x 1000 l tanks and a Litening LDP

The United Kingdom is the largest customer, with BAE Systems being the british partner within the 4
national Eurofighter consortium. BAE Systems had a 33% workshare in the development phase and
contributed the single- and twinseat prototypes DA2 & 4. The UK has commited to the purchase of 232
aircraft, including 37 twinseaters, though its commitment has become shaky over recent years. BAEs
production workshare is 37,5% with the company being responsible for the manufacturing of the front
fuselage, spine, outboard flaperons, fin and the first rear fuselage section. Final assembly for RAF
aircraft is conducted at BAEs Warton facility. The designation Typhoon was officially adopted by the
RAF on July 23rd 2002. Initial block 1 aircraft were designated Typhoon T.Mk1, while batch 2 aircraft
were designated T.Mk1A or F.Mk2 in their twin- and single seat versions respectively. The latest
multirole capable block 5 aircraft are dubbed T.Mk3 and FGR.4.
In RAF service the Typhoon will replace the Tornado F.Mk3 ADV interceptors and the Jaguar Gr.3/3A
attack aircraft.
The first Typhoon T.1 twinseat was handed over to the RAF at Warton on June 30th 2003. The
Operational Evaluation Unit No.17(R) squadron eventually stood up at Warton on December 17th
2003, followed by the No.29(R) squadron acting as Operational Conversion Unit which stood up at
Warton on May 19th 2004. Initial operations were carried out from Warton as part of the Case White
agreement in which BAE Systems trained first pilots and technicians and was responsible to support
the initial RAF operations with the type to ensure a high availability rate and smooth the entry into
service. Case White was successfully completed on April 1st 2005, two month earlier than expected,
followed by the transition of the No.17 & 29 squadrons to the RAF airbase Conningsby, Lincolnshire.
On March 31st 2006 the No.3(F) squadron stood up at Conningsby as the first operational frontline
unit. The next operational unit to be formed at Conningsby on March 29th 2007 was the No.11(F)
squadron. The RAF finally declared the Typhoon operational on June 29th 2007, with the Typhoon
squadrons at Conningsby sharing the QRA commitment with the Conningsby based No.25(F)
squadron flying Tornado ADV. Since April 1st 2008 the Typhoon is soley responsible for QRA duties
over South England, on that day the RAF declared the Typhoon fully operational for deployments
around the world in the Air-Air role as well. On July 1st 2008 the Typhoon eventually achieved full
operating capability as a multirole fighter with the No.11(F) squadron. The next unit to convert to the
Typhoon is the currently inactive No.6 squadron which will stand up at Conningsby in 2011, before
being transfered to RAF base Leuchars, Fife. The RAF plans to equip a total of 7 frontline squadrons
with the type which are intended to be multirole capable in long terms.

7
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Luftwaffe:

A Eurofighter from the JG 74 in an airsuperiority configuration with 2 IRIS-T and 6 METEOR missiles

Germany has commited to the procurement of 180 Eurofighter, including 33 twinseaters. The German
industrial partner within the Eurofighter consortium is EADS Military Air Systems which had a work
share of 33% for the development phase and which contributed the 2 single seat prototypes DA1 & 5
for the flight test program. With a 30% share on the series production EADS Germany is responsible
for building the complex centre fuselage and for final assembly of German and Austrian production
aircraft. In Luftwaffe service the Eurofighter will mainly replace the F-4F Phantom II airdefence fighters
and parts of the Tornado IDS fighter-bomber fleet. The first German twinseat production aircraft
arrived at the technical school of the Luftwaffe at Kaufbeuren on February 17th 2003 were the technical
personal is trained. The first aircraft was handed over at the manufacturers facility at Manching on
August 4th 2003, followed by the EADS led Service Instructor Pilots Taining (SIPT) course. The
Eurofighter eventually entered service with the 2nd squadron of the Jagdgeschwader 73 “Steinhoff” at
Laage airbase in north-east Germany on April 30th 2004. JG 73 is the Luftwaffes operational
conversion unit, but it will also take over airdefence duties if required. Germany was the only customer
which operated the type without industry support form the very beginning. The first operational unit to
convert to the Eurofighter was the Jagdgeschwader 74 at Neuburg which introduced the type on July
25th 2006. Following a first QRA scramble on January 8th 2008 JG 74s Eurofighters shared the QRA
commitment with the remaining F-4F of the unit before assuming sole responsibility for QRA over
southern Germany on June 3rd 2008. The Phantoms fly-out ceremony was held on June 12th 2008. In
late 2009 the Jagdbombergeschwader 31 “Bölcke” at Nörvenich will start conversation from the
Tornado IDS to the Eurofighter as the first multirole unit, followed by the Jagdgesdchwader 71
“Richthofen” at Wittmund in 2011 and the Jagdbombergesdchwader 33 at Büchel from 2013.

8
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Aeronatica Militare Italiana:

An AMI F-2000 from the 36° Stormo in an airdefence configuration with 2 IRIS-T and 4 AIM-120B
AMRAAM missiles and a centreline 1000 l drop tank

The Aeronatica Militare Italiana intends to receive a total of 121 Eurofighter Typhoon aircraft including
15 double seaters, which will be used in the air defence/air superiority role to replace the already
outphased F-104 Starfighters. From the mid 1990s the F-104 was complemented by 24 Tornado ADV
leased from the RAF before being temporarily replaced by 34 F-16A/B second hand aircraft, leased
from the USAF. The Italian partner in the Eurofighter consortium is Finemeccanica which held a work
share of 21% percent during the development phase and provided the 2 single seat prototypes DA3 &
7. Finemeccanica holds a production work share of 19.5% in the production phase and is responsible
for the production of the left wing and the 2nd and 3rd rear fuselage section as well as final assembly for
Italian production aircraft. First pilots and technicians were trained from October 2003 at the
manufacturers site in Caselle near Turin. The first twin seater was officially handed over to the AMI on
February 19th 2004 and was subsequently delivered to Cameri where the technical personal is trained.
On March 23rd 2004 the Eurofighter, which is designated F-2000 in AMI service, finally entered service
with the 9th Gruppo of 4° Stormo at Grossetto airbase. Between March 2004 and March 2006 initial
operations were support by the manufacturer as part of the BOSS agreement (Batch One Support
System). The 20th Gruppo was the second squadron to convert to the type and acts as OCU. From
December 16th 2005 AMI F-2000s were assigned to QRA/air surveillance missions, within the AMIs
national air defence system. Initial operating capability (IOC) was eventually declared on January 1st
2007. The 36° Stormos 12th Gruppo received its first aircraft on October 1st 2007. Full operating
capability is expected to be achieved by the end of 2008. The 5° Stormos 21st Gruppo at Servia and
the 37° Stormos 18th Gruppo at Trapani will be the next units to convert to the type, given Italy stays
commited to its planned buy of 121 aircraft.

9
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Ejercito del Aire:

An Ala 11 C.16 during an interdiction mission with 4 IRIS-T and METEOR missiles each, 2 GBU-16
LGBs, a Litening LDP and two 1000 l drop tanks

Spain intends to buy a total of 87 Eurofighter Typhoon aircraft, comprising 72 single seat and 15 twin
seat aircraft. The Spanish industrial partner EADS CASA had a work share of 13% in the development
phase and contributed the twin seat prototype DA6 to the test fleet. The EADS CASAs production
work share accounts for 13%, with the EADS CASA facility at Getafe near Madrid being responsible
for the manufacturing of the right wing and leading edge slats, as well as final assembly for the Ejercito
del Aires aircraft. The EdAs internal military designations are C.16 for the single seater and CE.16 for
the twin seater. The EdA officially accepted its first aircraft on September 5th 2003 followed by a 9
month long SIPT course and training of technicians before the first 3 aircraft entered service with the
Ala 11 at Moron airbase on May 27th 2004. The first squadron, the 113th Escuadron, was formally
activated on December 23rd 2003 and acts as operational conversion unit. The first operational unit ,
the 111th Escuadron stood up at Moron in 2006. Though first air surveillance/policing missions were
conducted as early as February 2007, QRA responsibility was not assigned before July 17 2008, with
FOC being expected in 2009. From that year the Escuadron 112 will be formed. The next units to be
equipped with the type will be the Escuadrons 141 and 142 of Ala 14 at Albacete airbase in 2011 and
2013 respectively. All four frontline units are intended to be multirole capable in the long term and the
type will eventually replace the Mirage F1M and some of the early EF-18A/B Hornets. The EdA started
to work in close cooperation with the industry but plans to become less dependent from the industry
over time.

10
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Bundesheer:

A Eurofighter from the Austrian Luftraumüberwachungsgeschwader on an


air policing mission with 2 IRIS-T AAMs

Austria is the first export customer for the Eurofighter Typoon aircraft. A fighter procurement
competition to replace the Bundesheers ageing J-35Ö Draken interceptors was initiated by the
Austrian government around 2000. EADS in place of the Eurofighter GmbH, Lockheed Martin and
Saab Dynamics competed for the final bidding process and the Eurofighter was surprisingly selected
by the Austrian evaluation committee on July 2nd 2002. Initial plans called for 24 single seaters, plus
options for 6 twin seaters. Heavy resistance from the political opposition and the costs related to the
flood catastrophe in August 2002 led to a reduction to 18 aircraft without options. The contract for the
delivery of 18 tranche 2 aircraft beginning in May 2007 was finally signed on July 1st 2003. Due the
delays in the signature of the tranche 2 contract, the 4 partner nations agreed to divert 6 of their
tranche 1 single seaters for Austria. As the Draken reached the end of its service life, Austria least 12
F-5E Tiger II from the Swiss in 2004 as a temporary replacement until the Eurofigher has become fully
operational. On June 27th 2007 the defence minister of the new Austrian government selected in
November 2006 announced the results of new negotiations with the Eurofighter GmbH. Austria will
receive only 15 aircraft which come from the tranche 1 contingent, 6 of which will be used aircraft from
the Luftwaffe. The Austrian Luftraumüberwachungsgeschwader at Zeltweg received its first aircraft on
July 12 2007 and declared the type operational in the intended air policing role on July 1st 2008. The
last aircraft will be delivered in 2009. Austrian aircraft are assembled at the EADS facility in Manching,
while technical and flying personal of the Bundesheer is being trained at the Luftwaffes training
facilities at Kaufbeuren and Laage.

The aircraft:

Airframe design:
The Eurofighter Typhoon is a relative small and compact aircraft built with advanced materials such as
carbon-fibre composites which account for 70% of the airframes surface. 12% account for glass-
reinforced plastics, 15% for metals and 3% for other materials. The result is a compact, light weight
airframe with enough structural strength to last for some 25-30 years of operational life equal to 6000
flight hours depending on the usage. The aerodynamics are optimised for high supersonic
performance and subsonic agility and manoeuvrability. The designers opted for an unstable
delta/canard configuration with large, highly swept delta wings, featuring full span trailing edge
flaperons and leading edge slats, all moveable canard foreplanes, a single fin, a large airbrake on the
spine and below fuselage mounted airlift intakes. This provides a low drag/high lift configuration with
sufficient airflow being provided to the engines over the entire flight envelope from low speeds/high
AoAs to supersonic speeds at high altitudes. The unstable configuration provides excellent subsonic
agility and low trim drag at supersonic speeds. The unstable configuration requires an electronic flight

11
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

control system however. The Typhoon features


an advanced quadruplex digital fly-by-wire
system with full carefree handling
characteristics over the entire flight envelope.
The FCS features an automatic low speed
recovery system and a dis-orientation recovery
capability. The latter one recovers the aircraft
in the case of pilot dis-orientation by pressing a
button. The FCS can additionally initiate a pull-
up if the aircraft is in danger to decent below
the programmed minimum radar altitude or to
collide with the ground.
The Eurofighter Typhoon is powered by two
modular designed Eurojet EJ200 twin-spool
turbofan afterburning engines, which feature
digital engine controls and electronic monitoring equipment. The EJ200 provides full carefree handling
characteristics as well and generates a static thrust of up to 60 kN (~13000 lb) of dry thrust and 90 kN
(~20000 lb) reheat thrust.
The result is a high performance aircraft with an excellent thrust to weight ratio in excess of 1:1 and a
low wing loading. The Typhoon is capable to go supersonic at all altitudes and achieves a top speed
of about mach 2 at altitude. In addition the aircraft provides a supercruise capability and is praised for
its high altitude performance. The aircraft impresses with its excellent nose pointing capabilities, high
subsonic and supersonic agility and manoeuvrability.
Though not designed as a stealth aircraft some LO treatments were incorporated to reduce the
aircrafts frontal radar cross section.

Cockpit:
From the outset designed as a single seat fighter to be
used in complex combat situations, a lot attention was
spent on creating the aircrafts sophisticated man machine
interface (MMI). Part of this MMI is the advanced cockpit
which is surprisingly spacey for such a compact aircraft
and which provides an excellent view. The pilot takes
place on an electronically controlled Martin Baker Mk-16A
00-ejection seat with a 18° inclination. Pilot protection is
assured by newly developed flying suits such as the APA
(Aircrew Protection Assembly). The APA comprises
pneumatic anti-g trousers which are connected to the
boots, complemented by a pneumatic anti-g west and a
positive pressure mask. German and Austrian pilots will
wear the even more advanced Libelle-G suit featuring
liquid muscles rather than air chambers. Fluid provides an ©Martin Rosenkranz
undelayed and more effective protection against high g-
loads and g-onsets. The cockpit additionally features an onboard oxygen generating system
(OBOGS). Completely new for a combat aircraft is the VTAS controls concept which combines the well
known hands on throttle and stick controls with a speaker dependent direct voice input system.
The fully night vision compatible full glass cockpit is dominated by three coloured high resolution
multifunctional head-down displays (MHDDs) each of which is surrounded by 17 programmeable soft
touch buttons. The primary flight instrument is the BAE Systems developed wide angle head up
display (HuD) which presents all relevant flight reference, navigation, targeting data etc. as well as
FLIR imagery. The Typhoon cockpit is also one of the first paperless cockpit environments with all
checklists for start-up or emergency procedures being available in electronic formats. Display formats
are switched automatically depending on the phase of flight and situation providing the pilot with
information on a need to know base. From 2009 Typhoon pilots will also wear the new HEA MkII+
helmet which features an integrated display unit which can present HuD like data, as well as FLIR and
NVE imagery. Night vision enhancement cameras can be optionally attached to the helmet if required.
The helmet additionally features an accurate optical sighting system which enables the pilot to cue
missile seekers and sensors by simply moving his head.

12
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Avionics:
The Eurofighter Typhoons advanced digital avionics suite is built to the federeated concept with all the
systems being divided into 7 sub-systems which are linked to each other via 5 digital MIL STD 1553B
and optical 2 STANAG 3910 databusses. This avionics networking enables the systems to exchange
data and results in a high level of systems integration and high degree of automation vastly reducing
the pilots workload, while improving the single systems performances.

The basic aircraft systems are controlled by the utility control system (UCS) which is complemented by
the integrated monitoring and recording system (IMRS). The IMRS features the audio and video
recorders as well as a digital flight data recording and the fully integrated and automated self
diagnostic and built in test equipment to monitor the aircrafts well being.

The navigation suite comprises a Litton LN-93EF laser inertial navigation system, complemented by a
jamming resistant digital multichannel GPS receiver, a Smith Industries radar altimeter, instrument and
microwave landing aids (ILS/MLS), a digital map generator, the TERPROM II terrain reference and
ground proximity warning sytem as well as DEM-P and TACAN radio navigation aids.

The complex autopilot augmented by an auto throttle function assist the pilot in flying the aircraft and
can free him from that task in certain situations. The autopilot can catch and hold speed, altitude and
heading, features attitude hold and flight director modes. The autopilot is capable to perform
automated terrain following flights, fly a pre-programmed CAP pattern, conduct a landing approach,
track the flight plan or even flight intercept maneuvers.

The communication equipment includes two VHF & UHF radios for civilian and military
communication. The UHF radios are compatible with HAVE QUICK I & II as well as SATURN
standards and ensure a secured and jamming resistant communication on secure but also unsecured
channels.

Another communication device is the MIDS-LVT/LINK 16 data link (Multifunction Information


Distribution System – Low Volume Terminal). The MIDS is an advanced digital bi-directional data link
system which ensures a secured and jamming resistant real time communication and data exchange.
MIDS provides the Eurofighter Typhoon with network centric warfare capabilities. MIDS enables up to
aircraft to exchange data directly with each other including sensor pictures, targeting and position data
etc. MIDS allows text message exchange and discrete voice communication over secured channels.
Navigation functions are incorporated as well.

The mission equipment includes the fully integrated electronic self defence and warfare system DASS
(Defensive Aids Sub System). The modular designed DASS is controlled by the defensive aids
computer which processes the threat warning sensor data and coordinates the deployment of counter
measures. The DASS threat warning sensors comprise electronic support measures for passive
detection, localisation, identification and priorisation of RF emitters, active missile approach warners
and in the case of RAF Typhoons also a laser warning receiver. The countermeasures include
automated chaff/flare dispensers, directed electronic counter measures and supersonic capable towed
radar decoys.

The fire control system is dominated by the digital mono-pulse doppler X-band multimode radar
Captor. The modular designed Captor radar features a mechanically scanned planar array, a
programmable signal processor and a receiver with 3 data processing channels, including one for CM
suppression. Captor works with variable PRFs, which are automatically selected depending on the
operating mode and situation. Unnecessary antenna movement is reduced by data adaptive scanning
techniques. The software is written in ADA and Captor provides a large number of BVR and CiC
aircombat modes as well as air to surface modes. The radar features a non-cooperative target
recognition, multiple target track and engagement and look down/shoot down capabilities. The ability
to present different display formats simultaneously on the cockpit displays provides the pilot with a 3-D
picture of the air space. The radar additionally features a fighter to missile data link and is
complemented by an automated IFF system. The Captor provides a long detection and tracking range,
high CM resistant, limited LPI characteristics (Low Probability of Interception) and great FOV.

In addition to the radar there is the PIRATE (Passive Infrared Airborne Tracking Equipment) dual-
band, imaging infrared sensor. The PIRATE acts as IRST (Infrared Search and Track) and as FLIR
(Forward Looking Infrared). As IRST the sensor can passively detect and track airborne targets at long

13
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

range and provides target images for priority targets for visual target recognition at long distances.
FLIR imagery can be presented on the HUD, HMD and the MHDDs.

The overall sensor performance is further enhanced by sensor data fusion realized by the attack and
identification system (AIS). The AIS fuses navigation and sensor data improving systems integration
as well as data quantity and quality, while reducing the pilots workload.

Weapons:
Typhoons armament comprises an internal 27 mm gun Mauser Bk27 with 150 rounds and a range of
external stores to be carried on up to 13 hardoints under the wings and fuselage. Current block 5
aircraft are cleared for up to 3 supersonic 1000 l drop tanks, IR-guided short range AAMs AIM-9L
Sidewinder, ASRAAM and IRIS-T, active radar guided BVR missiles AIM-120B/C-5 AMRAAM as well
as laser guided 2000 lb and 1000 lb bombs GBU-10/16 and Paveway II. With the RAFs austere AG
package the Enhanced Paveway II dual-mode bomb and Litening III LDP are added as well. Future
planned weapons include the Meteor BVRAAM, KEPD-350 Taurus Storm Shadow stand-off missiles,
Brimstone active-radar guided anti-armor missiles as well as EGBU-16 and EPW IV dual-mode
bombs. Other options being considered include 2000 l wing tanks, GBU-24 and Paveway III/EPW III
LGBs and dual-mode bombs, HOSBO/HOPE GPS guided glide munitions and LJDAM dual-mode
bombs. The industry offers integration of other weapons at customers request as well including anti
radiation and antiship missiles as well as reconnaissance pods etc.

14
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Appendix B:

Eurofighter Typhoon Flight Manual


Introduction:
The Eurofighter Typhoon Flight Manual is related to the Eurofighter Typhoon in the Falcon 4.0
simulator with the Open Falcon 4.7 only! It describes the aircraft and compares it to the real EF2000.
The Flight Manual provides you with tips how to fly and fight with the Eurofighter Typhoon and
includes a functionality description of the 3-D cockpit. The Flight Manual is sub divided into different
topics.

Aircraft versions:
Open Falcon 4.7 simulates 5 single seat versions of the Eurofighter Typhoon aircraft, by default
German, British, Italian, Spanish and Austrian aircraft. Each version features 2 skins representing
series production aircraft as they are in service with frontline units of the different airforces. In addition
every aircraft features individual weapon load configurations as for the real aircraft. As in reality
different designations are used by different customers.
Designations are Eurofighter (GER & AT), Typhoon FGR.4 (RAF), C.16 (ESP) and F-2000 (IT).
Note that the Austrian aircraft are designated as “Eurofighter A” to distinguish it from the German
aircraft.

3-D model and skins:


All Typhoons share a common 3-D model which hasn’t changed much since FF2. It’s neither the worst
nor the best looking one in Open Falcon. The proportions aren’t perfect and the 3-D model isn’t very
detailed at all. It lacks a modelled emergency arrestor hook and has only a one step animated
refuelling probe. The gear position looks crappy as well though the EFTP modifies the gear position so
that it looks more realistic, it’s at all a compromise between “good” looking and functionality. The 3-D
model features animated canards, flaps, slats, airbrake, undercarriage, vary cowls, rudder, nozzles
and canopy. Open Falcon 4.7 features 5 hires skin sets, each with 2 versions of the skin representing
Spanish, Italian, German, British and Austrian series production aircraft.

Basic aircraft data:


Basic aircraft data include the aircraft’s physical dimensions, masses and internal fuel load. Weight
and fuel load data are included in the dat-files meaning the ef2000.dat in case of the Eurofighter
Typhoon and in the vehicles & unit control data files. The weight and fuel data must be the same in all
files in order to work correctly. These data are correct now with OF 4.7. The same applies to the
dimensions which are defined in the ef2000.dat only.

Flight Model (FM):


Introduction:
The flight model (FM) is one of the most important features for a specific and realistic simulation of an
aircraft. In Falcon 4.0 all aircraft specific FM data are included in the aircraft’s associated dat file. The
Eurofighter Typhoon’s dat file is designated ef2000.dat. The dat files are typically located in the
simdata.zip which can be found in the zips folder for most patch standards. With OF the zips folder
and its associated zip files has been removed and replaced by direct accessable folders. Aircraft
specific dat files can be found in the sim/ACDATA folder.
Falcon 4.0’s flight model engine is relative complex and was further enhanced over the time. The
different BMS-versions introduced a number of improvements. Nonetheless it is worth noting that the
FM engine was originally developed and optimised for the F-16 Fighting Falcon. There’re a lot of
limitations for non F-16 aircraft, particularly in the area of flight control system (FCS) functions.
Therefore the Eurofighter Typhoon’s FM is for sure not perfect, but I have done my best to create one
which matches the flight performance and flight behaviour known for the real aircraft as close as
possible. Falcon provides a high level of flexibility when it comes to the complexity of flight models.
The FM used for the EFTP could be classed as medium complexity.

15
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Experienced FM designers might feel that the data tables look somewhat weird, but for me it’s the in
simulation result that counts, not how the data look in the file, though they are more realistic now than
in previous versions.

FM development history:
The ef2000.dat used by the Eurofighter Typhoon Package was originally developed by Joelhume back
in 2002/early 2003. It was designed for SP3 and I had the opportunity to test it in February 2003
among other modifications. Joelhume told me that the lift and drag tables were based on that of the F-
22. I conducted a comprehensive flight test campaign to evaluate the FM and was highly impressed by
the results. The FM closely matched the performance specifications of the real aircraft known to me at
that time. I identified only 4 issues, the first was the aircraft’s inability to accelerate in the vertical, the
second was insufficient roll performance at high AoAs, the third was a felt to low g-onset and the fourth
was a to high AoA (40°). I reported these issues to Joelhume and he quickly addressed them, sending
me the updated ef2000.dat soon afterwards in form a new simdata.zip. We hoped to see his FM being
incorporated into SP4, but that wasn’t going to happen. It was in fact FF2 which became the first
Falcon 4.0 patch standard to feature a fully developed and integrated Eurofighter Typhoon. Of course I
flight tested the FF teams FM, but quickly came to the conclusion that Joelhume’s FM was more
realistic. I searched for a way to integrate joelhume’s FM into FF2 and was eventually successful. As I
knew that the ef2000.dat was the Typhoon’s related FM file I started to study it, but my overall
understanding was limited particularly for the additional data section and some others as well. I
additionally compared it to the ef2000.dat developed by the FF team and decided to adapt its
additional and airframe data sections. I corrected the internal fuel load and empty weight, the
chaff/flare loadout and set the AoA at 35°. I finally received Joelhume’s permission to use his
ef2000.dat for my planned Eurofighter mod, which eventually became the first EF2000Patch. The first
version was designed for FF2 and was released in November 2003. I subsequently adapted the
ef2000.dat for the following versions of the EF2000 Patch series and later the Eurofighter Typhoon
Packages, versions of which were developed for nearly every Falcon 4 patch standard released since
FF2, including FF2.1, SP4/4.1, SP4.2+BMS 2.0, FF3+1n2 Hot fix, FF3.1+cobraone 1.1,
FF3.11+cobraone 1.1.1 and Redviper 1.0.0.2/3/4. Initially I just adapted the additional and airframe
data sections from the dat files shipped with new patch standards and made the same modification as
for the first version developed for FF2. In August 2004 I decided to evaluate the entire FM again as
additional and more up to date performance data for the real aircraft became known to me. I
discovered some shortcomings and that the FM didn’t fully behaved as before. This was caused by
differences in the additional data section and changes to the FM engine introduced by the BMS-exe. I
began to study the ef2000.dat once again and learned more about it. This was followed by some more
comprehensive modification work on the dat file. I changed some of the values in the reheat thrust
table and a single drag value to optimise acceleration performance, speed performance and
manoeuvre performance (sustained speed while manoeuvring at max AoA). Unfortunately the thrust
values become unrealistically high and another negative side effect was further increased fuel
consumption. The gear position looked horrible in FF3 and therefore I worked on it as well. The most
challenging aspect on this was to ensure that taxi stability wouldn’t be affected, but the efforts were
successful. For the last version of the EF2000 Patches (v8 series for FF3 versions) symmetrical
canard operations were introduced as for the real aircraft. FF3 featured realistic chaff/flare dispenser
locations but only for two of the four dispensers of the real aircraft. Mapi developed the missing
dispensers and approved their usage within the FM. The last work done were introduction of the IFF
for CobraOne users and changing some of the AG weapon release altitudes for AI controlled aircraft.
When developing the first EFTPs for FF3.11 and SP4.2+BMS2.0 in parallel I compared entries in the
additional data section for FF3 and SP4. This helped me to test some specific settings and features
and to introduce them for the other version. The FF3 version could be seen as the main version and I
introduced a realistic gun location and new refuelling data for easier air to air refuelling. I eventually
corrected the dimensions and carried the ef2000.dat over for the first RV compatible version of the
EFTP. When I received a doc file describing many of the entries in the additional data section I was
able to make additional improvements some of which made it into the EFTP v1.0RV. The most
important change was the elimination of the flap position in the takeoff/landing configuration (deployed
undercarriage). As some criticised the way to high fuel consumption, particularly at altitude below
36000 ft I changed the fuel multiplier and later set a new airbrake deployment angle for more realistic
looks and effectiveness. The last change introduced for the EFTP v1.1RV was an increased
engagement range for AI controlled aircraft. When the EFTP v1.1RV was released for RV1.0.0.4 in
early April I had started to enjoy RV with my latest EFTP. This didn’t last long as I soon encountered
some problems. I decided to evaluate the FM once again also taking into account the latest data for
the real aircraft and discovered a problem with inadequate supersonic performance at altitudes
between 20000 ft and 30000 ft and with external stores. I made the most comprehensive overhaul on

16
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

the FM. As further increasing thrust was out of question as they were already unrealistically high and
for reasons of fuel consumption I rewrote the entire military and reheat thrust tables. These became
more realistic and reasonable. To compensate the lower thrust most of the drag values for 0° AoA at
various speeds were changed. This eventually solved the problem of inadequate supersonic
performance at altitudes between 20000 ft and 30000 ft, but not that of inadequate supersonic
performance with stores. The changes additionally caused a new problem. While on landing approach
I noticed that the aircraft’s deceleration was way to slow even with the airbrake being deployed. I
experimented around with different airbrake deployment angles, without satisfying results. I eventually
choose a realistic looking angle and discovered an entry for the drag produced by the airbrake. This
finally solved the problem. As I felt that the max AoA of 35° might be too high, I reduced it to 33°. I
finally introduced new hardpoint groups and changed some entries for the stores drag in the limiters
section. This solved the problem with insufficient supersonic performance with external stores. The FM
was better than ever before but still not perfect. It might be worth noting that it was never publicly
released as I planed to wait for new patch standards. Nonetheless I realised that the FM was relative
simple and the limited number of break points in some of the different sections let little room for flexible
development. Lose of speed while manoeuvring was to low and I felt that the aircraft was a bit to
manoeuvrable. I eventually decided to develop a new FM, based on the last one which wasn’t
released. I used a lot of reference material such as the RP5, BMS and HFFM manuals, the doc file
received before and the F-16s HFFM dat files, not to copy the data but to get an idea about how
realistic data tables look like. Of particular interest for me was the relation and tendency of thrust, lift
and drag increase/decrease with various speeds, altitudes and AoAs. I significantly increased the
number of mach and AoA breakpoints for the basic aerodynamic coefficient section affecting lift, drag
and side forces and the number of altitude break points for the thrust section. This increased the FMs
complexity and allowed a greater level of flexibility. Placeholders were inserted filling the space
between the existing breakpoints and then I reworked the entire lift, drag, military thrust and reheat
thrust tables. The additional data section was completely restructured for easier editing and a couple
of additional edits on the entries were done. Flight testing did not begin until the basic work was
completed and different configurations were developed and then tested. Of course I opted for the most
complex configuration. The FM didn’t work at the beginning as I forgot to increase the value defining
the number of breakpoints in various sections. I solved the problem and further adjusted the FM to
achieve the desired performance and flight behaviour. I initially planned to introduce a g-override
function and engine optimised fuel flow with the new FM, but these efforts were unfortunately
unsuccessful. I experimented around with the limiters section but lacked a really useful description.
The changes additionally caused that the limiters didn’t work and stores had no impact on the flight
performance/behaviour. I replaced the modified limiters section with the one of the last working
configuration and eventually solved the problem. For the engine optimised fuel flow I used that of the
F-16s HFFM as example but based it on the available specific fuel consumption data for the EJ200
engine and suited it to the number of breakpoints defined in the thrust section. After work was
completed flight tests were started. Unfortunately the fuel flow tables didn’t work as expected and I
figured out that this problem is related to twin engine aircraft. As my requests for help remained
unheard/unanswered I decided to abandon these feature and to concentrate on more important parts
of the FM. Nonetheless I backed up the fuel flow tables for case I find a solution.
Further work in the additional data section included specific fuel tanks though I later read that this
feature was developed for the F-16 only. I decided to keep the data independent of if they work or not
as long as they cause no problems. I changed allowed max vertical speed for the undercarriage,
introduced a more realistic leading edge flap behaviour, animated wheels (doesn’t work for OF
probably due 3-D model differences) and a more realistic engine nozzle animations associated with
thrust, normal fuel flow factors, TFR data and some other data which seem to has no impact.
I changed some roll data and the CG position as well, slightly increased the angle of the deployed
nose wheel and introduced a kind of supersonic g-limiter by adjusting the lift and drag for various AoAs
at supersonic speeds. This work was successfully completed, but during flight testing I encountered an
increasing number of problems. The limiters don’t work once again and stores had no impact on the
FM too. Stability in level flight was problematic as the aircraft started to slightly pitch up or down at
various speeds. Acceleration at climb angles was insufficient resulting in inadequate climb
performance and the performance still not fully matches that of the real aircraft in various areas. The
most significant problem was an unexpected fast pitch up movement at altitudes above 50000 ft.
interestingly the aircraft didn’t exceed an AoA of 4°, while accelerating to speeds in excess of mach
2.4. Due the increasing number of problems I decided to freeze development and start with a safer
alternative approach. I took the modified and simpler last version of the FM and introduced some safe
changes done for the new FM. Based on the experience gained from the development of the new FM I
made some further modifications and eventually created a FM which is not more complex than the old
one, but which works without problems and matches the performance data known for the real aircraft

17
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

more closely. I have decided to include this FM into the EFTP v1.0OF. The version incorporated into
OF 4.7 features small modifications for more realistic low speed handling and Revientor’s camera
definitions.

FM flight performance and behaviour:


The Eurofighter Typhoon’s FM was optimised and fine tuned with help of extensive flight tests. As a
couple of performance data for the real aircraft are known it was necessary to test the aircraft’s flight
performance in the simulation and then optimising and fine tuning the basic FM. The result is
astonishing, though it’s for sure not perfect. It’s particularly difficult to say if the handling characteristics
are realistic, but the performance data comes very close to the data officially published, extracted from
pilot interviews, estimations based on known data from other aircraft and air show video
measurements.

The table below compares the know specs of the real aircraft with the performance data achieved in
the simulation:

Flight Performance real Eurofighter Eurofighter in OF with EFTP


Top Speed: >2150 kph (Mach 2,02) 2270 kph (Mach 2,14)
Top Speed at S/L: 1390 kph (Mach 1,14) 1400 kph (Mach 1,14)
Supercruise: Mach 1,4-1.5 Mach 1,47
Service Ceiling: >18000 m >18000 m
climb to 10975 m /accelerate to <2,5 min 2 min 6 sec
Mach 1,6:
climb to 12800 m: 1,5 min 1 min 33 sec
Acceleration Mach 0,3-1(S/L): <30 sec 27 sec
Acceleration Mach 0,8-1,2: 40 sec 37 sec
Acceleration Mach 0,8-1,4: 62 sec 59 sec
G-Loads: -3 g to +9 g -3 g to +9 g
AoA: 30-35° 30°
Roll rate: 240-250°/sec 245°/sec

As you can see in the table above the aircraft’s in simulation performance comes very close to that
published for the real aircraft. In some areas the EFTP aircraft performs even better, but it has to be
taken into account that some of the known performance data of the real aircraft are nothing else than
specifications defined in the requirements. That means this data can be seen as the minimum. They
might be equal or even better in reality. A good example for this is the aircraft’s speed performance.
The real aircraft’s top speed is often given with mach 2. As early as 1997 prototype DA2 demonstrated
its ability to achieve this speed, even with the less powerful RB199 engines. A speed of slightly more
than mach 2 was officially confirmed and the speed achieved in the simulation seems to be
reasonable and realistic. It’s nearly the same for the top speed at sea level (S/L). The real EF2000’s
speed here is given with 1390 kph (mach 1.14) and the EFTP FM is very close to that. Previous
versions of the EFTP FM lacked realistic supersonic performance in the 20k-30k ft area and with
payloads. This has been improved with the latest version. Like the real aircraft you will be able to
supercruise. The real aircraft’s supercruise speed in clean configuration is given with mach 1.4-1.5. As
you can see the performance can be achieved at altitudes of ~44k ft. It is slower at lower altitudes.
The aircraft’s service ceiling comes very close to the data known for the real aircraft, though exact
data are unavailable. The acceleration performance at various altitudes and speeds is accurate within
3 seconds and its climb performance looks realistic as well. Its agility and manoeuvrability looks
reasonable as well. Like in the real Typhoon you can pull sustained 9 g turns over a wide flight
envelope and pull into a max g turn in less than a second. You can fly sustained 5 g turns at mach 1.6
and fly the famous HAVV roles to a certain degree. As for the real Typhoon the low speed and high
AoA handling and manoeuvre qualities are excellent and data such as max. AoA, turning rates or roll
rates look reasonable as well and should be relative realistic. Though carefree handling isn’t really
simulated in Falcon 4 you will be able to fly the aircraft easily. There is no need to care about
aerodynamical limits in a clean or light air-to-air configuration.

Notes:
The full potential of the FM development has not been fully explored yet and it might be that you will
see even more realistic FMs in the future!

18
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

There’re also some known problems with the current FM. One of the problems is that the aircraft
makes a nose down movement when releasing the wheel brakes at low taxi speeds, the aircraft will
need some seconds to “recover”, but this shouldn’t have a great impact on the overall taxi
performance and has no impact on the flight performance. The reason for this is the CG position. The
CG was selected on the base of flight test results and the FM is fine tuned for this CG. Changing it
might solve the problem, but would require extensive flight trials and probably various modifications.

Signatures:
Falcon simulates visual, infrared and radar signatures to a limited degree. Though exact data are
unknown for the real aircraft it is known that the real Typhoon has relative low signatures and there
exist assumptions about the Eurofighter’s frontal radar cross section (RCS). The RCS has been
lowered for the aircraft providing it with a tactical advantage over the most adversaries except for real
stealth aircraft.

Various:
The real Eurofighter Typhoon provides exceptional short takeoff and landing (STOL) capabilities. The
real aircraft needs a takeoff run of about 300 m in a light fighter configuration and a landing distance of
about 500 m. This performance is relative accurately matched in the simulation. Like for the real
aircraft you are able to deploy a brake chute and the aircraft is equipped with an emergency arrestor
hook. External lightning is limited as there’re no formation lights. You only see one taxi light instead of
two and only 3 anti collision/nav lights instead of 5. The lights on the bottom of the fuselage and the fin
are missing in contrast to the real aircraft. Modifications are possible however. The aircraft features a
retractable refuelling probe as well. Falcon 4 wasn’t designed for the hose-drogue refuelling method,
but meanwhile it’s possible thanks to some data edits.

Cockpits:

Introduction:
The cockpit is the working place of the pilot. From here he flies the aircraft and controls its systems.
The real Eurofighter Typhoon features one of the most sophisticated man machine interfaces (MMI) in
the world. Falcon provides two different cockpits: the 2-D and the 3-D cockpit.
The 2-D cockpit offers a limited number of views, but it is highly functional and offers photo realistic
looking views. The 3-D cockpit looks less impressive and is less functional, but it allows a step less
rotation and supports the padlock function which is very helpful in dogfights and other situations.
Meanwhile 3-D cockpits can offer a much greater functionality and are clickable as the 2-D cockpit.
The EFTP features a simple 3-D cockpit for the Eurofighter Typhoon.

Eurofighter Typhoon 2-D cockpit


There is currently no freeware Eurofighter Typhoon 2-D cockpit available. If you like to use a 2-D
cockpit you have to stick with Aeyes EF2000 Superpit. For more details read Appendix C: “The how to
section”

Eurofighter Typhoon 3-D cockpit


The 3-D cockpit looks beta, but generally works. The 3-D cockpit is optimal suited for dogfights with
the implemented padlock view. The 3-D cockpit supplied with the EFTP doesn’t include any clickable
buttons and has also a limited functionality. The most important instruments are included, however.
Note that the RWR has no specific texture but RWR symbols will be displayed on the centre MHDD.

1 - Head-up-Display
2 - left MHDD
3 - right MHDD
4 - RWR display
5 - DED

19
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Note:
As of now the Spanish, Italian and Austrian aircraft are using the 3-D cockpit with RAF skin wings, this
might change in the future when the correct numbers for the Lods become known for these aircraft.

Avionics:

General:
Falcon 4.0 provides very realistic avionics for the F-16 and all other flyable aircraft in the simulation
use these avionics. In some areas the F-16s avionics matches that of the Typhoon, though only
basically. But some modifications for non F-16 aircraft are possible. In this chapter the avionics of the
real aircraft are described shortly and what systems are available in F4.

CAPTOR:
The CAPTOR radar of the real Eurofighter is one of the most advanced and most capable fighter
radars available today. Perhaps it’s the best of its kind with a mechanically steered array. The
CAPTOR, former ECR-90, is a digital monopulse Doppler X-band multi-mode radar. The AN/APG-68
of the F-16 simulated in F4 is less capable than the CAPTOR but it provides similar technologies and
modes. Thanks to some data edits it was possible to improve the performance of the radar for the
Eurofighter especially in terms of range and counter measure resistance, azimuth coverage, LPI and
scanning speed.

BVR Modes (AA):


Mode: real EF2000: EF2000 in OF:
TWS x x
RWS x x
VS x x
LRS - x
ULS - x

20
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

The AN/APG-68 radar of the F-16 in F4 provides nearly the same functions and modes as the real
CAPTOR radar. So TWS, RWS and VS modes are available. LRS and ULS modes are probably not
included in the real Eurofighter radar. The CAPTOR provides also functions as raid assessment,
NCTR and target trace indication. But compared to the real radar it’s not possible in F4 to engage 6
targets at once and to generate a 3-D picture of the airspace resulting in some disadvantages
compared to the real Eurofighter. Also the handling and presentation isn’t that of the Typhoon.

WVR Modes (AA):


Mode: real EF2000: EF2000 in OF:
Boresight x x
Vertical Acquisition x -
HuD Acquisition x -
Slaved Acquisition x -
Slew - x
20 - x
60 - x

Both the real CAPTOR and the AN/APG-68 simulated in F4 provide close air combat modes for fast,
automatic target acquisition. But there exist some different modes, with different search patterns. An
important mode of the real CAPTOR radar, which is not available in Falcon 4.0 is the so called “slaved
acquisition”. In this mode the pilot can point the radar to a target via the HMS.

AG Modes:
Mode: real EF2000: EF2000 in OF:
DBS x x
SAR x -
GMT x x
SEA x x
TA x -
PVU x -
FTT x x

As the table shows the AN/APG-68 provides only a fragmentation of the modes which will be
incorporated into the real CAPTOR radar. Missing modes are the SAR mapping mode for identification
of ground targets, terrain avoidance (TA) to paint pictures of the terrain ahead to avoid collisions and
the PVU mode for precision velocity update. The fixed target track and DBS mapping modes are
incorporated into the GM mode of the AN/APG-68 in F4. SEA and GMT modes are available as for the
real radar. Quality, presentation and handling couldn’t be simulated, however, and there’re limitations
in terms of performance.

Performance:
The real CAPTOR radar should be able to track fighter sized targets at more than 160 km (>85 nm)
and larger targets like bombers and transports at more than 300 km (>170 nm). The real CAPTOR is
very jamming resistant and is able to track more than 20 targets at once and engage 6 of them. Except
the multiple target engagement capability the other performance data are roughly matched by data
edits.

PIRATE:
The real Eurofighter will features the PIRATE (Passive Infrared Airborne Tracking Equipment) infrared
sensor. The PIRATE can be used as IRST for passive detection, tracking and identification of airborne
threats and as FLIR. The F4 avionics engine does not include IRST as a system for flyable aircraft, but
it’s available for AI controlled aircraft. AI steered Typhoons in F4 will have an IRST.

Striker:
The Striker is a highly advanced Helmet Mounted Display/Sighting system (HMD/S). On the HMD HuD
like data can be displayed, this would be an advantage, but HMDs aren’t simulated in F4. The Striker
also provides cueing functions to point missile seekers and sensors like radar or IRST to targets. A
simple HMS to cue missiles at enemy aircraft is available as the NVG function which is an option for
the real Eurofighter. At all the Striker isn’t simulated in F4, but some basic functions are integrated.

21
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

MIDS:
The NATO-compatible LINK-16 MIDS (Multifunction Information Distribution System) datalink for the
real Eurofighter is one of the best and most advanced datalink systems in the world. It can serve as
TACAN and receive navigation information. It can be used for text messaging and discrete voice
communication and it can exchange various data like sensor pictures, target data and position data.
These capabilities give the real Eurofighter pilot a superior situational awareness. The datalink in F4 is
very limited but provides the pilot with position data of the wingmen and information which targets they
have locked. The IDM introduced with Open Falcon provides additional capabilities such as target data
transmission and assignment which partitially match that of the real MIDS.

DASS:
The digital electronic self defence suite of the real Eurofighter Typhoon, called DASS (Defensive Aids
Sub System) is a fully integrated automatic working system. It’s one of the most complete and
advanced systems in the world consisting of radar warning receivers/electronic support measures
(RWR/ESM), laser warning receivers (LWR), missile approach warners (MAW), Chaff/Flare
dispensers, ECM and towed radar decoys depending on the customer. The EWS of the F-16 which is
simulated in F4 lacks the MAW, LWR and TRD so that the defensive systems of the Eurofighter in F4
are very limited in their capabilities. The RWR in F4 is like the RWR/ESM in the Eurofighter able to
identify radar emitters and to show the relative bearing to them. The system can also analyse whether
the radar is in search or track mode. But the receivers of the real DASS have much more capabilities
like ranging emitters, identifying them with IFF and detecting other radio sources. But at least ground
based radar systems in F4 are precisely located in the HSD with their lethal zones.
The Eurofighter in F4 has an internal jammer like the real aircraft but the ECM system of the real
Typhoon is probably much more capable than that available in F4. With the EFTP the strength of the
ECM is increased to better reflect the performance compared to older systems used in other aircraft as
in reality.
The real Typhoon has 2 BOL 510 chaff dispenser and 55 mm 2 flare dispenser mounted under the
wings. The outer chaff dispensers have a load capacity of 160 decoys each and the flare dispensers
carry 32 decoys at all. With the RV1 upgrade dispenser locations are simulated realistically, but there
were only 2 dispensers at all (one chaff and flare dispenser each) and the number of chaff and flares
for the Eurofighter was unrealistic. The EFTP corrects the number of decoys and bring it up to the
level of the real aircraft and additionally adds the two missing dispensers.

TEPROM II:
The TEPROM II (Terrain Profile Matching) is a digital terrain reference navigation system (TRN) based
on a digital database. It allows passive terrain following flights with collision warning without using
active signals, which could be detected by passive receivers. But unfortunadley such a system isn’t
present in Falcon 4.0, so the terrain following radar (TFR) is used for the Typhoon. The TFR provides
similar functions as the TRN but it’s working with active signals (radar waves).

IFF:
The real Eurofighter will be equipped with an advanced automatic IFF system. This automatically
identifies tracked radar targets and emitters detected by the DASS. In OF no IFF is simulated and
therefore you rely on the radars NCTR and AWACS support.

Other Systems:
Some of the avionic systems of the real Typhoon are not simulated in F4. So systems like the MLS
and DME-P are missing as sensor fusion does. Also the autopilot in F4 is much less flexible and
capable than the system of the real aircraft, missing functions like “auto approach”, “auto throttle”,
automatic CAP flying and attack profile flying, “tracking” and with a limited “steering” mode. The digital
map is limited in its presentation and does not offer different resolutions.

Weapons:
The real Eurofighter Typhoon was from the outset designed as a swing-role capable multirole fighter.
But the aircraft entered service as a pure air defence fighter. The current block 5 standard aircraft
have an austere AG capability and the full potential will be achieved with the later tranche 2 aircraft.
OF 4.7 reflects the planned future block 8 (tranche 2) multirole loadouts, except for Austria which only
operates block 5 aircraft. The weapons and loadout configurations will be described below.

22
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Weapon types:

Gun:
The Eurofighter Typhoon is equipped with a single barrel 27 mm gun Mauser Bk27. The gun is located
in the right wing root and has 150 rounds. The gun has a firing rate of up to 1700 rounds/min and a v0
of 3328 ft/sec. The EFTP v1.0OF increases effectiveness of the weapon and corrects the v0 and gun
location. The gun was previously designated 27 mm-1 and is renamed to Mauser Bk27 with the EFTP.

Drop tanks:
To increase range and endurance the Eurofighter can carry up to three 1000 l drop tanks, which are
supersonic capable. 1500 l under wing tanks were also tested, but they proved to be inefficient for
Eurofighter operations and were deleted from the requirements.

IRIS-T:
The IRIS-T is a highly agile off-boresight short range air to air missile (SRAAM) with an advanced wide
angel imaging IR-seeker and lock-on after launch (LOAL) capabilities. The weapon is jointly developed
by Germany, Italy, Spain, Greece, Norway and Sweden. Up to 4 IRIS-T can be carried by the Typhoon
and the weapon is used by German, Austrian, Italian and Spanish aircraft.

ASRAAM:
The ASRAAM is the standard WVR AAM for RAF Typhoons available since the introduction of the
Typhoon. It’s an agile missile with IIR wide-angle seeker and LOAL capabilities.

AMRAAM:
The AIM-120 AMRAAM is an active radar guided MRAAM and will initially be the primary BVR weapon
for all Typhoons. The aircraft can carry up to 6 AMRAAMs. The AMRAAM is used by Typhoons of all
customer nations except for Austria. Austria originally ordered some AIM-120B, but cancelled that
order later. For playability the AIM-120B was kept for Austrian Typhoons.

Meteor:
The Meteor also known as BVRAAM should be introduced from 2010 onwards as a replacement for
the AMRAAM. The missile is already available in F4 and is integrated into the Eurofighter. Compared
to the Meteor of the RV1 team the EFTP modifies the rocket motor to increase the range and to
enable a more realistic flight profile. A new DLZ timer is integrated which better suits the increased
engagement envelope. Further more the radar seeker of the missile is modified and now more CM
resistant.

GBU-10/16 Paveway II & GBU-24A/B Paveway III:


For precision bombing real Typhoons can be equipped with the laser guided 1000 lb bombs GBU-16
which is based on the Mk-83 and 2000 lb bombs GBU-10 which is based on the Mk-84. It is planned to
introduce the 2000 lb LGB GBU-24 Paveway III as well, which is based on Mk-84 and BLU-109. The
real aircraft might be able to carry up to 7 GBU-16 and up to at least 3 GBU-10/24. As the centreline
station will be used by the LDP only 6 or 4 weapons will be available. Therefore the centre line station
isn’t used for LGBs in the EFTP.

EGBU-16, Enhanced Paveway IV & GBU-54 LJDAM:


The EGBU-16, EPW IV and GBU-54 LJDAM are dual mode bombs with laser and GPS-guidance in
reality. As Falcon 4 doesn’t support dual mode bombs these weapons work like a GPS guided bomb
such as the JDAM series. Read the Dash34.pdf in your falcon4\docs folder for further details how to
employ these weapons. There is only one difference for these weapons, you can use the TGP as well!
In that case just point to a target with the TGP (as described in the dash34 manual) and drop the
bomb when in range, you don’t need the laser! Corrections after dropping the bomb are not possible!
The EGBU-16 is based on the 1000 lb GBU-16, the GBU-54 is based on the 500 lb GBU-38, while the
EPW IV is a 500 lb bomb.

Storm Shadow:
The Storm Shadow is an advanced stand-off missile using a complex guidance system comprising
INS/GPS/TRN and IIR. The weapon can follow preprogrammed courses at low level terrain following
flight and has a range greater than 250 km. Falcon 4 doesn’t model such guidance systems and the
missile behaves more like a Maverick AGM. It uses an optical seeker only but has a more effective
warhead and greater range. Range performance is further increased with the EFTP, but don’t forget
about the player bubble limitations in Falcon 4.

23
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Brimstone:
The Brimstone is a supersonic air-to-ground missile optimized for the destruction of vehicles including
tanks. The missile uses a mm-wave radar seeker and can be used at day and night and in all weather
conditions. The Brimstone has a range of ~10 km and can be fired in salvos. Falcon doesn’t simulate
the seeker or deployment options of the real weapon and the Brimstone is therefore limited to an
optical seeker and operations similar to that of the AGM-65 Maverick.

Litening LDP:
The Israeli Rafael Litening laser designator pod (LDP) is an advanced targeting pod for accurate
delivery of precision guided AG munitions. Falcon4 automatically activates the TGP function as soon
as LGBs are loaded, so the Litening is more of a cosmetic nature. The pod can be selected from the
“other” section in the weapon load screen and it can be loaded to the center line station as for the real
aircraft. As there is no half way ok looking 3-D model available the Litening uses the 3-D model and
skin of the low alt camera. When you load the Litening the TGP function will be activated independent
of LGBs being loaded or not. The Litening will restrict the FCS to CAT III until you drop it. The TGP
function will be retained however. You can only select the Litening (LDP) from the selective jettison
page (SJ) and you can jettison it there and with the emergency jettison function as well.

Weapon load configurations:


The tables below describe the available weapons for German, Austrian, British, Italian and Spanish
Eurofighter Typhoon aircraft.

Luftwaffe Eurofighter weaponry in OF:


Hardpoints -> 1 2 3 4 5 6 7 8 9 10 11 12 13
IRIS-T 1 1 1 1
AIM-120B/C 1 1 1 1 1 1
Meteor 1 1 1 1 1 1
GBU-24A/B 1 1
GBU-16 1 1 1 1 1 1
EGBU-16 1 1 1 1 1 1
GBU-54 1 1 1
1000 l Tank 1 1 1 1 1 1
Litening 1

RAF Eurofighter weaponry in OF:


Hardpoints -> 1 2 3 4 5 6 7 8 9 10 11 12 13
ASRAAM 1 1 1 1
AIM-120B/C 1 1 1 1 1 1 1 1
Meteor 1 1 1 1 1 1 1 1
GBU-16 1 1 1 1 1 1
GBU-24 1 1
EGBU-16 1 1 1 1 1 1
EPW IV 1 1 1 1 1 1
Storm Shadow 1 1
Brimstone 3 3 3 3 3 3
Litening 1
1000 l Tank 1 1 1

EdA C.16 weaponry in OF:


Hardpoints -> 1 2 3 4 5 6 7 8 9 10 11 12 13
IRIS-T 1 1 1 1
AIM-120B/C 1 1 1 1 1 1
Meteor 1 1 1 1 1 1
GBU-10/24A/B 1 1 1 1
GBU-16 1 1 1 1 1 1
EGBU-16 1 1 1 1 1 1
1000 l Tank 1 1 1
Litening 1

24
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Bundesheer Eurofighter weaponary in OF:


Hardpoints -> 1 2 3 4 5 6 7 8 9 10 11 12 13
IRIS-T 1 1 1 1
AIM-120B 1 1 1 1 1 1
1000 l Tank 1 1 1

AMI F-2000 weaponry in OF:


Hardpoints -> 1 2 3 4 5 6 7 8 9 10 11 12 13
IRIS-T 1 1 1 1
AIM-120B/C 1 1 1 1 1 1
Meteor 1 1 1 1 1 1
1000 l Tank 1 1 1

Additional weapon notes general:


- unguided bombs were deleted as they are rarely used in reality and due insufficient weapon
load logic of the ATO
- AIM-9 Sidewinder is not used as all customers primarily use the more advanced IRIS-T and
ASRAAM missiles
- The AMI will use the F-2000 for Air-to-Air missions only, therefore no AG weapons are
integrated
- The GBU-16 is added to all Typhoon aircraft, though not shown in all the tables, this has to do
with the fact that the fuel tanks will show up weird when such weapons aren’t available for
whatever reason. The weapon is not available in the campaign for aircraft which don’t use it!

Additional weapon notes RAF Typhoon:


- The RAF is also interested in using 2000 l under wing tanks in the future.
- The CRV-7 rocket pods, ALARM and BL-755 CBUs were deleted from the requirement and
will probably not be integrated into the real aircraft. But the option exists.

How to fly and fight with the Eurofighter Typhoon in Falcon 4.0 (VS F-16):

The real Eurofighter Typhoon is rated as one of the best fighters in the world by experts. The most of
them see the type on place 2. directly behind the US made F-22A Raptor. You can experience the
superiority of the Eurofighter Typhoon over other combat aircraft in Falcon 4.0 (F4) too.
But it has to be taken into account that F4 was originally designed as F-16 simulator. The F-16
Fighting Falcon is the only aircraft which is completely simulated in F4. For other aircraft there’re a lot
of limitations especially in terms of avionics. The EF2000 in F4 is in fact much less capable than the
real aircraft, but even with these limitations the aircraft is still superior to most other fighters in F4.

The excellent flight characteristics and flight performance alone give the EF2000 an edge over other
aircraft like the F-16. The large flight envelope of the EF2000 enables the aircraft to fly faster than the
F-16, even with a typical AA combat load consisting of missiles and drop tanks. The higher speed
increases the effective maximum range of BVR missiles. The much better operational ceiling enables
the Typhoon to operate at higher altitudes which has primarily two advantages. The first is that the
aircraft burns less fuel, so that the range is increased and the second is that you will be less
threatened by enemy air defences. High altitudes additionally increase the effective range of BVR
missiles.
The supercruise capability is another advantage for the Eurofighter. The aircraft can fly with super
sonic speeds without reheat. As a result you can pass dangerous zones more quickly and maintain a
higher speed while burning an equal amount of fuel. In combination with the strong acceleration the
EF2000 can also reach high super sonic speeds much faster than the F-16.
Thanks to its exceptional acceleration and climb rate the Typhoon is able to close up to an enemy very
quickly or to escape from the enemy if you have gone winchester. Further more the Eurofighter
regains energy much faster in a dogfight.
The superior agility and maneuverability enables the Typhoon to outmaneuver/outturn nearly any
other fighter and the good low speed handling is another plus for the type in a dogfight. As EF2000
pilot you needn’t care about stalling! The aircraft will not spin like in reality thanks to its advanced FCS.

25
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Eurofighter Typhoon also has a relative low radar cross section. Compared to the F-16 you will be
detected later by the enemy giving you a tactical advantage. But be aware you are not invincible! Later
or earlier you will be detected!

The Eurofighter specific cockpit improves the feeling to fly an individual aircraft, but due the use of F-
16 avionics the cockpit of the EF2000 does not really provide an advantage. Advanced technologies
like direct voice input are missing for example. The only plus is the third MFD that may increase the
situational awareness in some situations. But normally you will probably use it to display the RWR
picture as there is no dedicated RWR indicator in the EF2000 cockpit. (For Aeyes EF2000 Superpit
users only)

The avionics are the main weakness of Falcon 4.0 for non F-16 aircraft. Many useful features of the
real Eurofighter Typhoon are missing as the aircraft uses the F-16’s avionics. However some
modifications are possible for some of the systems. Eurofighter Typhoon has for example a which
enhances low level flights compared to other aircraft which are not equipped with this system.
The radar is basically that of the F-16 but you will probably realize very quickly that the performance of
the EF2000 radar is much better. You can detect and track targets at higher distances than with the F-
16 radar. Even in heavy jamming environments and under look up/down conditions. It also seems like
the radar draws maps in DBS mode faster.
The IRST sensor would be a useful feature for the pilot, unfortunately it’s only available for AI
controlled aircraft.
A good advantage for the EF2000 is its electronic self defense system. The high range of the RWR
increases the situational awareness while alert you early if threats appear. Additionally the higher
number of chaffs and the more effective ECM increases your chances to survive over the battlefield
compared to the F-16 for example.

Also the weapon load of the Eurofighter Typhoon is superior to that of the F-16. You can load
weapons on 13 different hardpoints instead of 9 and as the ECM is internal you can use all of them for
weapons and fuel tanks. For a precision strike you can carry for example 3 drop tanks, 8 AAM and 2
LGBs. So you can strike the target while maintaining an adequate self defense capability against
airborne threats. The Typhoon has at least much greater fire power and is more flexible during a
mission. In the EF2000 you rely less on escorts and can defend your self if you haven’t an escort.
The weapons systems its self provide further advantages. With stand-off missiles like the Storm
Shadow you will be able to attack strategic targets at large distances out of the range of enemy air
defences. So you will be able to destroy even hard defended targets while keeping relative safe!
Another useful weapon is the Brimstone. This anti-armor missile is equal effective as the AGM-65
Maverick, but due to its small size and weight the Typhoon can carry up to 18 of them! That makes a
lot of smoke and makes the EF2000 a very effective platform for close air support and interdiction
missions.
Real advantages are provided by the air-to-air missiles (AAMs). With the Meteor BVR missile you can
engage targets at twice the range of the AMRAAM and then the hit chance is even better due to the
significantly larger no escape zone! With the Meteor you will be able to engage enemy targets out of
their own weapon ranges. Train the use of this weapon in combination with the TWS mode to achieve
multiple target engagements. The DLZ timer of EFTP is much better than the original one but it’s not
perfect. Normally you can engage beyond the shown effective range and score a hit. To sum it up the
combination of flight performance, reduced RCS, more effective ECM, more powerful sensors and
weapons makes the Eurofighter Typhoon in Falcon 4.0 to a superior BVR platform with first look, first
shoot, first kill capability.
Not less important is the combination of the Helm Mounted Cueing system and highly agile IRIS-T and
ASRAAM IR-guided short range air-to-air missiles. If you haven’t used the padlock view in dogfights
until now then it is time to learn about and to use it! If you have locked a target in padlock and selected
IRIS-T or ASRAAM uncage the seeker and the missiles will be cued at the locked target. Wait until you
hear the high tone and then launch! With the HMS/IRIS-T or ASRAAM combination you will be able to
attack targets at close distances at very high off-boresight angels, even if they are on a near collision
course! But be careful the probability of a kill is still higher in boresight. If not necessary try to launch
the missiles directly at boresight.

26
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

Appendix C:

The how to section

Introduction:
This section includes some guides how to use Aeyes EF2000 Superpit and how to add new weapons
or new aircraft squadrons to a campaign using the free available data edit tools F4Browse and
TacEdit.

How to use Aeyes EF2000 Superpit:


Aeyes EF2000 Superpit is currently the only Eurofighter Typhoon 2-D cockpit which is available for
Falcon 4.0. The EF2000 Superpit is payware and can be purchased from www.cockpits.nl for 11 €.
Install instructions for using this pit in Open Falcon and an update for correct working reflections can
be found in Aeyes support forum at cockpits.nl.
The thread is:
http://www.cockpits.net/forum/showthread.php?tid=10.

Warning: Back up the original files before installing Aeyes EF2000 Superpit!

The EF2000 Superpit will overwrite some files during the installation procedure, therefore it is
recommended that you back up these files before installing Aeyes EF2000 Superpit.

The following files in the following locations should be backed up before:


art\ckptart\1495\3dckpt.dat
art\ckptart\2263\3dckpt.dat
terrdata\objects\KoreaObj – DDS files 2461 to 2476

After installing Aeyes EF2000 Superpit you can manually copy past the backed up files into the folders
again. This is required to keep the EFTP skins and the simple 3-D cockpit!

To use Aeyes EF2000 Superpit with the new Austrian, Italian and Spanish Eurofighter Typhoon
aircraft copy past the contents of the art\ckptart\1495\ folder into the following folders of the
same directory: 3837, 3838 and 3839. Make sure the original 3dckpt.dat file is included!

Note:
As the cockpit and wing models for the new Eurofighter Typhoon aircraft are currently unknown the
wings of the RAF Typhoon show up from the 2-D and 3-D cockpit views. This might be changed in the
future.

Aeyes EF2000 Superpit a brief description:


Aeyes EF2000 Superpit is a 1600x1200 2-D cockpit. It is widely functional and fully ramp start
capable. I think for users who really like to fly the Eurofighter Typhoon this 2-D cockpit is worse a
purchase. Take into account the install instructions for OF 4.7 and these for OF in general as
mentioned above! Aeyes EF2000 Superpit was designed for FF3 and SP4, to use it with OF you have
to select the SP4 install option from the EF2000 Superpit installer. The simple 3-D cockpit shipped
with the EF2000 Superpit doesn’t work with OF, make sure that you back up the original 3dckpt.dat
files in the 1495 and 2263 which are included into OF 4.7 as they work and copy them back into the
folders after you have installed Aeyes EF2000 Superpit.

27
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

How to add/change weapon loads:


Some people might like to add/change the weapon load configurations for playability or other reasons,
this section is a tutorial which shows you how to do it. In addition the files being affected by these
modifications are listed as well to enable you to forward the modified files or to backup the original files
prior starting the modifications which is recommended!

Warning: changing the weapon loadouts might cause problems in multiplayer mode, make
sure all of you are using the same standards!

Steps:

1.) Download F4Browse 2.31 (latest version) from here:


http://tactical.nekromantix.com/f4/downloads/F4Browse_v2.31.rar
2.) It is recommended to backup the files which are listed below!
Terrdata\objects folder:
Falcon4.UCD/WLD/SSD
3.) Start up F4Browse and browse to your terrdata\objects folder
4.) Browse to vehicles => aircraft like in the picture below

5.) Select the aircraft you want to edit and double click. An new window will pop up. The window
looks like this with the Eurofighter selected

6.) The 2 red circles mark the areas which are relevant for you. We start with the lower
Hardpoint/Weapons section. Double click on an entry and the following window will open

28
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

7.) If you like to delete a weapon just left click on an entry and press the “Delete” button on the
right site. To add a new weapon just click the “Add” button and the following window will
appear

8.) Select a weapon and enter the number of weapons you like to carry on that hardpoint.
Then click ok and repeat the process if you like to add other weapons. When you are
ready click the update button in the hard point data window (image under 6.)

9.) You can repeat this procedure with other hardpoints you like. If you are ready double
click the unit entry in the “unit with this” section in the vehicle data details window as
shown in 5.).

10.) The following window will open

11.) The Main Role and Role Scores are important for the ATO to generate
missions in the campaign. Change the roles scores for different missions by double
clicking an entry and enter a number between 0-100. Assign points to the mission
types you want to fly only! The higher the points for a role the higher the priority for
the ATO to generate such missions in the campaign. It is necessary to update both
units!

12.) Press the “SSD Ind?” button in the “Unit View” window and a new window will pop up

29
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

13.) Select the weapons from the list you would like to see in the campaign. Just double click an
entry and enter a number. This number is representive for the number of weapons of this type
in the campaign. If you have changed the values you want press update!

Congratulations you have successfully added new weapons to an aircraft, made them available for the
campaign and suited the ATO logic to generate missions!

How to add new squadrons to the campaign


You all know it, you like to fly a specific aircraft in a campaign, but it’s not available. This tutorial
describes how to add a new squadron to a campaign, not more not less.

Steps:

1.) Download TacEdit 2.48 (latest version) from here:


http://tactical.nekromantix.com/f4/downloads/tacedit.v2.48.rar
2.) To prepare the addition of a squadron identify an airbase where you want to add the
squadron. The best way is to start Falcon4 select a campaign and start it. Search for airbases
on the site you want to fight for (blue or red) and write it down.
3.) Backup the original files which are listed under 4.)
4.) End F4 and run TacEdit, open a campaign by browsing to campaign\save or Korea/2/3 or
Balkans\campaign\Balkans and select one of the campaign files save0/1/2.cam and open.
5.) Click insert and add unit as shown in the picture below

6.) The following window will open

7.) Select “New” => Squadron, “Type” => i.e. Fighter or any other type you want to add,
“SubType” JG Eurofighter or any other type you want to add. Press “OK” and the airbase
selection window will appear. Just select the Airbase you want to use and click “OK”
8.) The next window is called “squadron as shown below

30
(c) Viking[128th VFS] aka Scorpion82 6 August 2008

9.) In “Base Object” select the owner i.e. ROK or US when you want to fight for the blue site (note
that the Airbase must be owned by the specific site). In “Unit Properties” enter a number in the
field “Name” which is the squadron unit number for example 74 will appear as 74th in the
campaign. On the squadron page you have to choose a “Speciality” for the type of missions
you want to fly. “None” means multirole.
10.) Click ok and then save the campaign

Congratulations you successfully added a new squadron to a campaign!

31

Вам также может понравиться