Falcon 4.0 part 11: The (unlucky) OpenFalcon release
- DarkenedRoom
- Oct 3
- 6 min read
Updated: Oct 6
This is not a complete release guide for OpenFalcon due to the issues that have to date, defied a suitable solution and limitations in trying to use an emulation solution. Instead this guide will briefly cover the history, the patches and how to build the release.
The attempts to solve issues with both DirectX wrappers and emulation will be discussed. OpenFalcon is a product of its time, old enough to suffer from legacy DirectX issues but too new to be a suitable candidate for emulation.
Hopefully in the future the information presented here can be revisited, with perhaps later versions of DirectX wrappers, which will allow OpenFalcon to run without issue. Testing was performed with an nVidia graphics card, testing with AMD or Intel cards may yield different results.
OpenFalcon v4.7 is based on BMS 3.0, with the version presented below using BMS 3.9.1.6.
History
The OpenFalcon Group comprised of the remnants of the Realism Patch Group, the Unified Team (responsible for the SuperPaks) and some members of the BMS team. The aim was to create an optimum version of Falcon 4.0. At the time there were competing interests with the FreeFalcon team and the Lead Pursuit commercial offering Allied Force.
The first versions of OpenFalcon, beginning with v4.1 in August 2006 were distributed by word of mouth and/or peer-to-peer file sharing. Subsequent releases would follow a similar pattern culminating in the semi-official v4.5 release in August 2007.
The OpenFalcon community would continue to push hotfixes with v4.6 with the final community version of OpenFalcon v4.7 being released in December 2008.
For a far more detailed and accurate analysis, The Falcon Epopee is highly recommended.
Release patches
There are two patches that are applied for this release. The first is the OpenFalcon v4.5 installation patch, which is the main OpenFalcon patch/packaged installer. The second is the OpenFalcon v4.7 community update.
Neither patch is available on the Internet Archive as they seem to violate the terms of service and are removed. To find these patches requires searching the Internet for:
OF4.5.zip (OpenFalcon v4.5 installer)
OF47Update.exe (OpenFalcon v4.7 update)
Optionally there is a multiplayer enhanced launcher app:
Starting point
The starting point for the release is an install of the cd retail release only. There is no need to apply the last official patch or any other patches.
Building
The following steps are used to build the release under Win10 or a legacy WinXP machine:
Optionally install the full version of HiTiles using the HiTiles installer to create a HiTiles installation folder. This is not the HiTiles installer used to apply tiles from the HiTiles installation folder to a Falcon 4.0 installation.
Optionally update the full HiTiles installation with the HiTiles Balkan update.
Run the OpenFalcon v4.5 installation package to create the OpenFalcon installation. Select the full HiTiles option when shown.
Run the OpenFalcon v4.7 update package to update the OpenFalcon installation.
DirectX wrappers
The following DirectX wrappers were used to try and fix texture issues without success, hopefully a future version of a wrapper will be able to fix the texture issues. This list is included to identify existing wrappers that have been tested.
Actively developed and/or comprehensive wrappers that have been used for many other games:
DxWrapper (v1.3.7700.25 & v1.4.7900.25) tested alone and with ReShade 6.5.1.
DDrawCompat v2.0, v2.1, v3.2 as part of DxWrapper.
ForceD3D9On12 as part of DxWrapper.
DDrawCompat (v0.6.0)
dgVoodoo2 v2.86.2 (using the configuration app from v2.86.1. The v2.86.2 app generates a virus warning under Win10. This may be a false positive).
DxWnd v2_06_10_fx
Less popular/not as actively developed wrappers:
DXGL v0.5.24
d3d8to9 v1.13.0
cnc-ddraw
WINE based wrappers:
WineD3D for Windows v10.15
BoxedWine v20.1.2
Emulation
The following emulators were used to create WinXP virtual machines, and used to run OpenFalcon, either without success or without correcting the texture issue:
PCem v17
86Box (v4.2.1 & v5.1)
Legacy build
The legacy build followed the build instructions listed earlier. It was run on a legacy Win XP Home Edition SP3 machine, Core 2 Duo 6600 @ 2.40GHz, 4GB memory, SSD disk, nVidia GeForce 9800 GTX+. GeForce graphics drivers v340.52 did not suffer the texture problems present on the Win10 machine.
A Logitech X-52 Pro HOTAS was used, utilising native controller support. Track IR was supported in-game, however the Track IR hardware was not compatible with the last Track IR WinXP drivers.
HOTAS config
OpenFalcon has native controller support which means the it use the controller devices present in Windows. For those with separate stick, throttle and rudder pedals, each axis for each device can be configured in game. OpenFalcon supports axis shaping so vendor profiling software may not be needed at all (see In-game config).
However as a test, a TM TARGET profile was added, this may provide higher precision than the default precision provided by Windows, so may feel 'subjectively' better.
The axes were configured as follows:
Physical axis | DX axis |
Stick x-axis | DX_X_AXIS |
Stick y-axis | DX_Y_AXIS |
Throttle | DX_Z_AXIS |
Throttle (2nd engine) | DX_ZROT_AXIS |
Throttle slider | DX_SLIDER_AXIS |
Rudder pedals | DX_XROT_AXIS |
Due to the ability to split the throttle for twin engined aircraft, DX_ZROT_AXIS is assigned as a second throttle axis.
This means an axis is required for the rudder pedals, in this case DX_XROT_AXIS. In the game configuration menus, this axis is assigned as the rudder.
However, the above config limits the number of axes. The advantage of native controller support is the greater number of axes that can be configured (see In-game config), e.g. rudder x and y axes can be configured as left and right toe brake.
For WinXP this was tested with native controller support using a Logitech X-52 Pro. All stick and throttle axes worked as expected. The stick 'twist' axis was used as the rudder. Additional axes present on the throttle could also be used without issue.
Track IR support
Track IR support is built into OpenFalcon and is enabled through the in-game configuration settings with additional settings available with the F4-BMS Config Editor as shown.
The Track IR software should be running before starting the game. It is still recommended to use the Yassy BMS profile.
The Yassy profile is available from the Falcon BMS forum in the TrackIR 4/5 BMS Profile by Yassy topic. The first message uses a Dropbox location, however there are multiple alternatives throughout the thread.
Track IR support functioned normally under Win10 but could not be tested under WinXP as mentioned earlier.
Running
With the change in executable the command to run OpenFalcon becomes:
F4-BMS.exeThere is no need for any command line options.
In-game config
The following is brief look at some of the most noteworthy config options for running. In this example, native controller support is used to assign all of the stick, throttle and rudder axes.
Graphics options
You can use the T&L facilities of your graphics card.
Resolution can be increased to 1600x1200.
Sound options
There are new sound options that can be selected:
UI Radio Chatter
New Engine Sounds.
Enable Doppler Effect
Internal Sounds Outside Cockpit
Controller options
These next panels show examples of the comprehensive native controller support.
This is a reskinned but very similar panel to the standard Falcon 4.0 controller options. The advanced button provides access to further options.
Advanced options: View control
This panel allows selectins an axis to control the field of view or zoom.
3D cockpit options are shown here.
Axis shaping can be enabled on this panel.
Track IR settings can also be configured.
Advanced options: Flight control
Throttle and rudder axess are configured here.
A split throttle for twin engined aircraft is supported.
In this example the rudder x/y axes control the left and right toe brakes.
Advanced options: Avionics control
Further axes can be configured here.
In this example the antenna elevation is controlled with the throttle slider axis.
The MFD x/y cursor movement is controlled with the throttle x/y axes.
Documentation
OpenFalcon comes with a comprehensive set of documents including (but not limited to):
Realism Patch 5 manual.
SuperPak 3 manual.
SuperPak 4 manuals.
BMS 2.0 manual
BMS-34 manual
HFFM manual.
Airport layout and navigation charts.
Keymap layouts.
HOTAS layouts.
Mirage 2000 manual.
Eurofighter Typhoon manual.
Multi-Command handbook.
OpenFalcon noob guide.
OpenFalcon v4.7 update guide.
That should be enough to be getting on with!
Example video
Finally...
Credit and thanks go to the OpenFalcon Team for all their hard work in creating this upgrade to Falcon 4.0. We can only hope a future DirectX wrapper will allow us to fully enjoy it under Win10/11.
Good hunting!
Comments