https://www.airgoons.com/wiki/api.php?action=feedcontributions&user=Tippis&feedformat=atomAirgoons - User contributions [en]2024-03-29T13:36:55ZUser contributionsMediaWiki 1.39.0https://www.airgoons.com/wiki/index.php?title=Airgoons&diff=5726Airgoons2023-10-29T21:59:00Z<p>Tippis: /* Terrains and oddities */</p>
<hr />
<div>This page is primarily meant to let Airgoons list their modules and primary role interests so that mission makes can get an idea of exactly how infeasible their neat idea is as far as finding enough players (at least in MP) to actually play it. You will not be audited — not listing a module because you don't want to fly it will <del>result in commissar</del> not exactly have any consequences.<br />
<br />
If wiki markup is too headache-inducing, just [https://docs.google.com/forms/d/e/1FAIpQLScHEJVWQikBt8FGB4JIHaBVPi3k9ol0JcFjD2p07KGQLm42rg/viewform fill out this survey] and it'll be transferred here eventually. If not, the easiest way is to just copy/paste an existing line (don't forget the initial |- that separates one line from another) and edit to your own liking.<br />
<br />
== DCS Modules ==<br />
<br />
<br />
=== Jets ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! A-10C !! A-10C 2 !! AJS-37 !! AV-8B !! F-5 !! F-14 !! F-16C !! F/A-18C !! F-86 !! FC3 !! JF-17 !! MiG-15 !! MiG-19 !! MiG-21 !! M2k !! F1 !! F-15E<br />
|-<br />
| Andupor<br />
| X || X || || || X || X || || X || || X || || || || || || ||<br />
|-<br />
| Arbitrary<br />
| X || X || X || X || X || X || X || X || X || X || X || X || || X || || X || X<br />
|-<br />
| b0rt<br />
| X || X || X || X || X || X || X || X || || X || X || || || X || X || X ||<br />
|-<br />
| bear.is.flying<br />
| X || X || || X || || X || X || X || || X || || || || || X || ||<br />
|-<br />
| big_soda<br />
| X || X || X || X || X || X || X || || || X || || || || X || X || || <br />
|-<br />
| BlueNexa<br />
| || || X || X || X || X || || X || || || X || || || X || X || ||<br />
|-<br />
| Bonkers<br />
| X || || X || X || X || X || || X || || X || || X || || X || X || ||<br />
|-<br />
| Burno<br />
| X || X || X || X || X || X || X || X || X || X || X || X || X || X || X || ||<br />
|-<br />
| BurntCornMuffin<br />
| X || X || || X || X || || X || X || || || X || || || X || || ||<br />
|-<br />
| Commandante<br />
| X || || || X || || || || X || || || || || || || || ||<br />
|-<br />
| Commissar<br />
| X || X || || X || X || X || X || X || X || X || || X || X || X || || ||<br />
|- <br />
| Dandywalken<br />
| X || X || || || || || || || || X || || || || || || ||<br />
|-<br />
| Dark Off<br />
| || || X || X || || || X || X || || || || || || X || X || ||<br />
|-<br />
| DeadSeed<br />
| X || X || || X || X || X || X || X || || X || || || || X || X || X || X<br />
|-<br />
| eeme<br />
| || || || || || X || X || || || X || || || || || || ||<br />
|-<br />
| FatKao<br />
| || X || || || || || X || || || || || || || || || || X<br />
|-<br />
| Gooch<br />
| X || || X || X || X || X || X || X || X || X || || X || || X || X || ||<br />
|-<br />
| Jae<br />
| X || || || || X || X || || X || || X || || || || || || ||<br />
|-<br />
| JabbyJabara<br />
| X || X || || X || X || X || X || X || X || X || || X || X || X || X || ||<br />
|-<br />
| Jarmak<br />
| X || || || || || || || X || || || || || || || || ||<br />
|-<br />
| jzilla<br />
| X || || || || || X || X || X || X || X || || || || X || || ||<br />
|-<br />
| Kilonum<br />
| X || || || || || || || || || || || || || || || ||<br />
|-<br />
| king.crab<br />
| || || || || || || || || || || || || || || || ||<br />
|-<br />
| Limpet<br />
| X || X || || X || X || X || X || X || || X || || || || X || || ||<br />
|-<br />
| MadDog<br />
| || || || || X || X || || X || || X || X || || X || X || X || ||<br />
|-<br />
| Madman Theory<br />
| X || || X || X || X || X || X || X || X || X || X || X || X || X || X || ||<br />
|-<br />
| Makrond<br />
| X || || || || X || || || || X || X || || || || || || ||<br />
|-<br />
| Minto Took<br />
| X || || X || X || X || X || || X || X || X || || X || || X || X || ||<br />
|-<br />
| Nemahs<br />
| X || || || X || || X || X || X || || || || || || || || ||<br />
|-<br />
| Oglogod<br />
| X || || || || X || X || || X || X || X || || X || || || || ||<br />
|-<br />
| OhsH<br />
| X || || || X || || X || || X || X || X || || X || || X || X || ||<br />
|-<br />
| OwlofDoom<br />
| || || || || || X || || X || || X || || || || || || ||<br />
|-<br />
| Prime<br />
| X || X || || || X || X || X || X || || X || || || || || X || ||<br />
|-<br />
| puppies <br />
| || || || || || || || X || || || X || || || X || || ||<br />
|-<br />
| sadfunda<br />
| X || X || || X || || X || X || || || X || || || || || || ||<br />
|-<br />
| SaulKain<br />
| X || || X || X || X || X || X || X || X || X || X || X || || X || X || ||<br />
|-<br />
| Slip<br />
| X || || || || || || X || || || || || || || || || ||<br />
|-<br />
| Snapshot<br />
| X || X || X || X || X || X || X || X || || X || X || || || X || X || || X<br />
|-<br />
| SoapyTarantula<br />
| X || X || || X || X || X || X || X || || X || X || || || X || X || ||<br />
|-<br />
| SquadronROE<br />
| || || || || || || || || || || || || || || X || ||<br />
|-<br />
| TasogareNoKagi<br />
| X || X || X || X || X || X || X || X || || X || X || || || X || X || ||<br />
|-<br />
| TastyShrimpPlatter<br />
| X || X || || || || || X || X || || X || || || || || || ||<br />
|-<br />
| Teeter<br />
| || || || || X || || || X || || X || || || || || || ||<br />
|-<br />
| Tippis<br />
| X || X || X || X || X || X || X || X || X || X || X || X || X || X || X || || X<br />
|-<br />
| Triikon<br />
| X || || || || || X || || X || || X || || || || || || ||<br />
|-<br />
| Tythas<br />
| X || || X || || || X || ||X || || X || X || || || || || ||<br />
|-<br />
| wally<br />
| X || X || || X || X || X || X || X || || X || || || || || || ||<br />
|-<br />
| warcake<br />
| X || || || || || || || X || || X || || || || X || X || ||<br />
|-<br />
| woop<br />
| || || X || || || X || || X || X || X || || || || X || || ||<br />
|-<br />
| Xeno426<br />
| X || || X || || || X || X || X || || X || X || || X || || || X || X<br />
|-<br />
| Yooper<br />
| X || X || || || || || X || || || X || || || || || X || ||<br />
X <br />
|}<br />
<br />
=== Props and helos ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! Bf 109 !! Fw 190 A-8 !! Fw 190 D-9 !! Mosquito FB VI !!P-47 !! P-51D !! Spitfire !! I-16 !! AH-64D !! Ka-50 2 !! Mi-8 !! SA342 !! UH-1H !! Mi-24P !! Ka-50 3<br />
|-<br />
| Andupor<br />
| || || || || || || || || || || || || X || ||<br />
|-<br />
| Arbitrary<br />
| || || || X || || || || || X || X || X || || || X|| X<br />
|-<br />
| b0rt<br />
| || || || || || X || || || X || X || X || X || X || X||<br />
|-<br />
| bear.is.flying<br />
| || || || || || || || || || X || || || X || ||<br />
|-<br />
| big_soda<br />
| || || || || || || || || X || || || || X || X|| <br />
|-<br />
| BlueNexa<br />
| || || || || || || || || X || X || || || || || X<br />
|-<br />
| BurntCornMuffin<br />
| || || || || || X || || || || || || || || ||<br />
|-<br />
| Bonkers<br />
| || || || || || || || || || || || X || || ||<br />
|-<br />
| Burno<br />
| X || || X || || || X || X || || || X || X || X || X || ||<br />
|-<br />
| Commissar<br />
| || || || || || X || || || X || X || X || || X || X ||<br />
|-<br />
| Dandywalken<br />
| || || || || || || || || X || || X || || X || X ||<br />
|-<br />
| Dark Off<br />
| || || || || || || || || X || X || || || X || X ||<br />
|-<br />
| DeadSeed<br />
| X || X || || X || || || || || X || X || X || X || X || X || X<br />
|-<br />
| FatKao<br />
| || || || || || || || || || || || || X || ||<br />
|-<br />
| king.crab<br />
| || || || || || || || || || || || || || ||<br />
|-<br />
| Madman Theory<br />
| || || X || || || || || || || X || X || X || X || ||<br />
|-<br />
| JabbyJabara<br />
| X || X || X || || X || X || X || X || || || || || || ||<br />
|-<br />
| Jarmak<br />
| || || || || || X || || || || || || || || ||<br />
|-<br />
| Kilonum<br />
| || || || || || X || || || || || || || || ||<br />
|-<br />
| Limpet<br />
| || || || || || || || || || X || X || || X || ||<br />
|-<br />
| Makrond<br />
| || || || || || X || || || || X || X || X || X || ||<br />
|-<br />
| Minto Took<br />
| X || || X || || || X || || || || X || X || || X || ||<br />
|-<br />
| Nemahs<br />
| || || || || || X || || || || X || X || || X || ||<br />
|-<br />
| Oglogod<br />
| || || X || || || X || || || || X || X || || X || ||<br />
|-<br />
| Ohsh<br />
| || || X || || || X || || || || X || || || X || ||<br />
|-<br />
| Prime<br />
| || || || || || || X || || || || || || X || ||<br />
|-<br />
| puppies<br />
| || || || || || || || || || || X || || || X ||<br />
|-<br />
| SaulKain<br />
| || || || || || || || || || X || X || X || X || ||<br />
|-<br />
| Snapshot<br />
| || || || || || || || || X || X || X || X || X || X || X<br />
|-<br />
| SoapyTarantula<br />
| || || || || || || || || || X || X || || X || ||<br />
|-<br />
| TasogareNoKagi<br />
| || || || || || X || || || X || X || X || || X || X ||<br />
|-<br />
| TastyShrimpPlatter<br />
| || || || || || X || || || X || X || || || X || ||<br />
|-<br />
| Tippis<br />
| X || X || X || X || X || X || X || X || X || X || X || X || X || X || X<br />
|-<br />
| Triikon<br />
| || || || || || || || || || || || || X || ||<br />
|-<br />
| Tythas<br />
| || || || || || X || || || || X || || || X || ||<br />
|-<br />
| wally<br />
| || || || || || X || X || || || X || || || X || ||<br />
|-<br />
| warcake<br />
| || || || || || || || || || X || || || || ||<br />
|-<br />
| woop<br />
| || || || || || || || || || X || || || || ||<br />
|-<br />
| Xeno426<br />
| || || || || || || || X || X || X || || || || || X<br />
|-<br />
| MadDog<br />
| || || || || || || || || || X || || || X || X ||<br />
|}<br />
<br />
=== Trainers ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! C-101 !! CE2 !! L-39 !! MB-339 !! Hawk !! Yak-52<br />
|-<br />
| Arbitrary<br />
| || || X || || || <br />
|-<br />
| b0rt<br />
| || || X || || || <br />
|-<br />
| Burno<br />
| X || X || X || || X || X<br />
|-<br />
| Madman Theory<br />
| || || X || || || <br />
|-<br />
| Makrond<br />
| || || || || X || <br />
|-<br />
| Minto Took<br />
| X || X || || || || <br />
|-<br />
| Tippis<br />
| X || X || X || || || X<br />
|}<br />
<br />
=== Terrains and oddities ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! The Channel !! Nevada !! Normandy !! WWII Assets !! Persian Gulf !! Combined Arms !! Supercarrier !! Syria !! South Atlantic !! Normandy 2 !! Sinai<br />
|-<br />
| Andupor<br />
| || || || || X || X || X || X || || ||<br />
|-<br />
| Arbitrary<br />
| X || || || X || X || X || X || X || X || X || X<br />
|-<br />
| b0rt<br />
| || X || || || X || X || X || X || || ||<br />
|-<br />
| bear.is.flying<br />
| || X || || || X || || X || || || ||<br />
|-<br />
| big_soda<br />
| || X || || || X || X || X || X || X || || <br />
|-<br />
| BlueNexa<br />
| || X || || || || || || || || ||<br />
|-<br />
|-<br />
| Bonkers<br />
| || || || || X || || X || || || ||<br />
|-<br />
| Burno<br />
| || X || X || X || X || X || X || || || ||<br />
|-<br />
| BurntCornMuffin<br />
| X || X || || X || X || || X || X || || ||<br />
|-<br />
| Commandante<br />
| || || || || X || || || || || ||<br />
|-<br />
| Commissar<br />
| || X || || || X || X || X || X || || ||<br />
|-<br />
| Dark Off<br />
| || || || || X || || || || || ||<br />
|-<br />
| DeadSeed<br />
| X || X || X || X || X || X || X ||X || X || X || X<br />
|-<br />
| eeme<br />
| || || || || X || || || || || ||<br />
|-<br />
| FatKao<br />
| || || X || || X || X || || X || || ||<br />
|-<br />
| king.crab<br />
| || || || || || || || || || ||<br />
|-<br />
| Limpet<br />
| || X || || || X || || X || X || || ||<br />
|-<br />
| Madman Theory<br />
| || X || || || X || X || X || || || ||<br />
|-<br />
| JabbyJabara<br />
| X || X || X || X || X || || X || X || || ||<br />
|-<br />
| Jae<br />
| || || || || X || || || || || ||<br />
|-<br />
| Jarmak<br />
| || || || || X || || || || || ||<br />
|-<br />
| Kilonum<br />
| || || || || || X || || || || ||<br />
|-<br />
| Makrond<br />
| || || || || || X || || || || ||<br />
|-<br />
| Minto Took<br />
| || X || X || X || X || X || || || || ||<br />
|-<br />
| Nemahs<br />
| || X || || || X || || X || || || ||<br />
|-<br />
| Oglogod<br />
| || X || || || X || X || || || || ||<br />
|-<br />
| OhsH<br />
| || || || || X || || || || || ||<br />
|-<br />
| OwlofDoom<br />
| || X || X || X || X || X || || || || ||<br />
|-<br />
| Prime<br />
| X || X || X || X || X || || X || X || || ||<br />
|-<br />
| puppies<br />
| || || || || X || || X || X || || ||<br />
|-<br />
| sadfunda<br />
| || || || || X || || X || X || || ||<br />
|-<br />
| SaulKain<br />
| || X || X || X || X || X || || || || ||<br />
|-<br />
| Slip<br />
| || X || || || X || || ||X || || ||<br />
|-<br />
| Snapshot<br />
| || X || || X || X || X || X || X || X || X || X<br />
|-<br />
| SoapyTarantula<br />
| || || || || X || X || X || X || || ||<br />
|-<br />
| TasogareNoKagi<br />
| || || || || X || X || X || X || || ||<br />
|-<br />
| Tippis<br />
| X || X || X || X || X || X || X || X || X || X || X<br />
|-<br />
| Triikon<br />
| || || || || X || || || || || ||<br />
|-<br />
| Tythas<br />
| || || || || X || || || || || ||<br />
|-<br />
| wally<br />
| || X || X || X || X || X || X || X || || ||<br />
|-<br />
| warcake<br />
| || || || || X || || || || || ||<br />
|-<br />
| Xeno426<br />
| X || || X || X || X || X || X || X || X|| ||<br />
|-<br />
| MadDog<br />
| || || || || X || X || X || X || || ||<br />
|}<br />
<br />
== Skillz / interests ==<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! A2A !! A2G !! Refueling !! Carriers !! RIO/WSO !! Instruction !! GCI !! ATC !! LSO !! Click-fest<ref>In other words, you think cold-starts and similar systems-geekery can be fun at times.</ref> !! Modding<ref>You're comfortable and fine installing mods to play missions, e.g. the C-130J mod.</ref><br />
|-<br />
| Andupor<br />
| X || X || X || X || X || X || X || X || X || X || X<br />
|-<br />
| Arbitrary<br />
| X || X || X || X || X || X || X || X || X || X || X<br />
|-<br />
| b0rt<br />
| X || X || X || X || X || X || X || X || || X ||<br />
|-<br />
| big_soda<br />
| X || X || X || X || || X || X || X || || X || X<br />
|-<br />
| BlueNexa<br />
| X || X || X || X || X || || X || X || || X || X<br />
|-<br />
| Bonkers<br />
| X || X || X || X || || X || X || || || X ||<br />
|-<br />
| Burno<br />
| X || X || X || X || X || X || X || || || X ||<br />
|-<br />
| BurntCornMuffin<br />
| X || X || X || X || || X || X || || X || X ||<br />
|-<br />
| Commandante<br />
| X || X || X || X || || X || || || || X ||<br />
|-<br />
| Commissar<br />
| X || X || || X || || X || || || || X ||<br />
|-<br />
| Deadseed<br />
| X || X || X || X || X || X || || || || X || X<br />
|-<br />
| FatKao<br />
| X || X || || || X || || || || || X || X<br />
|-<br />
| Forums Terrorist<br />
| X || X || X || X || X || X || || || || X ||<br />
|-<br />
| JabbyJabara<br />
| X || X || X || X || X || X || X || X || X || X ||<br />
|-<br />
| Jae<br />
| X || || X || X || || X || || || || X ||<br />
|-<br />
| Jarmak<br />
| X || X || || X || || || || || || X ||<br />
|-<br />
| king.crab<br />
| || || || || || || || || || ||<br />
|-<br />
| Makrond<br />
| X || X || X || X || || || || || || X ||<br />
|-<br />
| Minto Took<br />
| X || X || X || X || X || || || || || X ||<br />
|-<br />
| Nemahs<br />
| X || X || X || X || X || || X || X || || X ||<br />
|-<br />
| Oglogod<br />
| X || X || X || X || X || || || || || X ||<br />
|-<br />
| OhsH<br />
| X || X || X || X || || || || || || X ||<br />
|-<br />
| Prime<br />
| X || X || X || X || X || || || || || X ||<br />
|-<br />
| puppies<br />
| X || X || || X || || || || || || X ||<br />
|-<br />
| sadfunda<br />
| X || X || X || X || X || X || || || || X || X<br />
|-<br />
| SaulKain<br />
| X || X || X || X || X || X || || || || X ||<br />
|-<br />
| Slip<br />
| X || X || X || || || || || || || X ||<br />
|-<br />
| Snapshot<br />
| X || X || X || X || X || X || || || || X ||<br />
|-<br />
| SoapyTarantula<br />
| X || X || X || X || X || || X || X || || X ||<br />
|-<br />
| Tippis<br />
| X || X || || X || X || X || X || || || X ||<br />
|-<br />
| Triikon<br />
| X || X || || X || || || || || || ||<br />
|-<br />
| Tythas<br />
| X || X || X || X || || || || || || X ||<br />
|-<br />
| warcake<br />
| X || X || X || X || || || || || || X ||<br />
|-<br />
| woop<br />
| || || || || || || || || || X ||<br />
|-<br />
| Xeno426<br />
| X || X || || || X || X || || || || X || X<br />
|}<br />
<br />
== Il-2 addons ==<br />
<br />
=== Battle of&hellip; ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name !! Bodenplatte !! Kuban !! Moscow !! Normandy !! Stalingrad<br />
|-<br />
| Andupor || X || X || X || X || X<br />
|-<br />
| Arbitrary || Pre || X || X || || Pre<br />
|-<br />
| b0rt || Pre || Pre || Pre || || X<br />
|-<br />
| Commissar || Pre || Pre || Pre || || Pre<br />
|-<br />
| Dark Off ||Pre || Pre || || || <br />
|-<br />
| Fraggsta || Pre || Pre || Pre || || Pre<br />
|-<br />
| Madman Theory || Pre || Pre || Pre || || Pre<br />
|-<br />
| sadfunda || X || X || || || X<br />
|-<br />
| Tippis || Pre || Pre || Pre || || Pre<br />
|}<br />
<br />
* X = Owns standard edition<br />
* Pre = Owns premium edition<br />
* Note any premium planes bought separately in the [[#Premium_planes|premium planes table]] below.<br />
<br />
=== Addons ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name !! Flying Circus !! Tank Crew<br />
|-<br />
| Andupor || || X<br />
|-<br />
| Arbitrary || Vol.1 ||<br />
|-<br />
| Commissar || X ||<br />
|-<br />
| Madman Theory || X || <br />
|-<br />
| Tippis || X || <br />
|}<br />
<br />
=== Collector planes ===<br />
Planes that are not part of any standard or premium collection.<br />
<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! Bf&nbsp;109&nbsp;G-6 !! Hurricane&nbsp;Mk.II !! Ju 52/Зm !! La-5FN !! U-2VS !! Yak-1b !! Yak-9 !! Yak-9T<br />
|-<br />
| Andupor<br />
| X || || X || X || || X || X || <br />
|-<br />
| Arbitrary<br />
| || || X || || X || || || <br />
|-<br />
| Commissar<br />
| || || || X || X || X || X || X<br />
|-<br />
| Fraggsta<br />
| X || || X || X || || X || || <br />
|- <br />
| Madman Theory<br />
| X || || X || X || X || X || || <br />
|-<br />
| Tippis<br />
| X || || X || X || || X || || <br />
|}<br />
<br />
=== Premium planes ===<br />
Planes that are part of the premium packages, but have been bought separately.<br />
<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! Ar&nbsp;234 !! Fw&nbsp;190&nbsp;A-3 !! Fw&nbsp;190&nbsp;D-9 !! Hs-129&nbsp;B-2 !! La-5<br />
! MC.202 !! P-38J !! P-40 !! Spit&nbsp;Mk.VB !! Spit&nbsp;Mk.XIV<br />
|-<br />
| Andupor<br />
| || X || X || || X<br />
| X || || X || || <br />
|}<br />
<br />
=== Standard and premium planes ===<br />
{| class="wikitable" style="text-align: center;"<br />
|-<br />
! Module !! Standard !! Premium<br />
|-<br />
! Battle&nbsp;of&nbsp;Bodenplatte<br />
| Bf&nbsp;109&nbsp;G-14, Bf&nbsp;109&nbsp;K-4, Fw&nbsp;190&nbsp;A-8, Me&nbsp;262, P-51D, P-47D, Spitfire&nbsp;Mk.IX, Tempest&nbsp;Mk.V<br />
| Fw&nbsp;190&nbsp;D-9, P-38J <br />
|-<br />
! Battle&nbsp;of&nbsp;Kuban<br />
| A-20B, Bf&nbsp;109&nbsp;G-4, Bf&nbsp;110&nbsp;G-2, Fw&nbsp;190&nbsp;A-5, He&nbsp;111&nbsp;H-16, Il-2&nbsp;AM-38F&nbsp;(1943), P-39L-1, Yak-7b<br />
| Hs-129&nbsp;B-2, Spitfire&nbsp;Mk.VB<br />
|-<br />
! Battle&nbsp;of&nbsp;Moscow<br />
| Bf&nbsp;109&nbsp;E-7, Bf&nbsp;109&nbsp;F-2, Bf&nbsp;110&nbsp;E-2, I-16, Il-2&nbsp;AM-38&nbsp;(1941), Ju&nbsp;88 A-4, MiG-3, Pe-2&nbsp;s.35<br />
| MC.202, P-40<br />
|-<br />
! Battle&nbsp;of&nbsp;Normandy<br />
| Bf&nbsp;109&nbsp;G-6&nbsp;&ldquo;late&rdquo;, Fw&nbsp;190&nbsp;A-6, Ju&nbsp;88&nbsp;C-6a, Me&nbsp;410, Mosquito&nbsp;F.B.&nbsp;Mk.VI, P-47D&nbsp;&ldquo;Razorback&rdquo;, P-51B/C, Typhoon&nbsp;Mk.Ib<br />
| Ar&nbsp;234, Spitfire&nbsp;Mk.XIV<br />
|-<br />
! Battle&nbsp;of&nbsp;Stalingrad<br />
| Bf&nbsp;109&nbsp;F-4, Bf&nbsp;109&nbsp;G-2, Il-2&nbsp;AM-38&nbsp;(1942), He&nbsp;111&nbsp;H-6, Ju&nbsp;87&nbsp;D-3, LaGG-3, Pe-2&nbsp;s.87, Yak-1<br />
| Fw&nbsp;190&nbsp;A-3, La-5<br />
|-<br />
! Flying&nbsp;Circus<br />
| Albatros&nbsp;D.Va, Bristol&nbsp;Fighter, Bristol&nbsp;Fighter&nbsp;F.III, Fokker&nbsp;D.VII, Fokker&nbsp;D.VIIF, Fokker&nbsp;Dr.1, Halberstadt&nbsp;CL.II, Halberstadt&nbsp;CL.II&nbsp;(200Hp), Pfalz&nbsp;D.IIIa, RAF&nbsp;S.E.5.a, Sopwith&nbsp;Dolphin, Sopwith&nbsp;Camel, Spad&nbsp;XIII<br />
| &mdash;<br />
|}</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Airgoons&diff=5725Airgoons2023-10-29T21:58:37Z<p>Tippis: /* Props and helos */</p>
<hr />
<div>This page is primarily meant to let Airgoons list their modules and primary role interests so that mission makes can get an idea of exactly how infeasible their neat idea is as far as finding enough players (at least in MP) to actually play it. You will not be audited — not listing a module because you don't want to fly it will <del>result in commissar</del> not exactly have any consequences.<br />
<br />
If wiki markup is too headache-inducing, just [https://docs.google.com/forms/d/e/1FAIpQLScHEJVWQikBt8FGB4JIHaBVPi3k9ol0JcFjD2p07KGQLm42rg/viewform fill out this survey] and it'll be transferred here eventually. If not, the easiest way is to just copy/paste an existing line (don't forget the initial |- that separates one line from another) and edit to your own liking.<br />
<br />
== DCS Modules ==<br />
<br />
<br />
=== Jets ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! A-10C !! A-10C 2 !! AJS-37 !! AV-8B !! F-5 !! F-14 !! F-16C !! F/A-18C !! F-86 !! FC3 !! JF-17 !! MiG-15 !! MiG-19 !! MiG-21 !! M2k !! F1 !! F-15E<br />
|-<br />
| Andupor<br />
| X || X || || || X || X || || X || || X || || || || || || ||<br />
|-<br />
| Arbitrary<br />
| X || X || X || X || X || X || X || X || X || X || X || X || || X || || X || X<br />
|-<br />
| b0rt<br />
| X || X || X || X || X || X || X || X || || X || X || || || X || X || X ||<br />
|-<br />
| bear.is.flying<br />
| X || X || || X || || X || X || X || || X || || || || || X || ||<br />
|-<br />
| big_soda<br />
| X || X || X || X || X || X || X || || || X || || || || X || X || || <br />
|-<br />
| BlueNexa<br />
| || || X || X || X || X || || X || || || X || || || X || X || ||<br />
|-<br />
| Bonkers<br />
| X || || X || X || X || X || || X || || X || || X || || X || X || ||<br />
|-<br />
| Burno<br />
| X || X || X || X || X || X || X || X || X || X || X || X || X || X || X || ||<br />
|-<br />
| BurntCornMuffin<br />
| X || X || || X || X || || X || X || || || X || || || X || || ||<br />
|-<br />
| Commandante<br />
| X || || || X || || || || X || || || || || || || || ||<br />
|-<br />
| Commissar<br />
| X || X || || X || X || X || X || X || X || X || || X || X || X || || ||<br />
|- <br />
| Dandywalken<br />
| X || X || || || || || || || || X || || || || || || ||<br />
|-<br />
| Dark Off<br />
| || || X || X || || || X || X || || || || || || X || X || ||<br />
|-<br />
| DeadSeed<br />
| X || X || || X || X || X || X || X || || X || || || || X || X || X || X<br />
|-<br />
| eeme<br />
| || || || || || X || X || || || X || || || || || || ||<br />
|-<br />
| FatKao<br />
| || X || || || || || X || || || || || || || || || || X<br />
|-<br />
| Gooch<br />
| X || || X || X || X || X || X || X || X || X || || X || || X || X || ||<br />
|-<br />
| Jae<br />
| X || || || || X || X || || X || || X || || || || || || ||<br />
|-<br />
| JabbyJabara<br />
| X || X || || X || X || X || X || X || X || X || || X || X || X || X || ||<br />
|-<br />
| Jarmak<br />
| X || || || || || || || X || || || || || || || || ||<br />
|-<br />
| jzilla<br />
| X || || || || || X || X || X || X || X || || || || X || || ||<br />
|-<br />
| Kilonum<br />
| X || || || || || || || || || || || || || || || ||<br />
|-<br />
| king.crab<br />
| || || || || || || || || || || || || || || || ||<br />
|-<br />
| Limpet<br />
| X || X || || X || X || X || X || X || || X || || || || X || || ||<br />
|-<br />
| MadDog<br />
| || || || || X || X || || X || || X || X || || X || X || X || ||<br />
|-<br />
| Madman Theory<br />
| X || || X || X || X || X || X || X || X || X || X || X || X || X || X || ||<br />
|-<br />
| Makrond<br />
| X || || || || X || || || || X || X || || || || || || ||<br />
|-<br />
| Minto Took<br />
| X || || X || X || X || X || || X || X || X || || X || || X || X || ||<br />
|-<br />
| Nemahs<br />
| X || || || X || || X || X || X || || || || || || || || ||<br />
|-<br />
| Oglogod<br />
| X || || || || X || X || || X || X || X || || X || || || || ||<br />
|-<br />
| OhsH<br />
| X || || || X || || X || || X || X || X || || X || || X || X || ||<br />
|-<br />
| OwlofDoom<br />
| || || || || || X || || X || || X || || || || || || ||<br />
|-<br />
| Prime<br />
| X || X || || || X || X || X || X || || X || || || || || X || ||<br />
|-<br />
| puppies <br />
| || || || || || || || X || || || X || || || X || || ||<br />
|-<br />
| sadfunda<br />
| X || X || || X || || X || X || || || X || || || || || || ||<br />
|-<br />
| SaulKain<br />
| X || || X || X || X || X || X || X || X || X || X || X || || X || X || ||<br />
|-<br />
| Slip<br />
| X || || || || || || X || || || || || || || || || ||<br />
|-<br />
| Snapshot<br />
| X || X || X || X || X || X || X || X || || X || X || || || X || X || || X<br />
|-<br />
| SoapyTarantula<br />
| X || X || || X || X || X || X || X || || X || X || || || X || X || ||<br />
|-<br />
| SquadronROE<br />
| || || || || || || || || || || || || || || X || ||<br />
|-<br />
| TasogareNoKagi<br />
| X || X || X || X || X || X || X || X || || X || X || || || X || X || ||<br />
|-<br />
| TastyShrimpPlatter<br />
| X || X || || || || || X || X || || X || || || || || || ||<br />
|-<br />
| Teeter<br />
| || || || || X || || || X || || X || || || || || || ||<br />
|-<br />
| Tippis<br />
| X || X || X || X || X || X || X || X || X || X || X || X || X || X || X || || X<br />
|-<br />
| Triikon<br />
| X || || || || || X || || X || || X || || || || || || ||<br />
|-<br />
| Tythas<br />
| X || || X || || || X || ||X || || X || X || || || || || ||<br />
|-<br />
| wally<br />
| X || X || || X || X || X || X || X || || X || || || || || || ||<br />
|-<br />
| warcake<br />
| X || || || || || || || X || || X || || || || X || X || ||<br />
|-<br />
| woop<br />
| || || X || || || X || || X || X || X || || || || X || || ||<br />
|-<br />
| Xeno426<br />
| X || || X || || || X || X || X || || X || X || || X || || || X || X<br />
|-<br />
| Yooper<br />
| X || X || || || || || X || || || X || || || || || X || ||<br />
X <br />
|}<br />
<br />
=== Props and helos ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! Bf 109 !! Fw 190 A-8 !! Fw 190 D-9 !! Mosquito FB VI !!P-47 !! P-51D !! Spitfire !! I-16 !! AH-64D !! Ka-50 2 !! Mi-8 !! SA342 !! UH-1H !! Mi-24P !! Ka-50 3<br />
|-<br />
| Andupor<br />
| || || || || || || || || || || || || X || ||<br />
|-<br />
| Arbitrary<br />
| || || || X || || || || || X || X || X || || || X|| X<br />
|-<br />
| b0rt<br />
| || || || || || X || || || X || X || X || X || X || X||<br />
|-<br />
| bear.is.flying<br />
| || || || || || || || || || X || || || X || ||<br />
|-<br />
| big_soda<br />
| || || || || || || || || X || || || || X || X|| <br />
|-<br />
| BlueNexa<br />
| || || || || || || || || X || X || || || || || X<br />
|-<br />
| BurntCornMuffin<br />
| || || || || || X || || || || || || || || ||<br />
|-<br />
| Bonkers<br />
| || || || || || || || || || || || X || || ||<br />
|-<br />
| Burno<br />
| X || || X || || || X || X || || || X || X || X || X || ||<br />
|-<br />
| Commissar<br />
| || || || || || X || || || X || X || X || || X || X ||<br />
|-<br />
| Dandywalken<br />
| || || || || || || || || X || || X || || X || X ||<br />
|-<br />
| Dark Off<br />
| || || || || || || || || X || X || || || X || X ||<br />
|-<br />
| DeadSeed<br />
| X || X || || X || || || || || X || X || X || X || X || X || X<br />
|-<br />
| FatKao<br />
| || || || || || || || || || || || || X || ||<br />
|-<br />
| king.crab<br />
| || || || || || || || || || || || || || ||<br />
|-<br />
| Madman Theory<br />
| || || X || || || || || || || X || X || X || X || ||<br />
|-<br />
| JabbyJabara<br />
| X || X || X || || X || X || X || X || || || || || || ||<br />
|-<br />
| Jarmak<br />
| || || || || || X || || || || || || || || ||<br />
|-<br />
| Kilonum<br />
| || || || || || X || || || || || || || || ||<br />
|-<br />
| Limpet<br />
| || || || || || || || || || X || X || || X || ||<br />
|-<br />
| Makrond<br />
| || || || || || X || || || || X || X || X || X || ||<br />
|-<br />
| Minto Took<br />
| X || || X || || || X || || || || X || X || || X || ||<br />
|-<br />
| Nemahs<br />
| || || || || || X || || || || X || X || || X || ||<br />
|-<br />
| Oglogod<br />
| || || X || || || X || || || || X || X || || X || ||<br />
|-<br />
| Ohsh<br />
| || || X || || || X || || || || X || || || X || ||<br />
|-<br />
| Prime<br />
| || || || || || || X || || || || || || X || ||<br />
|-<br />
| puppies<br />
| || || || || || || || || || || X || || || X ||<br />
|-<br />
| SaulKain<br />
| || || || || || || || || || X || X || X || X || ||<br />
|-<br />
| Snapshot<br />
| || || || || || || || || X || X || X || X || X || X || X<br />
|-<br />
| SoapyTarantula<br />
| || || || || || || || || || X || X || || X || ||<br />
|-<br />
| TasogareNoKagi<br />
| || || || || || X || || || X || X || X || || X || X ||<br />
|-<br />
| TastyShrimpPlatter<br />
| || || || || || X || || || X || X || || || X || ||<br />
|-<br />
| Tippis<br />
| X || X || X || X || X || X || X || X || X || X || X || X || X || X || X<br />
|-<br />
| Triikon<br />
| || || || || || || || || || || || || X || ||<br />
|-<br />
| Tythas<br />
| || || || || || X || || || || X || || || X || ||<br />
|-<br />
| wally<br />
| || || || || || X || X || || || X || || || X || ||<br />
|-<br />
| warcake<br />
| || || || || || || || || || X || || || || ||<br />
|-<br />
| woop<br />
| || || || || || || || || || X || || || || ||<br />
|-<br />
| Xeno426<br />
| || || || || || || || X || X || X || || || || || X<br />
|-<br />
| MadDog<br />
| || || || || || || || || || X || || || X || X ||<br />
|}<br />
<br />
=== Trainers ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! C-101 !! CE2 !! L-39 !! MB-339 !! Hawk !! Yak-52<br />
|-<br />
| Arbitrary<br />
| || || X || || || <br />
|-<br />
| b0rt<br />
| || || X || || || <br />
|-<br />
| Burno<br />
| X || X || X || || X || X<br />
|-<br />
| Madman Theory<br />
| || || X || || || <br />
|-<br />
| Makrond<br />
| || || || || X || <br />
|-<br />
| Minto Took<br />
| X || X || || || || <br />
|-<br />
| Tippis<br />
| X || X || X || || || X<br />
|}<br />
<br />
=== Terrains and oddities ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! The Channel !! Nevada !! Normandy !! WWII Assets !! Persian Gulf !! Combined Arms !! Supercarrier !! Syria !! South Atlantic !! Normandy 2 !! Sinai<br />
|-<br />
| Andupor<br />
| || || || || X || X || X || X || || ||<br />
|-<br />
| Arbitrary<br />
| X || || || X || X || X || X || X || X || X || X<br />
|-<br />
| b0rt<br />
| || X || || || X || X || X || X || || ||<br />
|-<br />
| bear.is.flying<br />
| || X || || || X || || X || || || ||<br />
|-<br />
| big_soda<br />
| || X || || || X || X || X || X || X || || <br />
|-<br />
| BlueNexa<br />
| || X || || || || || || || || ||<br />
|-<br />
|-<br />
| Bonkers<br />
| || || || || X || || X || || || ||<br />
|-<br />
| Burno<br />
| || X || X || X || X || X || X || || || ||<br />
|-<br />
| BurntCornMuffin<br />
| X || X || || X || X || || X || X || || ||<br />
|-<br />
| Commandante<br />
| || || || || X || || || || || ||<br />
|-<br />
| Commissar<br />
| || X || || || X || X || X || X || || ||<br />
|-<br />
| Dark Off<br />
| || || || || X || || || || || ||<br />
|-<br />
| DeadSeed<br />
| X || X || X || X || X || X || X ||X || X || X || X<br />
|-<br />
| eeme<br />
| || || || || X || || || || || ||<br />
|-<br />
| FatKao<br />
| || || X || || X || X || || X || || ||<br />
|-<br />
| king.crab<br />
| || || || || || || || || || ||<br />
|-<br />
| Limpet<br />
| || X || || || X || || X || X || || ||<br />
|-<br />
| Madman Theory<br />
| || X || || || X || X || X || || || ||<br />
|-<br />
| JabbyJabara<br />
| X || X || X || X || X || || X || X || || ||<br />
|-<br />
| Jae<br />
| || || || || X || || || || || ||<br />
|-<br />
| Jarmak<br />
| || || || || X || || || || || ||<br />
|-<br />
| Kilonum<br />
| || || || || || X || || || || ||<br />
|-<br />
| Makrond<br />
| || || || || || X || || || || ||<br />
|-<br />
| Minto Took<br />
| || X || X || X || X || X || || || || ||<br />
|-<br />
| Nemahs<br />
| || X || || || X || || X || || || ||<br />
|-<br />
| Oglogod<br />
| || X || || || X || X || || || || ||<br />
|-<br />
| OhsH<br />
| || || || || X || || || || || ||<br />
|-<br />
| OwlofDoom<br />
| || X || X || X || X || X || || || || ||<br />
|-<br />
| Prime<br />
| X || X || X || X || X || || X || X || || ||<br />
|-<br />
| puppies<br />
| || || || || X || || X || X || || ||<br />
|-<br />
| sadfunda<br />
| || || || || X || || X || X || || ||<br />
|-<br />
| SaulKain<br />
| || X || X || X || X || X || || || || ||<br />
|-<br />
| Slip<br />
| || X || || || X || || ||X || || ||<br />
|-<br />
| Snapshot<br />
| || X || || X || X || X || X || X || X || X || X<br />
|-<br />
| SoapyTarantula<br />
| || || || || X || X || X || X || || ||<br />
|-<br />
| TasogareNoKagi<br />
| || || || || X || X || X || X || || ||<br />
|-<br />
| Tippis<br />
| X || X || X || X || X || X || X || X || || ||<br />
|-<br />
| Triikon<br />
| || || || || X || || || || || ||<br />
|-<br />
| Tythas<br />
| || || || || X || || || || || ||<br />
|-<br />
| wally<br />
| || X || X || X || X || X || X || X || || ||<br />
|-<br />
| warcake<br />
| || || || || X || || || || || ||<br />
|-<br />
| Xeno426<br />
| X || || X || X || X || X || X || X || X|| ||<br />
|-<br />
| MadDog<br />
| || || || || X || X || X || X || || ||<br />
|}<br />
<br />
== Skillz / interests ==<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! A2A !! A2G !! Refueling !! Carriers !! RIO/WSO !! Instruction !! GCI !! ATC !! LSO !! Click-fest<ref>In other words, you think cold-starts and similar systems-geekery can be fun at times.</ref> !! Modding<ref>You're comfortable and fine installing mods to play missions, e.g. the C-130J mod.</ref><br />
|-<br />
| Andupor<br />
| X || X || X || X || X || X || X || X || X || X || X<br />
|-<br />
| Arbitrary<br />
| X || X || X || X || X || X || X || X || X || X || X<br />
|-<br />
| b0rt<br />
| X || X || X || X || X || X || X || X || || X ||<br />
|-<br />
| big_soda<br />
| X || X || X || X || || X || X || X || || X || X<br />
|-<br />
| BlueNexa<br />
| X || X || X || X || X || || X || X || || X || X<br />
|-<br />
| Bonkers<br />
| X || X || X || X || || X || X || || || X ||<br />
|-<br />
| Burno<br />
| X || X || X || X || X || X || X || || || X ||<br />
|-<br />
| BurntCornMuffin<br />
| X || X || X || X || || X || X || || X || X ||<br />
|-<br />
| Commandante<br />
| X || X || X || X || || X || || || || X ||<br />
|-<br />
| Commissar<br />
| X || X || || X || || X || || || || X ||<br />
|-<br />
| Deadseed<br />
| X || X || X || X || X || X || || || || X || X<br />
|-<br />
| FatKao<br />
| X || X || || || X || || || || || X || X<br />
|-<br />
| Forums Terrorist<br />
| X || X || X || X || X || X || || || || X ||<br />
|-<br />
| JabbyJabara<br />
| X || X || X || X || X || X || X || X || X || X ||<br />
|-<br />
| Jae<br />
| X || || X || X || || X || || || || X ||<br />
|-<br />
| Jarmak<br />
| X || X || || X || || || || || || X ||<br />
|-<br />
| king.crab<br />
| || || || || || || || || || ||<br />
|-<br />
| Makrond<br />
| X || X || X || X || || || || || || X ||<br />
|-<br />
| Minto Took<br />
| X || X || X || X || X || || || || || X ||<br />
|-<br />
| Nemahs<br />
| X || X || X || X || X || || X || X || || X ||<br />
|-<br />
| Oglogod<br />
| X || X || X || X || X || || || || || X ||<br />
|-<br />
| OhsH<br />
| X || X || X || X || || || || || || X ||<br />
|-<br />
| Prime<br />
| X || X || X || X || X || || || || || X ||<br />
|-<br />
| puppies<br />
| X || X || || X || || || || || || X ||<br />
|-<br />
| sadfunda<br />
| X || X || X || X || X || X || || || || X || X<br />
|-<br />
| SaulKain<br />
| X || X || X || X || X || X || || || || X ||<br />
|-<br />
| Slip<br />
| X || X || X || || || || || || || X ||<br />
|-<br />
| Snapshot<br />
| X || X || X || X || X || X || || || || X ||<br />
|-<br />
| SoapyTarantula<br />
| X || X || X || X || X || || X || X || || X ||<br />
|-<br />
| Tippis<br />
| X || X || || X || X || X || X || || || X ||<br />
|-<br />
| Triikon<br />
| X || X || || X || || || || || || ||<br />
|-<br />
| Tythas<br />
| X || X || X || X || || || || || || X ||<br />
|-<br />
| warcake<br />
| X || X || X || X || || || || || || X ||<br />
|-<br />
| woop<br />
| || || || || || || || || || X ||<br />
|-<br />
| Xeno426<br />
| X || X || || || X || X || || || || X || X<br />
|}<br />
<br />
== Il-2 addons ==<br />
<br />
=== Battle of&hellip; ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name !! Bodenplatte !! Kuban !! Moscow !! Normandy !! Stalingrad<br />
|-<br />
| Andupor || X || X || X || X || X<br />
|-<br />
| Arbitrary || Pre || X || X || || Pre<br />
|-<br />
| b0rt || Pre || Pre || Pre || || X<br />
|-<br />
| Commissar || Pre || Pre || Pre || || Pre<br />
|-<br />
| Dark Off ||Pre || Pre || || || <br />
|-<br />
| Fraggsta || Pre || Pre || Pre || || Pre<br />
|-<br />
| Madman Theory || Pre || Pre || Pre || || Pre<br />
|-<br />
| sadfunda || X || X || || || X<br />
|-<br />
| Tippis || Pre || Pre || Pre || || Pre<br />
|}<br />
<br />
* X = Owns standard edition<br />
* Pre = Owns premium edition<br />
* Note any premium planes bought separately in the [[#Premium_planes|premium planes table]] below.<br />
<br />
=== Addons ===<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name !! Flying Circus !! Tank Crew<br />
|-<br />
| Andupor || || X<br />
|-<br />
| Arbitrary || Vol.1 ||<br />
|-<br />
| Commissar || X ||<br />
|-<br />
| Madman Theory || X || <br />
|-<br />
| Tippis || X || <br />
|}<br />
<br />
=== Collector planes ===<br />
Planes that are not part of any standard or premium collection.<br />
<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! Bf&nbsp;109&nbsp;G-6 !! Hurricane&nbsp;Mk.II !! Ju 52/Зm !! La-5FN !! U-2VS !! Yak-1b !! Yak-9 !! Yak-9T<br />
|-<br />
| Andupor<br />
| X || || X || X || || X || X || <br />
|-<br />
| Arbitrary<br />
| || || X || || X || || || <br />
|-<br />
| Commissar<br />
| || || || X || X || X || X || X<br />
|-<br />
| Fraggsta<br />
| X || || X || X || || X || || <br />
|- <br />
| Madman Theory<br />
| X || || X || X || X || X || || <br />
|-<br />
| Tippis<br />
| X || || X || X || || X || || <br />
|}<br />
<br />
=== Premium planes ===<br />
Planes that are part of the premium packages, but have been bought separately.<br />
<br />
{| class="wikitable sortable" style="text-align: center;"<br />
|-<br />
! Name<br />
! Ar&nbsp;234 !! Fw&nbsp;190&nbsp;A-3 !! Fw&nbsp;190&nbsp;D-9 !! Hs-129&nbsp;B-2 !! La-5<br />
! MC.202 !! P-38J !! P-40 !! Spit&nbsp;Mk.VB !! Spit&nbsp;Mk.XIV<br />
|-<br />
| Andupor<br />
| || X || X || || X<br />
| X || || X || || <br />
|}<br />
<br />
=== Standard and premium planes ===<br />
{| class="wikitable" style="text-align: center;"<br />
|-<br />
! Module !! Standard !! Premium<br />
|-<br />
! Battle&nbsp;of&nbsp;Bodenplatte<br />
| Bf&nbsp;109&nbsp;G-14, Bf&nbsp;109&nbsp;K-4, Fw&nbsp;190&nbsp;A-8, Me&nbsp;262, P-51D, P-47D, Spitfire&nbsp;Mk.IX, Tempest&nbsp;Mk.V<br />
| Fw&nbsp;190&nbsp;D-9, P-38J <br />
|-<br />
! Battle&nbsp;of&nbsp;Kuban<br />
| A-20B, Bf&nbsp;109&nbsp;G-4, Bf&nbsp;110&nbsp;G-2, Fw&nbsp;190&nbsp;A-5, He&nbsp;111&nbsp;H-16, Il-2&nbsp;AM-38F&nbsp;(1943), P-39L-1, Yak-7b<br />
| Hs-129&nbsp;B-2, Spitfire&nbsp;Mk.VB<br />
|-<br />
! Battle&nbsp;of&nbsp;Moscow<br />
| Bf&nbsp;109&nbsp;E-7, Bf&nbsp;109&nbsp;F-2, Bf&nbsp;110&nbsp;E-2, I-16, Il-2&nbsp;AM-38&nbsp;(1941), Ju&nbsp;88 A-4, MiG-3, Pe-2&nbsp;s.35<br />
| MC.202, P-40<br />
|-<br />
! Battle&nbsp;of&nbsp;Normandy<br />
| Bf&nbsp;109&nbsp;G-6&nbsp;&ldquo;late&rdquo;, Fw&nbsp;190&nbsp;A-6, Ju&nbsp;88&nbsp;C-6a, Me&nbsp;410, Mosquito&nbsp;F.B.&nbsp;Mk.VI, P-47D&nbsp;&ldquo;Razorback&rdquo;, P-51B/C, Typhoon&nbsp;Mk.Ib<br />
| Ar&nbsp;234, Spitfire&nbsp;Mk.XIV<br />
|-<br />
! Battle&nbsp;of&nbsp;Stalingrad<br />
| Bf&nbsp;109&nbsp;F-4, Bf&nbsp;109&nbsp;G-2, Il-2&nbsp;AM-38&nbsp;(1942), He&nbsp;111&nbsp;H-6, Ju&nbsp;87&nbsp;D-3, LaGG-3, Pe-2&nbsp;s.87, Yak-1<br />
| Fw&nbsp;190&nbsp;A-3, La-5<br />
|-<br />
! Flying&nbsp;Circus<br />
| Albatros&nbsp;D.Va, Bristol&nbsp;Fighter, Bristol&nbsp;Fighter&nbsp;F.III, Fokker&nbsp;D.VII, Fokker&nbsp;D.VIIF, Fokker&nbsp;Dr.1, Halberstadt&nbsp;CL.II, Halberstadt&nbsp;CL.II&nbsp;(200Hp), Pfalz&nbsp;D.IIIa, RAF&nbsp;S.E.5.a, Sopwith&nbsp;Dolphin, Sopwith&nbsp;Camel, Spad&nbsp;XIII<br />
| &mdash;<br />
|}</div>Tippishttps://www.airgoons.com/wiki/index.php?title=NS_430_Navigation_system&diff=5663NS 430 Navigation system2023-02-18T19:42:01Z<p>Tippis: /* Missing features */</p>
<hr />
<div>{{Alpha}}<br />
{{RightImg|File:DCS-NS-430-Navigation-System-700x1000.jpg}}<br />
<br />
There are [[DCS_Modules|modules]] and there are ''modules'', and then there is this oddity. It is exactly what it says on the tin: a <strike>GNS 430</strike> &ldquo;NS 430&rdquo; GPS/Nav/Comm system for a whole slew of aircraft &mdash; notably ones that do not already have any kind of GPS functionality. Originally, this module was a plugin for the the [[Mi-8MTV2_Magnificent_Eight|Mi-8MTV2]] that bolted into the dashboard, but it has since been changed to be more universally applicable as a 2D overlay, and sub-modules are instead available that create in-cockpit interactive parts.<br />
<br />
{{Tocright}}<br />
<br />
It is a recreation of the GNS 430 (which, coincidentally, can be studied and learned in Garmin's own 400/500-series simulator app), and ever since the scope of the module was expanded to allow it to be used in more than just the Mi-8MTV2, it has the ''potential'' to almost become useful even though it is not the prettiest thing when just used as a 2D overlay. But only the potential, and only if it is ever actually made to work &mdash; which it doesn't &mdash; and is completed &mdash; which seems very unlikely. At the moment, it is mostly just a vanity fidget spinner; a funny hat for your airplane, with buttons on it that you can press to little or no effect.<br />
<br />
== Features ==<br />
Just like the real GSN 430, this module is meant to offer:<br />
* Dual VHF and VOR tuning with quick flip-blop between active and preparation frequencies.<br />
* GPS and VOR location tracking.<br />
* Moving map display with terrain and altitude warning indications.<br />
* Flight plan and waypoint management, including fuel planning.<br />
<br />
It is also meant to contain navigation and terrain data and tools for planning routes between and approaches to airports, which allows for more complex navigation under more adverse conditions than the baseline instruments do.<br />
<br />
'''Note: while it is not immediately obvious, you ''can'' use the mouse to interact with the 2D overlay even in &ldquo;non-clicky&rdquo; [[Flaming_Cliffs_3|FC3]]-style aircraft by first turning on the cursor ({{Key|LAlt}}{{Key|C}}) and then clicking away. In full-sim aircraft, this is the default state, so there is no need to do this extra step, and in the fully integrated cockpits, it is no different from other cockpit instruments.'''<br />
<br />
=== Missing features ===<br />
Even though the NS 430 is not labelled as &ldquo;early access&rdquo; in the DCS shop, it can not be considered to be properly released. It can't even be considered a proper beta, in part because the vast majority of functionality is still outright missing and has never been in a state where any kind of beta-testing can occur. In particular:<br />
* Airport, navpoint, and beacon database, including departure and approach procedures and emergency divert functionality.<br />
* Mission-editor options for selectively enabling/disabling the module are still lacking.<br />
* The is no real integration with any of the radio and navigation options suggested in the interface and in the store front blurb: COM/radio option can not be used for communications and is not integrated with any on-board radio systems, and the NDB/VOR receivers are not integrated with any on-board navigational systems and aren't actually being &ldquo;received&rdquo; in any sense. They are simply regular nav points that can be routed via the GPS flight plan programming.<br />
* The actual GPS navigation is for the most part broken and will not provide proper course directions to follow if you want to go anywhere.<br />
* The manual is still a work in progress in terms of describing how to operate the module.<br />
* It is not compatible with VR, and even has some bugs related to simple multi-monitor setups.<br />
<br />
The module has not seen any major (or even minor) updates since its release more than half a decade ago, and can for all intents and purposes be considered abandoned. It is not quite DCS: Hawk levels of broken and pointless, but very nearly given that it does not actually work in almost any respect and does not look likely to receive any attention any time soon.<br />
<br />
In addition to the core module itself, there five separate sub-modules that further expand on the NS 430's integration for other aircraft.<br />
<br />
=== NS 430 Navigation System for Mi-8MTV2 ===<br />
<br />
{{RightImgSmall|File:DCS-NS-430-Navigation-System-for-Mi-8MTV2-Cockpit-700x1000.jpg}}<br />
<br />
The [[Mi-8MTV2_Magnificent_Eight|Mi-8MTV2]] is not exactly lacking in navigation and radio equipment as it is, between its R-863, YaDRO-1A, R-828, ARK-9, and ARK-UD homing receivers and its DISS-15 doppler navigator, but they all rely on the presence of the appropriate transmitters, or on accurate relative position data and somewhat careful flying. It is all (mid-)20th century tech &mdash; the NS 430 brings the Magnificent Eight into the new millennium, or at least into the 1990s, with the ability to home to more modern aviation beacons and to use GPS navigation.<br />
<br />
If you already own the Mi-8MTV2 and the NS 430, this extra module turns the NS 430 into an actual in-cockpit system that exists alongside all the other dials, buttons, and gauges on the co-pilot's console. The functionality is the same, but you now manipulate it like any of the other stuff in the helicopter.<br />
<br />
(Perhaps not entirely) coincidentally, one of the campaigns for the Mi-8MTV2 is the [[Oilfield_Campaign_for_Mi-8MTV2|Oilfield Campaign]], which is all about mastering the helicopter's various navigation options. The NS 430 could certainly have helped with that particular problem, but the GPS is fortunately not available there, so getting it for that reason would not work. Then again, doing so would mean that half the challenge of the campaign is removed &mdash; and the NS 430 will also not do sling loading for you, which is the other half.<br />
<br />
=== NS 430 Navigation System for L-39C ===<br />
<br />
{{RightImgSmall|File:DCS-NS-430-Navigation-System-for-L-39%D0%A1-Cockpit-700x1000.jpg}}<br />
<br />
In sharp contrast, the [[L-39_Albatros|L-39C]], is not exactly blessed with an abundance of navigation aids. It has its NDB homing system, and the RSBN/ИСКРА radio navigation system &mdash; both of which rely on beacons that are increasingly rare. Indeed, ИСКРА is only half-available on the [[Caucasus]] map, and completely unavailable everywhere else &mdash; the ПРМГ landing mode is even more rare, as it is only supported by ''three'' airports in the entire game. This may make sense if you are actually a cadet trying to learn how to fly; it makes things quite inconvenient in all other cases.<br />
<br />
Here too, if you have the L-39C and the NS 430 already, this extra module adds the NS 430 as a 3D-rendered in-cockpit clicky system for the pilot. If the holographic sight has been removed in the L-39 Special options tab, the NS 430 will show up in place of the sight in the L-39C front seat, otherwise, it will be available in the back-seat. This allows the instructor to find new ways to challenge and monitor to poor front-seat student. The navigation system is not available (at least not as an integrated 3D instrument) in the ZA variant.<br />
<br />
=== NS 430 Navigation System for C-101EB and C-101CC ===<br />
<br />
{{RightImgSmall|File:N430-C101EB.jpg}}{{RightImgSmall|File:NS430-C101CC.jpg}}<br />
<br />
The silliest cash grab related to this abandoned module is to release cockpit integration addons for the [[C-101_Aviojet|C-101EB and CC]] aircraft. Separate modules &mdash; one for each of the two variants of the Aviojet. Since at this point, no mention has been made that the development of the NS 430 will be resumed, and since the C-101 addons still list functionality that the module isn't capable of, the sense in these modules even existing is questionable at best.<br />
<br />
The C-101 is far more able to navigate using traditional means than the L-39, and its built-in navigation tools actually work and send the pilot in the right direction, unlike the perpetually-bugged NS 430. But at least you can buy both addons for your single aircraft module at a very tiny discount &mdash; a little bit more, and they even throw in the actual aircraft at a much lower cost than any of the broken GPS modules.<br />
<br />
=== NS 430 Navigation System for SA342 Gazelle ===<br />
<br />
{{RightImgSmall|File:N430-SA342.jpg}}<br />
<br />
The [[SA342 Gazelle]] already features the fully integrated and highly competent and largely functional NADIR navigation system and is therefore an obvious candidate for a barely working disconnected bolt-on GPS. This would almost have made sense if it had been one of the bigger Garmin nav systems so the moving map and altitude display wasn't a pixelated low-resolution mess, but as it is, the module offers nothing of value that the Gazelle's built-in systems don't already do far better.<br />
<br />
== Links and files ==<br />
* [https://www8.garmin.com/support/download_details.jsp?id=3531 400W/500W Series Trainer] for Windows from Garmin.<br />
* [https://support.garmin.com/support/manuals/manuals.htm?partNo=010-00139-11&language=en&country=GB Manuals for GNS 430] from Garmin.<br />
* [https://www.digitalcombatsimulator.com/en/shop/modules/ns430/ DCS: NS 430 Navigation System] in the DCS shop.<br />
* [https://www.digitalcombatsimulator.com/en/shop/modules/ns430_mi8mtv2/ DCS: NS 430 Navigation System for Mi-8MTV2 Cockpit] in the DCS shop.<br />
* [https://www.digitalcombatsimulator.com/en/shop/modules/ns430_l39/ DCS: NS 430 Navigation System for L-39С Cockpit] in the DCS shop.<br />
* [https://www.digitalcombatsimulator.com/en/shop/modules/ns430_c-101eb/ DCS: NS 430 Navigation System for C-101EB] in the DCS shop.<br />
* [https://www.digitalcombatsimulator.com/en/shop/modules/ns430_c-101cc/ DCS: NS 430 Navigation System for C-101СС] in the DCS shop.<br />
* [https://www.digitalcombatsimulator.com/en/shop/modules/ns430_sa342/ DCS: NS 430 Navigation System for SA342 Gazelle] in the DCS shop.<br />
<br />
=== Related DCS modules ===<br />
* [[C-101 Aviojet]]<br />
* [[L-39 Albatros]]<br />
* [[Mi-8MTV2 Magnificent Eight|Mi-8MTV2 Magnificent Eight]]<br />
* [[SA342 Gazelle]]<br />
<br />
{{Add-ons}}<br />
[[Category:Add-on_Modules]][[Category:Modules]][[Category:Alpha_Modules]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Tasking&diff=5662Tasking2023-01-14T19:26:45Z<p>Tippis: </p>
<hr />
<div>A central part in both BMS and DCS is the tasking of an aircraft or package. <br />
<br />
== BMS Tasks ==<br />
In BMS, the tasking of a flight determines the mission success criteria for that flight, commonly in relation to the survival or destruction of some other set of units. Often, the flight has to check in and check out with AWACS, FAC, or other air controllers to explicitly start and end the tasking period, or the actions during the flight will simply not count towards mission completion.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Task !! Description !! BMS Success criteria !! DCS Equivalent<br />
|-<br />
! AI<br />
| '''A'''ir '''I'''nterdiction. missions to prevent reinforcements reaching the front line. There is no specific target assigned between the two target steerpoints and your flight is free to hunt down reinforcement and logistics units (actually any unit will do).<br />
| Destroy as many targets as possible. || CAS<br />
|-<br />
! AMBUSHCAP<br />
| '''Ambush''' '''C'''ombat '''A'''ir '''P'''atrol. Same as CAP but you are hiding from the OPFOR, usually behind a mountain at low altitude.<br />
| Arrive on time at the first CAP point and stay in the CAP for the assigned patrol time. || CAP<br />
|-<br />
! BARCAP<br />
| '''Bar'''rier '''C'''ombat '''A'''ir '''P'''atrol. A standard CAP where your flights will protect a geographical area from enemy aircraft. If you have to leave early for whatever reason you must request relief from the AWACS. Try not to fly too far from your CAP point and set a commit criterion of 25 NM. Flying too far from the CAP route stops the clock as far as counting towards your patrol time (usually 30 minutes but that depends on the flight plan).<br />
<br />
The difference between CAP and DCA is that CAP is not tied to specific assets so it is easier to get success with survival and CAP time, even if you did not shoot any OPFOR aircraft down.<br />
| Arrive on time at the first CAP point and stay in the CAP for the assigned patrol time. || CAP<br />
|-<br />
! BDA<br />
| '''B'''omb '''D'''amage '''A'''ssessment. Same as RECCE but post-strike to evaluate the strike effectiveness.<br />
| Fly within 2nm slant range carrying a Low Alt camera. || Reconnaissance<br />
|-<br />
! CAP<br />
| colspan="2" | Same as BARCAP<br />
| CAP<br />
|-<br />
! CAS<br />
| colspan="2" | Same as PRE-PLAN CAS<br />
| CAS<br />
|-<br />
! DCA<br />
| '''D'''efensive '''C'''ounter '''A'''ir. DCA missions are meant to protect friendly assets in a particular area. DCA flight plans have two CAP points and a patrol time. The main problem with DCA is knowing which asset to defend with a war going on around you.<br />
<br />
The difference between DCA and CAP is that CAP is not tied to specific assets so it is easier to get success with survival and CAP time, even if you did not shoot any OPFOR aircraft down.<br />
| Arrive on time at the first CAP point and stay in the CAP for the assigned patrol time. Assigned asset must survive. || CAP<br />
|-<br />
! DEAD<br />
| '''D'''estruction of '''E'''nemy '''A'''ir '''D'''efences. As the title implies you must destroy as many specific radars and/or launchers as possible at the target steerpoints.<br />
| At least one assigned radar and/or launcher asset must be destroyed. || SEAD<br />
|-<br />
! DEEP STRIKE<br />
| colspan="2" | Same as STRIKE but deep behind enemy lines.<br />
| Ground Strike, Precision Strike<br />
|-<br />
! ESCORT<br />
| Your flight must protect a package from OPFOR aircraft. You will meet with your target package and fly with them (usually in front of them to ensure they are not attacked by enemy aircraft). The trick with Escort is to find a good compromise between commit criteria and staying with the package. Enemy forces will try to drag you away from your target, so other enemy flights can destroy them while you are not there to protect them.<br />
| Assigned package must not sustain any losses. || Escort<br />
|-<br />
! FAC(A)<br />
| '''F'''orward '''A'''ir '''C'''ontroller ('''A'''ircraft) mission. Although the F-16 is not the best platform for FAC duties it is quite possible to direct strike flights in MP with the TGP and Laser Spot Tracker capabilities. You can now even illuminate and guide other flights’ LGB weapons. When tasked with FAC duties you must assist in the destruction of as many enemy ground units as possible around the 2 target steerpoints. This tasking is best flown in MP.<br />
| At least one assigned unit must be destroyed. || AFAC<br />
|-<br />
! HAVCAP<br />
| '''H'''igh '''Va'''lue '''CAP'''. Same as CAP but mission success is tied to the survival of the high value asset you are tasked to protect. CAP patrol time is usually longer with HAVCAP (defaults to 1 hour).<br />
| Arrive on time at the first CAP point and stay in the CAP for the assigned patrol time. Assigned asset must survive. || CAP<br />
|-<br />
! INTERCEPT<br />
| This Air to Air flight has a very specific target that must be intercepted and destroyed around the target steerpoint. This mission can unfortunately fail if another unit downed your target before you could.<br />
| The intercepted aircraft's mission must count as failed either by being shot down '''by you'' or being aborted. Oher friendly units killing the target ''does not'' count towards mission success. || Intercept<br />
|-<br />
! OCA STRIKE<br />
| '''O'''ffensive '''C'''ounter '''A'''ir '''Strike''' missions are targeted specifically against airbases or search radars. The purpose of OCA strikes is to help gain aerial supremacy by destroying assets on the ground. Should not be assigned to AI flights without ''complete'' air supremacy and fully suppressed air defences, since this type of mission will chew up AI flights like no other if any opposing units are alive in the target area.<br />
| Assigned target operational status must be reduced to below 70% after the strike. || Runway Attack, Ground Strike, Precision Strike<br />
|-<br />
! ON CALL CAS<br />
| '''On Call''' '''C'''lose '''A'''ir '''S'''upport. You are tasked to patrol an area (respect the patrol time) and standby for specific targets that will be transmitted to you by friendly assets (usually a FAC). The way the AI transmit target coordinates is tricky to follow and this type of mission is best flown in MP with a human FAC(A).<br />
| Stay on station for the full patrol time. At least one target must be destroyed. || CAS<br />
|-<br />
! PATROL<br />
| colspan="2" | Same as RECCE PATROL but the target is a naval unit.<br />
| Reconnaissance<br />
|-<br />
! PRE-PLAN CAS<br />
| '''Pre-plan'''ned '''C'''lose '''A'''ir '''S'''upport mission against known ground units. The FAC is not needed. Please note the flight plan will place two target steerpoints. The target is supposedly around these two steerpoints, usually moving on roads. Mission can unfortunately fail if your target was destroyed by other units and none are left for you to destroy.<br />
| At least one assigned unit must be destroyed. || CAS<br />
|-<br />
! RECCE<br />
| '''Rec'''onnaissanc'''e'''. Usually pre-strike recon mission against a specific target. Your aircraft will be loaded with the LOW ALT camera and you must photograph the target. Mission will be rated as success if you fly closer than 2 Nm (slant range) from target. Please note anything higher than 12000 feet is more than 2 Nm slant range.<br />
| Fly within 2nm slant range carrying a Low Alt camera. || Reconnaissance<br />
|-<br />
! RECCE PATROL<br />
| Same as RECCE but with two target steerpoints. Mission is aimed to search for enemy ground vehicles in the assigned area. Mainly used for choppers (which are not flyable by humans).<br />
| Fly within 2nm slant range carrying a Low Alt camera. || Reconnaissance<br />
|-<br />
! RESCAP<br />
| '''Res'''cue '''CAP'''. Same as CAP, but tied to friendly search-and-rescue assets (usually helicopters).<br />
| Arrive on time at the first CAP point and stay in the CAP for the assigned patrol time. Assigned asset must survive. || CAP, Escort<br />
|-<br />
! SEAD<br />
| '''S'''uppression of '''E'''nemy '''A'''ir '''D'''efences. The goal is not to destroy any specific ADA, but to protect a strike package from enemy air defences as needed on the way to, or during, their mission. The package is protected by keeping defences from attacking friendly units, either by destroying them, distracting them, or forcing them to switch off targeting systems to avoid destruction.<br />
| The assigned strike package must survive. || SEAD<br />
|-<br />
! SEAD ESCORT<br />
| colspan="2" | The old name for SEAD in BMS versions prior to 4.33.<br />
| SEAD<br />
|-<br />
! SEAD STRIKE<br />
| colspan="2" | The old name for DEAD in BMS versions prior to 4.33.<br />
| SEAD<br />
|-<br />
! STRIKE<br />
| Genuine Air to Ground strike mission against a variety of specific fixed strategic targets (other than airfields and radar installations &mdash; those are covered by OCA STRIKE).<br />
| Assigned target operational status must be reduced to below 70% after the strike. || Ground Strike, Precision Strike<br />
|-<br />
! SWEEP<br />
| Aggressive Air to Air flight that has no patrol time but 3 target steerpoints where you will attack and destroy as many OPFOR aircraft as possible without friendly losses in your flight.<br />
| Shoot down at least one enemy aircraft. || Fighter sweep<br />
|-<br />
! TARCAP<br />
| '''Tar'''get '''CAP'''. Same as CAP but you are protecting a specific target area (usually while other aircraft strike it).<br />
| Arrive on time at the first CAP point and stay in the CAP for the assigned patrol time. Strike aircraft operating in the area must survive. || CAP, Escort<br />
|-<br />
! TASMO<br />
| '''T'''actical '''A'''ir '''S'''upport for '''M'''aritime '''O'''perations. Effectively a STRIKE mission against naval targets &mdash; not as static as genuine STRIKE targets but also not as mobile or difficult to find as CAS.<br />
| Damage at least one ship at the attack steerpoint. || Anti-ship Strike<br />
|-<br />
! TRAINING<br />
| Training flight with no specific objectives. || Bring the jet back intact. || Nothing<br />
|}<br />
<br />
== DCS Tasks ==<br />
<br />
In DCS, tasking determines what aircraft are available (or more accurately the other way around), and also limits which weapon loadout presets are available to those aircraft. In addition, the tasking determines which advanced actions &mdash; notably tasks and enroute tasks &mdash; can be assigned to flight's waypoints.<br />
<br />
Some tasks also automatically apply specific enroute tasks by default, and for more control, the mission designer needs to go into the advanced waypoint settings and alter the parameters for these tasks. In practice, these pre-defined and automated assignments are invariably broken, bugged, idiotic in what behaviour and AI logic they generate, and otherwise utterly useless for the purpose of the actual task at hand. As a general rule, auto-applied tasks '''''should always''''' be removed and rebuilt from scratch. The only two exceptions are the AWACS and Tanker tasks, which for the most part cause no stupid behaviours if left alone (but for more complex missions should be removed and re-done anyway to actually operate in line with the correct waypoints). The CAS and CAP waypoint/enroute tasks should always be replaced by properly set up Search and Engage In Zone &mdash; or some variation thereof &mdash; task, which offers proper controls for what targets should be engaged and where.<br />
<br />
Due to the broad nature of DCS tasks and the many ways they can be customised with enroute and waypoint tasks, there are significant overlaps in what tasks can be used for what purpose, eg. using verious setups for both Escort and CAP tasking to create what in BMS would be considered the separate HAVCAP and TARCAP tasks. Again, the base task is more a matter of ''selecting aircraft and munitions'' than of fully defining what the flight is supposed to do and how it is meant to behave. All of that is set up with waypoint and enroute tasks.<br />
<br />
<br />
[[Category:Guides]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Fragging_a_package&diff=5661Fragging a package2023-01-13T14:36:45Z<p>Tippis: </p>
<hr />
<div><br />
''Adapted from wonko's discord instructions.''<br />
<br />
&ldquo;Fragging&rdquo; in [[Falcon Benchmark Simulator|BMS]] does not refer to the making happening of ludicrous gibs, but rather the creation of a core mission and assigning the various flights &mdash; strike aircraft, escorts, dedicated ECM, refuel, and awacs and whatever else is needed &mdash; to support that mission.<br />
<br />
Packages can be made hideously complex to set up and time correctly, but can be as simple as just a single wing or even a single aircraft. Even in the simple case, however, the complexities afforded by the game make it necessary to jump through a few hoops to get going.<br />
<br />
= Fragging a single flight =<br />
<br />
The (relatively speaking) most simple process for getting a single flight going is this:<br />
<br />
# Right click on the map in the general area you want your flight to be and select Add Package.<br/>[[File:Fraggin-add-package.png|200px|frameless|alt=Adding a package.]]<br />
# In the Add Package Window, click the Lock icon next to the Takeoff time.<br />
# Increase the takeoff time by 1-2 hours from the current time.<br />
# Click New<br/>[[File:Fraggin-time-package.png|400px|frameless|alt=Adding a package.]]<br />
# In the Add Flight window in the Aircraft dropdown, select the airframe you wish to use (e.g. F-16CM Block 40)<br />
# In the Role dropdown, select Training (see [[Tasking]] for more details on what each of these options mean)<br />
# In the Size dropdown, select 1<br />
# In the Squadron dropdown, select one of our squadrons, preferably one that is custom-added to be used by players (e.g. 420th Blazers, 421st Bogarts, etc.)<br />
# Click OK<br/>[[File:Fraggin-add-flight.png|400px|frameless|alt=Adding a flight.]]<br />
# Click the ATO button on the bottom bar (if you do not see this, click Mission Schedule on the top bar)<br />
# Expand Other<br />
# Expand Training Packages until you find the one you created from our squadron<br />
# Right click the Flight and click Join (note the Package Number, in this case 3230)<br/>[[File:Fraggin-ato-select.png|400px|frameless|alt=Selecting a flight via ATO.]]<br />
# Select Package 3230 from the FS Frag Order window on the left side of the screen<br />
# Click the blue aircraft to select the plane slot<br/>[[File:Fraggin-frago.png|200px|frameless|alt=Selecting a flight from the frag order.]]<br />
# Click the Flight Plan button on the bottom bar<br />
# Modify the TOS time to be ~20 minutes from the current time for Ramp start (see top right corner) or ~5 minutes for Taxi start<br />
#* Start by increasing setting TOS minutes to current minutes +30<br />
#* Decrease TOS hours to equal current hours<br />
#* Decrease TOS minutes one at a time until T-20 or T-5<br />
# Click the Red X to exit the Flight Plan<br/>[[File:Fraggin-flightplan.png|400px|frameless|alt=Retiming the flightplan.]]<br />
# Click Takeoff in the bottom right corner<br />
# Select Ramp or Taxi, and wait until you have loaded into the jet<br/>[[File:Fraggin-takeoff.png|500px|frameless|alt=Taking off.]]<br />
<br />
== The timing issue ==<br />
<br />
While in a local game, the simulation speeds up to quickly get you in the cockpit if your flight is not taking off for a while, multiplayer games generally have to keep the Server &ldquo;player&rdquo; in the 3D view to maintain stability. In addition, on an active server, there may be other players flying around and making a mess. In this state, the game cannot automatically accelerate time so any waiting time has to be ''actually waited out'', in real-time.<br />
<br />
This is why it is important to time the take-off correctly and to be mindful of whether you want to do a ramp start or a taxi start. If you time it wrong, you will end up having to wait 15 real-time minutes before your taxi start goes active, or you will miss your ramp start because the AI has already got the plane going and has started to taxi.<br />
<br />
= Video tutorials =<br />
<br />
<youtube>https://www.youtube.com/watch?v=7J4YdL8t8Mc</youtube><br />
<youtube>https://www.youtube.com/watch?v=QhcjkZdspKM</youtube><br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Talk:Fragging_a_package&diff=5660Talk:Fragging a package2023-01-13T14:35:35Z<p>Tippis: Created page with "A quick list of the mission types and their success factors ; AI : Air Interdiction missions to prevent reinforcements reaching the front line. There is no specific target assigned between the two target steerpoints and your flight is free to hunt down reinforcement and logistics units (actually any unit will do). To ensure success you must destroy as many targets as possible. ; AMBUSHCAP : Same as CAP but you are hiding from the OPFOR, usually behind a mountain at..."</p>
<hr />
<div>A quick list of the mission types and their success factors <br />
<br />
; AI : Air Interdiction missions to prevent reinforcements reaching the front line. There is no specific target assigned between the two target steerpoints and your flight is free to hunt down reinforcement and logistics units (actually any unit will do). To ensure success you must destroy as many targets as possible.<br />
; AMBUSHCAP : Same as CAP but you are hiding from the OPFOR, usually behind a mountain at low altitude.<br />
; BARCAP : Barrier CAP. A standard CAP (combat air patrol) where your flights will protect a geographical area from enemy aircraft. Arrive on time at the first CAP point and stay in the CAP for the assigned patrol time for mission success (usually 30 minutes but that depends on the flight plan). If you have to leave early for whatever reason you must request relief from the AWACS. Try not to fly too far from your CAP point and set a commit criterion of 25 Nm. The difference between CAP and DCA is that CAP is not tied to specific assets so it is easier to get success with survival and CAP time, even if you did not shoot any OPFOR aircraft down.<br />
; BDA : Bomb Damage Assessment. Same as reconnaissance but post-strike to evaluate the strike effectiveness. Mission success conditions are the same as for recon flights.<br />
; CAP : Same as BARCAP.<br />
; CAS : Same as Pre-Planned CAS.<br />
; DCA : Defensive Counter Air. DCA missions are meant to protect friendly assets in a particular area. DCA flight plans have two CAP points and a patrol time. To ensure success you must stay on station and prevent friendly assets in and around your AOR (Area of Responsibility) from being attacked by OPFOR. The main problem with DCA is knowing which asset to defend with a war going on around you.<br />
; DEAD : Destruction of Enemy Air Defences. As the title implies you must destroy as many specific radars and/or launchers as possible at the target steerpoints. That is the old SEAD STRIKE tasking from 4.32.<br />
; DEEP STRIKE : Same as STRIKE but deep behind enemy lines. Success conditions are the same as Strike.<br />
; ESCORT : Your flight must protect a package from OPFOR aircraft. You will meet with your target package and fly with them (usually in front of them to ensure they are not attacked by enemy aircraft). The trick with Escort is to find a good compromise between commit criteria and staying with the package. Enemy forces will try to drag you away from your target, so other enemy flights can destroy them while you are not there to protect them. For mission success the target package must not sustain any loss.<br />
; FAC(A) : Forward Air Controller (Aircraft) mission. Although the F-16 is not the best platform for FAC duties it is quite possible to direct strike flights in MP with the TGP and Laser Spot Tracker capabilities. You can now even illuminate and guide other flights’ LGB weapons. When tasked with FAC duties you must assist in the destruction of as many enemy ground units as possible around the 2 target steerpoints. This tasking is best flown in MP.<br />
; HAVCAP : High Value CAP. Same as CAP but mission success is tied to the survival of the high value asset you are tasked to protect. CAP patrol time is usually longer with HAVCAP (defaults to 1 hour).<br />
; INTERCEPT : This Air to Air flight has a very specific target that must be intercepted and destroyed around the target steerpoint. Mission success is tied to the failure of the intercepted aircraft mission. An abort by them is considered as success for you. This mission can unfortunately fail if another unit downed your target before you could.<br />
; OCA STRIKE : Offensive Counter Air Strike missions are targeted specifically against airbases or search radars. The purpose of OCA strikes is to help gain aerial supremacy by destroying assets on the ground. Mission success is tied to target damage of at least 30% (target must be under 70% operational status after the strike).<br />
; ON CALL CAS : On Call Close Air Support. You are tasked to patrol an area (respect the patrol time) and standby for specific targets that will be transmitted to you by friendly assets (usually a FAC). The way the AI transmit target coordinates is tricky to follow and this type of mission is best flown in MP with a human FAC(A). To ensure success you must destroy as many targets as possible.<br />
; PATROL : Same as RECCE Patrol but the task is to photograph naval units. See above for details.<br />
; PRE-PLAN CAS : Close Air Support mission against known ground units. The FAC is not needed. Destroy as many vehicles in the target battalion as possible to ensure mission success. Please note the flight plan will place two target steerpoints. The target is supposedly around these two steerpoints, usually moving on roads. Mission can unfortunately fail if your target was destroyed by other units.<br />
; RECCE : Reconnaissance. Usually pre-strike recon mission against a specific target. Your aircraft will be loaded with the LOW ALT camera and you must photograph the target. Mission will be rated as success if you fly closer than 2 Nm (slant range) from target. Please note anything higher than 12000 feet is more than 2 Nm slant range. Fly low level at the target.<br />
; RECCE PATROL : Same as Recce but with two target steerpoints. Mission is aimed to search for enemy ground vehicles in the assigned area. You must photograph the target with the LOW ALT camera. See RECCE for details. Mainly used for choppers (which are not flyable by humans).<br />
; SEAD : Suppression of Enemy Air Defences. This time you do not have to destroy specific ADA, but usually protect a strike package from enemy air defences. It is the old SEAD ESCORT tasking. Mission success is tied to the strike package sustaining no losses.<br />
; STRIKE : Genuine Air to Ground strike mission against a variety of specific targets. Decrease operational status of the assigned target by 30% at least to ensure success (target must be under 70% operational status after the strike).<br />
; SWEEP : Aggressive Air to Air flight that has no patrol time but 3 target steerpoints where you will attack and destroy as many OPFOR aircraft as possible without friendly losses in your flight. You must shoot down at least one enemy and survive for success.<br />
; TARCAP : Target CAP. Same as CAP but you are protecting a specific target area (usually while other aircraft strike it). You must ensure the strikers survive their attack.<br />
; TASMO : Tactical Air Support for Maritime Operations. Damage as many naval targets as possible at the attack steerpoint.<br />
; TRAINING : is a Training flight without specific objectives. Just bring the jet back for mission success.</div>Tippishttps://www.airgoons.com/wiki/index.php?title=BMS_Configuration&diff=5659BMS Configuration2023-01-07T00:07:31Z<p>Tippis: </p>
<hr />
<div>= Plentiful Preference Parameters =<br />
<br />
<br />
= Launcher =<br />
<br />
[[File:Bms-launcher.png|256px|frameless|right|alt=BMS Launcher]]<br />
<br />
[[File:Bms-launcher-highlight.png|322px|frameless|alt=Version selector in the BMS Launcher]]<br />
<br />
<br />
= Config program =<br />
<br />
[[File:Bms-config.png|256px|frameless|right|alt=BMS Launcher]]<br />
<br />
[[File:Bms-config-highlight.png|524px|frameless|alt=Selecting the right executable in the BMS configurator]]<br />
<br />
= In-game =<br />
<br />
<br />
= Config files and manual editing =<br />
<br />
== The three layers of config files ==<br />
<br />
== Backwards compatibility ==<br />
<br />
= VR Configuration =<br />
<br />
[[File:Bms-vr-config.png|256px|frameless|right|alt=BMS config VR settings]]<br />
<br />
[[File:Bms-vr-launcher.png|256px|frameless|right|alt=BMS launcher VR settings]]<br />
<br />
= Further reading =<br />
<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-user-manual.pdf BMS user manual] for the most immediately available configuration options and a description of the launcher.<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-technical-manual.pdf BMS technical manual] for a full listing of all configuration options and parameters, including configuration of support applications like IVC, RTTR, server hosting and modding programs.<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=File:Bms-vr-launcher.png&diff=5658File:Bms-vr-launcher.png2023-01-07T00:07:26Z<p>Tippis: </p>
<hr />
<div></div>Tippishttps://www.airgoons.com/wiki/index.php?title=File:Bms-vr-config.png&diff=5657File:Bms-vr-config.png2023-01-07T00:07:15Z<p>Tippis: </p>
<hr />
<div></div>Tippishttps://www.airgoons.com/wiki/index.php?title=Chuck%27s_Guides&diff=5656Chuck's Guides2023-01-06T15:45:08Z<p>Tippis: </p>
<hr />
<div>This is a backup repository of Chuck's Guides to [[DCS Modules|DCS aircraft modules]].<br />
<br />
* [https://www.airgoons.com/guides/DCS%20A-10C%20Warthog%20Guide.pdf DCS A-10C Warthog Guide]<br />
* [https://www.airgoons.com/guides/DCS%20AH-64D%20Guide.pdf DCS AH-64D Guide]<br />
* [https://www.airgoons.com/guides/DCS%20AJS-37%20Viggen%20Guide.pdf DCS AJS-37 Viggen Guide]<br />
* [https://www.airgoons.com/guides/DCS%20AV-8B%20Harrier%20Guide.pdf DCS AV-8B Harrier Guide]<br />
* [https://www.airgoons.com/guides/DCS%20Bf.109K-4%20Guide.pdf DCS Bf.109K-4 Guide]<br />
* [https://www.airgoons.com/guides/DCS%20C-101CC%20Guide.pdf DCS C-101CC Guide]<br />
* [https://www.airgoons.com/guides/DCS%20DH98%20Mosquito%20FB%20Mk%20VI%20Guide.pdf DCS DH98 Mosquito FB Mk VI Guide]<br />
* [https://www.airgoons.com/guides/DCS%20F-14B%20Tomcat%20Guide.pdf DCS F-14B Tomcat Guide]<br />
* [https://www.airgoons.com/guides/DCS%20F-16C%20Viper%20Guide.pdf DCS F-16C Viper Guide]<br />
* [https://www.airgoons.com/guides/DCS%20F-5E%20Tiger%20II%20Guide.pdf DCS F-5E Tiger II Guide]<br />
* [https://www.airgoons.com/guides/DCS%20F-86F%20Sabre%20Guide.pdf DCS F-86F Sabre Guide]<br />
* [https://www.airgoons.com/guides/DCS%20FA-18C%20Hornet%20Guide.pdf DCS FA-18C Hornet Guide]<br />
* [https://www.airgoons.com/guides/DCS%20FW-190A-8%20Guide.pdf DCS FW-190A-8 Guide]<br />
* [https://www.airgoons.com/guides/DCS%20FW-190D-9%20Guide.pdf DCS FW-190D-9 Guide]<br />
* [https://www.airgoons.com/guides/DCS%20Hawk%20T.1A%20Guide.pdf DCS Hawk T.1A Guide]<br />
* [https://www.airgoons.com/guides/DCS%20I-16%20Ishak%20Guide.pdf DCS I-16 Ishak Guide]<br />
* [https://www.airgoons.com/guides/DCS%20JF-17%20Thunder%20Guide.pdf DCS JF-17 Thunder Guide]<br />
* [https://www.airgoons.com/guides/DCS%20Ka-50%20Guide.pdf DCS Ka-50 Guide]<br />
* [https://www.airgoons.com/guides/DCS%20L-39ZA%20Albatros%20Guide.pdf DCS L-39ZA Albatros Guide]<br />
* [https://www.airgoons.com/guides/DCS%20Mi-24P%20Hind%20Guide.pdf DCS Mi-24P Hind Guide]<br />
* [https://www.airgoons.com/guides/DCS%20Mi-8MTV2%20Guide.pdf DCS Mi-8MTV2 Guide]<br />
* [https://www.airgoons.com/guides/DCS%20MiG-15bis%20Guide.pdf DCS MiG-15bis Guide]<br />
* [https://www.airgoons.com/guides/DCS%20MiG-19P%20Guide.pdf DCS MiG-19P Guide]<br />
* [https://www.airgoons.com/guides/DCS%20MiG-21bis%20Guide.pdf DCS MiG-21bis Guide]<br />
* [https://www.airgoons.com/guides/DCS%20Mirage%202000C%20Guide.pdf DCS Mirage 2000C Guide]<br />
* [https://www.airgoons.com/guides/DCS%20P-47D%20Thunderbolt%20Guide.pdf DCS P-47D Thunderbolt Guide]<br />
* [https://www.airgoons.com/guides/DCS%20P-51D%20Mustang%20Guide.pdf DCS P-51D Mustang Guide]<br />
* [https://www.airgoons.com/guides/DCS%20SA-342M%20Gazelle%20Guide.pdf DCS SA-342M Gazelle Guide]<br />
* [https://www.airgoons.com/guides/DCS%20Spitfire%20Mk%20IX%20Guide.pdf DCS Spitfire Mk IX Guide]<br />
* [https://www.airgoons.com/guides/DCS%20UH-1H%20Huey%20Guide.pdf DCS UH-1H Huey Guide]<br />
* [https://www.airgoons.com/guides/DCS%20Yak-52%20Guide.pdf DCS Yak-52 Guide]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Joining_a_BMS_server&diff=5655Joining a BMS server2023-01-03T23:58:27Z<p>Tippis: </p>
<hr />
<div>''Adapted from wonko's discord instructions.''<br />
<br />
[[Falcon Benchmark Simulator|BMS]] is at its heart Falcon 4.0, and Falcon 4.0 is an ''old'' game &mdash; its idea of getting a multiplayer game going is quite literally from an another era. As such, joining a multiplayer game has its own set of BMSism and quirks that can cause a seemingly straight-forward process to be slightly less than intuitive.<br />
<br />
= Connecting to the server =<br />
<br />
As a prerequisite to playing BMS online, you need to open up (and/or possibly forward in your router) the following port:<br />
* BMS needs UDP ports 2934 and 2935 to be opened/forwarded.<br />
* IVC needs UDP ports 9987, 9988, and 9989 to be opened/forwarded.<br />
<br />
The installer should have set the correct permissions in the Windows firewall as part of the install process, and any reasonably modern and user-friendly router will open the necessary ports automatically, so in most cases this requires no manual intervention even in cases when you want to join a server with non-standard ports.<br />
<br />
However, if you have a more restricted router setup, you may have to adjust these manually. The same goes if for whatever reason you want to run the game and IVC on non-standard ports &mdash; the process for this is described in the manuals, should it ever be needed.<br />
<br />
== The phonebook ==<br />
<br />
In keeping with its 20th century simulationist pretences, BMS does not have a &ldquo;server list&rdquo;. Instead, it has a &ldquo;phonebook&rdquo; to deal with your &ldquo;comms&rdquo; needs. To join a server you need to add and connect to it via that phonelist.<br />
<br />
[[File:Bms-phonebook.png|right|400px|frameless|alt=Adding a server to the BMS phonebook.]]<br />
<br />
In BMS, the process is this:<br />
<br />
# Click Multiplayer<br />
# Enter a server name, then the Server IP address and (optionally) Server Port number from the server information provided by the host (in the form xxx.xxx.xxx.xxx:nnnnn). If no port is provided by the server information, it is running on a standard configuration and a port number does not need to be provided.<br />
# Set Network Bandwidth. Most commonly, this is 2048 up and down.<br />
# Unless the server is ''not'' running IVC, which should be exceedingly rare, leave the two IVC buttons turned on. Enter IVC IP address and IVC Port number from the server information provided by the host (in the form xxx.xxx.xxx.xxx:nnnnn). If no port is provided by the server information, it is running on a standard configuration and a port number does not need to be provided. If the IVC server has a password, enter it here, otherwise the password field can be left blank.<br />
# Click Save.<br />
<br />
== Connecting ==<br />
<br />
[[File:Bms-connecting.png|right|400px|frameless|alt=Connecting to a BMS server.]]<br />
<br />
With the server saved in your phonebook, you can connect by:<br />
<br />
# Click Multiplayer<br />
# Select the Saved Server in the phonebook list.<br />
# Click Connect <br />
<br />
You should see this window if connection was successful, including to IVC, and you COMMS button at the top of the screen should be blinking to indicate that the chat window is active and has a new message in it:<br />
<br />
[[File:Bms-connected.png|300px|frameless|alt=A successful server connection.]]<br />
<br />
== Troubleshooting ==<br />
<br />
f you see this message, check IVC IP, port, and password then retry (may require closing BMS and the IVC client, then restarting BMS). You may also have set your bandwidth too low for the connection to work reliably. Again, make sure you have both up- and download set to at least 2048 kb/s (and of course, that you have that much bandwidth available).<br />
<br />
[[File:Bms-failed-connection.png|300px|frameless|alt=IVC server error.]]<br />
<br />
= Joining the campaign =<br />
<br />
Joining an online campaign works much like joining one locally, except that instead of loading a save file, you pick an online campaign from a separate tab.<br />
<br />
[[File:Bms-join-campaign.png|right|400px|frameless|alt=Joining an online campaign and squadron.]]<br />
<br />
# Click Campaign.<br />
# Click Online.<br />
# Click the campaign name, commonly called &ldquo;[Host]'s Game&rdquo; or something similar.<br />
# Click the relevant squadron in the list. Commonly, well set-up campaigns have custom squadrons with easy names to find and indicate which you should use as a starting point, such as &ldquo;PLAYERS JOIN HERE&rdquo;.<br />
# Click Commit Online<br />
# In the Rules of Engagement window, click OK<br />
<br />
If your connection to the campaign was successful, you should see the Campaign UI:<br />
<br />
[[File:Bms-campaign-ui.png|300px|frameless|alt=The campaign UI once successfully connected and loaded.]]<br />
<br />
From here, you are ready to join a package or [[Fragging a package|creating your own]] to get flying.<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=BMS_Configuration&diff=5654BMS Configuration2023-01-03T22:54:15Z<p>Tippis: </p>
<hr />
<div>= Plentiful Preference Parameters =<br />
<br />
<br />
= Launcher =<br />
<br />
[[File:Bms-launcher.png|256px|frameless|right|alt=BMS Launcher]]<br />
<br />
[[File:Bms-launcher-highlight.png|322px|frameless|alt=Version selector in the BMS Launcher]]<br />
<br />
<br />
= Config program =<br />
<br />
[[File:Bms-config.png|256px|frameless|right|alt=BMS Launcher]]<br />
<br />
[[File:Bms-config-highlight.png|524px|frameless|alt=Selecting the right executable in the BMS configurator]]<br />
<br />
= In-game =<br />
<br />
<br />
= Config files and manual editing =<br />
<br />
== The three layers of config files ==<br />
<br />
== Backwards compatibility ==<br />
<br />
= VR Configuration =<br />
<br />
<br />
<br />
= Further reading =<br />
<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-user-manual.pdf BMS user manual] for the most immediately available configuration options and a description of the launcher.<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-technical-manual.pdf BMS technical manual] for a full listing of all configuration options and parameters, including configuration of support applications like IVC, RTTR, server hosting and modding programs.<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=File:Bms-config-highlight.png&diff=5653File:Bms-config-highlight.png2023-01-03T22:53:57Z<p>Tippis: </p>
<hr />
<div></div>Tippishttps://www.airgoons.com/wiki/index.php?title=File:Bms-launcher-highlight.png&diff=5652File:Bms-launcher-highlight.png2023-01-03T22:53:46Z<p>Tippis: </p>
<hr />
<div></div>Tippishttps://www.airgoons.com/wiki/index.php?title=File:Bms-config.png&diff=5651File:Bms-config.png2023-01-03T22:47:25Z<p>Tippis: </p>
<hr />
<div></div>Tippishttps://www.airgoons.com/wiki/index.php?title=BMS_Configuration&diff=5650BMS Configuration2023-01-03T22:40:33Z<p>Tippis: </p>
<hr />
<div>= Plentiful Preference Parameters =<br />
<br />
<br />
= Launcher =<br />
<br />
<br />
= Config program =<br />
<br />
<br />
= In-game =<br />
<br />
<br />
= Config files and manual editing =<br />
<br />
== The three layers of config files ==<br />
<br />
== Backwards compatibility ==<br />
<br />
= VR Configuration =<br />
<br />
<br />
<br />
= Further reading =<br />
<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-user-manual.pdf BMS user manual] for the most immediately available configuration options and a description of the launcher.<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-technical-manual.pdf BMS technical manual] for a full listing of all configuration options and parameters, including configuration of support applications like IVC, RTTR, server hosting and modding programs.<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=BMS_Configuration&diff=5649BMS Configuration2023-01-03T22:40:20Z<p>Tippis: </p>
<hr />
<div>= Plentiful Preference Parameters =<br />
<br />
<br />
= Launcher =<br />
<br />
<br />
= Config program =<br />
<br />
<br />
= In-game =<br />
<br />
<br />
= Config files and manual editing =<br />
<br />
== The three layers of config files ==<br />
<br />
== Backwards compatibility ==<br />
<br />
= VR Configuration =<br />
<br />
<br />
<br />
= Further reading =<br />
<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-user-manual.pdf BMS user manual] for the most immediately available configuration options and a description of the launcher.<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-technical-manual.pdf BMS technical manual] for a full listing of all configuration options and parameters, including configuration of support applications like IVC, RTTR, server hosting and modding programs.<br />
<br />
[Category:BMS Articles]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=BMS_Configuration&diff=5648BMS Configuration2023-01-03T22:40:02Z<p>Tippis: Created page with "= Plentiful Preference Parameters = = Launcher = = Config program = = In-game = = Config files and manual editing = == The three layers of config files == == Backwards compatibility == = VR Configuration = = Further reading = [https://wiki.falcon-bms.com/manuals/4_37/bms-user-manual.pdf BMS user manual] for the most immediately available configuration options and a description of the launcher. [https://wiki.falcon-bms.com/manuals/4_37/bms-technical-manual...."</p>
<hr />
<div>= Plentiful Preference Parameters =<br />
<br />
<br />
= Launcher =<br />
<br />
<br />
= Config program =<br />
<br />
<br />
= In-game =<br />
<br />
<br />
= Config files and manual editing =<br />
<br />
== The three layers of config files ==<br />
<br />
== Backwards compatibility ==<br />
<br />
= VR Configuration =<br />
<br />
<br />
<br />
= Further reading =<br />
<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-user-manual.pdf BMS user manual] for the most immediately available configuration options and a description of the launcher.<br />
[https://wiki.falcon-bms.com/manuals/4_37/bms-technical-manual.pdf BMS technical manual] for a full listing of all configuration options and parameters, including configuration of support applications like IVC, RTTR, server hosting and modding programs.</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Getting_and_installing_BMS&diff=5647Getting and installing BMS2023-01-03T22:24:52Z<p>Tippis: </p>
<hr />
<div>In the olden days, getting and installing [[Falcon Benchmark Simulator|BMS]] could be a bit of a chore, but at least it was (sort of) free because Falcon 4.0 was largely abandonware and while the installer required you to point to a valid Falcon4.exe file, that file could be &ldquo;found&rdquo; trivially on the internet. The bigger obstacle was a very long and obnoxious registration and log-in requirement to download a multipart sequence of builds and updates from a slow website.<br />
<br />
These days, it costs a trivial amount to get your hands on a legal copy of Falcon 4.0, which you sort of need because the ownership checking is a bit more thorough. But on the other hand, no registration or login is needed (in spite of the official instructions saying so, but they are written for an older version anyway) and between direct download and torrent options, and having a sensible and working updater, the download process is much more palatable.<br />
<br />
To get the instruction from the source, go to the [https://wiki.falcon-bms.com/start-with-falcon-bms/install-update Falcon BMS install/update help page], or directly to the [https://www.falcon-bms.com/downloads/ downloads page], which link to further documentation.<br />
<br />
= Requirements =<br />
<br />
The official requirements are listed as:<br />
* Windows 7 (64 bits)<br />
* i5 2500K 3.3 GHz<br />
* 4Gb RAM<br />
* 3D GFX card 2Gb dedicated VRAM (DX11 compatible mandatory)<br />
* 15Gb HDD space required<br />
<br />
What is ''not'' listed, but requires a special mention in spite of sounding like a trivial detail, is a sound card. It is worth mentioning because even if you intend to install BMS for the purpose of running an online multiplayer server, you ''still'' need that sound card as well as a DX11-compaible graphics card. If you intend to run the server in a virtualised environment, the virtualisation needs to cover those media capabilities as well.<br />
<br />
== Falcon 4.0 ==<br />
<br />
To install [[Falcon Benchmark Simulator|BMS]], you ned to have Falcon 4.0 installed. While you can technically get rid of Falcon 4 once BMS is installed, that adds an unnecessary step to future repairs and re-installs, so the (relatively) piddling size of this late-'90s game might as well be considered part of the BMS installation footprint.<br />
<br />
You can most readily get Falcon 4 from [https://www.gog.com/game/falcon_collection GOG.com] (along with Falcon, Falcon A.T. and Falcon 3.0 + a couple of expansions), or from [https://store.steampowered.com/app/429530/Falcon_40/ Steam]. Steam also offers the same package as GOG for a extra cents.<br />
<br />
= Download &amp; install =<br />
<br />
Go to [https://www.falcon-bms.com/downloads/ the official BMS download page] and get either the downloader tool and run it, or get the full installer via torrent. Either way, you end up with the full installer .exe file in a location of your liking &mdash; just run it and follow the instructions.<br />
<br />
== What you get ==<br />
<br />
BMS nature as a community and fan project with a bias towards the more ''involved'' side of flight simming reveals itself immediately when looking at what gets installed by default as part of the download package. In older versions, the collage of special tools and utilities and optional capabilities made for a bit of a mess, but at the same time, an additional fan tool in the form of the &ldquo;alternate BMS launcher&rdquo; was available to guide the user through that jungle.<br />
<br />
In later versions, the launcher is no longer alternate and is instead a default part of the install, and should be the main interface for the regular user as far as getting to the many different components of the game.<br />
<br />
=== BMS Launcher ===<br />
<br />
[[File:Bms-launcher.png|512px|frameless|alt=The BMS launcher.]]<br />
<br />
[[File:BMS updater icon.png|32px|left|frameless]]<br />
The launcher offers immediate access to the most common tools one might want to use in connection to BMS: the game update tool, the base configuration tool, the acronym salad of IVC, RTTR, AVC, and the most popular third-party tools.<br />
<br />
[[File:BMS config icon.png|32px|left|frameless]]<br />
The launcher also provides a means to set up all the controls and key- and button binds you might need via a modern and highly capable interface. This bypasses the arcane, antiquated, and utterly byzantine input definition system that BMS uses to define its inputs. While the in-game settings screen ostensibly offers a page for button and axis binding, this is a left-over from Falcon 4.0 and '''should not be used''' &mdash; odds are that using it will break things rather than provide any workable binding.<br />
<br />
''Always use the launcher to set and adjust your binds''. This means you have to quit and restart BMS every time you want to make a control setup adjustment, but better that than to run the risk of breaking the bind files by using the in-game bind mechanic.<br />
<br />
For further information, check the [[BMS Configuration]] article.<br />
<br />
=== IVC ===<br />
<br />
[[File:IVC client icon.png|32px|left|frameless]]<br />
[[File:IVC server icon.png|left|32px|frameless]]<br />
IVC, or the &ldquo;Internal Voice Communications&rdquo; tool is the voice communication system for BMS. It is essentially a bespoke TeamSpeak 3 implementation that interfaces with the in-game radios to let players use the in-cockpit radio communication systems (and their related HOTAS controls) to speak to each other.<br />
<br />
IVC consists of a client and a server component. Unless you intend to host a BMS server, the server component can be ignored completely. The client generally auto-launches and auto-connects if a server has IVC set up, but it can also be launched manually if you want to set up the audio devices it should use.<br />
<br />
=== RTT Remote ===<br />
<br />
[[File:RTTR client icon.png|32px|left|frameless]]<br />
[[File:RTTR server icon.png|32px|left|frameless]]<br />
RTT Remote &mdash; the original meaning of which is lost in mists of time &mdash; is an instrument extraction tool for BMS. Beyond the more trivial case of making things like MFDs show up on a separate screen, it also allows for complex setups for pit builders, where a different computer can host the display and feed inputs back from, say, a touch screen over a network connection.<br />
<br />
=== Avionics Configurator ===<br />
<br />
[[File:AVC icon.png|32px|left|frameless]]<br />
For anyone who has been frustrated with Eagle Dynamics' philosophy of &ldquo;our SMEs tell us that plane X never flew with Y fitted&rdquo; the Avionics Configurator is the tool that lets you adjust how the different aircraft in BMS are equipped. This allows enterprising game modders to create all kinds of subvariants or frankenplane versions of the already extensive library of F-16s (and other airframes) on offer in the game.<br />
<br />
Its use is more for single-player setups, since this kind of alteration of the core data files can cause a fair amount of conflicts with how planes work and behave in multiplayer unless the same set of alterations are distributed and used by all players.<br />
<br />
=== Editor ===<br />
<br />
[[File:Editor icon.png|32px|fleft|frameless]]<br />
Much like how the Avionics Configurator lets you alter aircraft data, the nondescript &ldquo;Editor&rdquo; lets you modify weapons and vehicle data beyond just the avionics of aircraft. Also much like the AC, this kind of editing is more for setting up or tweaking local single-player games, as mismatches can cause conflicts in multiplayer.<br />
<br />
=== Documentation ===<br />
<br />
With all the different components included in the instal, and with the core conceit of the game being a ''thorough'' simulation of a multitude of F-16 variants in a complex combat environment, it should come as no surprise that BMS comes with an extensive set of documentation and manuals.<br />
<br />
The main documents can be found online on the [https://wiki.falcon-bms.com/manuals BMS manuals] page of the man website, and includes almost 1,400 pages covering how the different bits of software work on top of the functionality of the F-16 avionics and weapon systems. On top of this, another 400 pages describe the many training missions included in the game and the different threats you will encounter.<br />
<br />
Beyond what is available on the website, the actual game install also includes technical documentation on how to connect all kinds of input (and output) devices for cockpit building, on modding and module- and theatre development, printable checklists, as well as maps and navigation aids for the built-in Koraean theatre. There are also visual quick guides to the other flyable planes in the game: the A-10, AV-8B, F-4, F-15, F/A-18, JA-37, MiG-29, Mirage 2000, and Tornado. In total, the documentation directory for BMS takes up more disk space than the entire install of the original Falcon 4.0&hellip;<br />
<br />
== Additional downloads ==<br />
<br />
A second row of program icons on the launcher will at first cause a file browser show when clicked. The purpose of this browser window is to tell the launcher where you have installed some of the more popular add-on tools for BMS, each of which needs to be downloaded separately. Three of these &mdash; Weapon Delivery Planner, Mission Commander, and Weather Commander &mdash; can be found downloaded from the developer's website: [https://www.weapondeliveryplanner.nl/download/index.html weaponsdeliveryplanner.nl]. The other two are found via their respective threads on the official BMS forum.<br />
<br />
=== Weapons Delivery Planner ===<br />
<br />
[[File:WDP icon.png|32px|left|frameless]]<br />
[https://www.weapondeliveryplanner.nl/about/index.html Weapon Delivery Planner] is a utility that imports flight- and package data from a save game file and uses it to create kneeboard, data cassette (DTC) settings, and various weapon and, as the name suggests, weapon delivery settings such as laser codes for laser-guided bombs.<br />
<br />
The DTC is the system in the F-16 that lets you set up just about any parameter for programmable systems on the aircraft: threats, target points, and polygons for the navigation system; release programs for the countermeasure system; radio settings etc. Most of this can be adjusted from inside the game, but the interface for it is old and clunky. WDP gives you easier access to all of those settings, at the cost of requiring you to save the game so WDP has a source to import data from.<br />
<br />
WDP ''can'' be used in multiplayer as well, again by simply creating a save from the current game state and importing it in the utility, but since multiplayer games tend to be running in real time, this process requires a bit more forethought and planning so you don't miss the take-off time while you are fiddling with all the settings.<br />
<br />
=== Mission Commander ===<br />
<br />
[[File:MC icon.png|32px|left|frameless]]<br />
[https://www.weapondeliveryplanner.nl/about/mc.html Mission Commander] is a utility for mission and campaign makers and server operators. If all you ever do is play ready-made missions or participate as a client in online campaigns, this tool offers little of any use.<br />
<br />
It imports and exports savegame data to let the user change everything from individual flights to entire campaign setups. Commonly, it is used to customise campaigns for multiplayer use, to create custom squadrons that the online players can use. This gives players access to specific variants (or weapon systems) that may otherwise be in short supply in the base campaign, or just not available at all, and allows for setups where players do not compete with the AI for tasking or flying specific packages.<br />
<br />
=== Weather Commander ===<br />
<br />
[[File:WC icon.png|32px|left|frameless]]<br />
[https://www.weapondeliveryplanner.nl/about/wc.html Weather Commander] is even more of a mission-maker's tool than Mission Commander. It lets the mission-maker create weather files for a mission or for an entire campaign though a very easy-to-use system of literally painting temperatures, clouds, and pressure zones onto the map.<br />
<br />
On its own, it is entirely capable but also takes a fair bit of effort to create even a single map of interesting weather. Fortunately, its can be used in conjunction with&hellip;<br />
<br />
=== F4Wx Real Weather ===<br />
<br />
[[File:F4Wx icon.png|32px|left|frameless]]<br />
[https://forum.falcon-bms.com/topic/8267/f4wx-real-weather-converter F4Wx (Falcon 4 Weather Converter] is a utility that imports real-world weather data and forecasts to create everything from a single weather map to several weeks worth of evolving weather for campaign use. What can require a lot of effort in Weather Commander is here done by just a few button clicks and waiting for a but of processing. The weather maps can then be further tweaked and refined in WC, if the real world happens to be boring this week.<br />
<br />
=== F4RADAR ===<br />
<br />
[[File:F4radar icon.png|32px|left|frameless]]<br />
[https://forum.falcon-bms.com/topic/18356/f4radar-lightweight-standalone-radar-application F4Radar] is a developing utility that ultimately aims to become something similar to [[LotATC_4_DCS|LotATC]]. For now, it is mostly a radar picture exporter of sorts but it still allows for some limited GCI usage.<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=HSD&diff=5646HSD2023-01-03T18:50:12Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
==Horizontal Situation Display==<br />
<br />
<br />
The Horizontal Situation Display (HSD) is one of the most important pages available on your MFD. It is a moving-map display of the current horizontal situation around you, showing friendly and enemy aircraft, the route you are flying, the area being scanned by your radar, and many other useful pieces of information. The HSD is used to maintain situational awareness of your present location and of what is happening around you. <br />
<br />
You can imagine the HSD as what you would see if you were directly above your aircraft, looking straight down. There are three range rings, each representing one third of the currently selected display range (so for example, if you have selected 15 miles, each ring is another increment of 5 miles. If you have selected 60 miles, each ring is another increment of 20 miles). Your aircraft is in the center of these range rings, and the map is oriented so that your aircraft's heading is straight up. Each range ring has four spokes, representing north, east, west, and south. The north spoke on the innermost range ring is replaced with a solid white triangle, to show you what your heading is.<br />
<br />
==DEP== <br />
There are two view positions that the HSD can use. In the default mode (DEP), your aircraft's position and the center of the range rings are depressed to about 1/3rd of the height of the screen. This gives you a better view of what is in front of the aircraft (since you are usually more interested in what's in front of you than what's behind you). In the second view mode (CEN), your aircraft is positioned in the center of the MFD, so that you can see the same distance in all directions. Pressing this OSB toggles between these two modes.<br />
==DCPL== <br />
Your HSD range can be either decoupled (DCPL) or coupled (CPL) to the FCR range. If coupled, the HSD will automatically scale so that it shows the same distance as the FCR, and if decoupled, you can manually select the range. Pressing this OSB toggles between these two modes.<br />
==NORM== <br />
Pressing this OSB toggles the current zoom level on the HSD. You can select NORM (normal view), EXP1 (area around your aircraft is expanded), and EXP2 (area around your aircraft is expanded even more).<br />
==CNTL== <br />
This opens the HSD control menu (see below).<br />
==FRZ== <br />
If this OSB is selected, the HSD will freeze in its current position, and will not turn with your aircraft or reposition itself to keep you centered. This is useful to give yourself a static view of a particular area. Remember to deselect this before you fly off the HSD!<br />
==DCLT==<br />
Pressing this OSB will declutter the display, removing some information to make the map easier to read.<br />
==Up/Down== <br />
These OSBs are displayed on the top two buttons on the left row. Pressing up will increase the range displayed on the HSD, and pressing down will decrease the range. If you cannot increase or decrease the range any more, the arrow symbol will disappear. These OSBs are only available if the range is decoupled from the FCR (see above).<br />
<br />
<br />
<br />
<br />
<br />
<br />
When you press the CNTL OSB on the main page, the OSB configuration changes to allow you to select which information you want displayed on the HSD. Each OSB can be toggled to turn the associated item on/off. <br />
<br />
<br />
==FCR== <br />
Toggles display of the radar scan area and the "ghost" cursor showing the position of your FCR cursor.<br />
==PRE== <br />
Toggles the display of enemy targets that were programmed into your aircraft's computer before takeoff.<br />
==AIFF== <br />
Toggles the display of IFF responses from other aircraft.<br />
==CNTL== <br />
Leaves the CNTL menu and returns you to the main page.<br />
==LINE 1 - 4== <br />
Toggles the display of map information lines on the HSD. Currently LINE 1 is the only line with any information - it shows the FLOT (forward line of troops).<br />
==RINGS== <br />
Toggles the display of range rings around your aircraft.<br />
==ADLNK== <br />
Toggles the display of threats uploaded to your computer from an air data link (such as an AWACS aircraft).<br />
==GDLNK== <br />
Toggles the display of threats uploaded to your computer from a ground data link.<br />
==NAV 1 - 3== <br />
These toggle the display of your navigational routes. Only NAV 1 has any information - it shows the flight path for your mission.<br />
<br />
[[Category:Guides]]<br />
[[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=FCR&diff=5645FCR2023-01-03T18:50:00Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
<strong>Fire-Control Radar. </strong><br />
<br />
This is the main page for interacting with your radar, and targeting planes.<br />
<br />
<br />
==Overview==<br />
<img src="https://i.imgur.com/8pJ3pxq.png?1/%22/%3E><br />
<br />
==Locking targets==<br />
<br />
Press TMS Up. Pickle. <br />
<br />
<br />
<br />
==TWS and RWS modes==<br />
<br />
<br />
{{#evu:https://www.youtube.com/watch?v=5SKI9_36AWg&feature=youtu.be}}<br />
<br />
blah blah blah<br />
<br />
<img src="https://i.imgur.com/xjm71cr.png><br />
<br />
[[Category:Guides]]<br />
[[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=MFD&diff=5644MFD2023-01-03T18:49:52Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
Multi-Function Displays. These are the main doohicky displays that show basic information about your plane, the outside world, and various sensors, such as radar. They have pages, and all these pages have sort of functionality and purpose. They are listed here.<br />
<br />
<br />
<br />
==MFD Pages==<br />
<br />
[[FCR]]<br />
<br />
[[HSD]]<br />
<br />
[[SMS]]<br />
<br />
[[TFR]]<br />
<br />
[[HAD]]<br />
<br />
[[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=HUD&diff=5643HUD2023-01-03T18:49:36Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
{{stub}}<br />
==Heads Up Display==<br />
<br />
<br />
It displays the most pertinent and crucial information such as altitude, speed, heading, bullseye, and basic targeting information. <br />
<br />
https://i.pinimg.com/originals/f6/f8/46/f6f846786cbcb302cd37dce5a2a3acea.jpg<br />
<br />
[[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=DED&diff=5642DED2023-01-03T18:49:23Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
==Data Entry Display==<br />
<br />
While [[ICP]] is used to interact, DED is used to display the information that you have interacted with, such as datalinks, waypoints, and time calculations.<br />
<br />
https://i.ytimg.com/vi/5KDrxVzVpbE/hqdefault.jpg<br />
<br />
[[Category:Guides]][[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=ICP&diff=5641ICP2023-01-03T18:49:13Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
<br />
'''Integrated Control Panel'''<br />
The Integrated Control Panel (ICP) is a set of buttons located prominently at the front of the cockpit, directly underneath the HUD. The ICP is used to control the Data Entry Display, and can also be used to set the master mode of the aircraft. <br />
<br />
<br />
If you are not using your HOTAS, you are most likely using this to interact with your plane. By default, most of its functions are on your numpad.<br />
<br />
<br />
Arrowkeys on your keypad are RTN - SEQ and UP and DOWN of the ICP Dopper. Also known as DCS Data Command Switch - 4 way hat switch below the 8 and 9 keys on the ICP. Described in the DED section.<br />
<br />
<br />
Your numpad + and - are the functions of the rocker on the lower left. Enter is enter, and numpad keys correspond to the functions ingame.<br />
<br />
<br />
<br />
<br />
HUD Brightness Knob - this is the knob marked SYM in the upper left corner of the ICP. It is used to control the brightness of the HUD - clicking on the knob increases the brightness, and right clicking on it decreases the brightness.<br />
<br />
A-A and A-G Buttons - these buttons are used to control the master mode of the aircraft. Pressing either button when the aircraft is in NAV mode will set the aircraft to the air-air or air-ground mode. You can press the button for the selected mode again to put the aircraft back into NAV mode.<br />
<br />
Drift C/O Switch - the pitch ladder on the HUD is usually aligned so that it is centered on the flight path marker. If the aircraft is in a situation where the nose of the aircraft is pointed in a significantly different direction than the actual flight path (for example, during a steep turn) the pitch ladder could be partially off the display or not visible at all. However, if this switch is set to DRIFT C/O, the pitch ladder will always be centered in the HUD, regardless of the position of the flight path. (C/O stands for "cutout" by the way).<br />
<br />
<br />
Other controls on the ICP used in conjunction with the Data Entry Display, are described on that page.<br />
<br />
<br />
<br />
<br />
http://falcon4.wikidot.com/local--files/avionics:icp/icp.jpg<br />
<br />
[[Category:Guides]]<br />
[[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Master_Mode&diff=5640Master Mode2023-01-03T18:48:50Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
"Master mode" is used in several different contexts in Falcon, but it most often refers to the master mode of the Fire Control Computer (FCC), which is sometimes referred to as the master mode of the airplane. There are three primary master modes - Air-to-Air, Air-to-Ground, and Navigation. The master mode is selected using the A-A and A-G buttons on the [[ICP]] - press the button for the mode you want to activate that mode, and press it again to get back to NAV mode.<br />
<br />
Each mode has its own [[HUD]] and [[MFD]] settings. For example, if you select the [[FCR]], [[TGP]], and TGR pages on your left MFD in NAV mode, when you switch to a combat mode after arriving at your destination you will find that those pages are no longer available (the FCC has reverted the MFD back to its default for the A-A mode). However, if you switch back to NAV mode, the MFD configuration you selected will still be there. For this reason, it is important to set up your MFDs in each master mode before arriving at your target.<br />
<br />
The master modes have the following effects on your avionics:<br />
<br />
==NAV== <br />
Selects the FCR in CRM-RWS mode on the left MFD and the HSD on the right MFD. No weapon is selected.<br />
<br />
==A-A== <br />
Selects the FCR in CRM-RWS mode on the left MFD and the SMS page on the right MFD. The first available air-to-air missile is selected, or guns if there are no missiles remaining.<br />
<br />
==A-G== <br />
Selects the FCR in ground map mode on the left MFD and the SMS page on the right MFD. The first available air-to-ground weapon is selected, or guns if there are no bombs or missiles remaining.<br />
<br />
[[Category:Guides]]<br />
[[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Angle_of_Attack&diff=5639Angle of Attack2023-01-03T18:48:34Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
<br />
http://code7700.com/images/airfoil_terminology_2.png<br />
<br />
Angle of attack (AOA) is an important concept in aerodynamics and aviation. It is one of the first concepts taught to all pilots, both civilian and military, since it plays a large role in most flight maneuvers and in keeping the aircraft under control.<br />
<br />
Angle of attack is defined as the angle between the chord line of the aircraft's wing and the relative wind(direction of the wind flow striking the leading edge of the wing). In non-technical terms, this basically means that it is the difference between the aircraft's pitch angle and the vertical angle that the aircraft is actually flying.<br />
<br />
<br />
<br />
==AOA and Lift==<br />
[[File:Lift curve.jpg|thumb|upright=1.5|A typical lift curve. In this case, the critical angle of attack is at around 16 degrees]]<br />
<br />
As angle of attack increases, the lift generated by the wing increases as well, up until a certain angle (called the critical angle of attack). After the critical AoA, lift rapidly decreases and drag increases as the airflow separates from the wing<br />
<br />
{{tip|In a stall, '''the wing is still producing lift''', just less lift}}<br />
<br />
To recover from the stall, simply reduce the AoA of the wing by releasing pressure on the stick.<br />
<br />
<br style="clear:both"><br />
==AOA and Drag==<br />
<br />
Drag is produced whenever the wing is generating lift (known as induced drag). This drag increases as the angle of attack is increased (since more lift is being generated).<br />
<br />
What this means for the average goon is that while AoA being high might not ruin all of your lift, it might still be a huge negative factor in your drag. If you need to regain airspeed quickly, you should unload the wing, decreasing AoA and thus drag.<br />
<br />
==Determining Your AOA in F-16==<br />
<br />
===AoA Gauge===<br />
Unlike many civilian aircraft, angle of attack is actually quite easy to determine in the F-16. There are multiple instruments which directly tell you your AoA, and several indirect indications as well. The angle of attack gauge (located underneath the analog altimeter and directly next to your left knee) tells you your angle of attack, in degrees. It also has color bands which correspond to the angle of attack indexer next to the HUD.<br />
<br />
https://i.imgur.com/UbishWI.jpg<br />
<br />
===Degrees vs Units===<br />
The AOA indicators on older aircraft do not display absolute angles of attack, but are arbitrary units grouped around the optimum with specific areas of interest. The Navy typically uses a 30 degree scale while the Air Force doesn't really have a pattern.<br />
<br />
[[Category:Guides]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Airspeed&diff=5638Airspeed2023-01-03T18:48:25Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
<br />
==Calibrated Airspeed (CAS)==<br />
Calibrated airspeed is the default airspeed type that is selected when you start your aircraft up. Calibrated airspeed is basically the actual airspeed being computed by the air data system (as shown on the analog airspeed indicator), corrected for errors introduced by the air data system. This is determined by a calibration done on a per-aircraft basis. Calibrated airspeeds are given in KIAS (knots indicated airspeed - IAS is the "uncalibrated" airspeed, but there is usually a small enough difference between IAS and CAS that they are interchangeable).<br />
<br />
==True Airspeed (TAS)==<br />
True airspeed is equivalent to CAS corrected for non-standard temperature and pressure. Your airspeed indicator is calibrated based on the standard pressure and temperature at sea level. If the actual pressure and temperature are different from this value (hint: they always are) your calibrated airspeed will be incorrect. This error is negligible at ground level, but as you start to climb, your CAS will begin to diverge more and more from your TAS (generally speaking, your CAS will become lower and lower relative to your TAS as the air density decreases). TAS is calculated from CAS using a simple calculation which takes into account the air's density. True airspeeds are given in KTAS (knots true airspeed).<br />
<br />
==Ground Speed (GS)==<br />
Your ground speed is equivalent to the speed your aircraft is actually travelling over the ground. If you are at 400 KTAS going straight up, your ground speed is 0. In addition, if you are at 400 KTAS but have a 100 knot headwind, your actual ground speed is 300 knots. This is generally computed using the aircraft's INS. Ground speeds are given in plain knots.<br />
<br />
==Mach Number==<br />
The Mach number is a ratio between your aircraft's speed and the speed of sound. It is extremely important to note that there is no one-to-one mapping between airspeed and Mach number - this is a common misconception. The actual speed of Mach 1 depends primarily on the outside air temperature. Mach 1 is approximately 660 knots at sea level on a standard day, but is much slower at high altitudes, especially when the temperature is cold. The Mach number is important because the aircraft's handling characteristics change somewhat when your airspeed is close to Mach 1 (~Mach .8*-1.2, the transonic region). You will notice some turbulence when flying at these speeds.<br />
<br />
==Airspeed Display==<br />
Your airspeed and Mach number are displayed on the Heads Up Display, as well as the analog airspeed indicator on the main instrument panel. You can select which type of airspeed is displayed on the HUD using this switch on the right console.<br />
<br />
[[Category:Guides]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Bullseye&diff=5637Bullseye2023-01-03T18:48:17Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
==Overview==<br />
"Bullseye" is a term used in military radio communication. The bullseye is a pre-defined point which is used as a reference for radio calls indicating a position. For example, if someone says they have a radar contact at "bullseye 050 at 30 miles", the radar contact is 30 miles away from the bullseye point at a heading of 050 (roughly northeast).<br />
<br />
Bullseye is used in case radio communications are intercepted by the enemy - since the bullseye point is agreed upon prior to the flight and is not stated over the radio, the enemy will not be able to determine where you are referring to if you use bullseye terminology. In addition, using bullseye coordinates helps improve situational awareness, since it is an absolute frame of reference. If AWACS tells another aircraft that they have enemy fighters at "7 o'clock, 15 miles", you have no idea where they are. However, saying that the fighters are at "bullseye 077 at 15 miles" tells you exactly where they are located.<br />
<br />
Use of bullseye in radio communications can be controlled in the game settings menu. If active, bullseye will be used, and if not, standard bearing/range will be used in radio communications. You can view the location of the bullseye point in the theater map by right clicking on the map and selecting "bullseye"<br />
<br />
<br />
<br />
<br />
==Symbology on F-16==<br />
The bullseye is displayed on both the [[FCR]] and [[HSD]] as a bullseye symbol. In addition, the navigation cue on the lower left hand side of each MFD page can be changed to a bullseye cue. To do this, press the LIST button on the ICP, then select MISC, and then BULL. Pressing the 0 key on this page will toggle between the bullseye cue and the regular course deviation cue.<br />
<br />
The bullseye cue displays three important pieces of information:<br />
<br />
The relative bearing to the bullseye is displayed by the triangle on the outside of the circle. If the triangle is at the top of the circle, your aircraft is pointed at the bullseye.<br />
Your aircraft's current bullseye position. In the picture below, the aircraft is at bullseye 211 at 5 miles.<br />
The bullseye position of your cursor. In the picture above, the cursor of the HSD, the lower right bullsey, is at bullseye 049 at 9 miles. This is useful for identifying places to go to, or look out for. The same place on lower left side is the FCRs current targeting cursor, shown on HSD. It is currently pointed at Bulls 347 for 17 miles. It is useful for identifying friendly and hostile aircraft (for example, if you have an unknown contact, you would say "ray gun bullseye 347 for 17 miles", and if it is a friendly target, they would reply "buddy spike" when they look at their own bullsey after hearing "raygun" call).<br />
<br />
https://i.ytimg.com/vi/6q4BtIYnBfg/maxresdefault.jpg<br />
<br />
[[Category:Guides]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Goonserver&diff=5636Goonserver2023-01-03T18:48:00Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
Our dedicated server.<br />
<br />
<br />
Currently we have none. However, here would be the required settings to connect, the up-to-date IP address and IVC address, and AISPY connection info. This information is placeholder from the now-dead goonserver.<br />
==General Information==<br />
<br />
<br />
BMS is no longer free, you must own and install a copy of Falcon 4.0 before BMS 4.33 U5 will install or run. This is checked each time BMS is started.<br />
<br />
KTO Interactive Map - Click on the airfield icons to get information (TACAN, tower freqs, ILS, etc): http://www.combatsimchecklist.net/MAPKOREA/<br />
<br />
<br />
Connection Details<br />
<br />
Server IP: 50.35.93.27<br />
<br />
Bandwidth: 2000<br />
<br />
64-bit Client<br />
<br />
Theater: Korea Strong DPRK<br />
<br />
IVC Enabled<br />
<br />
No Passwords<br />
<br />
==Connection Instructions==<br />
<br />
Verify the correct THEATER is selected<br />
<br />
Click COMMS<br />
<br />
Enter the Server IP into both of the red boxes<br />
<br />
Set Connection Bandwidth and enable IVC<br />
<br />
Click SAVE<br />
<br />
Click CONNECT<br />
<br />
http://i.imgur.com/d1SPzWW.png<br />
<br />
<br />
==Current Campaign==<br />
<br />
Korea Strong DPRK Theater - Rolling Fire Campaign<br />
<br />
Default AI prioritization. Added 4 ROK Air Defense Brigades to defend the goonbase (total of 8 Patriot, 8 HAWK, 4 AAA battalions). Battalions are spread around the areas of Chuncheon City (north), Hoengsong Airbase (Goonbase), Chungju Airbase (southwest), and Yangpyeong City (west).<br />
<br />
<br />
<br />
<br />
Player Squadrons<br />
<br />
Hoengsong Airbase<br />
<br />
F-16CM-52<br />
<br />
F-16CM-42<br />
<br />
F-15E-229 Strike Eagle<br />
<br />
F/A-18C Hornet<br />
<br />
F/A-18E Super Hornet<br />
<br />
Mirage 2000EGM<br />
<br />
JA-37<br />
<br />
<br />
[[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Flight_Basics&diff=5635Flight Basics2023-01-03T18:47:50Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
==Getting into a plane and loadout==<br />
<br />
{{#evu:https://www.youtube.com/watch?v=N7g6TKu-_EY}}<br />
<br />
==Taxi and takeoff==<br />
<br />
<br />
==Navigation==<br />
<br />
<br />
==Using weapons==<br />
<br />
==Landing==<br />
{{#evu:https://www.youtube.com/watch?v=iejpi6BhDYg&feature=youtu.be}}<br />
<br />
[[Category:BMS Guides]][[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Installing_BMS&diff=5634Installing BMS2023-01-03T18:46:57Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
Our goonguide to getting the game installed.<br />
<br />
<br />
==Current Version==<br />
It is 4.33 U5. <br />
<br />
You need a legal copy. Get it from Steam: https://store.steampowered.com/app/429530/Falcon_40/<br />
<br />
Or from GoG. <br />
<br />
<br />
Installers for the incremental updates. <br />
* U1: http://www.e-haf.org/PublicFTP/320/BMS_4.33/Falcon_BMS_4.33_U1_Setup.zip<br />
* U2: https://drive.google.com/open?id=1Ho2wlakVvEUd7YRnKxQ0IEr8CCqkkLky<br />
* U3: https://drive.google.com/open?id=1jOSd7RQ0re5WOvj7tBenGhgVKjaiHq5U<br />
* U4: https://drive.google.com/open?id=1fzV83mJYlrMz4zaYn_3cZU7iFhcAzUof<br />
* U5: https://drive.google.com/open?id=1wGAJv2pcca3DnKu_FSOXdKxWXHPmA0zO<br />
<br />
For now, direct download links for the installers.<br />
<br />
==Preparing==<br />
<br />
Install a legit copy of Falcon 4.0 anywhere. Doesn't have to run, so don't waste SSD space. <br />
Run U1 of BMS install. This is your CONFIGURATION game folder. Not your game folder, thus it does not require SSD either. THis folder is the installaton that you use to configure, update, and modify your actual Falcon install.<br />
<br />
==Installing patches U2-U5==<br />
<br />
Install these into the same folder where you installed Falcon U1.<br />
<br />
==Installing==<br />
<br />
Now, after installing all patches, run the installer from the folder that you have them all installed from. Decide a location for your game, preferably SSD.<br />
<br />
<br />
<br />
#Install U1<br />
##Easiest is to place the setup at C:\Falcon BMS 4.33 U1 Setup<br />
##Verify install works<br />
##Verify version FALCON BMS 4.33.1 (x64) BUILD 15227<br />
#Update U2<br />
##Make sure you install the update into the U1 SETUP folder<br />
##Rerun the setup and update to U2<br />
##Verify version FALCON BMS 4.33.2 (x64) BUILD 15754<br />
#Update U3<br />
##Make sure you install the update into the U1 SETUP folder<br />
##Rerun the setup and update to U3<br />
##[http://www.unitedoperations.net/wiki/BMS_Configuration_and_Setup#Enabling_Borderless_Windowed_Mode Configure for windowed mode]<br />
##Verify version FALCON BMS 4.33.3 (x64) BUILD 16068<br />
#Update U4<br />
##Make sure you install the update into the U1 SETUP folder<br />
##Rerun the setup and update to U4<br />
#Update U5<br />
##Make sure you install the update into the U1 SETUP folder<br />
##Rerun the setup and update to U5<br />
<br />
After the installation is finished, '''don’t delete the setup folder''', as you’ll need it to patch the game later. BMS always checks for a valid Falcon 4 install, so do not uninstall Falcon 4.<br />
<br />
==Patching BMS==<br />
To update to a newer version of BMS, download the update and apply it in the same manner as the Update 3 executable above, then run setup.exe again. The game will automatically detect your install and patch the game to the downloaded version.<br />
<br />
=Configuring BMS=<br />
After installing the game, run the shortcut to the game and click Configuration in the launcher. In this window are options that cannot be changed in game, like advanced graphics options and avionics options. The settings are down to personal preference.<br />
VKing recommends Color MFD, EPAF Radar Cues, Gray scale AG Radar, and Smaller HSD/Bullseye Symbols.<br />
<br />
In the game, click Logbook at the top of the screen. This will show your player profile. Change both name and callsign to your nickname and pick a pilot picture and/or squadron patch if you like.<br />
<br />
Go to the Setup screen and check “Radio calls use bullseye”, then configure the rest the way you like.<br />
<br />
==Alternate launcher - configuring the rest==<br />
To remain sane, get the alternate launcher: https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases<br />
<br />
This gives you immediate access to all the exe:s you want to run for BMS: the game itself, the IVC radio voice chat client, the configurator, and all the stuff you need if you ever want to run a server or create complex custom things like weather and mission info sheets.<br />
<br />
Above all, the alternate launcher provides a modern way of binding your controls: just pick a function and input the right button or axis on your keyboard/joystick/whatever. In the olden days, this had to be done using complex and unintuitive excel sheets where you had to keep track of hardware ID numbers and similar silly things. The modern binding functionality of the launcher removes all of that (although some things, like triggering function on button releases, or using function switches, for more advanced HOTAS setups is still a bit complex).<br />
<br />
=Balkans Theater for Goon Campaign=<br />
https://drive.google.com/open?id=1fFhYLJY9-9gW03otth7xxxkZoh1AVg4V<br />
<br />
[[Category:BMS Guides]]<br />
[[Category:BMS]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=CH_HOTAS&diff=5633CH HOTAS2023-01-03T18:46:48Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
Readme in there.<br />
<br />
<br />
https://www.dropbox.com/s/yav1l0q2ag1o2a8/CH%20Products%20BMS%20setup.zip?dl=0&file_subpath=%2FCH+Products+BMS+setup<br />
<br />
[[Category:Hardware]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Thrustmaster_Warthog&diff=5632Thrustmaster Warthog2023-01-03T18:46:38Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
For 4.33, I recommend Morphine's Profile.<br />
<br />
<br />
Morphine's profile uses TARGET profile manager from Thrustmaster. However, this is a great profile with all the F-16 HOTAS controls, and all buttons used for something. In addition, the lights on throttle indicate milpower and afterburner status. The file includes pictures, readme guide, and everything you need.<br />
<br />
<br />
Download: [https://drive.google.com/open?id=1n2KmuaIyOGBlcoU6szJuP47ILBiGKaev]<br />
<br />
[[Category:Hardware]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Saitek_X45&diff=5631Saitek X452023-01-03T18:46:28Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
I get it, you like to roll old school. <br />
<br />
<br />
Here is a very basic .key file that requires no external profiler, and has most of the vital functions. This keyfile assumes a Track IR or other form of head tracking. It includes pictures of function, and an install guide.<br />
<br />
https://drive.google.com/open?id=1NUKvkCjNw-7mreQLUhFB7RMASYg-miTG<br />
<br />
[[Category:Hardware]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Controller&diff=5630Controller2023-01-03T18:45:44Z<p>Tippis: </p>
<hr />
<div>{{cleanup}}<br />
There are various extremely common HOTAS controllers. Odds are most of you will find a profile for Falcon BMS here.<br />
<br />
==Common control schemes==<br />
Here are sub pages for controllers, and some fan favorite .key files for them for easy setup.<br />
<br />
[[Thrustmaster Warthog]]<br />
<br />
[[Saitek X45]]<br />
<br />
[[Saitek X52]]<br />
<br />
[[Thrustmaster T16000 Hotas]]<br />
<br />
[[CH HOTAS]]<br />
<br />
==Overview of the F-16 HOTAS==<br />
<br />
It is laid out in two parts, the stick and the throttle. We'll go through some basic meanings of the buttons. <br />
<br />
<br />
<br />
http://falcon4.wdfiles.com/local--files/avionics%3Ahotas/stick.jpg<br />
<br />
'''Trigger''' The trigger on the SSC is a two-stage trigger (Modeled on most game controllers). The first detent performs several functions, including starting ACMI recording. The second stage fires the aircraft's cannon.<br />
<br />
'''Weapon Release''' The weapon release switch (also called the "pickle" button) is used to fire missiles, drop bombs, and jettison stores. The exact switch usage to release the weapon depends on which weapon is being used.<br />
<br />
'''Trim Hat''' This hat switch is used to control the aircraft's trim. Pressing up/down on the switch changes the pitch trim position, and pressing left/right changes the roll trim position. Most players do not use this switch, since trim is rarely required to keep the aircraft stable. Instead, it is usually used to control the view direction.<br />
<br />
'''Target Management Switch''' TMS<br />
<br />
'''Display Management Switch''' DMS<br />
<br />
'''Countermeasures Management Switch''' The countermeasures management switch is used to control the various countermeasures of the aircraft, including the jammer and chaff/flares. <br />
<br />
'''Missile Step/NWS''' This switch has a number of different functions depending on what mode the aircraft is in and where it is located. When the aircraft is on ground, it toggles the nose wheel steering system. If the aircraft is connected to a tanker during in-air refueling, it disconnects from the boom. If the aircraft is in A-A master mode, it is used to toggle the missile hardpoint to be used for the next launch. If the aircraft is in A-G mode, it toggles between CCRP, CCIP, and other bombing modes.<br />
<br />
'''Pinky Switch''' This switch is used to cycle the field of view for the currently selected sensor of interest. This works for many MFD pages, including the FCR, infrared/laser targeting, and the HSD.<br />
<br />
'''Paddle Switch''' This acts as a momentary disconnect for the aircraft's autopilot while it is engaged. As long as the switch is held down, the pilot will have control of the aircraft (instead of the autopilot). If the autopilot is not engaged, the switch has no effect.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
http://falcon4.wdfiles.com/local--files/avionics%3Ahotas/throttle.jpg<br />
<br />
'''Communications Switch''' This switch is used to talk on various radio frequencies and handle datalink functions.<br />
<br />
'''Uncage Switch '''This switch is used to "uncage" the seeker head for infrared missiles such as the AIM-9. When the seeker head is uncaged, it freely seeks targets and is not slaved to the aircraft's radar.<br />
<br />
'''Antenna Elevation Knob''' This rotary knob is used to set the elevation angle for the radar antenna. This can be used to scan different altitudes for enemy aircraft. There is generally a detent at the central position to allow the pilot to easily re-center the antenna.<br />
<br />
'''Dogfight/Missile Override Switch''' This is a three-way switch which is used to select the dogfight and missile override modes. If the switch is in the center position, neither override mode is selected.<br />
<br />
'''Cursor Control''' This joystick-type control is used to move the cursor on the FCR and HSD MFD pages. It is also used to slew the radar antenna in the ACM 30x20 mode.<br />
<br />
'''Blackout Switch''' The HOBO (hands-on blackout) switch is used to allow the pilot to control the aircraft's lighting with the HOTAS.<br />
<br />
[[Category:Hardware]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Falcon_Benchmark_Simulator&diff=5629Falcon Benchmark Simulator2023-01-03T18:38:17Z<p>Tippis: </p>
<hr />
<div><youtube>https://www.youtube.com/watch?v=658ax0y8KHs</youtube><br />
<br />
= What is it? =<br />
<br />
Falcon '''B'''ench'''M'''ark '''S'''imulator, the ultimate F-16 and dynamic war simulator for your groggy needs.<br />
<br />
Falcon BMS is a fully clickable, extremely realistic, definitive simulation of the F-16 in various conflicts, with a full, immersive, emergent campaign that will proceed with or without you. Built on top of the now quarter-century old Falcon 4.0, BMS focuses on the F-16 &mdash; it is fully clickable, and most of its systems are accurately modeled. This might not be the easiest game to learn, but it has its rewards. With recent updates, it has also slowly started to expand beyond just the Viper, and it now offers the A-10 (A and C models), AV-8B (night attack and radar variant), F-4, F-15C and E, F/A-18, JA-37 Viggen, MiG-29, Mirage 2000, and Tornado as playable aircraft with dedicated cockpits and light models. They are not as thoroughly simulated, especially on the systems and avionics side, as the Viper, but with the breakthrough in coding done with BMS 4.37 where player aircraft no longer have to be F-16s in disguise, this will all improve over time.<br />
<br />
This is nothing like propgames and World War 2 aerial warfare. You don't just fly this plane, you also dive head first into all the millions of buttons and complex computer systems. Falcon is a great simulator of warfare, but it is also a very able and very hard flight simulator. You click buttons in the cockpit. You plan strikes. You read up on radar warning tones. You learn about capabilities of air defence systems. You learn about all kinds of systems, tactics, procedures and concepts that will blow your mind in their complexity. You'll learn why piloting is such an awesome and glorified concept in our society. You could drown yourself into boatloads of manuals and guides to learn you to pilot this bird, and if you do, you can very likely operate an actual one on a basic level. If you need or want help, just ask. But don't just pop into mumble with "k, i wanna fly the F-16". You HAVE to be prepared to read, too.<br />
<br />
It is also not like DCS, where there is certainly a bunch of reading and learning procedures, but where world outside of the aircraft in many cases is just decorative. BMS' (and Falcon 4.0 before it) claim to fame is its unprecedented and unrivalled dynamic campaign engine where what you do actually matters. You are a part of a flight with a specific role, part of a package with a specific objective, part of a strategical push to an end goal. If you waste planes and missiles, they will run out and you will no longer be able to project force, and then you lose. You have to actually communicate with AWACS and JSTARS and ATC, or you will be ambushed, or fire on the wrong target, or just collide in the air or on the runway, and again, you lose. The world is alive in a way that no other flight simulator offers and to an extent, you can even play BMS as an RTS, moving assets across the map and only rarely &mdash; if ever &mdash; step into the cockpit.<br />
<br />
You don't just fly a single mission or a jumble of aircraft. You are in a 24/7 war.<br />
<br />
= Get going =<br />
<br />
[[Getting and installing BMS]]<br />
<br />
[[BMS Configuration]]<br />
<br />
[[Joining a BMS server]]<br />
<br />
[[Fragging a package]], aka creating a flight and joining it.<br />
<br />
<youtube>https://youtu.be/n-K5bvaVBRM</youtube><br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Fragging_a_package&diff=5628Fragging a package2023-01-03T01:26:21Z<p>Tippis: </p>
<hr />
<div><br />
''Adapted from wonko's discord instructions.''<br />
<br />
&ldquo;Fragging&rdquo; in [[Falcon Benchmark Simulator|BMS]] does not refer to the making happening of ludicrous gibs, but rather the creation of a core mission and assigning the various flights &mdash; strike aircraft, escorts, dedicated ECM, refuel, and awacs and whatever else is needed &mdash; to support that mission.<br />
<br />
Packages can be made hideously complex to set up and time correctly, but can be as simple as just a single wing or even a single aircraft. Even in the simple case, however, the complexities afforded by the game make it necessary to jump through a few hoops to get going.<br />
<br />
= Fragging a single flight =<br />
<br />
The (relatively speaking) most simple process for getting a single flight going is this:<br />
<br />
# Right click on the map in the general area you want your flight to be and select Add Package.<br/>[[File:Fraggin-add-package.png|200px|frameless|alt=Adding a package.]]<br />
# In the Add Package Window, click the Lock icon next to the Takeoff time.<br />
# Increase the takeoff time by 1-2 hours from the current time.<br />
# Click New<br/>[[File:Fraggin-time-package.png|400px|frameless|alt=Adding a package.]]<br />
# In the Add Flight window in the Aircraft dropdown, select the airframe you wish to use (e.g. F-16CM Block 40)<br />
# In the Role dropdown, select Training (see https://www.airgoons.com/w/Tasking for more details on what each of these options mean)<br />
# In the Size dropdown, select 1<br />
# In the Squadron dropdown, select one of our squadrons, preferably one that is custom-added to be used by players (e.g. 420th Blazers, 421st Bogarts, etc.)<br />
# Click OK<br/>[[File:Fraggin-add-flight.png|400px|frameless|alt=Adding a flight.]]<br />
# Click the ATO button on the bottom bar (if you do not see this, click Mission Schedule on the top bar)<br />
# Expand Other<br />
# Expand Training Packages until you find the one you created from our squadron<br />
# Right click the Flight and click Join (note the Package Number, in this case 3230)<br/>[[File:Fraggin-ato-select.png|400px|frameless|alt=Selecting a flight via ATO.]]<br />
# Select Package 3230 from the FS Frag Order window on the left side of the screen<br />
# Click the blue aircraft to select the plane slot<br/>[[File:Fraggin-frago.png|200px|frameless|alt=Selecting a flight from the frag order.]]<br />
# Click the Flight Plan button on the bottom bar<br />
# Modify the TOS time to be ~20 minutes from the current time for Ramp start (see top right corner) or ~5 minutes for Taxi start<br />
#* Start by increasing setting TOS minutes to current minutes +30<br />
#* Decrease TOS hours to equal current hours<br />
#* Decrease TOS minutes one at a time until T-20 or T-5<br />
# Click the Red X to exit the Flight Plan<br/>[[File:Fraggin-flightplan.png|400px|frameless|alt=Retiming the flightplan.]]<br />
# Click Takeoff in the bottom right corner<br />
# Select Ramp or Taxi, and wait until you have loaded into the jet<br/>[[File:Fraggin-takeoff.png|500px|frameless|alt=Taking off.]]<br />
<br />
== The timing issue ==<br />
<br />
While in a local game, the simulation speeds up to quickly get you in the cockpit if your flight is not taking off for a while, multiplayer games generally have to keep the Server &ldquo;player&rdquo; in the 3D view to maintain stability. In addition, on an active server, there may be other players flying around and making a mess. In this state, the game cannot automatically accelerate time so any waiting time has to be ''actually waited out'', in real-time.<br />
<br />
This is why it is important to time the take-off correctly and to be mindful of whether you want to do a ramp start or a taxi start. If you time it wrong, you will end up having to wait 15 real-time minutes before your taxi start goes active, or you will miss your ramp start because the AI has already got the plane going and has started to taxi.<br />
<br />
= Video tutorials =<br />
<br />
<youtube>https://www.youtube.com/watch?v=7J4YdL8t8Mc</youtube><br />
<youtube>https://www.youtube.com/watch?v=QhcjkZdspKM</youtube><br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Fragging_a_package&diff=5627Fragging a package2023-01-03T01:25:32Z<p>Tippis: </p>
<hr />
<div><br />
''Adapted from wonko's discord instructions.''<br />
<br />
&ldquo;Fragging&rdquo; in [[Falcon Benchmark Simulator|BMS]] does not refer to the making happening of ludicrous gibs, but rather the creation of a core mission and assigning the various flights &mdash; strike aircraft, escorts, dedicated ECM, refuel, and awacs and whatever else is needed &mdash; to support that mission.<br />
<br />
Packages can be made hideously complex to set up and time correctly, but can be as simple as just a single wing or even a single aircraft. Even in the simple case, however, the complexities afforded by the game make it necessary to jump through a few hoops to get going.<br />
<br />
= Fragging a single flight =<br />
<br />
<br />
# Right click on the map in the general area you want your flight to be and select Add Package.<br/>[[File:Fraggin-add-package.png|200px|frameless|alt=Adding a package.]]<br />
# In the Add Package Window, click the Lock icon next to the Takeoff time.<br />
# Increase the takeoff time by 1-2 hours from the current time.<br />
# Click New<br/>[[File:Fraggin-time-package.png|400px|frameless|alt=Adding a package.]]<br />
# In the Add Flight window in the Aircraft dropdown, select the airframe you wish to use (e.g. F-16CM Block 40)<br />
# In the Role dropdown, select Training (see https://www.airgoons.com/w/Tasking for more details on what each of these options mean)<br />
# In the Size dropdown, select 1<br />
# In the Squadron dropdown, select one of our squadrons, preferably one that is custom-added to be used by players (e.g. 420th Blazers, 421st Bogarts, etc.)<br />
# Click OK<br/>[[File:Fraggin-add-flight.png|400px|frameless|alt=Adding a flight.]]<br />
# Click the ATO button on the bottom bar (if you do not see this, click Mission Schedule on the top bar)<br />
# Expand Other<br />
# Expand Training Packages until you find the one you created from our squadron<br />
# Right click the Flight and click Join (note the Package Number, in this case 3230)<br/>[[File:Fraggin-ato-select.png|400px|frameless|alt=Selecting a flight via ATO.]]<br />
# Select Package 3230 from the FS Frag Order window on the left side of the screen<br />
# Click the blue aircraft to select the plane slot<br/>[[File:Fraggin-frago.png|200px|frameless|alt=Selecting a flight from the frag order.]]<br />
# Click the Flight Plan button on the bottom bar<br />
# Modify the TOS time to be ~20 minutes from the current time for Ramp start (see top right corner) or ~5 minutes for Taxi start<br />
#* Start by increasing setting TOS minutes to current minutes +30<br />
#* Decrease TOS hours to equal current hours<br />
#* Decrease TOS minutes one at a time until T-20 or T-5<br />
# Click the Red X to exit the Flight Plan<br/>[[File:Fraggin-flightplan.png|400px|frameless|alt=Retiming the flightplan.]]<br />
# Click Takeoff in the bottom right corner<br />
# Select Ramp or Taxi, and wait until you have loaded into the jet<br/>[[File:Fraggin-takeoff.png|500px|frameless|alt=Taking off.]]<br />
<br />
== The timing issue ==<br />
<br />
While in a local game, the simulation speeds up to quickly get you in the cockpit if your flight is not taking off for a while, multiplayer games generally have to keep the Server &ldquo;player&rdquo; in the 3D view to maintain stability. In addition, on an active server, there may be other players flying around and making a mess. In this state, the game cannot automatically accelerate time so any waiting time has to be ''actually waited out'', in real-time.<br />
<br />
This is why it is important to time the take-off correctly and to be mindful of whether you want to do a ramp start or a taxi start. If you time it wrong, you will end up having to wait 15 real-time minutes before your taxi start goes active, or you will miss your ramp start because the AI has already got the plane going and has started to taxi.<br />
<br />
= Video tutorials =<br />
<br />
<youtube>https://www.youtube.com/watch?v=7J4YdL8t8Mc</youtube><br />
<youtube>https://www.youtube.com/watch?v=QhcjkZdspKM</youtube><br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Fragging_a_package&diff=5626Fragging a package2023-01-03T01:22:44Z<p>Tippis: </p>
<hr />
<div><youtube>https://www.youtube.com/watch?v=7J4YdL8t8Mc</youtube><br />
<br />
<br />
''Adapted from wonko's discord instructions.''<br />
<br />
&ldquo;Fragging&rdquo; in [[Falcon Benchmark Simulator|BMS]] does not refer to the making happening of ludicrous gibs, but rather the creation of a core mission and assigning the various flights &mdash; strike aircraft, escorts, dedicated ECM, refuel, and awacs and whatever else is needed &mdash; to support that mission.<br />
<br />
Packages can be made hideously complex to set up and time correctly, but can be as simple as just a single wing or even a single aircraft. Even in the simple case, however, the complexities afforded by the game make it necessary to jump through a few hoops to get going.<br />
<br />
# Right click on the map in the general area you want your flight to be and select Add Package.<br/>[[File:Fraggin-add-package.png|200px|frameless|alt=Adding a package.]]<br />
# In the Add Package Window, click the Lock icon next to the Takeoff time.<br />
# Increase the takeoff time by 1-2 hours from the current time.<br />
# Click New<br/>[[File:Fraggin-time-package.png|400px|frameless|alt=Adding a package.]]<br />
# In the Add Flight window in the Aircraft dropdown, select the airframe you wish to use (e.g. F-16CM Block 40)<br />
# In the Role dropdown, select Training (see https://www.airgoons.com/w/Tasking for more details on what each of these options mean)<br />
# In the Size dropdown, select 1<br />
# In the Squadron dropdown, select one of our squadrons, preferably one that is custom-added to be used by players (e.g. 420th Blazers, 421st Bogarts, etc.)<br />
# Click OK<br/>[[File:Fraggin-add-flight.png|400px|frameless|alt=Adding a flight.]]<br />
# Click the ATO button on the bottom bar (if you do not see this, click Mission Schedule on the top bar)<br />
# Expand Other<br />
# Expand Training Packages until you find the one you created from our squadron<br />
# Right click the Flight and click Join (note the Package Number, in this case 3230)<br/>[[File:Fraggin-ato-select.png|400px|frameless|alt=Selecting a flight via ATO.]]<br />
# Select Package 3230 from the FS Frag Order window on the left side of the screen<br />
# Click the blue aircraft to select the plane slot<br/>[[File:Fraggin-frago.png|200px|frameless|alt=Selecting a flight from the frag order.]]<br />
# Click the Flight Plan button on the bottom bar<br />
# Modify the TOS time to be ~20 minutes from the current time for Ramp start (see top right corner) or ~5 minutes for Taxi start<br />
#* Start by increasing setting TOS minutes to current minutes +30<br />
#* Decrease TOS hours to equal current hours<br />
#* Decrease TOS minutes one at a time until T-20 or T-5<br />
# Click the Red X to exit the Flight Plan<br/>[[File:Fraggin-flightplan.png|400px|frameless|alt=Retiming the flightplan.]]<br />
# Click Takeoff in the bottom right corner<br />
# Select Ramp or Taxi, and wait until you have loaded into the jet<br/>[[File:Fraggin-takeoff.png|500px|frameless|alt=Taking off.]]<br />
<br />
While in a local game, the simulation speeds up to quickly get you in the cockpit if your flight is not taking off for a while, multiplayer games generally have to keep the Server &ldquo;player&rdquo; in the 3D view to maintain stability. In addition, on an active server, there may be other players flying around and making a mess. In this state, the game cannot automatically accelerate time so any waiting time has to be ''actually waited out'', in real-time.<br />
<br />
This is why it is important to time the take-off correctly and to be mindful of whether you want to do a ramp start or a taxi start. If you time it wrong, you will end up having to wait 15 real-time minutes before your taxi start goes active, or you will miss your ramp start because the AI has already got the plane going and has started to taxi.<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Getting_and_installing_BMS&diff=5625Getting and installing BMS2023-01-03T00:34:42Z<p>Tippis: /* Additional downloads */</p>
<hr />
<div>In the olden days, getting and installing [[Falcon Benchmark Simulator|BMS]] could be a bit of a chore, but at least it was (sort of) free because Falcon 4.0 was largely abandonware and while the installer required you to point to a valid Falcon4.exe file, that file could be &ldquo;found&rdquo; trivially on the internet. The bigger obstacle was a very long and obnoxious registration and log-in requirement to download a multipart sequence of builds and updates from a slow website.<br />
<br />
These days, it costs a trivial amount to get your hands on a legal copy of Falcon 4.0, which you sort of need because the ownership checking is a bit more thorough. But on the other hand, no registration or login is needed (in spite of the official instructions saying so, but they are written for an older version anyway) and between direct download and torrent options, and having a sensible and working updater, the download process is much more palatable.<br />
<br />
To get the instruction from the source, go to the [https://wiki.falcon-bms.com/start-with-falcon-bms/install-update Falcon BMS install/update help page], or directly to the [https://www.falcon-bms.com/downloads/ downloads page], which link to further documentation.<br />
<br />
= Requirements =<br />
<br />
The official requirements are listed as:<br />
* Windows 7 (64 bits)<br />
* i5 2500K 3.3 GHz<br />
* 4Gb RAM<br />
* 3D GFX card 2Gb dedicated VRAM (DX11 compatible mandatory)<br />
* 15Gb HDD space required<br />
<br />
What is ''not'' listed, but requires a special mention in spite of sounding like a trivial detail, is a sound card. It is worth mentioning because even if you intend to install BMS for the purpose of running an online multiplayer server, you ''still'' need that sound card as well as a DX11-compaible graphics card. If you intend to run the server in a virtualised environment, the virtualisation needs to cover those media capabilities as well.<br />
<br />
== Falcon 4.0 ==<br />
<br />
To install [[Falcon Benchmark Simulator|BMS]], you ned to have Falcon 4.0 installed. While you can technically get rid of Falcon 4 once BMS is installed, that adds an unnecessary step to future repairs and re-installs, so the (relatively) piddling size of this late-'90s game might as well be considered part of the BMS installation footprint.<br />
<br />
You can most readily get Falcon 4 from [https://www.gog.com/game/falcon_collection GOG.com] (along with Falcon, Falcon A.T. and Falcon 3.0 + a couple of expansions), or from [https://store.steampowered.com/app/429530/Falcon_40/ Steam]. Steam also offers the same package as GOG for a extra cents.<br />
<br />
= Download &amp; install =<br />
<br />
Go to [https://www.falcon-bms.com/downloads/ the official BMS download page] and get either the downloader tool and run it, or get the full installer via torrent. Either way, you end up with the full installer .exe file in a location of your liking &mdash; just run it and follow the instructions.<br />
<br />
== What you get ==<br />
<br />
BMS nature as a community and fan project with a bias towards the more ''involved'' side of flight simming reveals itself immediately when looking at what gets installed by default as part of the download package. In older versions, the collage of special tools and utilities and optional capabilities made for a bit of a mess, but at the same time, an additional fan tool in the form of the &ldquo;alternate BMS launcher&rdquo; was available to guide the user through that jungle.<br />
<br />
In later versions, the launcher is no longer alternate and is instead a default part of the install, and should be the main interface for the regular user as far as getting to the many different components of the game.<br />
<br />
=== BMS Launcher ===<br />
<br />
[[File:Bms-launcher.png|512px|frameless|alt=The BMS launcher.]]<br />
<br />
[[File:BMS updater icon.png|32px|left|frameless]] The launcher offers immediate access to the most common tools one might want to use in connection to BMS: the game update tool, the base configuration tool, the acronym salad of IVC, RTTR, AVC, and the most popular third-party tools.<br />
<br />
[[File:BMS config icon.png|32px|left|frameless]] The launcher also provides a means to set up all the controls and key- and button binds you might need via a modern and highly capable interface. This bypasses the arcane, antiquated, and utterly byzantine input definition system that BMS uses to define its inputs. While the in-game settings screen ostensibly offers a page for button and axis binding, this is a left-over from Falcon 4.0 and '''should not be used''' &mdash; odds are that using it will break things rather than provide any workable binding.<br />
<br />
''Always use the launcher to set and adjust your binds''. This means you have to quit and restart BMS every time you want to make a control setup adjustment, but better that than to run the risk of breaking the bind files by using the in-game bind mechanic.<br />
<br />
For further information, check the [[BMS Configuration]] article.<br />
<br />
=== IVC ===<br />
<br />
[[File:IVC client icon.png|32px|left|frameless]][[File:IVC server icon.png|left|32px|frameless]] IVC, or the &ldquo;Internal Voice Communications&rdquo; tool is the voice communication system for BMS. It is essentially a bespoke TeamSpeak 3 implementation that interfaces with the in-game radios to let players use the in-cockpit radio communication systems (and their related HOTAS controls) to speak to each other.<br />
<br />
IVC consists of a client and a server component. Unless you intend to host a BMS server, the server component can be ignored completely. The client generally auto-launches and auto-connects if a server has IVC set up, but it can also be launched manually if you want to set up the audio devices it should use.<br />
<br />
=== RTT Remote ===<br />
<br />
[[File:RTTR client icon.png|32px|left|frameless]][[File:RTTR server icon.png|32px|left|frameless]] RTT Remote &mdash; the original meaning of which is lost in mists of time &mdash; is an instrument extraction tool for BMS. Beyond the more trivial case of making things like MFDs show up on a separate screen, it also allows for complex setups for pit builders, where a different computer can host the display and feed inputs back from, say, a touch screen over a network connection.<br />
<br />
=== Avionics Configurator ===<br />
<br />
[[File:AVC icon.png|32px|left|frameless]] For anyone who has been frustrated with Eagle Dynamics' philosophy of &ldquo;our SMEs tell us that plane X never flew with Y fitted&rdquo; the Avionics Configurator is the tool that lets you adjust how the different aircraft in BMS are equipped. This allows enterprising game modders to create all kinds of subvariants or frankenplane versions of the already extensive library of F-16s (and other airframes) on offer in the game.<br />
<br />
Its use is more for single-player setups, since this kind of alteration of the core data files can cause a fair amount of conflicts with how planes work and behave in multiplayer unless the same set of alterations are distributed and used by all players.<br />
<br />
=== Editor ===<br />
<br />
[[File:Editor icon.png|32px|fleft|rameless]] Much like how the Avionics Configurator lets you alter aircraft data, the nondescript &ldquo;Editor&rdquo; lets you modify weapons and vehicle data beyond just the avionics of aircraft. Also much like the AC, this kind of editing is more for setting up or tweaking local single-player games, as mismatches can cause conflicts in multiplayer.<br />
<br />
=== Documentation ===<br />
<br />
With all the different components included in the instal, and with the core conceit of the game being a ''thorough'' simulation of a multitude of F-16 variants in a complex combat environment, it should come as no surprise that BMS comes with an extensive set of documentation and manuals.<br />
<br />
The main documents can be found online on the [https://wiki.falcon-bms.com/manuals BMS manuals] page of the man website, and includes almost 1,400 pages covering how the different bits of software work on top of the functionality of the F-16 avionics and weapon systems. On top of this, another 400 pages describe the many training missions included in the game and the different threats you will encounter.<br />
<br />
Beyond what is available on the website, the actual game install also includes technical documentation on how to connect all kinds of input (and output) devices for cockpit building, on modding and module- and theatre development, printable checklists, as well as maps and navigation aids for the built-in Koraean theatre. There are also visual quick guides to the other flyable planes in the game: the A-10, AV-8B, F-4, F-15, F/A-18, JA-37, MiG-29, Mirage 2000, and Tornado. In total, the documentation directory for BMS takes up more disk space than the entire install of the original Falcon 4.0&hellip;<br />
<br />
== Additional downloads ==<br />
<br />
A second row of program icons on the launcher will at first cause a file browser show when clicked. The purpose of this browser window is to tell the launcher where you have installed some of the more popular add-on tools for BMS, each of which needs to be downloaded separately. Three of these &mdash; Weapon Delivery Planner, Mission Commander, and Weather Commander &mdash; can be found downloaded from the developer's website: [https://www.weapondeliveryplanner.nl/download/index.html weaponsdeliveryplanner.nl]. The other two are found via their respective threads on the official BMS forum.<br />
<br />
=== Weapons Delivery Planner ===<br />
<br />
[[File:WDP icon.png|32px|left|frameless]] [https://www.weapondeliveryplanner.nl/about/index.html Weapon Delivery Planner] is a utility that imports flight- and package data from a save game file and uses it to create kneeboard, data cassette (DTC) settings, and various weapon and, as the name suggests, weapon delivery settings such as laser codes for laser-guided bombs.<br />
<br />
The DTC is the system in the F-16 that lets you set up just about any parameter for programmable systems on the aircraft: threats, target points, and polygons for the navigation system; release programs for the countermeasure system; radio settings etc. Most of this can be adjusted from inside the game, but the interface for it is old and clunky. WDP gives you easier access to all of those settings, at the cost of requiring you to save the game so WDP has a source to import data from.<br />
<br />
WDP ''can'' be used in multiplayer as well, again by simply creating a save from the current game state and importing it in the utility, but since multiplayer games tend to be running in real time, this process requires a bit more forethought and planning so you don't miss the take-off time while you are fiddling with all the settings.<br />
<br />
=== Mission Commander ===<br />
<br />
[[File:MC icon.png|32px|left|frameless]] [https://www.weapondeliveryplanner.nl/about/mc.html Mission Commander] is a utility for mission and campaign makers and server operators. If all you ever do is play ready-made missions or participate as a client in online campaigns, this tool offers little of any use.<br />
<br />
It imports and exports savegame data to let the user change everything from individual flights to entire campaign setups. Commonly, it is used to customise campaigns for multiplayer use, to create custom squadrons that the online players can use. This gives players access to specific variants (or weapon systems) that may otherwise be in short supply in the base campaign, or just not available at all, and allows for setups where players do not compete with the AI for tasking or flying specific packages.<br />
<br />
=== Weather Commander ===<br />
<br />
[[File:WC icon.png|32px|left|frameless]] [https://www.weapondeliveryplanner.nl/about/wc.html Weather Commander] is even more of a mission-maker's tool than Mission Commander. It lets the mission-maker create weather files for a mission or for an entire campaign though a very easy-to-use system of literally painting temperatures, clouds, and pressure zones onto the map.<br />
<br />
On its own, it is entirely capable but also takes a fair bit of effort to create even a single map of interesting weather. Fortunately, its can be used in conjunction with&hellip;<br />
<br />
=== F4Wx Real Weather ===<br />
<br />
[[File:F4Wx icon.png|32px|left|frameless]] [https://forum.falcon-bms.com/topic/8267/f4wx-real-weather-converter F4Wx (Falcon 4 Weather Converter] is a utility that imports real-world weather data and forecasts to create everything from a single weather map to several weeks worth of evolving weather for campaign use. What can require a lot of effort in Weather Commander is here done by just a few button clicks and waiting for a but of processing. The weather maps can then be further tweaked and refined in WC, if the real world happens to be boring this week.<br />
<br />
=== F4RADAR ===<br />
<br />
[[File:F4radar icon.png|32px|left|frameless]] [https://forum.falcon-bms.com/topic/18356/f4radar-lightweight-standalone-radar-application F4Radar] is a developing utility that ultimately aims to become something similar to [[LotATC_4_DCS|LotATC]]. For now, it is mostly a radar picture exporter of sorts but it still allows for some limited GCI usage.<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Category:BMS_Articles&diff=5624Category:BMS Articles2023-01-02T23:47:32Z<p>Tippis: Created page with "The following pages discuss Falcon Benchmark Simulator (BMS)."</p>
<hr />
<div>The following pages discuss [[Falcon Benchmark Simulator]] (BMS).</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Getting_and_installing_BMS&diff=5623Getting and installing BMS2023-01-02T23:42:41Z<p>Tippis: /* Documentation */</p>
<hr />
<div>In the olden days, getting and installing [[Falcon Benchmark Simulator|BMS]] could be a bit of a chore, but at least it was (sort of) free because Falcon 4.0 was largely abandonware and while the installer required you to point to a valid Falcon4.exe file, that file could be &ldquo;found&rdquo; trivially on the internet. The bigger obstacle was a very long and obnoxious registration and log-in requirement to download a multipart sequence of builds and updates from a slow website.<br />
<br />
These days, it costs a trivial amount to get your hands on a legal copy of Falcon 4.0, which you sort of need because the ownership checking is a bit more thorough. But on the other hand, no registration or login is needed (in spite of the official instructions saying so, but they are written for an older version anyway) and between direct download and torrent options, and having a sensible and working updater, the download process is much more palatable.<br />
<br />
To get the instruction from the source, go to the [https://wiki.falcon-bms.com/start-with-falcon-bms/install-update Falcon BMS install/update help page], or directly to the [https://www.falcon-bms.com/downloads/ downloads page], which link to further documentation.<br />
<br />
= Requirements =<br />
<br />
The official requirements are listed as:<br />
* Windows 7 (64 bits)<br />
* i5 2500K 3.3 GHz<br />
* 4Gb RAM<br />
* 3D GFX card 2Gb dedicated VRAM (DX11 compatible mandatory)<br />
* 15Gb HDD space required<br />
<br />
What is ''not'' listed, but requires a special mention in spite of sounding like a trivial detail, is a sound card. It is worth mentioning because even if you intend to install BMS for the purpose of running an online multiplayer server, you ''still'' need that sound card as well as a DX11-compaible graphics card. If you intend to run the server in a virtualised environment, the virtualisation needs to cover those media capabilities as well.<br />
<br />
== Falcon 4.0 ==<br />
<br />
To install [[Falcon Benchmark Simulator|BMS]], you ned to have Falcon 4.0 installed. While you can technically get rid of Falcon 4 once BMS is installed, that adds an unnecessary step to future repairs and re-installs, so the (relatively) piddling size of this late-'90s game might as well be considered part of the BMS installation footprint.<br />
<br />
You can most readily get Falcon 4 from [https://www.gog.com/game/falcon_collection GOG.com] (along with Falcon, Falcon A.T. and Falcon 3.0 + a couple of expansions), or from [https://store.steampowered.com/app/429530/Falcon_40/ Steam]. Steam also offers the same package as GOG for a extra cents.<br />
<br />
= Download &amp; install =<br />
<br />
Go to [https://www.falcon-bms.com/downloads/ the official BMS download page] and get either the downloader tool and run it, or get the full installer via torrent. Either way, you end up with the full installer .exe file in a location of your liking &mdash; just run it and follow the instructions.<br />
<br />
== What you get ==<br />
<br />
BMS nature as a community and fan project with a bias towards the more ''involved'' side of flight simming reveals itself immediately when looking at what gets installed by default as part of the download package. In older versions, the collage of special tools and utilities and optional capabilities made for a bit of a mess, but at the same time, an additional fan tool in the form of the &ldquo;alternate BMS launcher&rdquo; was available to guide the user through that jungle.<br />
<br />
In later versions, the launcher is no longer alternate and is instead a default part of the install, and should be the main interface for the regular user as far as getting to the many different components of the game.<br />
<br />
=== BMS Launcher ===<br />
<br />
[[File:Bms-launcher.png|512px|frameless|alt=The BMS launcher.]]<br />
<br />
[[File:BMS updater icon.png|32px|left|frameless]] The launcher offers immediate access to the most common tools one might want to use in connection to BMS: the game update tool, the base configuration tool, the acronym salad of IVC, RTTR, AVC, and the most popular third-party tools.<br />
<br />
[[File:BMS config icon.png|32px|left|frameless]] The launcher also provides a means to set up all the controls and key- and button binds you might need via a modern and highly capable interface. This bypasses the arcane, antiquated, and utterly byzantine input definition system that BMS uses to define its inputs. While the in-game settings screen ostensibly offers a page for button and axis binding, this is a left-over from Falcon 4.0 and '''should not be used''' &mdash; odds are that using it will break things rather than provide any workable binding.<br />
<br />
''Always use the launcher to set and adjust your binds''. This means you have to quit and restart BMS every time you want to make a control setup adjustment, but better that than to run the risk of breaking the bind files by using the in-game bind mechanic.<br />
<br />
For further information, check the [[BMS Configuration]] article.<br />
<br />
=== IVC ===<br />
<br />
[[File:IVC client icon.png|32px|left|frameless]][[File:IVC server icon.png|left|32px|frameless]] IVC, or the &ldquo;Internal Voice Communications&rdquo; tool is the voice communication system for BMS. It is essentially a bespoke TeamSpeak 3 implementation that interfaces with the in-game radios to let players use the in-cockpit radio communication systems (and their related HOTAS controls) to speak to each other.<br />
<br />
IVC consists of a client and a server component. Unless you intend to host a BMS server, the server component can be ignored completely. The client generally auto-launches and auto-connects if a server has IVC set up, but it can also be launched manually if you want to set up the audio devices it should use.<br />
<br />
=== RTT Remote ===<br />
<br />
[[File:RTTR client icon.png|32px|left|frameless]][[File:RTTR server icon.png|32px|left|frameless]] RTT Remote &mdash; the original meaning of which is lost in mists of time &mdash; is an instrument extraction tool for BMS. Beyond the more trivial case of making things like MFDs show up on a separate screen, it also allows for complex setups for pit builders, where a different computer can host the display and feed inputs back from, say, a touch screen over a network connection.<br />
<br />
=== Avionics Configurator ===<br />
<br />
[[File:AVC icon.png|32px|left|frameless]] For anyone who has been frustrated with Eagle Dynamics' philosophy of &ldquo;our SMEs tell us that plane X never flew with Y fitted&rdquo; the Avionics Configurator is the tool that lets you adjust how the different aircraft in BMS are equipped. This allows enterprising game modders to create all kinds of subvariants or frankenplane versions of the already extensive library of F-16s (and other airframes) on offer in the game.<br />
<br />
Its use is more for single-player setups, since this kind of alteration of the core data files can cause a fair amount of conflicts with how planes work and behave in multiplayer unless the same set of alterations are distributed and used by all players.<br />
<br />
=== Editor ===<br />
<br />
[[File:Editor icon.png|32px|fleft|rameless]] Much like how the Avionics Configurator lets you alter aircraft data, the nondescript &ldquo;Editor&rdquo; lets you modify weapons and vehicle data beyond just the avionics of aircraft. Also much like the AC, this kind of editing is more for setting up or tweaking local single-player games, as mismatches can cause conflicts in multiplayer.<br />
<br />
=== Documentation ===<br />
<br />
With all the different components included in the instal, and with the core conceit of the game being a ''thorough'' simulation of a multitude of F-16 variants in a complex combat environment, it should come as no surprise that BMS comes with an extensive set of documentation and manuals.<br />
<br />
The main documents can be found online on the [https://wiki.falcon-bms.com/manuals BMS manuals] page of the man website, and includes almost 1,400 pages covering how the different bits of software work on top of the functionality of the F-16 avionics and weapon systems. On top of this, another 400 pages describe the many training missions included in the game and the different threats you will encounter.<br />
<br />
Beyond what is available on the website, the actual game install also includes technical documentation on how to connect all kinds of input (and output) devices for cockpit building, on modding and module- and theatre development, printable checklists, as well as maps and navigation aids for the built-in Koraean theatre. There are also visual quick guides to the other flyable planes in the game: the A-10, AV-8B, F-4, F-15, F/A-18, JA-37, MiG-29, Mirage 2000, and Tornado. In total, the documentation directory for BMS takes up more disk space than the entire install of the original Falcon 4.0&hellip;<br />
<br />
== Additional downloads ==<br />
<br />
https://www.weapondeliveryplanner.nl/download/index.html<br />
<br />
=== Weapons Delivery Planner ===<br />
<br />
[[File:WDP icon.png|32px|left|frameless]] <br />
https://www.weapondeliveryplanner.nl/about/index.html<br />
<br />
=== Mission Commander ===<br />
<br />
[[File:MC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/mc.html<br />
<br />
=== Weather Commander ===<br />
<br />
[[File:WC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/wc.html<br />
<br />
=== F4Wx Real Weather ===<br />
<br />
[[File:F4Wx icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/8267/f4wx-real-weather-converter<br />
<br />
=== F4RADAR ===<br />
<br />
[[File:F4radar icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/18356/f4radar-lightweight-standalone-radar-application<br />
<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Getting_and_installing_BMS&diff=5622Getting and installing BMS2023-01-02T22:23:59Z<p>Tippis: /* BMS Launcher */</p>
<hr />
<div>In the olden days, getting and installing [[Falcon Benchmark Simulator|BMS]] could be a bit of a chore, but at least it was (sort of) free because Falcon 4.0 was largely abandonware and while the installer required you to point to a valid Falcon4.exe file, that file could be &ldquo;found&rdquo; trivially on the internet. The bigger obstacle was a very long and obnoxious registration and log-in requirement to download a multipart sequence of builds and updates from a slow website.<br />
<br />
These days, it costs a trivial amount to get your hands on a legal copy of Falcon 4.0, which you sort of need because the ownership checking is a bit more thorough. But on the other hand, no registration or login is needed (in spite of the official instructions saying so, but they are written for an older version anyway) and between direct download and torrent options, and having a sensible and working updater, the download process is much more palatable.<br />
<br />
To get the instruction from the source, go to the [https://wiki.falcon-bms.com/start-with-falcon-bms/install-update Falcon BMS install/update help page], or directly to the [https://www.falcon-bms.com/downloads/ downloads page], which link to further documentation.<br />
<br />
= Requirements =<br />
<br />
The official requirements are listed as:<br />
* Windows 7 (64 bits)<br />
* i5 2500K 3.3 GHz<br />
* 4Gb RAM<br />
* 3D GFX card 2Gb dedicated VRAM (DX11 compatible mandatory)<br />
* 15Gb HDD space required<br />
<br />
What is ''not'' listed, but requires a special mention in spite of sounding like a trivial detail, is a sound card. It is worth mentioning because even if you intend to install BMS for the purpose of running an online multiplayer server, you ''still'' need that sound card as well as a DX11-compaible graphics card. If you intend to run the server in a virtualised environment, the virtualisation needs to cover those media capabilities as well.<br />
<br />
== Falcon 4.0 ==<br />
<br />
To install [[Falcon Benchmark Simulator|BMS]], you ned to have Falcon 4.0 installed. While you can technically get rid of Falcon 4 once BMS is installed, that adds an unnecessary step to future repairs and re-installs, so the (relatively) piddling size of this late-'90s game might as well be considered part of the BMS installation footprint.<br />
<br />
You can most readily get Falcon 4 from [https://www.gog.com/game/falcon_collection GOG.com] (along with Falcon, Falcon A.T. and Falcon 3.0 + a couple of expansions), or from [https://store.steampowered.com/app/429530/Falcon_40/ Steam]. Steam also offers the same package as GOG for a extra cents.<br />
<br />
= Download &amp; install =<br />
<br />
Go to [https://www.falcon-bms.com/downloads/ the official BMS download page] and get either the downloader tool and run it, or get the full installer via torrent. Either way, you end up with the full installer .exe file in a location of your liking &mdash; just run it and follow the instructions.<br />
<br />
== What you get ==<br />
<br />
BMS nature as a community and fan project with a bias towards the more ''involved'' side of flight simming reveals itself immediately when looking at what gets installed by default as part of the download package. In older versions, the collage of special tools and utilities and optional capabilities made for a bit of a mess, but at the same time, an additional fan tool in the form of the &ldquo;alternate BMS launcher&rdquo; was available to guide the user through that jungle.<br />
<br />
In later versions, the launcher is no longer alternate and is instead a default part of the install, and should be the main interface for the regular user as far as getting to the many different components of the game.<br />
<br />
=== BMS Launcher ===<br />
<br />
[[File:Bms-launcher.png|512px|frameless|alt=The BMS launcher.]]<br />
<br />
[[File:BMS updater icon.png|32px|left|frameless]] The launcher offers immediate access to the most common tools one might want to use in connection to BMS: the game update tool, the base configuration tool, the acronym salad of IVC, RTTR, AVC, and the most popular third-party tools.<br />
<br />
[[File:BMS config icon.png|32px|left|frameless]] The launcher also provides a means to set up all the controls and key- and button binds you might need via a modern and highly capable interface. This bypasses the arcane, antiquated, and utterly byzantine input definition system that BMS uses to define its inputs. While the in-game settings screen ostensibly offers a page for button and axis binding, this is a left-over from Falcon 4.0 and '''should not be used''' &mdash; odds are that using it will break things rather than provide any workable binding.<br />
<br />
''Always use the launcher to set and adjust your binds''. This means you have to quit and restart BMS every time you want to make a control setup adjustment, but better that than to run the risk of breaking the bind files by using the in-game bind mechanic.<br />
<br />
For further information, check the [[BMS Configuration]] article.<br />
<br />
=== IVC ===<br />
<br />
[[File:IVC client icon.png|32px|left|frameless]][[File:IVC server icon.png|left|32px|frameless]] IVC, or the &ldquo;Internal Voice Communications&rdquo; tool is the voice communication system for BMS. It is essentially a bespoke TeamSpeak 3 implementation that interfaces with the in-game radios to let players use the in-cockpit radio communication systems (and their related HOTAS controls) to speak to each other.<br />
<br />
IVC consists of a client and a server component. Unless you intend to host a BMS server, the server component can be ignored completely. The client generally auto-launches and auto-connects if a server has IVC set up, but it can also be launched manually if you want to set up the audio devices it should use.<br />
<br />
=== RTT Remote ===<br />
<br />
[[File:RTTR client icon.png|32px|left|frameless]][[File:RTTR server icon.png|32px|left|frameless]] RTT Remote &mdash; the original meaning of which is lost in mists of time &mdash; is an instrument extraction tool for BMS. Beyond the more trivial case of making things like MFDs show up on a separate screen, it also allows for complex setups for pit builders, where a different computer can host the display and feed inputs back from, say, a touch screen over a network connection.<br />
<br />
=== Avionics Configurator ===<br />
<br />
[[File:AVC icon.png|32px|left|frameless]] For anyone who has been frustrated with Eagle Dynamics' philosophy of &ldquo;our SMEs tell us that plane X never flew with Y fitted&rdquo; the Avionics Configurator is the tool that lets you adjust how the different aircraft in BMS are equipped. This allows enterprising game modders to create all kinds of subvariants or frankenplane versions of the already extensive library of F-16s (and other airframes) on offer in the game.<br />
<br />
Its use is more for single-player setups, since this kind of alteration of the core data files can cause a fair amount of conflicts with how planes work and behave in multiplayer unless the same set of alterations are distributed and used by all players.<br />
<br />
=== Editor ===<br />
<br />
[[File:Editor icon.png|32px|fleft|rameless]] Much like how the Avionics Configurator lets you alter aircraft data, the nondescript &ldquo;Editor&rdquo; lets you modify weapons and vehicle data beyond just the avionics of aircraft. Also much like the AC, this kind of editing is more for setting up or tweaking local single-player games, as mismatches can cause conflicts in multiplayer.<br />
<br />
=== Documentation ===<br />
<br />
https://wiki.falcon-bms.com/manuals<br />
<br />
== Additional downloads ==<br />
<br />
https://www.weapondeliveryplanner.nl/download/index.html<br />
<br />
=== Weapons Delivery Planner ===<br />
<br />
[[File:WDP icon.png|32px|left|frameless]] <br />
https://www.weapondeliveryplanner.nl/about/index.html<br />
<br />
=== Mission Commander ===<br />
<br />
[[File:MC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/mc.html<br />
<br />
=== Weather Commander ===<br />
<br />
[[File:WC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/wc.html<br />
<br />
=== F4Wx Real Weather ===<br />
<br />
[[File:F4Wx icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/8267/f4wx-real-weather-converter<br />
<br />
=== F4RADAR ===<br />
<br />
[[File:F4radar icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/18356/f4radar-lightweight-standalone-radar-application<br />
<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Getting_and_installing_BMS&diff=5621Getting and installing BMS2023-01-02T22:23:34Z<p>Tippis: /* BMS Launcher */</p>
<hr />
<div>In the olden days, getting and installing [[Falcon Benchmark Simulator|BMS]] could be a bit of a chore, but at least it was (sort of) free because Falcon 4.0 was largely abandonware and while the installer required you to point to a valid Falcon4.exe file, that file could be &ldquo;found&rdquo; trivially on the internet. The bigger obstacle was a very long and obnoxious registration and log-in requirement to download a multipart sequence of builds and updates from a slow website.<br />
<br />
These days, it costs a trivial amount to get your hands on a legal copy of Falcon 4.0, which you sort of need because the ownership checking is a bit more thorough. But on the other hand, no registration or login is needed (in spite of the official instructions saying so, but they are written for an older version anyway) and between direct download and torrent options, and having a sensible and working updater, the download process is much more palatable.<br />
<br />
To get the instruction from the source, go to the [https://wiki.falcon-bms.com/start-with-falcon-bms/install-update Falcon BMS install/update help page], or directly to the [https://www.falcon-bms.com/downloads/ downloads page], which link to further documentation.<br />
<br />
= Requirements =<br />
<br />
The official requirements are listed as:<br />
* Windows 7 (64 bits)<br />
* i5 2500K 3.3 GHz<br />
* 4Gb RAM<br />
* 3D GFX card 2Gb dedicated VRAM (DX11 compatible mandatory)<br />
* 15Gb HDD space required<br />
<br />
What is ''not'' listed, but requires a special mention in spite of sounding like a trivial detail, is a sound card. It is worth mentioning because even if you intend to install BMS for the purpose of running an online multiplayer server, you ''still'' need that sound card as well as a DX11-compaible graphics card. If you intend to run the server in a virtualised environment, the virtualisation needs to cover those media capabilities as well.<br />
<br />
== Falcon 4.0 ==<br />
<br />
To install [[Falcon Benchmark Simulator|BMS]], you ned to have Falcon 4.0 installed. While you can technically get rid of Falcon 4 once BMS is installed, that adds an unnecessary step to future repairs and re-installs, so the (relatively) piddling size of this late-'90s game might as well be considered part of the BMS installation footprint.<br />
<br />
You can most readily get Falcon 4 from [https://www.gog.com/game/falcon_collection GOG.com] (along with Falcon, Falcon A.T. and Falcon 3.0 + a couple of expansions), or from [https://store.steampowered.com/app/429530/Falcon_40/ Steam]. Steam also offers the same package as GOG for a extra cents.<br />
<br />
= Download &amp; install =<br />
<br />
Go to [https://www.falcon-bms.com/downloads/ the official BMS download page] and get either the downloader tool and run it, or get the full installer via torrent. Either way, you end up with the full installer .exe file in a location of your liking &mdash; just run it and follow the instructions.<br />
<br />
== What you get ==<br />
<br />
BMS nature as a community and fan project with a bias towards the more ''involved'' side of flight simming reveals itself immediately when looking at what gets installed by default as part of the download package. In older versions, the collage of special tools and utilities and optional capabilities made for a bit of a mess, but at the same time, an additional fan tool in the form of the &ldquo;alternate BMS launcher&rdquo; was available to guide the user through that jungle.<br />
<br />
In later versions, the launcher is no longer alternate and is instead a default part of the install, and should be the main interface for the regular user as far as getting to the many different components of the game.<br />
<br />
=== BMS Launcher ===<br />
<br />
[[File:Bms-launcher.png|512px|frameless|alt=The BMS launcher.]]<br />
<br />
[[File:BMS updater icon.png|32px|left|frameless]][[File:BMS config icon.png|32px|left|frameless]] The launcher offers immediate access to the most common tools one might want to use in connection to BMS: the game update tool, the base configuration tool, the acronym salad of IVC, RTTR, AVC, and the most popular third-party tools.<br />
<br />
The launcher also provides a means to set up all the controls and key- and button binds you might need via a modern and highly capable interface. This bypasses the arcane, antiquated, and utterly byzantine input definition system that BMS uses to define its inputs. While the in-game settings screen ostensibly offers a page for button and axis binding, this is a left-over from Falcon 4.0 and '''should not be used''' &mdash; odds are that using it will break things rather than provide any workable binding.<br />
<br />
''Always use the launcher to set and adjust your binds''. This means you have to quit and restart BMS every time you want to make a control setup adjustment, but better that than to run the risk of breaking the bind files by using the in-game bind mechanic.<br />
<br />
For further information, check the [[BMS Configuration]] article.<br />
<br />
=== IVC ===<br />
<br />
[[File:IVC client icon.png|32px|left|frameless]][[File:IVC server icon.png|left|32px|frameless]] IVC, or the &ldquo;Internal Voice Communications&rdquo; tool is the voice communication system for BMS. It is essentially a bespoke TeamSpeak 3 implementation that interfaces with the in-game radios to let players use the in-cockpit radio communication systems (and their related HOTAS controls) to speak to each other.<br />
<br />
IVC consists of a client and a server component. Unless you intend to host a BMS server, the server component can be ignored completely. The client generally auto-launches and auto-connects if a server has IVC set up, but it can also be launched manually if you want to set up the audio devices it should use.<br />
<br />
=== RTT Remote ===<br />
<br />
[[File:RTTR client icon.png|32px|left|frameless]][[File:RTTR server icon.png|32px|left|frameless]] RTT Remote &mdash; the original meaning of which is lost in mists of time &mdash; is an instrument extraction tool for BMS. Beyond the more trivial case of making things like MFDs show up on a separate screen, it also allows for complex setups for pit builders, where a different computer can host the display and feed inputs back from, say, a touch screen over a network connection.<br />
<br />
=== Avionics Configurator ===<br />
<br />
[[File:AVC icon.png|32px|left|frameless]] For anyone who has been frustrated with Eagle Dynamics' philosophy of &ldquo;our SMEs tell us that plane X never flew with Y fitted&rdquo; the Avionics Configurator is the tool that lets you adjust how the different aircraft in BMS are equipped. This allows enterprising game modders to create all kinds of subvariants or frankenplane versions of the already extensive library of F-16s (and other airframes) on offer in the game.<br />
<br />
Its use is more for single-player setups, since this kind of alteration of the core data files can cause a fair amount of conflicts with how planes work and behave in multiplayer unless the same set of alterations are distributed and used by all players.<br />
<br />
=== Editor ===<br />
<br />
[[File:Editor icon.png|32px|fleft|rameless]] Much like how the Avionics Configurator lets you alter aircraft data, the nondescript &ldquo;Editor&rdquo; lets you modify weapons and vehicle data beyond just the avionics of aircraft. Also much like the AC, this kind of editing is more for setting up or tweaking local single-player games, as mismatches can cause conflicts in multiplayer.<br />
<br />
=== Documentation ===<br />
<br />
https://wiki.falcon-bms.com/manuals<br />
<br />
== Additional downloads ==<br />
<br />
https://www.weapondeliveryplanner.nl/download/index.html<br />
<br />
=== Weapons Delivery Planner ===<br />
<br />
[[File:WDP icon.png|32px|left|frameless]] <br />
https://www.weapondeliveryplanner.nl/about/index.html<br />
<br />
=== Mission Commander ===<br />
<br />
[[File:MC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/mc.html<br />
<br />
=== Weather Commander ===<br />
<br />
[[File:WC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/wc.html<br />
<br />
=== F4Wx Real Weather ===<br />
<br />
[[File:F4Wx icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/8267/f4wx-real-weather-converter<br />
<br />
=== F4RADAR ===<br />
<br />
[[File:F4radar icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/18356/f4radar-lightweight-standalone-radar-application<br />
<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Falcon_Benchmark_Simulator&diff=5620Falcon Benchmark Simulator2023-01-02T22:23:06Z<p>Tippis: </p>
<hr />
<div><youtube>https://www.youtube.com/watch?v=658ax0y8KHs</youtube><br />
<br />
[[Getting and installing BMS]]<br />
<br />
[[BMS Configuration]]<br />
<br />
[[Joining a BMS server]]<br />
<br />
[[Fragging a package]], aka creating a flight and joining it.<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=Getting_and_installing_BMS&diff=5619Getting and installing BMS2023-01-02T22:22:20Z<p>Tippis: /* What you get */</p>
<hr />
<div>In the olden days, getting and installing [[Falcon Benchmark Simulator|BMS]] could be a bit of a chore, but at least it was (sort of) free because Falcon 4.0 was largely abandonware and while the installer required you to point to a valid Falcon4.exe file, that file could be &ldquo;found&rdquo; trivially on the internet. The bigger obstacle was a very long and obnoxious registration and log-in requirement to download a multipart sequence of builds and updates from a slow website.<br />
<br />
These days, it costs a trivial amount to get your hands on a legal copy of Falcon 4.0, which you sort of need because the ownership checking is a bit more thorough. But on the other hand, no registration or login is needed (in spite of the official instructions saying so, but they are written for an older version anyway) and between direct download and torrent options, and having a sensible and working updater, the download process is much more palatable.<br />
<br />
To get the instruction from the source, go to the [https://wiki.falcon-bms.com/start-with-falcon-bms/install-update Falcon BMS install/update help page], or directly to the [https://www.falcon-bms.com/downloads/ downloads page], which link to further documentation.<br />
<br />
= Requirements =<br />
<br />
The official requirements are listed as:<br />
* Windows 7 (64 bits)<br />
* i5 2500K 3.3 GHz<br />
* 4Gb RAM<br />
* 3D GFX card 2Gb dedicated VRAM (DX11 compatible mandatory)<br />
* 15Gb HDD space required<br />
<br />
What is ''not'' listed, but requires a special mention in spite of sounding like a trivial detail, is a sound card. It is worth mentioning because even if you intend to install BMS for the purpose of running an online multiplayer server, you ''still'' need that sound card as well as a DX11-compaible graphics card. If you intend to run the server in a virtualised environment, the virtualisation needs to cover those media capabilities as well.<br />
<br />
== Falcon 4.0 ==<br />
<br />
To install [[Falcon Benchmark Simulator|BMS]], you ned to have Falcon 4.0 installed. While you can technically get rid of Falcon 4 once BMS is installed, that adds an unnecessary step to future repairs and re-installs, so the (relatively) piddling size of this late-'90s game might as well be considered part of the BMS installation footprint.<br />
<br />
You can most readily get Falcon 4 from [https://www.gog.com/game/falcon_collection GOG.com] (along with Falcon, Falcon A.T. and Falcon 3.0 + a couple of expansions), or from [https://store.steampowered.com/app/429530/Falcon_40/ Steam]. Steam also offers the same package as GOG for a extra cents.<br />
<br />
= Download &amp; install =<br />
<br />
Go to [https://www.falcon-bms.com/downloads/ the official BMS download page] and get either the downloader tool and run it, or get the full installer via torrent. Either way, you end up with the full installer .exe file in a location of your liking &mdash; just run it and follow the instructions.<br />
<br />
== What you get ==<br />
<br />
BMS nature as a community and fan project with a bias towards the more ''involved'' side of flight simming reveals itself immediately when looking at what gets installed by default as part of the download package. In older versions, the collage of special tools and utilities and optional capabilities made for a bit of a mess, but at the same time, an additional fan tool in the form of the &ldquo;alternate BMS launcher&rdquo; was available to guide the user through that jungle.<br />
<br />
In later versions, the launcher is no longer alternate and is instead a default part of the install, and should be the main interface for the regular user as far as getting to the many different components of the game.<br />
<br />
=== BMS Launcher ===<br />
<br />
[[File:Bms-launcher.png|512px|frameless|alt=The BMS launcher.]]<br />
<br />
[[File:BMS updater icon.png|32px|left|frameless]][[File:BMS config icon.png|32px|left|frameless]] The launcher offers immediate access to the most common tools one might want to use in connection to BMS: the game update tool, the base configuration tool, the acronym salad of IVC, RTTR, AVC, and the most popular third-party tools.<br />
<br />
The launcher also provides a means to set up all the controls and key- and button binds you might need via a modern and highly capable interface. This bypasses the arcane, antiquated, and utterly byzantine input definition system that BMS uses to define its inputs. While the in-game settings screen ostensibly offers a page for button and axis binding, this is a left-over from Falcon 4.0 and '''should not be used''' &mdash; odds are that using it will break things rather than provide any workable binding.<br />
<br />
''Always use the launcher to set and adjust your binds''. This means you have to quit and restart BMS every time you want to make a control setup adjustment, but better that than to run the risk of breaking the bind files by using the in-game bind mechanic.<br />
<br />
=== IVC ===<br />
<br />
[[File:IVC client icon.png|32px|left|frameless]][[File:IVC server icon.png|left|32px|frameless]] IVC, or the &ldquo;Internal Voice Communications&rdquo; tool is the voice communication system for BMS. It is essentially a bespoke TeamSpeak 3 implementation that interfaces with the in-game radios to let players use the in-cockpit radio communication systems (and their related HOTAS controls) to speak to each other.<br />
<br />
IVC consists of a client and a server component. Unless you intend to host a BMS server, the server component can be ignored completely. The client generally auto-launches and auto-connects if a server has IVC set up, but it can also be launched manually if you want to set up the audio devices it should use.<br />
<br />
=== RTT Remote ===<br />
<br />
[[File:RTTR client icon.png|32px|left|frameless]][[File:RTTR server icon.png|32px|left|frameless]] RTT Remote &mdash; the original meaning of which is lost in mists of time &mdash; is an instrument extraction tool for BMS. Beyond the more trivial case of making things like MFDs show up on a separate screen, it also allows for complex setups for pit builders, where a different computer can host the display and feed inputs back from, say, a touch screen over a network connection.<br />
<br />
=== Avionics Configurator ===<br />
<br />
[[File:AVC icon.png|32px|left|frameless]] For anyone who has been frustrated with Eagle Dynamics' philosophy of &ldquo;our SMEs tell us that plane X never flew with Y fitted&rdquo; the Avionics Configurator is the tool that lets you adjust how the different aircraft in BMS are equipped. This allows enterprising game modders to create all kinds of subvariants or frankenplane versions of the already extensive library of F-16s (and other airframes) on offer in the game.<br />
<br />
Its use is more for single-player setups, since this kind of alteration of the core data files can cause a fair amount of conflicts with how planes work and behave in multiplayer unless the same set of alterations are distributed and used by all players.<br />
<br />
=== Editor ===<br />
<br />
[[File:Editor icon.png|32px|fleft|rameless]] Much like how the Avionics Configurator lets you alter aircraft data, the nondescript &ldquo;Editor&rdquo; lets you modify weapons and vehicle data beyond just the avionics of aircraft. Also much like the AC, this kind of editing is more for setting up or tweaking local single-player games, as mismatches can cause conflicts in multiplayer.<br />
<br />
=== Documentation ===<br />
<br />
https://wiki.falcon-bms.com/manuals<br />
<br />
== Additional downloads ==<br />
<br />
https://www.weapondeliveryplanner.nl/download/index.html<br />
<br />
=== Weapons Delivery Planner ===<br />
<br />
[[File:WDP icon.png|32px|left|frameless]] <br />
https://www.weapondeliveryplanner.nl/about/index.html<br />
<br />
=== Mission Commander ===<br />
<br />
[[File:MC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/mc.html<br />
<br />
=== Weather Commander ===<br />
<br />
[[File:WC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/wc.html<br />
<br />
=== F4Wx Real Weather ===<br />
<br />
[[File:F4Wx icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/8267/f4wx-real-weather-converter<br />
<br />
=== F4RADAR ===<br />
<br />
[[File:F4radar icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/18356/f4radar-lightweight-standalone-radar-application<br />
<br />
<br />
[[Category:BMS Articles]]</div>Tippishttps://www.airgoons.com/wiki/index.php?title=File:BMS_config_icon.png&diff=5618File:BMS config icon.png2023-01-02T22:21:57Z<p>Tippis: </p>
<hr />
<div></div>Tippishttps://www.airgoons.com/wiki/index.php?title=File:BMS_updater_icon.png&diff=5617File:BMS updater icon.png2023-01-02T22:21:47Z<p>Tippis: </p>
<hr />
<div></div>Tippishttps://www.airgoons.com/wiki/index.php?title=Getting_and_installing_BMS&diff=5616Getting and installing BMS2023-01-02T22:18:31Z<p>Tippis: </p>
<hr />
<div>In the olden days, getting and installing [[Falcon Benchmark Simulator|BMS]] could be a bit of a chore, but at least it was (sort of) free because Falcon 4.0 was largely abandonware and while the installer required you to point to a valid Falcon4.exe file, that file could be &ldquo;found&rdquo; trivially on the internet. The bigger obstacle was a very long and obnoxious registration and log-in requirement to download a multipart sequence of builds and updates from a slow website.<br />
<br />
These days, it costs a trivial amount to get your hands on a legal copy of Falcon 4.0, which you sort of need because the ownership checking is a bit more thorough. But on the other hand, no registration or login is needed (in spite of the official instructions saying so, but they are written for an older version anyway) and between direct download and torrent options, and having a sensible and working updater, the download process is much more palatable.<br />
<br />
To get the instruction from the source, go to the [https://wiki.falcon-bms.com/start-with-falcon-bms/install-update Falcon BMS install/update help page], or directly to the [https://www.falcon-bms.com/downloads/ downloads page], which link to further documentation.<br />
<br />
= Requirements =<br />
<br />
The official requirements are listed as:<br />
* Windows 7 (64 bits)<br />
* i5 2500K 3.3 GHz<br />
* 4Gb RAM<br />
* 3D GFX card 2Gb dedicated VRAM (DX11 compatible mandatory)<br />
* 15Gb HDD space required<br />
<br />
What is ''not'' listed, but requires a special mention in spite of sounding like a trivial detail, is a sound card. It is worth mentioning because even if you intend to install BMS for the purpose of running an online multiplayer server, you ''still'' need that sound card as well as a DX11-compaible graphics card. If you intend to run the server in a virtualised environment, the virtualisation needs to cover those media capabilities as well.<br />
<br />
== Falcon 4.0 ==<br />
<br />
To install [[Falcon Benchmark Simulator|BMS]], you ned to have Falcon 4.0 installed. While you can technically get rid of Falcon 4 once BMS is installed, that adds an unnecessary step to future repairs and re-installs, so the (relatively) piddling size of this late-'90s game might as well be considered part of the BMS installation footprint.<br />
<br />
You can most readily get Falcon 4 from [https://www.gog.com/game/falcon_collection GOG.com] (along with Falcon, Falcon A.T. and Falcon 3.0 + a couple of expansions), or from [https://store.steampowered.com/app/429530/Falcon_40/ Steam]. Steam also offers the same package as GOG for a extra cents.<br />
<br />
= Download &amp; install =<br />
<br />
Go to [https://www.falcon-bms.com/downloads/ the official BMS download page] and get either the downloader tool and run it, or get the full installer via torrent. Either way, you end up with the full installer .exe file in a location of your liking &mdash; just run it and follow the instructions.<br />
<br />
== What you get ==<br />
<br />
BMS nature as a community and fan project with a bias towards the more ''involved'' side of flight simming reveals itself immediately when looking at what gets installed by default as part of the download package. In older versions, the collage of special tools and utilities and optional capabilities made for a bit of a mess, but at the same time, an additional fan tool in the form of the &ldquo;alternate BMS launcher&rdquo; was available to guide the user through that jungle.<br />
<br />
In later versions, the launcher is no longer alternate and is instead a default part of the install, and should be the main interface for the regular user as far as getting to the many different components of the game.<br />
<br />
=== BMS Launcher ===<br />
<br />
[[File:Bms-launcher.png|512px|frameless|alt=The BMS launcher.]]<br />
<br />
The launcher offers immediate access to the most common tools one might want to use in connection to BMS: the game update tool, the base configuration tool, the acronym salad of IVC, RTTR, AVC, and the most popular third-party tools.<br />
<br />
The launcher also provides a means to set up all the controls and key- and button binds you might need via a modern and highly capable interface. This bypasses the arcane, antiquated, and utterly byzantine input definition system that BMS uses to define its inputs. While the in-game settings screen ostensibly offers a page for button and axis binding, this is a left-over from Falcon 4.0 and '''should not be used''' &mdash; odds are that using it will break things rather than provide any workable binding.<br />
<br />
''Always use the launcher to set and adjust your binds''. This means you have to quit and restart BMS every time you want to make a control setup adjustment, but better that than to run the risk of breaking the bind files by using the in-game bind mechanic.<br />
<br />
=== IVC ===<br />
<br />
[[File:IVC client icon.png|32px|left|frameless]][[File:IVC server icon.png|left|32px|frameless]] IVC, or the &ldquo;Internal Voice Communications&rdquo; tool is the voice communication system for BMS. It is essentially a bespoke TeamSpeak 3 implementation that interfaces with the in-game radios to let players use the in-cockpit radio communication systems (and their related HOTAS controls) to speak to each other.<br />
<br />
IVC consists of a client and a server component. Unless you intend to host a BMS server, the server component can be ignored completely. The client generally auto-launches and auto-connects if a server has IVC set up, but it can also be launched manually if you want to set up the audio devices it should use.<br />
<br />
=== RTT Remote ===<br />
<br />
[[File:RTTR client icon.png|32px|left|frameless]][[File:RTTR server icon.png|32px|left|frameless]] RTT Remote &mdash; the original meaning of which is lost in mists of time &mdash; is an instrument extraction tool for BMS. Beyond the more trivial case of making things like MFDs show up on a separate screen, it also allows for complex setups for pit builders, where a different computer can host the display and feed inputs back from, say, a touch screen over a network connection.<br />
<br />
=== Avionics Configurator ===<br />
<br />
[[File:AVC icon.png|32px|left|frameless]] For anyone who has been frustrated with Eagle Dynamics' philosophy of &ldquo;our SMEs tell us that plane X never flew with Y fitted&rdquo; the Avionics Configurator is the tool that lets you adjust how the different aircraft in BMS are equipped. This allows enterprising game modders to create all kinds of subvariants or frankenplane versions of the already extensive library of F-16s (and other airframes) on offer in the game.<br />
<br />
Its use is more for single-player setups, since this kind of alteration of the core data files can cause a fair amount of conflicts with how planes work and behave in multiplayer unless the same set of alterations are distributed and used by all players.<br />
<br />
=== Editor ===<br />
<br />
[[File:Editor icon.png|32px|fleft|rameless]] Much like how the Avionics Configurator lets you alter aircraft data, the nondescript &ldquo;Editor&rdquo; lets you modify weapons and vehicle data beyond just the avionics of aircraft. Also much like the AC, this kind of editing is more for setting up or tweaking local single-player games, as mismatches can cause conflicts in multiplayer.<br />
<br />
=== Documentation ===<br />
<br />
https://wiki.falcon-bms.com/manuals<br />
<br />
== Additional downloads ==<br />
<br />
https://www.weapondeliveryplanner.nl/download/index.html<br />
<br />
=== Weapons Delivery Planner ===<br />
<br />
[[File:WDP icon.png|32px|left|frameless]] <br />
https://www.weapondeliveryplanner.nl/about/index.html<br />
<br />
=== Mission Commander ===<br />
<br />
[[File:MC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/mc.html<br />
<br />
=== Weather Commander ===<br />
<br />
[[File:WC icon.png|32px|left|frameless]]<br />
https://www.weapondeliveryplanner.nl/about/wc.html<br />
<br />
=== F4Wx Real Weather ===<br />
<br />
[[File:F4Wx icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/8267/f4wx-real-weather-converter<br />
<br />
=== F4RADAR ===<br />
<br />
[[File:F4radar icon.png|32px|left|frameless]]<br />
https://forum.falcon-bms.com/topic/18356/f4radar-lightweight-standalone-radar-application<br />
<br />
<br />
[[Category:BMS Articles]]</div>Tippis