Falcon 4.0

» see microprose.com as it lived, on the wayback machine

~ the goodbye ~

i remember falcon 4.0 from the late-90s pc magazine window. by '98 i was fourteen, on a 33.6k modem at home in ankara, reading bilgisayar dünyası and pixel and the international magazines that landed at the news stand on tunalı. falcon 4.0 was in every preview rotation for two years before it shipped, with cover features promising the most ambitious civilian f-16 sim anyone had tried to ship. the dynamic campaign was the headline. you would fly missions inside a war that was actually being run by an underlying simulation, not a scripted scenario list.

i never bought it. my rig at the time was a pentium ii 233 with 32 mb of ram and an s3 trio64 card, which would have run falcon 4.0 at a slideshow. the recommended spec was a pentium ii 300 with a real 3d card and 64 mb of ram, the kind of machine i would not have until 2001. the sim was for the dedicated, the people who built dedicated rigs with hotas sticks and printed-out kneeboards.

microprose released falcon 4.0 on december 11 1998 in north america and december 18 in the uk. the alameda studio had been developing the project since 1992, originally inside spectrum holobyte before the 1993 microprose merger. hasbro interactive owned the parent company by the time the box hit shelves, having closed the seventy million dollar tender offer in august. the launch was buggy. magazines that gave it 95 percent reviews still printed the bug list as a sidebar. patches came every few weeks through 1999.

~ the chronicle ~

~ what it actually was ~

falcon 4.0 was a complete f-16c block 50 simulation with a real flight model, a real avionics suite, and a real korean peninsula war happening in the background. the dynamic campaign generated missions based on the current state of the front line. air tasking orders, ground orders of battle, fuel consumption by squadron, all of it ran whether the player was flying or not. you could fly one mission while the rest of the war kept moving without you. nothing else in the consumer sim space worked that way.

the manual was 600 pages of f-16 systems documentation, written by ex-air force pilots and avionics engineers under the supervision of a former f-16 instructor named pete bonanni. the printed manual alone was longer than the source novel of most rpgs that shipped that year. people who had never been near a real cockpit learned to start the engine through a printed checklist that took twenty minutes to execute. you did not casually open falcon 4.0 for a quick mission after dinner.

~ how it actually ended ~

the source code leaked online on april 9 2000, between official patches 1.07 and 1.08. kevin klemmick later claimed responsibility for the leak in a forum post years later. microprose was already winding down, hasbro had announced studio cuts, the alameda office that built falcon 4.0 was closing within the year. the official patch line stopped at 1.08. there was no falcon 5.0 in development that survived the shutdown.

the leak turned out to be the saving event. several community teams forked the leaked source and started fixing the bugs the official team never got to. realism patch, superpak, open falcon, all came out of the leaked code. by 2003 the community had a more stable falcon 4.0 than microprose ever shipped. falcon bms split off from open falcon in 2003 and became the main fork by the end of the decade.

~ the long tail ~

falcon bms version 4.38 shipped in july 2025. that is twenty-seven years after the original retail release. the bms team has rewritten most of the avionics, added new aircraft, updated the campaign generator, ported it to modern windows. the engine is still recognizably the same alameda code from 1998 underneath. it has the longest community-maintained tail of any commercial flight sim ever shipped.

the lesson the bms run teaches is awkward for the industry. falcon 4.0 the retail product failed in the marketplace. falcon 4.0 the codebase has outlived every commercial competitor that came out the same decade. the only thing the alameda team needed for the project to keep going was for the project to escape them. the box copy from 1998 promised a sim that would be the f-16 reference for years to come. it has been the f-16 reference for almost three decades because nobody at the publishers gets to decide when it stops.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »