top of page

Search Results

Search this site

221 results found with an empty search

  • F-16 Aggressor: Aggressively fixing issues

    This is a guide on running F-16 Aggressor in Windows 10. F-16 Aggressor was developed by General Simulations Incorporated (GSI) in 1998. Based on the F-16C Fighting Falcon the game is often considered a spiritual successor to Origins' Strike Commander as with both games you play as a mercenary carrying out missions for the highest bidder. For the rest of the guide F-16 Aggressor will be referred to as Aggressor. Contents Strategy This guide is laid out a little differently to improve consistency. There is a preparation section covering media image creation and game management. Installation shows the installation process with points to note. Graphics, sound and movie sections covering the compatibility tools to use to fix those components. The control section covers joystick/HOTAS config and other controls like head tracking. Documentation covers where to find documentation including supplemental documents often not included in re-releases. An example video section to show the results and finally credit and thanks. Version & patch history There have been surprising few official releases of Aggressor and there have been no official patches released for the game. Initial retail release (1998) The initial retail release occurred in 1998. Developed by General Simulations Incorporated (GSI) and published by Virgin Interactive Entertainment and Bethesda Softworks. It was distributed on a single CD-ROM and features a 32-bit installer, making it compatible with Win10. No CD patch (Mar 1999) The only unofficial patch was a no cd CD patch release in Mar 1999, by an unknown creator. It is a file replacement patch replacing the game executable. This patch is available from GameCopyWorld but is not recommended as it results in the CD audio tracks no longer playing during the game. Sold Out Software re-release (2001) The Sold Out Software budget re-release was published in 2001. It was released on 2 x CD-ROMs with the first CD containing Internet Explorer 6, Shockwave Flash, a pdf reader and menu system and a preview of other Sold Out Software releases. The second CD is equivalent to the initial retail release and continues to use a 32-bit installer. Preparation The following section covers ripping retail media, recommended mounting tools and game management. Retail media Due to the age or the media and the drives required to read it, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The CD-ROMs should be ripped to a bin/cue image pair format to preserve the CD audio tracks. Only the second CD of the Sold Out Software re-release needs to be ripped. CD images It is recommended that a CD image tool be used to allow CD images be mounted, such as Daemon Tools Lite v11 (an earlier free version without ads) or WinCDEmu, as this allows the CD audio to be played during the game. Game management It is recommended to use a game management strategy or similar. The recommended game management folders are: cd - for any CD images. conf - for joystick/HOTAS configuration files and to store DIrectX wrapper files/settings in sub-folders, if you to wish to try an alternative wrapper. docs - for game documents. patch - for compatibility patches. These management folders can be found in the following game folder (as an example): X:\Games\Win\F-16 Aggressor Setup Alongside the Aggressor installation folder: X\Games\Win\F-16 Aggressor Installation The following gallery shows the steps involved in installing the game: Running The game requires the CD/image to be mounted before running the game. The game is run with the following: f-16.exe Graphics The compatibility tools recommended for Aggressor are DDrawCompat or dgVoodoo2. DDrawCompat provides a 'softer' image and may be a preferable for those wishing to use the original 4:3 aspect ratio. However, playing the intro movie with DDrawCompat is often problematic. dgVoodoo2 provides a 'harder' image and due to the verticality of the cockpit in a 4:3 aspect ratio, running in a 16:9 stretched aspect ratio is possible and may provide a better image with dgVoodoo2. Movies play more consistently with dgVoodoo2 although there is some stuttering at higher resolutions. Although the game also supports Glide, at present attempts to use Glide under Win10 have proven unsuccessful. Using Glide in the game may required a PCem or 86Box virtual machine using an emulated 3Dfx card which is out of scope for this guide. The following galleries shows DDrawCompat and dgVoodoo2 graphics in-game at a 1024x768 resolution: The choice of wrapper is left to personal preference. Note the Display Device field. Both wrappers will exhibit a display device issue, where resolutions are shown in the display device field preventing the game from starting (see screenshot). This is suspected to be due to both wrappers providing more resolutions to the game than it can handle. The configs for both wrappers adjust the config to prevent this issue. dgVoodoo2 The version used is dgVoodoo v2.87.3. It is available from the dgVoodoo2 GitHub, Releases. To install: Download dgVoodoo2 (dgVoodoo2_87_3.zip) and extract to a new folder. Copy the following dgVoodoo2 files to the Aggressor installation folder. Note: the paths are not important you just need to add the files: dgVoodooCpl.exe MS\x86\D3D8.dll MS\x86\D3D9.dll MS\x86\D3DImm.dll MS\x86\DDraw.dll The following gallery shows the config for dgVoodoo2. To access the extended options right click in the dgVoodoo banner and select, Show all sections of the configuration. In the General tab, the scaling mode can be set to Stretched (for 16:9) or Stretched, 4:3 Aspect Ratio. In the DirectX tab, the Resolution should set to Unforced. In the GeneralExt tab, in System hooks, both GDI and Cursor should be checked. In the DirectExt tab, in Enumerated resolutions, the Defaults should be set to Classics. In the DirectExt tab, in Enumerated resolutions, additional resolutions can be set in Extras field as a comma separated list in the format: x@. Only a few should be set, too many will result in the display device issue occurring. The above config is included below: DDrawCompat The version used is DDrawCompat v0.7.1. It is available from the DDrawCompat GitHub, Releases. To install: Download DDrawCompat (DDrawCompat-v0.7.1.zip) and extract ddraw.dll to the Aggressor installation folder. A DDrawCompat config file (DDrawCompat.ini) is required and can be found below. It should be downloaded and extracted to the Aggressor installation folder. This file can be edited to replace the 1600x1200 or 1920x1200 resolutions with your own prefered resolution. Sound The following compatibility tools to enable sound should both be used. Compatibility database A Microsoft compatibility database is required for Aggressor. The database patch can be opened and examined in the Microsoft Compatibility Administrator (32-bit), part of the Microsoft Application Deployment Kit (ADK). For further info on the Microsoft Compatibility Administrator see, A retro gamers friend: Microsoft Compatibility administrator. Download the patch and extract to a folder. The zip archive comprises of: PatchInstall.bat, to install the database. PatchUninstall.bat, to remove the database. F-16 Aggressor.sdb, the compatibility database containing the fix F-16 Aggressor.sdb contains a single compatibility fix, EnableHardwareMixer. It forces legacy applications or video games that rely on DirectSound or older Windows audio wrappers to utilize hardware-accelerated audio mixing rather than falling back to software emulation. Run PatchInstall.bat, to install the database. DSOAL DSOAL (DirectSound via OpenAL) is used to improve the sound in the game, e.g. it stops the engine drowning out the instructors voice. Those wishing to use headphones may wish to experiment with settings in alsoft.ini to optimise sound. The latest version is used, DSOAL r694 + OpenAL Soft r10692, available from DSOAL GitHub Releases. The following files should be extracted from the zip/7z archive into the Aggressor installation folder: \DSOAL\Win32\dsoal-aldrv.dll \DSOAL\Win32\dsound.dll \DSOAL\Win32\alsoft.ini Note: the file paths are not copied into the installation folder, just the files themselves Movies The intro movie uses the Intel Indeo v5.0 codec. If Indeo videos are playing correctly on your machine the following installation advice may not be required. Installation If the intro movie does not play then the codec may be disabled. One method is to download and install the K-Lite Codec Pack. The Basic install is known to include these codecs, (as listed on the Comparison of abilities page) and after installation the K-Lite Codec Pack Tweak Tool can be used to enable them (if not already). The K-Lite Codec Pack is available from Codec Guide, Download K-Lite Codec Pack. Playing Playing the intro movie may be problematic when using DDrawCompat. dgVoodoo2 is usually more successful but at higher resolutions there may be some stuttering. To play the movies smoothly, using the in-game configuration to: Switch the Graphics Device to Software: DirectDraw. Switch the Resolution to 640x480 (8 bit). After playing the movie, switch back to your preferred device and resolution. Controls The following section covers joystick/HOTAS setup and head tracking. HOTAS config Joystick, throttle and rudder pedals are supported. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. The physical axes to Windows axes were configured as follows: For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controllers are detected by Aggressor. [6][7][8]. The physical axes to Windows axes were configured as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder DX_ZROT_AXIS Additional settings In addition to the above, the device (physical or virtual) to use must be set as the Preferred device in the Advanced options of the Windows Game Controllers panel (joy.cpl) as shown below: Head tracking The Aggressor virtual cockpit uses a mouselook scheme to look around the virtual cockpit, enabled by holding the right mouse button and disabled by releasing the button. The head tracking will be pitch (y-axis) and yaw (x-axis) only as these are the only facilities provided by the underlying mouselook mechanism. Fortunately this head tracking to mouse conversion is well supported. There are two recommended methods utilising this conversion, detailed below. TrackIR This is a pure TrackIR solution, it uses the standard TrackIR 5 software and the TrackIR utility, TrackIR Mouse Emulation (TIRmouse.exe). This is found in the TrackIR install folder. Once a profile is configured for Mouse Emulation in the TrackIR 5 software, the mouse emulation utility is run. Head motion should now be reflected in the mouse emulation utility. The utility must remain open and in the foreground (until covered by the game window), it can not be minimised and will not run in the background. OpenTrack Opentrack has been covered in combination with AITrack in the article, Head tracking with Opentrack & AITrack. The Opentrack utility supports mouse emulation, so Opentrack and AITrack provide the head tracking solution, and instead of sending TrackIR data to Super Hornet, Opentrack can send mouse data, allowing head tracking in the virtual cockpit. In-game configuration The in-game configuration is straightforward once a 3D hardware graphics device is selected with a preferred resolution, all other options are enabled or set to maximum. Sound volume is a personal preference with other options enabled, as shown below: Documentation The only known documentation is the manual. This is available on the CD of the initial retail release and on the first CD of the Sold Out Software re-release. The only known on-line copy is available from Old-Games.RU, F-16 Aggressor, Files as a rar archive/pdf document. Example video F-16 Aggressor using dgVoodoo2, DSOAL, stick throttle and rudder pedals in 1920x1200 resolution. Finally... Credit and thanks goes to: The developers of Daemon Tools Lite and WinCDEmu. narzoul for DDrawCompat. dege for dgVoodoo2. kcat for DSOAL. Codec Guide for hosting the K-Lite Codec Pack. The developers of TrackIR. The OpenTrack and AITrack developers. Old-Games.RU for hosting documentation. Good hunting!

  • Silent Thunder: A-10 Tank Killer 2: Deadzone defeated!

    This is a guide on fixing the onerous deadzone problem present in Silent Thunder: A-10 Tank Killer 2. The previous Silent Thunder guide, Silent Thunder: A-10 Tank Killer 2: Boxing clever to defeat the dead zone, covered an alternative mapping profile to try to solve the problem of an extensive deadzone on the x and y axes. Although this alternative profile helped, it wasn;t as intuitive and required careful flying. Contents Strategy This time we'll be using vJoy coupled with a Joystick Gremlin profile, this time using intuitive controls coupled with deadzone handling to finally fix these issues. An improved choice of a CH Flightstick Pro and CH Pedals as the HOTAS device in 86Box and Win98 will complete the setup. This is a supplemental article only and to setup other game components, the original Silent Thunder: A-10 Tank Killer 2: Boxing clever to defeat the dead zone, guide should be iued. Compatibility tools configuration For this solution the vJoy/Joystick Gremlin combo will be used to correct the deadzone issue. Joystick Gremlin (JG) is used to set a deadzone on our joystick response for x and y axes. This effectively causes the joystick response to 'jump past' the in-game deadzone on these axes providing more responsive behaviour. Each tool will be configured manually in addition command line options are provided which would prove useful for inclusion in startup scripts. Further details on command line options can be found in Controllers and retro sims part 10: vJoy/Joystick Gremlin/HidHide command line options. vJoy config Silent Thunder supports 4 axes (x, y, z and rotation x), 8 buttons (although the device emulated in 86Box will be a 4 button CH Flightstick Pro) and a single POV hat. In vJoy this is configured as follows: vJoyConfig.exe Enable on vJoyConfig.exe 1 -f -a X Y Z Rx -b 4 -p 1 vJoy configuration Joystick Gremlin config The Joystick Gremlin configuration is a key part of the solution. Instead of mapping directly to a vJoy axis the x and y axes are modified by a JG response curve prior to mapping to a vJoy axes as shown in the screenshot: Joystick x-axis with deadzone added. The joystick x and y axis have a deadzone added with the Response Curve action. A deadzone of 0.25 is applied, (highlighted in red), although the exact value may be dependent on the physical joystick. It is recommended to use the cursor keys to precisely define equal dead zones on each side of the centre point. Once the dead zone is defined the Map to vJoy action is added. The example above shows the response curve for the x-axis. The response curve for the y-axis is identical. The command line options to load and start a Silent Thunder profile (SilentThunder.xml) are: "X:\\joystick_gremlin.exe" --start-minimized --enable --profile "X:\\SilentThunder.xml" HidHide config In this instance HidHide is not required and can be omitted or left disabled. This is due to 86Box joystick input settings allowing a particular device to be selected, in this case the vJoy virtual controller, and ignoring other controllers. Emulation configuration The following section covers the HOTAS configuration by emulation components, the 86Box emulator and Win98 OS running within the emulator. 86Box HOTAS config The 86Box configuration remains identical to the original virtual machine in Silent Thunder: A-10 Tank Killer 2: Boxing clever to defeat the dead zone, except for the following joystick input device: Input devices Joystick: CH Flightstick Pro + CH Pedals If an 86Box profile already exists for Silent Thunder, this profile can be modified. The input device settings and vJoy to CH Flightstick Pro + CH Pedals mappings are shown below: Win98 HOTAS config In Control Panel the Game Controllers option allows a CH FlightStick Pro to be added. As pedals are also available the rudder option is checked. For those without a rudder axis this can be omitted. Finally the CH FlightStick Pro is calibrated and once calibrated can be tested. In-game configuration The In-game configuration remains unchanged from Game config in Silent Thunder: A-10 Tank Killer 2: Boxing clever to defeat the dead zone. Finally... Credit and thanks in providing a Silent Thunder deadzone solution goes to: The developers of 86Box. The developers of vJoy and Joystick Gremlin. Good hunting!

  • Silent Thunder: A-10 Tank Killer 2: Boxing clever to defeat the dead zone

    A guide to running the sequel, Silent Thunder: A-10 Tank Killer 2 to the classic, A-10 Tank Killer. Developed by Dynamix and published by Sierra in 1996, Silent Thunder tries to one up the original in every department, more missions, more weapons, insanely large targets, the graphics are textured, the sound is improved and the soundtrack isn't half bad... and the joystick dead zone, is larger than ever. What could have been a fun little sim, is dealt a huge blow by the awful dead zone which feels even larger than the one they introduced with A-10 Tank Killer v1.5. It's hard to tell exactly how large of a dead zone is, but at a rough estimate approximately 35%-45% on each half of each axis making it borderline unplayable with a stick. These seems like an bizarre decision for a game that supports stick, throttle and rudder, so presumably was expected to be played with a period HOTAS. What's even stranger is that the dead zone is only present on the x and y axis, with the throttle and rudder axes operating normally! Can this sim be saved and made playable with a HOTAS? Contents Strategy The retail install cd supports both Win3.1 and Win95 which means DOSBox Staging running Win3.x, PCem or native Win10 are all potential options to run the sim, but the most stable seems to be 86Box. Building a suitable VM becomes an important part of the install. When it comes to HOTAS config, creating a stick, throttle and rudder config is straightforward but suffers from the excessive deadzone on the stick axes. However, this can be used to create a suitable HOTAS in the VM and calibrate it in-game. Once fully calibrated another HOTAS config is created replacing the absolute axes with key mappings. This increases responsiveness to the same level as keyboard control at the cost of converting stick absolute axes into relative axes. Like the prequel A-10 Tank Killer v1.5, using the keyboard remains a viable option for playing this sim. An option made more attractive by the patch which introduces self levelling controls on the roll (x) axis. Version & patch history Initial retail release (Feb 1996) Developed by Dynamix and released by Sierra On-Line in Feb 1996 on a single cd-rom. The game featured both Win3.x and Win95 installers. This initial retail version is v1.0. The release notes (converted to pdf) are shown below: Silent Thunder Patch v1.01 (May 1996) The one and only patch was released in May 1996, upgrading the version to v1.01. This is a bug fix and enhancement patch. The bugs fixed include: joystick code changes, increased sound card support, better DirectDraw support and flight model changes. Enhancements include: a new joystick calibration option, an additional DirectSound option and weapons release changes. This patch is a self installing executable. This is a recommended patch for the initial retail v1.0 release. This patch can be found at: Internet Archive Old-Games.RU The Sierra Help Pages, A-10 Tank Killer Series Updates Compilation releases (1997-2000) Silent Thunder was included in a number of compilation releases from 1997 until 2000. It's not known which version was included with each compilation, but it is expected to be v1.0A. Xplosiv retail re-release (2003) The Empire Interactive budget label, Xplosiv released Silent Thunder in 2003 on a single cd-rom. This is v1.0A (v1.0 pre-patched with the Silent Thunder Patch v1.01) created at the same time as the patch in May 1996. Both Win3.x and Win95 installers are included. Media This guide assumes any physical cds will be ripped to an image file, to reduce wear and tear on media and drives. The retail versions of Silent Thunder contains 12 cd music tracks and should be ripped to a bin/cue image pair format to preserve the music. At present there is no digital release of Silent Thunder. Game Management As a windows game running under 86Box emulation, the installation folder will be created in the 86Box virtual machine. However some limited game management is still useful for files used in the setup. The setup files for Silent Thunder can be found in the same 86Box setup folder (my own, as an example): D:\Games\86Box\ D:\Games\86Box\Silent Thunder Setup The following setup folders can be used: cd - to store any cd images. conf - to store any HOTAS profile configuration files. docs - to store any useful documents, manuals, etc. patch - to store a copy of recommended patches. 86Box The optimum method of running Silent Thunder is with 86Box emulation. This guide assumes the latest version of 86Box, (v5.3 build 8200 at time of writing). This is available from 86Box GitHub repository Releases. Virtual Machine (VM) The Silent Thunder release notes state the minimum spec is a 486 DX 66, 8MB RAM, Win95. The spec used is higher, but not too high. Having a spec that runs the game too quickly and makes it unplayable is not the intended result. Instead the spec used is: System Machine: [ALi ALADDiN V] ASUS P5A CPU: Intel Pentium / 120 MHz Memory: 128 MB Display Video: [AGP] 3dfx Voodoo3 3000 Storage Disks: 3.2 GiB (IDE) Floppy: 3.5" 1.44M CD-ROM: 32x 86Box 86B_CD 3.50 (ATAPI) Audio Audio: [ISA16] Sound Blaster 16 MIDI Out: System MIDI Network NIC: None Input devices Keyboard: PS/2 Keyboard Mouse: PS/2 Mouse Joystick: CH Flightstick + CH Pedals Ports Serial ports: None Parallel ports: None The preferred operating system is Windows 98 Second Edition (Win98SE). Notes The above is a suggested spec only and can be changed if required. The following can be changed to suit personal preferences: A 3.2GB hard disk is large enough but can be larger. Audio is provided by a Sound Blaster 16 but an AWE 32 could also be used. MIDI Out is using the host Win10 MIDI support but this can be changed to an 86Box emulation option. A Network Interface Card (NIC) is not required and has been omitted. The Joystick option is suitable for a 4-axes HOTAS. Those with 3 or fewer axes may wish to omit rudder pedals or switch to an option which more closely matches their joystick hardware. Serial and parallel ports are not required and use machine resources that could be allocated elsewhere. Configuration The following is the configuration file created by 86Box for this specification. It is the config file only and does not contain a hard disk image with Win98SE. 86Box should be used to replace the hard disk image in this config file with one of your own. Building the VM A complete set of instructions to build an 86Box Win98 virtual machine is beyond the remit of this guide. However, before trying to create your own it is recommended to become familiar with the process by reading the following guide by milnak: Install Windows 98 SE in 86Box Phil of PhilsComputerLab has produced the following recommended video. The video description contains links to some downloads also used in this virtual machine. 86Box Windows 98 Setup Notes The following notes are supplemental to the above to assist in creating a virtual machine. The hard disk image file type should be vhd. This hard disk image type can be mounted in Win10. This allows downloaded zip file contents to be extracted in Win10 and then copied onto the mounted vhd disk image. The disk image can then be ejected in Win10 and used with 86Box to run the virtual machine. Before installing Win98SE the BIOS configuration menus should be used to disable serial and parallel ports in the virtual machine. A Win98SE OEM installation cd image should be used, as this is a bootable cd image which does not require a separate floppy boot disk image. A suitable image may be obtained from WinWorld. This virtual machine should not require additional chipset drivers, being fully supported by Win98SE. The Voodoo 3 drivers used are Voodoo 3 driver kit v1.07.00 (voodoo3tm_driver_kit_1.07.00-whql.zip) available from PhilsComputerLab. The Sound Blaster 16 drivers are included in the Win98SE cd image, however the latest Win98 drivers for the Sound Blaster 16/AWE 32 (sbw9xup.exe) are available from PhilsComputerLab. This virtual machine uses DirectX 6.1a included as part of the Win98SE cd image. Once complete the Win98 Device Manager should show all hardware working and there should be no errors reported from the DirectX diagnostics, as shown below: Taking a copy Once the virtual machine is built and working it is recommended to take a copy of the 86Box virtual machine folder or to zip up the virtual machine folder. This ensures a 'clean' working virtual machine is available for any other future games requiring a similar virtual machine to be emulated. HOTAS Config Joystick, throttle and rudder are supported by Silent Thunder. Configuring axes may not be required if your single device HOTAS has 4 axes or less. When using multiple HOTAS devices totaling more than 4 axes, a virtual controller can be used, limited to 4 axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controller is detected by 86Box. Setup config As 86Box only supports a single HOTAS device, we can create a fairly standard 'setup' 4 axis virtual controller in Win10 (see setup axis mapping). This controller can be mapped to the 86Box CH FlightStick and CH pedals joystick devices configured in 86Box. Once the 86Box VM is started, the CH FlightStick & pedals are added in Win98SE and calibrated. This 86Box virtual device can be used in Silent Thunder. When playing a mission for the first time the in-game joystick calibration is used to ensure a well calibrated controller. 86Box mapping 86Box joystick mapping The following screenshot shows a fairly standard axes mapping, from the Win10 virtual controller to the 86Box virtual controller. The Device is the Win10 virtual controller as seen by 86Box. Win98SE controller As a CH FlightStick and pedals have been configured in 86Box we now need to add them to Win98SE. In Control Panel the Game Controllers option allows a CH FlightStick to be added. As pedals are also available the rudder option is checked. For those without a rudder axis this can be omitted. Finally the CH FlightStick is calibrated and once calibrated can be tested. This concludes the HOTAS config until the game is installed and the in-game preferences are set. Play config This Win10 'setup' virtual controller can continue to be used, but if we wish to increase x-axis and y-axis responsiveness we can change the config (or create a new config) to replace the DirectX axes with roll and pitch 'hold' keypresses instead to create a 'play' virtual controller. As an example the changes are shown in this TARGET config. Similar functionality exists in Joystick Gremlin, you may have to split axes, and then map each side of the split axis to the appropriate hold keypress. e.g. split the x-axis into two and map the left side to a roll left hold keypress and map the right side to a roll right hold keypress. The existing 86Box mapping and Win98SE controller remain unchanged. Due to the previous 'setup' controller calibration we know the throttle and rudder should remain well calibrated. We can't calibrate the 'play' controller as it is sending keypresses rather than DirectX axis data for the x-axis and y-axis. This may be easier to visualize using the axis mapping table below. Axis mapping The physical axes to Windows axes were configured as follows for setup and play virtual controllers: Physical axis Windows axis (setup) Windows axis (play) Joystick x-axis DX_X_AXIS Roll left and right hold keypress Joystick y-axis DX_Y_AXIS Pitch up and down hold keypress Throttle DX_Z_AXIS DX_Z_AXIS Rudder DX_XROT_AXIS DX_XROT_AXIS Installation To install the Silent Thunder cd image should be mounted in the 86Box virtual cd drive. The cd can opened to begin the install process. Note: There should be no virtual hard disk or cd-rom images mounted in Win10 before installing Silent Thunder as they will be identified by 86Box and cause the testing phase of the installation to fail with an error. If this occurs shutdown the virtual machine, unmount the images and restart the virtual machine. The Sierra installation menu allows the hardware to be tested, which can be done first or as part of the install process. The installation process is shown in the gallery below: Running To play Silent Thunder the cd image must remain mounted in the 86Box virtual cd drive. Game config In-game configuration options are accessed through the Preferences menu option (see screenshot). Sound, Direct Sound, Voice, Music, Joystick, Clouds and Fullscreen can be enabled. Low Res should be disabled. Detail and Distance options should be set to maximum. Initial mission After starting the initial mission (use the Fly One Mission option and select the training mission), the Preferences should be accessed and the Joystick Calibration performed. It is recommended to fly the training mission with this 'setup' joystick control scheme, the keyboard control scheme and the 'play' joystick control scheme to find your preferred scheme. To set the 'play' joystick control scheme, see Play config. Documentation The core documentation is supplied as a Windows help file, available in game. However certain releases also supplied an installation booklet and quick reference card available from: Internet Archive, Installation booklet, pdf document. Internet Archive, Quick reference card, pdf document. Old-Games.RU, pdf documents. Example video Silent Thunder running in an 86Box virtual machine Finally... Credit and thanks go to: The Internet Archive and Old-Games.RU for hosting the patch and documation. The Sierra Help Pages for hosting the patch. The developers of 86Box. milnak for the Win98 installation guide for 86Box. Phil of PhilsComputerLab for his Win98 installation video for 86Box and for hosting Voodoo 3 and Sound Blaster drivers. WinWorld for hosting Win98 Second Edition. The developers of vJoy, Joystick Gremlin and HidHide. RedLir Live for the Joystick Gremlin split axes video. Good hunting!

  • F-22 Raptor: A dinosaur in Windows

    F-22 Raptor is one of NovaLogic's light sim offerings in the same vein as MiG-29 Fulcrum or F-16 Multi-Role Fighter. The second sim to feature the F-22, it was essentially a Win95 remake of the earlier DOS based F22 Lightning II. However unlike these later sims F-22 Raptor (F-22) has one serious disadvantage which was it's reliance on the WinMM library which preceded DirectX. In later years this would result in the sim being incompatible with DirectInput and USB controllers, causing the sim to fall by the wayside. This guide will get F-22 running in the Win10 and with working joystick or HOTAS controllers using a number of open source tools to do so, breathing new life into this legacy sim. Contents Strategy A previous guide, F-22 Raptor: Running in PCem covered running this game in the PCem emulator. This time the game will be running natively in Win10. The WinMM controller issue has been covered in detail in the previous article, Controllers & retro sims part 11: The WinMM problem, so this guide will cover configuration and settings to implement the optimised solution. Patch and version history This is a brief version and patch history, the are no version numbers shown in game and the patches are organised by date only as they would normally be obtained from the NovaLogic FTP site, when the NovaWorld app was run or via an update utility in-game. Original retail release (November 1997) The original retail release was developed and published by NovaLogic in 1997. It was distributed on a single CD-ROM. This release uses a 32-bit Windows installer compatible with Win10. No version number is listed for the release. Update 30 June 1998 The 30 June 1998 update is not a complete patch but a replacement update tool that is designed to contact NovaLogic FTP servers for additional patch files. The FTP servers are no longer operational and this patch is superseded by a later patch, making this patch unnecessary. It is not known what the complete collection of patch files changed but may have been a multiplayer based patch. This patch uses a 32-bit installer making it compatible with Win10. It is available from the following site, but Win10 flags it as a (false positive) infected download: NovaLogic FTP server (f22r_update_063098_xx.exe) Update 7 September 1999 The 30 June 1998 update installs the Integrated Battle Space (IBS) app, allowing F22 Raptor players to fly alongside F-16 Multi-Role Fighter and MiG-29 Fulcrum players in a multiplayer environment. This patch does not seem to update any single player game files. This patch uses a 32-bit installer making it compatible with Win10. It is available from: NovaLogic FTP server (f22r_update_070999_xx.exe) Jet Pack compilation release (June 2001) The NovaLogic Jet Pack was a compilation release of MiG-29 Fulcrum, F-22 Raptor and F-16 Multi-Role Fighter. Released in 2001 it was published by NovaLogic and distributed on 3 x CD-ROM, one for each of the products. Although unconfirmed it would be expected to be multiplayer pre-patched using 32-bit installers and Win10 compatible. MiG-29 Fulcrum / F-22 Raptor compilation release (2002) Published by Focus Multimedia in 2002, this was a compilation release of MiG-29 Fulcrum and F-22 Raptor. It was distributed on 3 x CD-ROM, one for each of the games and a manual and patches CD, featuring manuals and patches for a variety of NovaLogic games. Although unconfirmed it would be expected to be multiplayer pre-patched. The installers are 32-bit making them compatible with Win10. Retail media Due to the age or the media and the drives required to read it, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The CD-ROMs can be ripped to a data only .iso image format as there is no CD audio on the CD. Game management It is recommended to use my game management strategy or similar strategy you may have developed. The recommended game management folders for F22 are: cd - for any cd images. conf - to store HOTAS configuration files. docs - for documents. patch - to store any patches. tools - as a compatibility tool installation folder. The F22 management folders would be found in the following game folder (as an example): D:\Games\Win\F22 Raptor Setup Installation The F22 installer app (setup.exe) is an 32-bit app compatible with Win10. It should be run from the CD/image to install the game. The setup is straightforward and is shown in the gallery below: Once the file copying is complete, DirectX 6.0 should NOT be installed. Patching Due to the multiplayer nature and early release date of the patches, it is recommended that the game remain unpatched for all releases. For those wishing to experiment with multiplayer it is recommended to only update the original retail release with the Update 7 September 1999. Compatibility tools The following compatibility tools allow this Win95/98 game to run successfully under Win10. Further background information on the controller optimised solution can be found in Controllers & retro sims part 11: The WinMM problem. The GremlinEx (GEX) and XInput Plus (XIP) tools both provide configuration options, however GEX provides most of the configuration with XIP limited to essential configuration only. dgVoodoo2 Graphics compatibility is provided by dgVoodoo2, created by Dege. The dgVoodoo2 wrapper is used to wrap DirectX components. The version used is v2.87.3. It is available from the dgVoodoo2 GitHub repository, Releases. To install: Download dgVoodoo2 (dgVoodoo2_87_3.zip) and extract to a new folder. Copy the following dgVoodoo2 files to the F-22 installation folder. Note: the paths are not important you just need to add the files: dgVoodooCpl.exe MS\x86\D3D8.dll MS\x86\D3D9.dll MS\x86\D3DImm.dll MS\x86\DDraw.dll Configuration Download and extract the dgVoodoo.conf in the below zip file, to the F-22 installation folder. In the DirectX section the dgVoodoo Watermark is turned on for testing purposes, once confirmed working it can be turned off. ViGem Bus Driver The ViGem Bus Driver (ViGem), created by Benjamin Höglinger-Stelzer, allows the creation and configuration of a virtual XBox 360 XInput controller similarly to vJoy creating and configuring a virtual DirectInput controller. The recommended ViGEm Bus Driver version is the latest one, ViGEmBus Setup 1.22.0 "It's dead, Jim" Release available from GitHub ViGEm Bus Driver repository, Releases. Installation is straightforward using the executable installer app, ViGEmBus_1.22.0_x64_x86_arm64.exe. GremlinEx GremlinEx (GEX), created by muchimi, extends the original Joystick Gremlin and allows multiple DirectInput devices to be mapped to a single XInput device using the ViGEm Bus Driver. Although stated in earlier articles the following points are worth repeating: GEX is still very much a work in progress with continuous releases of varying robustness. Although GEX seems to function reliably during gaming, exceptions and faults should be expected when configuring devices. Since configuration is an initial 'one and done' task, this should be considered a fairly minor issue. It is recommended to save frequently when creating the config. GEX uses the older Joystick Gremlin release 13 style of configuration. Those familiar with the release 14/15 style will need to adapt to this older style. GEX takes longer to start than Joystick Gremlin as it needs to initialise ViGEm. The recommended version is the latest release candidate, which changes frequently (so is not listed). It is available from JoystickGremlinEx repository, Releases. Installation is straightforward using the installer zip package. It should be downloaded and extracted into a suitable folder. Update: Once installed it is recommended to go to Tools > Options > VIGEM and ensure the Gamepad count is set to 1 (see screenshot). A setting of 0 will disable ViGEm. HOTAS config Configuring axes will be required no matter how many axes are available as DirectInput axes are mapped to XInput axes. It is recommended that most of the HOTAS configuration be carried out in the GEX tool, limiting XInput Plus configuration as much as possible. Those with fewer than 4 axes should map remaining axes to the keyboard in the in-game configuration. Those with fewer than 4 buttons should leave any remaining buttons unconfigured. For further background material on this HOTAS config, it is recommended to consult the optimized solution covered in Controllers & retro sims part 11: The WinMM problem. Stick, throttle and rudder are supported. The physical axes to Xinput and F-22 axes were configured as follows: Physical axis XInput axis F-22 axis Joystick x-axis Left stick x-axis Roll axis Joystick y-axis Left stick y-axis* Pitch axis Joystick button 1 Button A Button 1 Joystick button 2 Button B Button 2 Joystick button 3 Button X Button 3 Joystick button 4 Button Y Button 4 Throttle Right stick y-axis* Throttle axis Rudder Right stick x-axis Rudder/yaw axis Note: Axes marked with * may require the axis to be inverted in GEX. It is recommended to use a profile name that explicitly indicates it is a GEX profile, e.g. F22-raptor-gex.xml. XInput Plus XInput Plus, created by 0dd14lab, is a tool that allows you to configure detailed settings for XInput controllers, e.g. XBox 360 controllers, such as key assignments, input sensitivity, axis inversion, auto-fire, hold, and vibration intensity. The recommended version is the latest one, v4.16.1, available from 0dd14lab, Download. Once downloaded the installer package (XInputPlus Ver4.16.1.zip) should be extracted to a suitable folder. Configuration The following gallery shows the configuration settings to be applied to XIP: Configuration should not be attempted until a suitable F-22 profile has been loaded into GEX and enabled. The following gallery shows the limited settings that should be applied to XIP. The Target Program box should be set to the game executable (Raptor.exe). In the Vibration tab, vibration settings should be disabled. In the DirectInput tab: Enable DirectInput Output should be checked. The Right Stick (x/y axes) should be set to Z Rot/Z Axis. The LT/RT triggers should be set to Button 11/12, so they do not interfere with the Right Stick. The Info tab should show a single XInput controller (created by GEX and ViGem). The Total Test button will show a representation of a controller, which can be used to test XInput axes and buttons. The menu button, ≡ is used to save settings, from the drop down menu select, Apply Only Ini File. Creating the launcher shortcut XInput Plus Loader XInput Plus includes a loader utility, XInput Plus Loader (XInputPlusLoader.exe) which is used to create a shortcut to forcibly inject the appropriate wrapper, (WinMM in this case) into the game. To create this shortcut: Go to the XIP installation folder and then into the Loader folder. Open XInputPlusLoader.exe. Select Create ShortCut. Drag the game executable (Raptor.exe) into the XInputPlusLoader app window (see screenshot). A shortcut (Raptor - XInputPlus) will be created on the desktop. Optionally, rename and/or move/copy this shortcut into a suitable location. In plain sight (HidHide) F-22 Raptor is very robust and indifferent to additional devices being present. It seems to ignore both DirectInput and XInput devices. This means that a HidHide device firewall can be omitted. The optimised controller solution remains unchanged. The ramp start (running) Due to the required order of running tools and the limited command line options available to GEX, running the game requires a manual or 'ramp start' sequence. The steps are as follows: Mount the F-22 Raptor CD/image in Win10. Start GEX, load the F-22 profile (e.g. F22-raptor-gex.xml) and enable the profile. Start the game using the XInput Plus launcher shortcut, e.g. Raptor - XInputPlus. When the game is quit, to return the system to a clean state: Disable the iF-22 profile and close GEX. Eject the F-22 CD/image. In-game configuration In game controller configuration is straightforward and is shown in the below screenshot: Documents The following documents are available: User manual, pdf document. Internet Archive, F-22 Raptor: Users Manual (borrow only). The following documents are available from: Old-Games.RU, F-22 Raptor, Files as rar achives, pdf documents: User manual. Quick start guide. Reference card. Keyboard overlay. Example video F-22 Raptor with stick, throttle and rudder pedal support. Finally... Credit and thanks goes to the following individuals and groups for making the game accessible under Win10: NovaLogic for hosting patches. Benjamin Höglinger-Stelzer for ViGEm Bus Driver. muchimi for GremlinEx. 0dd14lab for XInput Plus. Dege for dgVoodoo2. Internet Archive and Old-Games.RU for hosting documents. Hap for GremlinEx, ViGEm options. Good hunting!

  • iF-22: Windows is alright for controllers and flight

    A guide for adding joystick and HOTAS support to Interactive Magic's iF-22. iF-22 has been notoriously difficult to get USB or DirectInput controller to work. This guide will be covering a solution to this problem using a number of open source projects. Note: The following solution was developed and tested on Win10, but remains untested on Win11. Contents Before we begin Strategy Tools ViGem Bus Driver GremlinEx HOTAS config Xidi HidHide Configuration Ramp start (running) In-game configuration Remaining issues Example video Finally... Before we begin This guide is a continuation from the earlier, iF-22: Infuriating F-22! guide. As such it assumes: iF-22 has been installed and patched as appropriate. DDramCompat and the specific iF-22 DDrawCompat fixes have been obtained and utilised. ViGem Bus Driver may have already been installed, but this is not a prerequisite. HidHide may have already been installed, but this is not a prerequisite. vJoy, Joystick Gremlin, XOutput and x360ce may have been installed. These tools are not used in this guide and the decision to keep or remove them is left to personal preference, they should not interfere with the required tools specified below. The following RetroBridge config and libraries are not used and should be removed from the iF-22 installation folder (if present): retrobridge.config.yml retrobridge_core.dll winmm.dll Strategy The strategy employed uses the optimized solution covered in Controllers & retro sims part 11: The WinMM problem. As the background material has already been covered, this guide will concentrate on installation and configuration settings for the tools used. The GremlinEx (GEX) and Xidi tools both provide configuration options, however only GEX is configured, with Xidi using a default configuration. The reasons for a single GEX config are as follows: Spreading the config between GEX and Xidi makes the config more complex and less intuitive and more difficult to manage. It is assumed that GEX will be easier to configure, as it based on an earlier version of Joystick Gremlin, which many will already be familiar with, despite GEX using an earlier Joystick Gremlin configuration style (release 13 and earlier), rather than the current style (release 14/15). GEX provide finer grain config options that some may wish to use, e.g. response curves. GEX can be used to map additional buttons, not used by Xidi, to keyboard commands. Tools It is recommended to keep a copy of the tools installation files in the game management tools folder for safe-keeping. ViGem Bus Driver The ViGem Bus Driver (ViGem), created by Benjamin Höglinger-Stelzer, allows the creation and configuration of a virtual XBox 360 XInput controller similarly to vJoy creating and configuring a virtual DirectInput controller. The recommended ViGEm Bus Driver version is the latest one, ViGEmBus Setup 1.22.0 "It's dead, Jim" Release available from GitHub ViGEm Bus Driver repository, Releases. Installation is straightforward using the executable installer app, ViGEmBus_1.22.0_x64_x86_arm64.exe. GremlinEx GremlinEx (GEX), created by muchimi, extends the original Joystick Gremlin and allows multiple DirectInput devices to be mapped to a single XInput device using the ViGEm Bus Driver. Although stated in earlier articles the following points are worth repeating: GEX is still very much a work in progress with continuous releases of varying robustness. Although GEX seems to function reliably during gaming, exceptions and faults should be expected when configuring devices. Since configuration is an initial 'one and done' task, this should be considered a fairly minor issue. It is recommended to save frequently when creating the config. GEX uses the older Joystick Gremlin release 13 style of configuration. Those familiar with the release 14/15 style will need to adapt to this older style. GEX takes longer to start than Joystick Gremlin as it needs to initialise ViGEm. The recommended version is the latest release candidate, which changes frequently (so is not listed). It is available from JoystickGremlinEx repository, Releases. Installation is straightforward using the installer zip package. It should be downloaded and extracted into a suitable folder. GremlinEx (GEX) Update: Once installed it is recommended to go to Tools > Options > VIGEM and ensure the Gamepad count is set to 1 (see screenshot). A setting of 0 will disable ViGEm. HOTAS config Configuring axes will be required no matter how many axes are available as DirectInput axes are mapped to XInput axes. It is recommended that the HOTAS configuration be carried out in the GEX tool only. Xidi should use its default configuration. Those with fewer than 4 axes should map remaining axes to the keyboard in the in-game configuration. Those with fewer than 4 buttons should leave any remaining buttons unconfigured. For further background material on this HOTAS config, it is recommended to consult the optimized solution covered in Controllers & retro sims part 11: The WinMM problem. Stick, throttle and rudder are supported. The physical axes to Xinput and iF-22 axes were configured as follows: Physical axis XInput axis iF-22 axis Joystick x-axis Left stick x-axis Roll axis Joystick y-axis Left stick y-axis* Pitch axis Joystick button 1 Button A Button 1 Joystick button 2 Button B Button 2 Joystick button 3 Button X Button 3 Joystick button 4 Button Y Button 4 Throttle Right stick x-axis Throttle axis Rudder Right stick y-axis* Rudder/yaw axis Note: Axes marked with * may require the axis to be inverted in GEX. The XInput throttle and rudder axes may seem counterintuitive but will be correct in the game. It is recommended to use a profile name that explicitly indicates it is a GEX profile, e.g. iF-22-gex.xml. Xidi Xidi, created by Samuel Grossman, improves the gameplay experience when using modern XInput-based controllers (such as Xbox controllers) with older games that use DirectInput or WinMM to communicate with game controllers. Xidi was originally rejected as a solution but this may have been due to the recommended Hookshot method used, which may have tried to use DirectInput and DirectInput wrapper libraries with iF-22. The method presented below only uses the winmm.dll library copied into the game installation folder. The recommended Xidi version is the latest one, v5.0.0, available from GitHub Xidi repository, Releases. To install: The installer package, Xidi-v5.0.0.zip, should be downloaded and extracted. The libraries used should be 32-bit to match the 32-bit iF-22 game not 64-bit. They can be found in the Win32 folder. The following libraries should be copied into the iF-22 installation folder: Winmm.dll Xidi.32.dll Although the Hookshot method, using the HookModule form of Xidi is recommended, this should be avoided to prevent DirectInput library use. HidHide HidHide is a device firewall created by Benjamin Höglinger-Stelzer, hiding devices from any app not explicitly allowed through the firewall. The recommended HidHide version is the latest one, HidHide Drivers v1.5.230, available from GitHub HidHide repository, Releases. Installation is straightforward using the executable installer app, HidHide_1.5.230_x64.exe. Configuration In order for iF-22 to start and work with controllers, GEX and the Xidi libraries should be allowed to see through the device firewall with all devices hidden from iF-22. The affected part of the optimised solution is shown below: The following application and libraries should be added to the list of applications allowed to see through the firewall: gremlinex.exe (GremlinEx/GEX) Winmm.dll (Xidi 32-bit library) Xidi.32.dll (Xidi 32-bit library) GEX needs to see through the firewall to map physical DirectInput controllers to a virtual XInput controller. The Xidi libraries need to see through the firewall to receive the virtual XInput controller inputs and pass them to the game. All controllers including physical DirectInput and virtual XInput controllers must be hidden by HidHide. Example config settings are shown in the gallery below: Ramp start (running) Due to the required order of running tools and the limited command line options available to GEX, running the game requires a manual or 'ramp start' sequence. The steps are as follows: Start GEX, load the iF-22 profile (e.g. iF-22-gex.xml) and enable the profile. Start HidHide and ensure, in the Devices tab, all controllers including the Controller (XBOX 360 For Windows) virtual controller is hidden. Check the Enable device hiding checkbox and close HidHide. Go to the iF-22 installation folder and run the game, if22.exe. When the game is quit, to return the system to a clean state: Uncheck the Enable device hiding checkbox and close HidHide. Disable the iF-22 profile and close GEX. In-game configuration This section supplements the exiting In-game configuration in the earlier, iF-22: Infuriating F-22! guide. The following gallery shows the settings for joystick, throttle and rudder pedals: Remaining issues Further work corrected a broken Indeo video codec installation with the K-Lite codec pack tweak tool. This fixed the video playback, however, the WinMM library used by Xidi seems to have issues with video playback so the animations should remain disabled. Example video iF-22 with full HOTAS support Finally... Credit and thanks go to the following individuals without which, iF-22 would still be languishing without joystick or HOTAS support:: Samuel Grossman for Xidi. Benjamin Höglinger-Stelzer for ViGEm Bus Driver. muchimi for GremlinEx. Hap for the GemlinEx, ViGem options. Good hunting!

  • Controllers & retro sims part 11: The WinMM problem

    This article will be taking a look the problems associated with games that use the legacy WinMM library for joystick support. This games have had particular problems under the latest versions of Win10/11 rendering them unplayable with modern controllers. This article will be explaining the problem and a solution to enable full HOTAS support for these games. In order to help understanding, the problem and solutions will be broken down into smaller problems and solutions, working backwards from the game to physical controllers. The complete solution is presented, before an optimised solution is discussed. Finally, the role of device hiding will be covered. Contents The problem The WinMM problem/solution The XInput problem/solution The multiple controller problem/solution The complete solution The optimized solution A place for (Hid) hiding F22 Raptor (NovaLogic) iF-22 (Interactive Magic) Finally... The problem Windows Multimedia API (WinMM) was first released in October 1991, as part of Windows 3.0 with Multimedia Extensions 1.0. With the release on Win95 in August 1995 it transitioned into the 32-bit WinMM library. DirectX was released soon after in September 1995 as the Windows Game SDK (DirectX v1.0). However not all games released around this time would use DirectX and some would only support the existing WinMM library. Fast-forward to the present day and with modern multi-controller HOTAS and DirectInput devices, the games relying on the WinMM library will either fail to recognise modern controllers or even freeze or hang during startup. The WinMM library works with the legacy style gameport controllers. However modern PCs not longer have a gameport and solutions for using these controllers usually involves converting them into a USB device. Trying to fly these flight sims without a joystick or HOTAS becomes rather difficult and not at all intuitive. The WinMM problem/solution The first problem is to get the WinMM library to work with a USB controller. It would be preferable if it were a DirectInput device (which joysticks/HOTAS are), but any controller would be better than nothing. When looking at replacement WinMM libraries or WinMM wrappers, most are designed to fix issues with the multimedia/MIDI components and there are few, if none, specifically designed to fix joystick issues. However, a different approach provides a solution. XInput was the controller library developed for the XBox in December 2005 and integrated into DirectX in April 2006 as XInput 1.1. XInput in a simpler library than DirectInput and provides a controller library for XInput controllers like the XBox 360 controller. Games must support XInput in order to use XInput libraries. MicroSoft made the 360 controller both an XInput and DirectInput device to provide DirectInput compatibility, however customisation was often limited. The customisation issue resulted in various open source projects to improve the situation with DirectInput mapping and some would go on to provide support for WinMM. Two such projects are: Xidi, a DirectInput interface for XInput controllers, created by Samuel Grossman. XInput Plus, a tool which performs a setup of an XInput device, created by 0dd14lab. This provides us with a WinMM wrapper/library that is compatible with an XInput controller, as shown below: The XInput problem/solution The next problem is now to create an XInput controller. Fortunately both Xidi and XInput Plus require a logical XInput controller, this can be: A physical XInput controller, e.g. an XBox 360 controller. A virtual XInput controller. This means a method is needed to convert a DirectInput joystick/HOTAS into a virtual XInput controller. Fortunately such an open source project exists, the ViGEm Bus Driver. ViGEm Bus Driver is a Windows kernel-mode driver emulating well-known USB game controllers, created by Benjamin Höglinger-Stelzer. ViGEm Bus Driver does not provide a configuration tool, so for such a tool, other open source projects are required. Two such projects are: XOutput, created by Ármin Csutorás. x360ce, created by the x360ce team. The above tools were primarily designed to map a single DirectInput device to a virtual XInput device, for those with a single DirectInput device this may be sufficient, as shown below: The multiple controller problem/solution The XOutput and x360ce tools in combination with the ViGEm Bus Driver, seems to solve the problem. However, these tools do not work well with multiple DIrectInput devices. There can be freezes or a loss of response with one or more of the DirectInput controller. Fortunately the logical DirectInput device used by XOutput or x360ce can be: A physical DirectInput device. A virtual DirectInput device. The final problem and solution is to convert multiple DirectInput devices into a single virtual DirectInput device. This issue has already been encountered many times and the solution is to use vJoy and Joystick Gremlin, as has been discussed previously, [6][7][8], and shown below: The complete solution The individual solutions can now be combined into a single workflow, converting multiple modern joystick/HOTAS devices into a device which can be supported by a WinMM wrapper, used by the game: This is a complex workflow, but it proves WinMM can work with multiple modern HOTAS controllers. However, with many 'moving parts'/components, more things can go wrong. Can this solution be optimised to make it simpler and more robust? The optimized solution The complete solution above relies in WinMM libraries/wrappers that cannot be changed, but the multiple DirectInput devices converted to a single XInput device can be simplified, with a single tool, GremlinEx (GEX), created by muchimi. From the GitHub repository: GremlinEx (GEX) is a universal controller integrator: it allows you to take input from multiple hardware devices from different manufacturers connected to a local machine, or a remote machine, such as joysticks and HID controllers, OSC (Open Sound Control), MIDI, Keyboard and mouse inputs and map them to virtual outputs like VJOY, or keyboard or mouse output, convert text to speech and play sounds. It can send output to a game or another process. GremlinEx extends the original Joystick Gremlin and allows multiple DirectInput devices to be mapped to a single XInput device using the ViGEm Bus Driver, used in the complete solution. This drastically simplifies the workflow and the number of 'moving parts'. However, the following points should be noted: GremlinEx is still very much a work in progress with continuous releases of varying robustness. Although GremlinEx seems to function reliably during gaming, exceptions and faults should be expected when configuring devices. Since configuration is an initial 'one and done' task, this should be considered a fairly minor issue. GremlinEx uses the older Joystick Gremlin release 13 style of configuration. Those familiar with the release 14/15 style will need to adapt to this older style. Utilising GremlinEx, the optimized solution is shown below: A place for (Hid) hiding So far the role of device hiding has not been discussed with the compete or optimised solution we may have the following devices present: Physical DirectInput controllers. Virtual DirectInput controller. Virtual XInput controller. Which of these devices (if any) should be visible through a device firewall like HidHide? The answer is game specific and is best explained with examples: F22 Raptor (NovaLogic) F22 Raptor is very robust and indifferent to additional devices being present. It seems to ignore both DirectInput and XInput devices. This means that a HidHide device firewall isn't required and can be omitted. The optimised solution remains unchanged. iF-22 (Interactive Magic) iF-22 is the exact opposite of F-22 Raptor. If any DirectInput or XInput devices are detected it will hang during startup. iF-22 requires a HidHide device firewall to hide all devices, both physical and virtual. In order for iF-22 to start and work with controllers, GremlinEx and the Xidi libraries should be allowed to see through the device firewall with all devices hidden from iF-22. The affected part of the optimised solution is shown below: Finally... Credit and thanks go to the following individuals and teams without which these old sims would never work on later Windows systems: Samuel Grossman for Xidi. 0dd14lab for Xinput Plus. Benjamin Höglinger-Stelzer for ViGEm Bus Driver. Ármin Csutorás for XOutput. The team behind x360ce. muchimi for GremlinEx. Good hunting!

  • Wing Commander III: Heart of the Tiger: Big cats playing in a DOSBox & staring out of Windows

    A guide to running DOS versions of Wing Commander III: Heart of the Tiger in DOSBox Staging. Converting DOS version to Windows compatible versions and optimising these to run natively in Win10. The third game in the Wing Commander series marked a radical change in the technology. The colorful animated cutscenes of I and II replaced with Full Motion Video featuring Hollywood actors, Mark Hamill, Malcolm McDowell, Tom Wilson, Jason Bernard, Ginger Lynn and featuring the voice acting talents of Tim Curry. The bitmaps of the previous games replaced with texture mapped polygons. The campaign marks a culmination of 30 years of war with the Kilrathi with the conflict ending one way or another. At the time it was considered groundbreaking blurring the lines between game or interactive movie and breaking records in game production costs at $3m. For the rest of this guide Wing Commander III: Heart of Tiger will be referred to as WC3. This guide will only be covering DOS and Windows versions. For further background information on WC3 it's recommended to take a look at the Wing Commander CIC. Contents Strategy Version & patch history CD retail edition (November 1994) ATI Mach 64 Patch (1994) Alternate Joystick Routines (January 1995) Joystick Patch for Notebook Gameport (May 1995) QVision Video Patch (May 1995) Joystick Patch for Thrustmaster FCS (TM) and 100%-compatible joysticks (Logitech Wingman Extreme) (May 1995) Kilrathi Saga edition (September 1996) EA CD-ROM Classics edition (1997) Windows 2000 Update (Kilrathi Saga edition) (May 2004) Movie Crashing Patch (Kilrathi Saga edition) (March 2009) DDHack (2010) Digital edition (September 2011) Wing Commander Loader (March 2020) Wing Commander 3 HD Video Pack (March 2021) Wing Commander III Enhancement Patch (May 2024) Wing Commander III Enhancement Patch VLC libraries (March 2025) Restored Scenes IFF Packs (February 2026) Patching strategies CD Retail, EA CD-ROM Classics and digital editions (DOSBox) CD Retail, EA CD-ROM Classics and digital editions (Windows 10/11) Kilrathi Saga edition Retail media Game management HOTAS config DOS editions HOTAS config DOSBox Staging config Installation and configuring Retail CD edition Merging discs Digital edition Sound options Sound Blaster Roland music Roland MT-32/LAPC-1 Roland Sound Canvas General MIDI music VirtualMIDISynth and MIDIMapper WC3 Launcher Installing Windows editions Wing Commander Loader (DOS editions) Retail CD version Creating a WingLoader compatible install Digital version Creating a fresh install Kilrathi Saga edition Installing Wing Commander III Enhancement Patch (all editions) Optional: Installing Wing Commander 3 HD Video Pack (all editions) Patching with Wing Commander Loader (DOS editions) Running Configuring Enhancement patch config (optional) In-game config HOTAS config (optional) Documents Digital edition Extras Novels Strategy guides Kilrathi Saga edition Other editions Strategy guides Example videos Finally... Strategy This guide is split into two main sections. The first covers the DOS version of the game, either the CD retail or the digital release running in DOSBox Staging. It will cover the various options for running the DOS version including recommendations. One advantage of the DOS version is the wide range of MIDI music options available. The second section covers converting the DOS releases to a native Windows release. It will also cover the fan made patches available to support the game under Win10 and optional patches to run an enhanced version of the game. It covers the steps necessary to convert one edition of the game in another and then the steps to create an enhanced version of the game compatible with Win10/11. Version & patch history The version and patch history provides an overview of the various releases over time and the patches they support. Not only is this useful for a DOS based DOSBox release or native Win10 release but may also be of use to those wishing to run the game on legacy hardware. This also helps avoid downloading patches that aren't required. CD retail edition (November 1994) The original CD retail edition was distributed in November 1994 on 4 x CD-ROM's. This is a DOS only release. ATI Mach 64 Patch (1994) An official patch from Origin Systems Inc. This patch fixes distorted videos in the Wing Commander III demo only for the ATI Mach 64 video card. It is not a recommended patch as it is only applicable to specific legacy hardware running the demo. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, ATI Mach 64 Patch. Alternate Joystick Routines (January 1995) This is an official patch from Origin Systems Inc. Taken from the release notes: This alternate joystick DLL (set of alternate routines) is being provided for users who are experiencing problems with Wing Commander III's initial joystick calibration phase during the install program. You must have a joystick to use this patch. This is not a recommended patch and is only applicable for those having issues with legacy joysticks on legacy hardware. It is not required when using DOSBox on Win10/11. It is available from: Internet Archive, Wing Commander III joystick calibration-fix. Internet Archive, Game Patches and Fixes Archive Letter W Wing Commander CIC, Wing Commander Encyclopedia, Alternate Joystick Routines. Joystick Patch for Notebook Gameport (May 1995) This is an official patch from Origin Systems Inc. Taken from the release notes: WC3JOY.DLL is a set of alternate joystick routines used to provide support for Colorado Spectrum's Notebook Gameport. Joysticks tested with the Notebook Gameport in combination with this patch include the CH Flightstick, the CH Flightstick Pro, the Thrustmaster FCS, and the Gravis Analog Pro. This is not a recommended patch and is only applicable for those having issues with legacy joysticks on specific legacy hardware. It is not required when using DOSBox on Win10/11. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, Colorado Spectrum Joystick Patch. QVision Video Patch (May 1995) This is an official patch from Origin Systems Inc. Taken from the release notes: VIDEO.DLL is an alternate set of video routines used to provide support for certain video cards. VIDEO.DLL installs itself when Wing Commander III is initialized. The VIDEO.DLL that accompanies this text file is to be used for the Compaq QVision card only. During initialization, the patch will attempt to detect the Compaq QVision. If the Compaq QVision is not detected, the patch will not install itself and display a message asking you if you wish to continue. If the Compaq QVision is detected, a message will let you know the DLL was installed and you should be able to use the SVGA capabilities of the Compaq QVision. This is not a recommended patch and is only applicable for those having issues with specific legacy hardware. It is not required when using DOSBox on Win10/11. It is available from: Internet Archive, Wing Commander III SVGA-patch for Compaq Qvision. Wing Commander CIC, Wing Commander Encyclopedia, QVision Video Patch. Joystick Patch for Thrustmaster FCS (TM) and 100%-compatible joysticks (Logitech Wingman Extreme) (May 1995) This is an official patch from Origin Systems Inc. Taken from the release notes: WC3JOY.DLL is a set of alternate joystick routines used to provide support for Thrustmaster (TM) and 100%-compatible joystick (such as the Logitech Wingman Extreme). Joysticks tested include the Thrustmaster FCS, the Thrustmaster FLCS, and the Logitech Wingman Extreme. This is not a recommended patch and is only applicable for those having issues with specific legacy joysticks. It is not required when using DOSBox on Win10/11. It is available from: Internet Archive, Wing Commander III Thrustmaster support. Wing Commander CIC, Wing Commander Encyclopedia, Thrustmaster Joystick Patch. Kilrathi Saga edition (September 1996) The Kilrathi Saga is the a compilation of Windows ports of Wing Commander, Wing Commander II and Wing Commander III. This was released on 5 x CDs with the first CD for WC1 & 2 and the remaining 4 for WC3. This was considered the optimum version of WC1 (and still is for WC2) until the AllTinker W.C.A.T. mod for WC1, due to unofficial fan made patches for these games supporting later versions of Windows. EA CD-ROM Classics edition (1997) The EA CD-ROM Classics edition remains the DOS version of the game enhanced with a WIn95 installer app. It was distributed on 4 x CDs. Although not explicitly covered in this guide, once installed in Windows the DOSBox setup process and conversion to a Windows version should be very similar. Windows 2000 Update (Kilrathi Saga edition) (May 2004) Created by NStriker. This patch may also fix compatibility issues in WinXP. Taken from some creator notes: I've created patches for WC3 Kilrathi Saga, WC4 CD, and WC4 DVD that fix an offending API call and allow them to run under Win2K. There still seem to be some outstanding issues like WC3 being unstable in general and I have yet to get my joystick to work in WC4, though I believe neither are related to my patches. This is no longer a recommended patch for WC3 having been superseded by a later 'Mash' patch. Unfortunately it can't be downloaded as Windows 10 reports a probable virus false positive. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, Windows 2000 Update (Kilrathi Saga edition) Movie Crashing Patch (Kilrathi Saga edition) (March 2009) Created by by 'Mash' Matt Wells the first version was released in 2009. The latest release of this patch, v1.2, occurred in May 2011. This patch is compatible with the DDHack patch. Taken from the release notes: This patch is an attempt to fix some of the problems associated with running the Windows version of Wing Commander 3 on modern OSes and on modern hardware. This release includes a fix for the 'Ingame Movie Crashing Bug', a slowdown fix for the Nav Map Screen and a series of slowdown fixes for the Pre Flight Power-up Screen. This patch was created and tested on Windows 7 64 Bit but should also work fine on XP or Vista, 32 or 64 Bit. It will probably work with Windows 2000 as well. No Game files are modified to install this patch. Instead the patch works by pretending to be the Direct Sound Library file (dsound.dll) which the Wing Commander EXE loads itself when it is run. As well as modifying the game the patch also redirects calls made to the real "dsound.dll" where it resides in the Windows System Directory. Note: This patch now exploits the "dsound.dll" rather than the "ddraw.dll" as the previous version. This was done to avoid clashing with Sol_hsa's "DirectDraw Hack" graphics patch. This is no longer a recommended patch for WC3 having been superseded by a later 'Mash' patch. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, Movie Crashing Patch (Kilrathi Saga edition) DDHack (2010) Created by Jari Komppa (Sol). The latest version of this patch is v1.0. Taken from the release notes: This is a replacement ddraw.dll designed to work better with the host environment. Meaning, no palette corruption, no switching the whole system to a different graphics mode, no 256 color mode windows, no need to kill explorer.exe, etc. Technically, it's a DLL that implements the directdraw interface (directdraw, directdraw2, directdrawsurface and directdrawpalette) - or well, the parts of it that I have implemented so far. Then it takes what the game wants to display, dumps it into an OpenGL texture and renders this on screen. ddhack is still at a very early stage, and may be somewhat unstable. It has been mainly tested with the 'kilrathi saga' wing commander 1, wing commander 2, wing commander 3 and wing commander 4 CD. If any other directdraw programs work, it's a miracle! This is no longer a recommended patch for WC3 having been superseded by later patches. It is available from: Google Code Archive, ddhack Wing Commander CIC, Wing Commander Encyclopedia, DirectDraw Hack Digital edition (September 2011) The digital edition is comparable to the CD retail edition. The 4 x CDs of files are merged into a single image file, removing the need for swapping between CD images when playing. The digital edition is available on gog.com and at Electronic Arts. Wing Commander Loader (March 2020) The Wing Commander Loader (or WingLoader) is a utility for launching optimised versions of the Kilrathi Saga versions of WC1 and WC2. However, it also includes patching support for WC3. Created by Destro. the latest version of the WingLoader is v0.92. Taken from the release notes: Wing Loader is a launcher for the Kilrathi Saga versions of Wing Commander 1 & 2 that aims to deliver the most complete versions of these classic masterpieces. Features: Wing Commader III, IV, Prophecy & Secret Ops GOG Support and Wing Commander Saga! What fun! This is the recommended utility for converting from DOS WC3 releases to a Windows compatible release. This utility is available from: MEGA, WingLoader v0.92 - Hotfix.zip Wing Commander CIC, Forums, Wing Commander Chat Zone, Fan Projects & Editing, Wing Loader (KS/WCDX) Loader & Voice Over Mod Wing Commander 3 HD Video Pack (March 2021) The Wing Commander 3 HD Video Pack, created by ODVS is an AI upscaled set of WC3 movies played throughout the campaign. It also includes restored content which was originally missing. The current version of the pack is v2.0. When first released this was not integrated into the game, a situation remedied with the Wing Commander III Enhancement Patch. Taken from ODVS notes: As well as improving remaster quality over V1.0, V2.0 contains the following improvements: All FMV footage remastered to 1080p Full HD using Machine Learning AI Original low frame-rate of 15fps remastered to full 30fps using Machine Learning AI Improved contrast balance in all footage This is a recommended pack for Windows versions of the game, for an optimised experience. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, Wing Commander 3 HD Video Pack Wing Commander III Enhancement Patch (May 2024) The Wing Commander III Enhancement Patch, created by 'Mash' Matt Wells, adds higher resolutions and improved window handling with DirectX 11. It also supports the Wing Commander 3 HD Video Pack and adds native controller support to the game allowing the use of stick, throttle and rudder. The latest version of the patch is v0.14.1. Taken from the GitHub description: This patch was created for the Windows version of the PC game "Wing Commander III". Which came as part of the "Wing Commander Kilrathi Saga" compilation. It can also be used with the GOG DOS version of the game. But will require some extra files and a little more work to set things up. The best and easiest option is to install Wing Loader. Wing Loader also has some upgrades and fixes for other Wing Commander games. This patch uses DirectX 11 for rendering and will likely require Windows 10 or greater to use. This patch makes use of DLL injection to make changes to the game's executable file. And is loaded by the game itself by pretending to be the Direct Draw library file "ddraw.dll". It is thus incompatible with patches which use the same method to load eg. DirectDraw_Hack. HD Movie playback is achieved using libvlc. This is the recommended patch for enhancing WC3 and providing compatibility with Win10/11. It is available from: GitHub, mattwells77, Wing_Commander_III_Enhancement_Patch Wing Commander III Enhancement Patch VLC libraries (March 2025) As the above description notes, 'HD Movie playback is achieved using libvlc.'. This required obtaining all the VLC libraries as part of one complete [package. The Wing Commander III Enhancement Patch VLC libraries (libvlc_min_pack_3.0.21) are the minimal set of VLC libraries required by the enhancement patch. This is recommended patch when running the enhancement patch. It is available from: GitHub, mattwells77, Wing_Commander_III_Enhancement_Patch, Releases, libvlc_min_pack_3.0.21 Restored Scenes IFF Packs (February 2026) The Wing Commander III Enhancement Patch supports the Wing Commander 3 HD Video Pack. The HD Video pack also includes restored content videos, however, having the videos is not enough to restore them in-game. The Restored Scenes IFF Packs (Restored_Scenes_IFF_Packs) are the set of files that restore the restored video content to the game campaign. This is recommended patch when running the Wing Commander III Enhancement Patch and Wing Commander 3 HD Video Pack. It is available from: GitHub, mattwells77, Wing_Commander_III_Enhancement_Patch, Releases, Restored_Scenes_IFF_Packs Patching strategies The following are the recommended patching strategies for each edition. CD Retail, EA CD-ROM Classics and digital editions (DOSBox) Install Wing Commander III release. CD Retail, EA CD-ROM Classics and digital editions (Windows 10/11) Install Wing Commander III release. Install WingLoader utility. Apply Wing Commander III Enhancement Patch. Apply Wing Commander III Enhancement Patch VLC libraries. Optional: Apply Wing Commander 3 HD Video Pack. Optional: Apply Restored Scenes IFF Packs. Patch with WingLoader utility. Kilrathi Saga edition Install Wing Commander III (Kilrathi Saga) release. Apply Wing Commander III Enhancement Patch. Apply Wing Commander III Enhancement Patch VLC libraries. Optional: Apply Wing Commander 3 HD Video Pack. Optional: Apply Restored Scenes IFF Packs. Retail media Due to the age or the media and the drives required to read it, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The CD-ROMs can be ripped to a data only .iso image format as there is no CD audio on the CDs. Game management It is recommended to use my DOSBox game management strategy or similar strategy you may have developed. The recommended game management folders for the DOS version are: cd - for any cd images. hdd - the folder use as the emulated DOSBox hard disk conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store any patches. When using the DOS version of the game, these management folders can be found in the following game folder (as an example): D:\Games\DOS\Wing Commander 3 When using the Windows version of the game (or converting to the Windows version, these management folders can be found in the following game folder (as an example): D:\Games\Win\Wing Commander 3 Setup HOTAS config Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controller is detected by DOSBox. [6][7][8]. There are separate configs for DOS and Windows versions. DOS editions This section of the guide deals with the DOS editions of the game and optimising the DOSBox and installation as much as possible. The DOS version may be preferable for a legacy retro experience or for MIDI music which has a variety of options. HOTAS config Only the joystick is supported with the DOS version. The physical axes to Windows axes were configured as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS DOSBox Staging config The DOS version is configured to run under the latest released DOSBox Staging version, v0.83.0-RC1 (at time of writing). # This is the configuration file for Wing Commander III: Heart of the Tiger. [render] deinterlacing = on [cpu] cpu_cycles_protected = 75000 cycleup = 500 cycledown = 500 [voodoo] voodoo = off [mt32] model = cm32l romdir = "D:\Midi\Versioned" [fluidsynth] soundfont = "Shan SGM Pro 15.SF2" soundfont_dir = "D:\Midi\Soundfonts" [soundcanvas] soundcanvas_model = sc55 soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] # Other valid options: mt32, fluidsynth, port mididevice = soundcanvas [joystick] joysticktype = ch timed = off swap34 = on deadzone = 0 [autoexec] @echo off # Hard disk folder # mount c "D:\Games\Dos\Wing Commander 3\hdd" # Digital edition install folder # mount c "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III" # Retail CD images # mount d "D:\Games\Dos\Wing Commander 3\cd\wc3*.iso" -t cdrom # Merged retail CDs image # mount d "D:\Games\Dos\Wing Commander 3\cd\data.dat" -t cdrom # Digital edition CD image # mount d "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III\data.dat" -t cdrom mixer master 100 /noshow d: wc3.exe pause exit The following zip file contains this example DOSBox Staging config. It should be changed to match your hardware and personal preferences. DOSBox Staging introduces a new deinterlacer feature to remove black lines from full motion videos (FMVs). This is enabled in the [render] section of the config, there are additional settings to control the strength of the deinterlacing. The cpu_cycle setting of 75000 as recommended in the DOSBox Staging wiki. cycleup/down settings are changed to values rather than percentages. Voodoo emulation isn't required and is disabled. The mixer settings are a personal preference. WC3 supports a wide variety of MIDI sound devices including Roland MIDI and general MIDI devices. Sound Blaster is also another option for music. The default Sound Blaster settings are appropriate for Sound Blaster music and digital sounds. Multiple general MIDI devices are configured in the [mt32], [fluidsynth] and [soundcanvas] sections. A Win10 MIDI synth can also be used with DOSBox Staging (see Compatibility tools). The optimum Roland sound settings use the CM32L device, as described in List of MT-32-compatible computer games. The FluidSynth soundfont is a personal preference. In the above example, Shan SGM Pro v15 is used, an excellent general purpose soundfont. DOSBox Staging v0.83.0-RC1 introduces Sound Canvas support. The Sound Canvas config, like the Roland MIDI config, requires a model to be selected and a folder containing the Sound Canvas ROMs to be specified. The MIDI section specifies a the soundcanvas MIDI device as this was the original hardware the game was designed for as noted in List of MT-32-compatible computer games. Alternate DOSBox MIDI components can be chosen or an external Win10/11 MIDI synth (see VirtualMIDISynth and MIDIMapper). The joystick settings are a personal preference and suitable for my joystick hardware. A ch joystick type allows the joystick hat to be used in-game. The autoexec mount settings are examples only, demonstrating how to mount multiple floppy disk images or a cd image for CD or digital editions. The mixer setting restores the master volume to 100%. The game is run from the CD/image. If game config settings aren't available, this will run the installation and configuration utility built into the game. Installation and configuring The DOS version has an unusual installer integrated into the game executable and most game files remain on the CD/image. The first time WC3 is run there are no config files available and the installer utility is run, which created these config files. If the config files are available, the game is run without invoking the install utility. To run the install utility the first time, simply run the game: D:\> wc3.exe Once config files are created the installation utility can be run again with: D:\> wc3.exe -i The steps to configure and install are shown in the gallery below: Retail CD edition For the retail CD version the following mount commands should be used: [autoexec] ... # Hard disk folder mount c "D:\Games\Dos\Wing Commander 3\hdd" # Retail CD images mount d "D:\Games\Dos\Wing Commander 3\cd\wc3*.iso" -t cdrom ... It's assumed the names given to the WC3 CD images will start wc3. The wildcard in the mount command mounts all CD images to the same drive, use Ctrl + F4 to swap between images. Merging discs To prevent CD image swapping mid-game the 4 x CD images can be merged into a single image. The process to do so in Win10 is: Mount the CD image of WC3 disc 1 in Win10 and copy the contents of the CD image to a folder, e.g. D:\Games\DOS\Wing Commander 3\cd\merged Do this for each of the other 3 CD images, replacing duplicate files as required. Use a CD burning/imaging utility (e.g. ImgBurn) to create a CD image of the merged folder contents. Note: only the folder contents/files should be added to the CD image, not the folder itself. Open the new single CD image in Win10 and make sure files can be seen and accessed, e.g. open the readme.txt file. Eject the CD image. The final single CD image can be renamed to data.dat. This creates a suitable CD image suitable for conversion to a Windows version. The following mount command replaces the earlier CD mount command: [autoexec] ... # Merged retail CDs image mount d "D:\Games\Dos\Wing Commander 3\cd\data.dat" -t cdrom ... Digital edition The digital edition should installed using the digital platform client app (e.g. gog.com Galaxy) or digital platform offline installer package. This guide uses the following folder as a digital edition installation folder example: D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III For the digital version the following mount commands should be used: [autoexec] ... # Digital edition install folder mount c "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III" # Digital edition CD image mount d "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III\data.dat" -t cdrom ... Sound options WC3 supports a wide variety of digital sound and music options. The WC3 Launcher can swap between MIDI devices during a DOSBox session, and coupled with VirtualMIDISynth allows switching between soundfonts 'on-the-fly'. However once a preference has been settled on, you may wish to make this the default without having to choose the preferred sound/music devices each time. When reconfiguring music/sound devices the following command should be used: D:\> wc3 -i Sound Blaster Can be selected for music and sound. The default DOSBox config Sound Blaster settings are Ideal. Music/sound should be set in the config utility to Sound Blaster 16. Sound Blaster 16 digital settings: Digital I/O port: 220 Digital IRQ: 7 Digital DMA Lo: 1 Digital DMA: Hi: 5 Sound Blaster 16 music settings: N/A, simply select Sound Blaster 16 as the music device. Roland music This includes the Roland MT-32 and Roland Sound Canvas. Can be selected for music only. The music setting for both devices is: I/O port: 330 Roland MT-32/LAPC-1 In the DOSBox Staging config, the optimum Roland MT-32 setting is the cm32l device, as described in List of MT-32-compatible computer games. [mt32] model = cm32l romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 In the config utility, under music device, select: Roland MT-32/LAPC-1. Roland Sound Canvas In the DOSBox Staging config, the optimum Sound Canvas setting is the sc55 device, as described in List of MT-32-compatible computer games. [soundcanvas] soundcanvas_model = sc55 soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] mididevice = soundcanvas In the config utility, under music device, select the dedicated MIDI driver: Roland RAP-10/SCC-1 or the general MIDI driver: MPU-401 General Midi. General MIDI music Can be selected for music only. In the config utility, under music device, select: MPU-401 General MIDI. The music setting for General MIDI devices is: I/O port: 330 DOSBox Staging built-in MIDI devices includes FluidSynth or Sound Canvas, e.g. [fluidsynth] soundfont = "Shan SGM Pro 15.SF2" soundfont_dir = "D:\Midi\Soundfonts" [midi] mididevice = fluidsynth # or mididevice = soundcanvas DOSBox Staging also supports external (to DOSBox) MIDI devices. For further info consult, DOSBox Staging and MIDI, e.g. [midi] mididevice = port midiconfig = 0 VirtualMIDISynth and MIDIMapper These are optional MIDI tools that can be used by DOSBox Staging and WC3, as General MIDI (GM) is supported as a WC3 music option. The built in features of DOSBox Staging can do the job of these tools but they may make things easier for those who wish to try out multiple soundfonts (VirtualMIDISynth) or switch between different Win10/11 MIDI synths (MIDIMapper). For a further discussion on using these tools with the latest DOSBox Staging, see DOSBox Staging and MIDI. WC3 Launcher This is a batch file menu launcher (wc3menu.bat) that performs a number of functions: Start the game. Run the install/setup utility to reconfigure music/sound settings. Switch to a different DOSBox MIDI device (MT32, FluidSynth or Sound Canvas). Switch to an external (Port) MIDI device (e.g. VirtualMIDISynth, MIDIMapper). Return to the DOSBox command prompt. Close DOSBox. This launcher should be compatible with cd retail and digital editions. It allows switching MIDI devices to try out various MIDI options, to find a preference. Installing Download the launcher below: In Win10./11, extract the menu to the game installation folder. Change the WC3 DOSBox Staging config as shown: From [autoexec] ... d: wc3.exe pause exit To [autoexec] ... c: cd \ call wc3menu.bat Windows editions The WIndows version of WC3 includes the Kilrathi Saga edition or a DOS edition converted into the Windows version. The Windows version replaces MIDI for digital music, losing the ability to change MIDI synths or soundfonts. The enhanced version also adds native controller support allowing the game to support stick, throttle and rudder pedals. The steps to install and enhance the Kilrathi Saga or converted DOS versions are as follows: Wing Commander Loader (DOS editions) For those converting a DOS edition, the first step is download and install the Wing Commander Loader (WingLoader). Download Wingloader and extract the contents of the zip archive. An example folder used in the rest of this guide is: D:\Games\Win\WingLoader Within the WingLoader installation folder create a Wing Commander III folder, e.g. D:\Games\Win\WingLoader\Wing Commander III Retail CD version Th retail CD version is not officially supported by WingLoader, however the digital (gog.com) edition is. This section covers creating a 'digital edition like' install compatible with WingLoader, from an existing CD retail install. Creating a WingLoader compatible install These steps should be performed in Win10/11: Copy the following files from the following game folders in Win10/11: D:\Games\DOS\Wing Commander 3\hdd\WC3 OBJECTS.TRE WC3.CFG WC3.CON D:\Games\DOS\Wing Commander 3\cd DATA.DAT Into the WingLoader WC3 folder: D:\Games\Win\WingLoader\Wing Commander III Digital version The digital edition is compatible with WingLoader but it recommended to create a fresh install in the WingLoader WC3 folder. The WingLoader and Enhancement patches will apply comprehensive changes. Using the original digital edition installation folder is possible, but if the game install is validated or reinstalled after patching, then all the patch changes will be lost. A fresh install in a new folder means the patch changes cannot be accidentally lost. Creating a fresh install These steps should be performed in Win10/11: Copy the following files from the following digital edition game folder in Win10/11: D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III OBJECTS.TRE WC3.CFG WC3.CON DATA.DAT Into the WingLoader WC3 folder: D:\Games\Win\WingLoader\Wing Commander III Kilrathi Saga edition The Kilrathi Saga edition is already a Windows edition of the game. There is no need for the WIngLoader patch to convert this edition. The Kilrathi Sage uses a 32-bit installer app making it compatible with Win10/11. When installing, only WC3 needs to be installed in a suitable installation folder of your choosing. For the rest of this guide the following example is used: D:\Games\Win\Kilrathi Saga\Wing Commander III Installing Wing Commander III Enhancement Patch (all editions) These steps should be performed in Win10/11: Download the Wing Commander III Enhancement Patch and extract the contents of patch into the WingLoader WC3 folder or Kilrathi Sage installation folder: D:\Games\Win\WingLoader\Wing Commander III D:\Games\Win\Kilrathi Saga\Wing Commander III Download the Wing Commander III Enhancement Patch VLC libraries and extract the contents of patch into the WingLoader WC3 folder or Kilrathi Sage installation folder. Optional: Installing Wing Commander 3 HD Video Pack (all editions) If the optional Wing Commander 3 HD Video Pack is to be installed and used in-game, follow these steps in Win10/11: Download the Wing Commander 3 HD Video Pack and extract the contents of patch into the WingLoader WC3 folder or Kilrathi Sage installation folder. Download the Restored Scenes IFF Packs and extract the contents of patch into the WingLoader WC3 folder or Kilrathi Sage installation folder. Patching with Wing Commander Loader (DOS editions) The following gallery shows the WingLoader patching steps: Go to the WingLoader folder: D:\Games\Win\WingLoader Run WingLoader.exe. Once patching is complete, simply close the WingLoader window. Running When running the Kilrathi Saga or converted DOS editions the following game executable should be used: D:\Games\Win\WingLoader\Wing Commander III\wc3w.exe D:\Games\Win\Kilrathi Saga\Wing Commander III\wc3w.exe Configuring With the addition of the patch and native controller support, there's some additional configuration to optimise the game. Enhancement patch config (optional) There is a separate config file (wc3w_en.ini) for the Wing Commander III Enhancement Patch. Each setting is explained in the file, however the following settings were used in combination with the Wing Commander 3 HD Video Pack: [MOVIES] SHOW_ORIGINAL_MOVIES_INTERLACED=0 ENABLE_ORIGINAL_MOVIES_LIMITED_SCALING=0 ENABLE_ORIGINAL_MOVIES_LINEAR_UPSCALING=1 In-game config Configuration options are shown in the gallery below. In-game config options set from the Main Terminal (in-game). The Joystick Calibration button now opens a new native controller configuration dialog. Finally when on a mission (or in the in-game simulator) Alt + O will open the in-flight options. HOTAS config (optional) The new controller support means the game can now support stick, throttle and rudder pedals. It would seem there is no need for an external HOTAS config, however, the Controller Setup dialog will list all controller devices as 'HID compliant device'. This makes configuration 'trial and error' until the correct controller and axis is located. Note: this is an entirely optional step. Creating a virtual controller with the 4 axes supported in-game means only a single controller is available with only the required 4 axes, which may make thing easier. This also allows the advanced facilities available to the HOTAS profiling software to be used, e.g. button macros, chained commands, etc. It is recommended to map physical to Windows axes as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder DX_ZROT_AXIS Documents The following documents are available: Digital edition Additional resources downloaded separately. 'Victory Streak' manual. Playguide. Reference Card. Warbirds (fighter datasheets). Extras WC3 Behind the Scenes Tape. WC3 Deleted Scenes. WC3 Script. WC3 Wallpaper. The Wing Commander Universe Bible. Novels Fleet Action. Strategy guides Origin's Official Guide to Wing Commander III. Wing Commander III Authorized Combat Guide. Kilrathi Saga edition Kilrathi Saga manual, pdf download. Wing Commander CIC, Wing Commander Encyclopedia, Wing Commander: The Kilrathi Saga Manual Other editions 'Victory Streak' manual, pdf download. Internet Archive, Wing Commander III (Victory Streak) Wing Commander CIC, Wing Commander Encyclopedia, Victory Streak Playguide, pdf download. Wing Commander CIC, Wing Commander Encyclopedia, Wing Commander III: Heart of the Tiger Playguide Reference Card, pdf download. Wing Commander CIC, Wing Commander Encyclopedia, Wing Commander III Reference Card (PDF) Warbirds datasheets, jpg/pdf download. Internet Archive, Wing Commander III (Foldout) Wing Commander CIC, Wing Commander Encyclopedia, Warbirds (JPG) Wing Commander CIC, Wing Commander Encyclopedia, Warbirds (PDF) Wing Commander III Additional Troubleshooting, pdf download. Internet Archive, Wing Commander III (Troubleshooting) Strategy guides Origin's Official Guide to Wing Commander III. Internet Archive, Wing Commander III Guide Wing Commander III Authorized Combat Guide. Internet Archive, Wing Commander III Combat Guide Wing Commander III The Ultimate Strategy Guide Internet Archive, Wing Commander III The Ultimate Strategy Guide Example videos Wing Commander III in DOSBox Staging v0.83.0-RC1 Wing Commander III running natively in Win10 Finally... Credit and thanks for all the hard work involved goes to: Wing Commander CIC, for all the patches, forums, contributors, documents, in fact the premiere resource for Wing Commander franchise information on the Internet. Internet Archive for hosting documents and patches. NStriker. for Windows 2000 Update (Kilrathi Saga edition) fan patch. 'Mash' Matt Wells for Movie Crashing Patch (Kilrathi Saga edition), Wing Commander III Enhancement Patch and associated fan patches. Jari Komppa (Sol) for the DDHack fan patch. Destro for the Wing Commander Loader. ODVS for the Wing Commander 3 HD Video Pack. John Novak and the DOSBox Staging team for DOSBox Staging v0.83.0-RC1. CoolSoft developers for VirtualMIDISynth and MIDIMapper. Good hunting!

  • Jane's Fighters Anthology: Going wide in Windows

    Jane's Fighters Anthology (JFA) has received a couple of new widescreen patches recently. These patches allow the cockpit to be shown in a widescreen resolution. These are file replacement patches replacing the original fa.exe file. There are three patches: FA_Widescreen_zip: Created by ohyeah2389. FA_Widescreen_1920x1080.zip: Created by ohyeah2389. FA_Widescren_nocd.zip: The widescreen patch modified by kuoyichen (hawke) so the CD is no longer needed, this does not support 1920x1080. FA_1920x1080_nocd.zip: The 1920x1080 widescreen patch modified by kuoyichen (hawke) so the CD is no longer needed. FAex.zip: A general purpose resolution and HUD patch by kuoyichen (hawke). The resolution can be specified in a config file. Patch release notes The widescreen patch has been created by ohyeah2389 and was released on the 24 June 2026. The following notes have been edited from those provided by ohyeah2389. So here's FA.EXE with the following changes: 16bit scanline counter 800x600 now runs at 1024x600 (with HUD support) 1024x768 now runs at 1280x768 (without HUD support) 640x480 was not changed to a widescreen variant as it's the mode the menus use, and it would corrupt their drawing. This WILL NOT WORK if your display driver does not support 1024x600/1280x768, which my system does not. You can work around this by using a DDraw wrapper that supplies this display mode, such as cnc-ddraw. Otherwise, FA will try to set the video mode a few times, and then fail with an error "Could not set video mode X". Note: The 1920x1080 resolution should be supported by a majority of display drivers, it replaces the original 1024x768 (without HUD support). Further notes Issues remain when trying to access the Jane's reference material in-game, this has been a long-standing issue with JFA. A previous article provided a workaround by using an alternative wrapper (not compatible with this patch). A suggestion is to take a copy of an existing JFA installation folder and apply the patch and cnc-ddraw wrapper to this new installation and use it for running missions. The existing JFA installation can be used to access the reference material. Obtaining Both patches can be obtained from the Internet Archive at the Jane's Fighters Anthology widescreen patch archive. They are also available at the Combat Flight Sim Tavern, janes-fa channel. Installation Installation is simple, the steps are as follows: Extract one of zip archives to the JFA installation folder. Optional: backup the existing fa.exe file. Rename the patch executable to fa.exe. cnc-ddraw As discussed in the release notes the patch requires a display driver support 1024x600/1280x768. The DirectX wrapper cnc-ddraw can provide this support if needed. cnc-ddraw can be obtained from the cnc-ddraw GitHub repository Releases. The cnc-draw zip archive should be extracted into the JFA installation folder. Screenshots There is no example video as recording with cnc-ddraw active, resulted in a video recorded in the original 4:3 aspect ratio. However, the following screenshots should provide examples of the patch. General purpose resolution & HUD patch This is a general purpose resolution patch (FAex.zip) created by hawke. From some (edited) notes supplied by hawke: We only have two resolutions supported (1920x1080, 1280x1024), maybe a startup program with config file will be a good solution. So here is the FAex. Here is 3 files you will need, FAex is written with python (include source), there is also a standalone version (FAex.exe), so you don't need install python env, the FA.exe just use 1.02F NOCD version. change the resolution in FAex_Config.txt file, then you can enjoy all different resolution. By the way, I also put the hudpatch in, if you set hudPatch = true in FAex_Config.tx, then you will have Hud in any resolution (still a little problem, the little round still in the middle of screen). Obtaining This can be obtained from the Internet Archive at the Jane's Fighters Anthology widescreen patch archive. They are also available at the Combat Flight Sim Tavern, janes-fa channel. Installation, configuration & running The patch allows the configuring a resolution supported by display drivers. As a valid display driver should be used, it can be used without cnc-ddraw, which means it is compatible with DxWrapper as used in the previous article, Bringing it all together with Jane's Fighters - Anthology. The steps are: Download and extract FAex.zip to the JFA installation folder. Open FAex_Config.txt and set the resolution and HUD settings. An example is shown below: # Thank ohyeah2389 in Discord # By kuoyichen (hawke), https://sites.google.com/site/fashape/home # Show HUD graphic regardless of resolution hudPatch = true bgPolyFix = false # Force specific resolution # Note that in sim options you must select 1024x768 to use thisforceResolution = true resolutionWidth = 1280 resolutionHeight = 720 Run the game with FAex.exe. Playnite config When using the Playnite game library manager, the scripts should be configured as follows: Playnite scripts The FAex.exe process ends after starting JFA. This causes Playnite to think the game has been quit, causing Playnite to become the active window. After the game starts a 20 second delay gives the game time to start the intro video, this will be interrupted by Playnite, but you can switch back to the game. Without this delay, the game hangs at the first splash dialog. Scripts to close any joystick/HOTAS profiling apps should not be used. These apps should be closed manually. Example video Playing in 1280x720 resolution with a HUD Finally... Huge credit and thanks for all the hard work, goes to: ohyeah2389, for creating the widescreen patch. kuoyichen (hawke), for creating the no CD version of the patch and the general purpose resolution patch. FunkyFr3sh, for cnc-ddraw. Good hunting!

  • Rowan's Battle of Britain: Battling Windows compatibility

    A guide to running Rowan's Battle of Britain under Windows 10. This is a World War II flight sim set in the British theater during the Battle of Britain timeframe. Fly as a pilot or commander for the British RAF of German Luftwaffe with a dynamic campaign. There is a choice of the Hawker Hurricane and Supermarine Spitfire for the RAF or Junkers Ju-87 "Stuka", Messerschmitt Bf-109 or Messerschmitt Bf-110 for the Luftwaffe. Generally considered one of the better WW2 flight sims on release, it had a dedicated fan following. Once Rowan stopped developing flight sims the source code for this (and MiG Alley) was released and development continued by the fan led Battle of Britain/MiG Alley Development Group (BDG). The rest of the guide will use BoB for Rowan's Battle of Britain. Contents Strategy Patch and version history Initial retail release (November 2000) CD-ROM copy protection fix (January 2001) Battle of Britain Mini-Patch (April 2001) Update patch (July 2001) BDG patch (November 2001) Xplosiv budget release (October 2002) Digital release (October 2008) Retail media Game management HOTAS config Installation Patching Compatibility tools DDrawCompat Compatibility settings Creative ALchemy In-game configuration BDG patch configuration Head tracking Running recommendations Mods and enhancements Graphics mod for original Rowan's BoB Cloud replacement fix D-type hangar fix Rowan's BoB Update 1 City texture mod Rowan's BoB 2024 mod Documents Example video Finally... Strategy This is a very tricky game to get running well in Windows 10. It may run in Windows 11 but this is untested. This game is very crash/freeze prone with most crashes/freezes occurring when exiting the 3D flight engine to return to menus/campaign. There seem to be specific settings and actions which seem to greatly increase the chance of a crash, so this guide includes 'rules' for running the sim, with recommended actions to reduce the likelihood of a crash and actions to absolutely avoid. There are also settings which may slightly increase the crash/freeze risk but you may wish to try with your own setup, including 3D sound, DirectSound wrappers (e,g, Creative ALchemy), CPU affinity and Compatibility settings. It is unlikely that a 'one size fits all' optimal solution could be found, applicable for every machine but this guide should provide a good starting point for your own setup. This first part covers running a fairly vanilla version and the second part covers the optional graphics mods available. Patch and version history The following is a brief patch and version history for BoB. The graphics mods are covered in Mods and enhancements. Initial retail release (November 2000) The initial retail release occurred in November 2000, developed by Rowan and published by Empire Interactive. The game required a Pentium II machine, Windows 95 and DirectX 7. This is version 1.00 of the game. This was distributed on a single CD-ROM. Like MiG Alley, BoB was released with native controller support. CD-ROM copy protection fix (January 2001) An official patch, released in January 2001. This patch was for systems having problem with the game's copy protection not detecting their CD-ROM drives properly. This corrects the copy protection, it is not a 'no-cd' patch. It is not a recommended patch having been superseded by later patches. It is available from: CNET Download, Windows, Games, Simulation, Rowan's Battle of Britain CD-Protection Fix UK patch. Battle of Britain Mini-Patch (April 2001) An official patch, released in April 2001. Taken from the release notes: This patch fixes the following problems: 1. Sky banding in 16 bit graphics modes has been fixed. 2. "Stuttering" seen on certain high-end PC configurations has been reduced. It is not a recommended patch having been superseded by later patches. Update patch (July 2001) An official patch, released in July 2001. Taken from the release notes: Previous stutter fixes - use 10,13,20, or 40 as minimum fametime in ms. If that does not remove your stutter then try reducing the 3d detail level. Improved range of supported 3D cards. Fixed campaign bugs to do with RAF squadron selection. Fixed missing damage report target names (English only). This patch preceded any BDG patch and is not a recommended patch, having been superseded. It is available from: The Patches Scrolls, Rowan's Battle of Britain, Patches. BDG patch (November 2001) The Battle of Britain Development Group (later the Battle of Britain/Mig Alley Development Group) (BDG) patch development began with the v0.60 patch released in November 2001. Development would continue until November 2004 with the v0.99 patch. Not so much a patch rather a fan led development effort, the extensive comprehensive changes are too numerous to list here, and resulted in an entire manual (BDG v0.99 Patch Manual) describing the patch changes, installed alongside the patch. This is the only recommended patch which incorporates or supersedes earlier patches. It is available from: Dropbox, bob_v099. Xplosiv budget release (October 2002) This budget release occurred in October 2002 and was published by Empire Interactive under the Xplosiv budget label. This was distributed on a single CD-ROM. This is identical to the initial retail release with the game remaining at v1.00. The CD also contained the Battle of Britain Mini-Patch and Update patch. Documentation is included with the BoB Manual and Key Guide. Digital release (October 2008) The game was released on the GamersGate platform in October 2008. This is the only known digital release at present. It's not known what this release includes. Retail media Due to the age or the media and the drives required to read it, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The CD-ROMs can be ripped to a data only .iso image format as there is no CD audio on the CDs. Game management It is recommended to use my game management strategy or similar strategy you may have developed. The recommended game management folders for BoB are: cd - for any cd images. conf - to store HOTAS configuration files. docs - for documents. patch - to store any patches. The BoB management folders can be found in the following game folder (as an example): D:\Games\Win\Rowans Battle of Britain Setup HOTAS config BoB supports 5 axes, X & Y stick axes, single throttle axis (for single engined fighters), split throttle axes (for the twin engined bomber) and a rudder axis. Fortunately BoB has native controller support so multiple controllers from multiple vendors are supported. However, this does mean some of the advanced functionality provided by profiling software will not be available if only native controller support is relied upon. First the bad news, the HidHide, vJoy and Joystick Gremlin suite has problems with BoB. Testing has revealed that, for some unexplained reason, changing the throttle axis/axes also affects the ailerons causing unwanted dramatic manoeuvres with the Thrustmaster Warthog. Therefore this controller software suite isn't recommended for BoB when using this controller. Alternative HOTAS controllers may function better, but testing is required. This issue does not affect the TM TARGET profiling software and software from other vendors may also be unaffected. For those with a multiple vendor setup, a combination of native controller support for axes plus additional software such as JoyToKey, or the BDG Keyboard Manager (included in the BDG patch) for button assignment may be sufficient. Native controller support means axes can be configured as required, the below is a suggested axes setup which is known to work. The physical axes to Windows axes were configured as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle (single) DX_Z_AXIS Throttle (split) DX_ZROT_AXIS Rudder DX_XROT_AXIS Note: Those with a DX_SLIDER_AXIS or DX_THROTTLE_AXIS may wish to use these axes instead, depending on the controller. Note: With my Thrustmaster setup there is better controller response using a single virtual controller rather than using each controller natively. Controller response seems to be linked to the number of controller used in the game, so the fewer the better. Note: One (for single engined fighters) or two (for the twin engined bomber) axes can be assigned to prop pitch if they are available. Installation BoB uses a 32-bit installer (setup.exe) compatible with Win10. Setup is straightforward and the setup steps are shown below: Patching The only patch required is the BDG v0.99 patch. This is a file replacement patch distributed as an executable (bob_v099.exe). The patching steps are shown below: Compatibility tools The following compatibility tools and settings are used to run BoB. DDrawCompat DDrawCompat is used at a DirectX wrapper, created and maintained by narzoul. The recommended version is the latest one, version v0.7.1 (at time of writing). DDrawCompat is available from the DDrawCompat GitHub repository, in Releases. The following DDrawCompat configuration (DDrawCompat.ini) is used: # DDrawCompat config file for Rowan's Battle of Britain ConfigHotkey = shift+ctrl+f11 StatsHotKey = shift+ctrl+f12 CpuAffinity = 1 CpuAffinityRotation = on The config and stats hotkeys are changed as the default hotkeys are also used by BoB. Only one of the CPU's is made available for the game as this seems to reduce crashes/freezes. The spread the CPU load/heat, CPU affinity rotation is enabled. Note: Ensure that Antialiasing is disabled as this causes very bad landscape 'pop-in' to occur and dramatically increases the risk of crashes. Multiple CPU's may causes crashes/freezes when the Remove cockpit view (F8) is active. If not used, then using multiple CPU's may be possible, with the following: CpuAffinity = all A copy of this config is included below: To install the ddraw.dll and DDrawCompat.ini files need to be copied into BoB installation folder. bob.exe compatibility properties Compatibility settings The following Windows compatibility settings were applied to the game executable (bob.exe). The compatibility mode is set to Windows XP (Service Pack 2) which allows intro movies to play full screen. Other settings seem to reduce the risk of crashes/freezes but you may wish to experiment with your own system. The following screenshot, shows the Compatibility tab of bob.exe Properties. Creative ALchemy BoB has support for EAX 2.0 which is no longer support in Win10 but can be enabled with the Creative ALchemy wrapper (for Creative sound cards) or Creative ALchemy Universal (for any sound card). DSOAL would be another option, if it didn't seem to increase the risk of a crash/freeze. So for now, DSOAL isn't recommended. If crashes/freezes occur you may wish to disable 3D sound and revert to Stereo. In-game configuration The following shows the in-game configuration menus. The following settings are considered mandatory to prevent crashes/freezes: Do not use anti-aliasing in the DDrawCompat wrapper. Do not use a resolution higher than 1280 x 1024 (5:4 aspect ratio). The aspect ratio is less important so 1280 x 960 (4:3), 1280 x 800 (16:10), 1280 x 720 (16:9) or lower should be ok. Either 16 or 32-bit colour depth should be fine. Always turn Ground Collisions: Off from the options. This prevents the 'spin of death' a known cause of crashes/freezes. Set Town and forest raises to Off when using BDG patch textures (BDG textures are enabled by default). When making config changes it is recommended to quit immediately afterwards as this ensures changes are written to the config file. BDG patch configuration Some of the BDG patch options are available through the in-game options above. Additional options can be found in the BDG patch configuration file (bdg.txt), located in the BoB installation folder. It is recommended to consult the BDG Patch 0.99 Manual in the Docs folder when changing BDG patch options. The following options differ from the default options initially set in this file: # (floating point) numbers : VIEW_DIST_FACTOR = 0.530000 INFOLINE_COLOUR = ffffffff # On/Off switches: ENEMY_POSITION_INDICATOR=ON DRAW_PADLOCK_CENTER_BOX=OFF GET_KEY_MAPS_FROM_FILE=ON HEAD_BOBBING=OFF SHOW_INFOLINE_BACKGROUND=ON BOB_DISABLE_STALL_HORN=ON REINIT_JOYSTICK_OFTEN=OFF SHORTENED_LABELS=ON HIDE_AMMO_COUNTER=OFF BOB_SMOOTHER_DEADZONE=OFF START_FROM_PEN=OFF HIDE_POWER_INFO=OFF # AutoGen stuff (experimental): ENABLE_AUTO_GEN=ON TEMP_AG_SN[14,0]=59 TEMP_AG_SN[15,2]=62 TEMP_AG_SN[15,3]=62 The INFOLINE_COLOUR and SHOW_INFOLINE_BACKGROUND are personal preferences to make info line text easier to read at higher resolutions. Head tracking Head tracking is supported through TrackIR. To enable head tracking enable the TrackIR setting in the BDG patch game options config menu (in-game), or enable it within the BDG patch config file (bdg.txt) with: # On/Off switches: TRACKIR=ON The AITrack and OpenTrack software is also compatible with BoB. However, enabling TrackIR may significantly increase the risk of a crash/freeze. Running recommendations The following recommendations are suggested to reduce the risk of freezes/crashes. They should not be considered definitive and may well depend on the machine/OS combination. These settings seem to work well for my machine, but feel free to experiment and let me know if you discover other settings which seem to help. Do not use anti-aliasing in the DDrawCompat wrapper. Do not use a resolution higher than 1280 x 1024 (5:4 aspect ratio). The aspect ratio is less important so 1280 x 960 (4:3), 1280 x 800 (16:10), 1280 x 720 (16:9) or lower should be ok. Either 16 or 32-bit colour depth should be fine. Always turn Ground Collisions: Off from the options. This prevents the 'spin of death' a known cause of crashes/freezes. Always quit a mission (Alt + X) from within the cockpit (F7). Do not try and quit from an external view. Gun camera footage can be recorded and played, with the following recommendations: Use the gun camera toggle (C) to enable/disable the gun camera. Disable before quitting. Wait 10-20 seconds after firing the guns and disabling the gun camera, before quitting the mission (from within the cockpit). After viewing the footage (from an internal or external view) return to the cockpit before quitting the playback (Alt + X) or using the eject button on the playback controls. Mods and enhancements Following the BDG patch a number of graphics mods were released to increase the fidelity of textures. These mods and fixes were taken from the The A2A Simulations Community, BOB2 General Discussion forum, GRAPHIC MOD FOR ORIGINAL ROWAN BOB post. All mods and fixes were created and released by rogeroger. The order of installation is important and each of the mods are described below. The order of installations is: Graphics mod for original Rowan's BoB. Cloud replacement fix. D-type hangar fix. Rowan's BoB Update 1. City texture mod. Rowan's BoB 2024 mod. Graphics mod for original Rowan's BoB The Graphics mod for original Rowan's BoB was posted in the forum on 14th May 2019. The Graphics mod for original Rowan's BoB is available from: MediaFire, RR ROWANBOB GRAPHICS MOD. Before installation it's recommended to backup the BDG patch config file (bdg.txt) and the Keyboard config (keys.xml in the KEYBOARD folder), if it has been edited, as this mod supplies alternative config files. In addition to the graphics mod it also includes BDG patch v0.98 and manual, BDG patch v0.99 and manual, alternative water textures and the creator's JoyToKey settings. To install: Extract the contents of the 7zip archive (RR ROWANBOB GRAPHICS MOD.7z). Copy the contents of the bob main folder into your BoB installation folder, replacing files as required. Optional: Extract the contents of the alternative water texture 7zip archive (alt water texture.7z) and copy the contents into the Landmap2 folder (in the BoB installation folder). Copy your backup BDG patch config file (bdg.txt) back into the BoB installation folder, replacing the graphics mod config file. Apply the following setting to the BDG patch config file (bdg.txt): # (floating point) numbers : ... VIEW_DIST_FACTOR = 0.530000 ... Delete the Keyboard config (keys.xml in the KEYBOARD folder) and replace with the backup. You can also delete the keys.xml file without replacing it, as a new default version will be created when the game is started. Cloud replacement fix This cloud replacement fix replaces one of cloud shapes with a hard outline with an alternative version. It was posted in the forum on 15th May 2019. This fix is available from: MediaFire, Cloud replacement fix Rbob. To install: Extract the contents of the 7zip archive (Cloud replacement fix Rbob.7z). Copy the .dds files into the Maskmap16 folder (in the BoB installation folder), replacing any existing files. D-type hangar fix This D-type hangar fix replaces the D-type hanger texture with a higher quality one. It was posted in the forum on 15th May 2019. This fix is available from: MediaFire, d type. To install: Extract the contents of the 7zip archive (d type.7z). Copy the .pcx file in IMAGEMAP folder (in the BoB installation folder), replacing the existing file. Rowan's BoB Update 1 This is a texture and sound update. It includes brighter terrain, tree, ME-109 and spitfire textures. The RAF cockpit sight texture has been changed. RAF and Luftwaffe engine sounds have been ported from Battle of Britain 2. Some additional textures have been changed. It was posted in the forum on 27th December 2019. This fix is available from: MediaFire, ROWANBOB UPDATE1. To install: Extract the contents of the 7zip archive (ROWANBOB UPDATE1.7z). Copy the folders into your BoB installation folder, replacing files as required. City texture mod This is an alternate city textures mod. It was posted in the forum on 28th December 2019. This fix is available from: MediaFire, city texture mod. To install: Extract the contents of the 7zip archive (city texture mod.7z). Copy the .dds files into the Landmap2 folder (in the BoB installation folder) replacing any existing files. Rowan's BoB 2024 mod This mod contains new terrain, water and road textures. It replaces missing textures on an airfield building. It was posted in the forum on 26th May 2024. This fix is available from: MediaFire, rowanbob 2024 mod. To install: Remove existing tree .txt files from the ObjectAdds folder (in the BoB installation folder). Extract the contents of the rar archive (rowanbob 2024 mod.rar). Copy the folders into your BoB installation folder, replacing files as required. Documents The game documentation is available in pdf format of the installation CD of the Xplosiv budget release. It consists of: Manual, pdf download. pdfcoffee, Rowan's Battle of Britain Key Guide The BDG Patch v0.99 also has a manual, installed alongside the patch. It is found in the Docs folder of the BoB installation folder. Example video Win10, with HOTAS, DDrawCompat, Creative ALchemy and TrackIR Finally... Credit and tanks goes to the following, for their contribution in getting the game running in WIn10: The Battle of Britain/MiG Alley Development Group for the BDG patches. narzoul for DDrawCompat. CNET, The Patches Scrolls, Dropbox and MediaFire for hosting patches. rogerroger for the graphics mods. NaturalPoint, AITrack and OpenTrack devs for head tracking software. And this is the 200th article on this website! Good hunting!

  • DOSBox Staging and MIDI

    VirtualMIDISynth and MIDIMapper are optional MIDI tools that can be used by DOSBox Staging and games supporting MIDI music. However with the latest config changes in DOSBox Staging v0.83.0-RC1 it may be worth taking another look at DOSBox MIDI both built-in and external synths in Win10/11. Further information on obtaining and installing these tools can be found in VirtualMIDISynth and MIDIMapper. They are not required and existing DOSBox facilities can do the job but these tools may prove more convenient. VirtualMIDISynth is a Win10/11 software MIDI synth that supports soundfonts. It does the same job as FluidSynth built into DOSBox Staging (which also supports soundfonts). However, with VirtualMIDISynth the soundfont can be changed 'on-the-fly' as the game is running allowing many soundfonts to be tried and tested. Changing soundfonts with fluidsynth requires shutting down DOSBox changing the soundfont in the config and restarting DOSBox. MIDIMapper is a Win10/11 MIDI synth selector. It can be used to select the default Microsoft Synth, VirtualMIDISynth or another MIDI synth that may be installed in Win10/11 (e.g. a Yamaha synth). This is another optional tool as the DOSBox config and DOSBox commands can be used to send MIDI music to a specific Win10/11 synth. Alternatively DOSBox can sent MIDI music to the MIDIMapper and let it decide the Win10/11 synth that should be used. The following example demonstrates how the same result can be achieved using the different tools: DOSBox is configured to send MIDI music to the built-in FluidSynth. FluidSynth is using soundfont X. DOSBox is configured to send MIDI music to VirtualMIDISynth. VirtualMIDISynth is using soundfont X. DOSBox is configured to send MIDI music to MIDIMapper. MIDIMapper is configured to send MIDI music to VirtualMIDISynth. VirtualMIDISynth is using soundfont X. Example DOSBox config For the purposes of this article we'll assume there is an example DOSBox config with MT32, FluidSynth and Sound Canvas components configured, as shown in this config: [mt32] model = cm32l romdir = "D:\Midi\Versioned" [fluidsynth] soundfont = "Shan SGM Pro 14.SF2" soundfont_dir = "D:\Midi\Soundfonts" [soundcanvas] soundcanvas_model = sc55 soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] mididevice = mt32 midiconfig = 0 Finding MIDI components We can find a list of MIDI components configured in DOSBox by running the following DOSBox command: C:\> mixer /listmidi From this we get the following pages of results: The mt32 section shows the valid Roland devices available from the Roland ROMs found in the Roland ROM path. The the mt32 section we can see an active CM32L device (in green text). This is the device set in the config file. The soundcanvas section shows the valid Sound Canvas devices available from the Sound Canvas ROMs folder. The fluidsynth section shows all of the soundfonts discovered. The win32 sections shows external (to DOSBox Staging) MIDI devices in Win10/11. Device 0 is the MIDIMapper device, a MIDI synth selector. Device 1 is the default Microsoft GS Wavetable Synth always present in Win10/11. Device 2 is VirtualMIDISynth. Using DOSBox Staging MIDI components The [midi] section of the DOSBox Staging config determines the built-in component that will handle MIDI music. Some examples: [midi] mididevice = mt32 mididevice = fluidsynth mididevice = soundcanvas The midiconfig setting has no effect when using a built-in component. The Roland MT32 option is strictly speaking not a General MIDI (GM) device but a General Standard (GS) device. General Standard is General MIDI but with a lot of propriety Roland extras added. The difference in General MIDI (GM) and General Standard (GS) devices is why there is often a Roland sound (MT32, CM32L or LAPC-1) option and a General MIDI option when installing or configuring games. Each option has its own section in the DOSBox config for configuring the device, e.g, [mt32], [fluidsynth] or [soundcanvas]. Using external MIDI components By external we mean external to DOSBox Staging, so not an internal built-in DOSBox component. The [midi] section of the DOSBox Staging config allows the use of external MIDI components with: [midi] mididevice = port Or the following DOSBox command can be run from within DOSBox: C:\> config -set midi mididevice=port The mixer /listmidi command has provided a list of Win10/11 MIDI devices: Device 0: MIDIMapper. Device 1: Microsoft GS Wavetable Synth Device 2: VirtualMIDISynth We can choose a synth to use directly with the midiconfig setting, the midiconfig setting matching the device to use, e.g. to use VirtualMIDISynth: [midi] mididevice = port midiconfig = 2 Or the following DOSBox command can be run from within DOSBox: C:\> config -set midi midiconfig=2 We don't have to choose a MIDI synth, we can select the MIDIMapper and let it decide which Win10/11 MIDI synth should be used. To use the MIDIMapper: [midi] mididevice = port midiconfig = 0 Or the following DOSBox command can be run from within DOSBox: C:\> config -set midi mididevice=port C:\> config -set midi midiconfig=0 Finally... Credit and thanks go to: The CoolSoft developers of VirtualMIDISynth and MIDIMapper. John Novak and the rest of the DOSBox Staging team. Good hunting!

  • Frontier: Elite 2: Pushing back the staging frontiers

    A guide to running the classic space sim Frontier Elite II (FE2) on modern hardware with DOSBox Staging and natively in Win10. Frontier: Elite II marked a significant departure from the existing Elite universe. The game-like space flight controls are replaced with Newtonian physics. The species making up GalCorp are replaced with a simulation of the galaxy populated by the human only Federation and Empire superpowers. There is no plot to follow, so you have the freedom to become a trader, miner, pirate or a freelance agent for the Federation or Empire, some or all of the above! Note: This article is only covering Frontier: Elite II, the sequel Frontier: First Encounters is not covered. Strategy The DOS version will run in the latest version of the DOSBox Staging emulator (v0.83.0-RC1 at the time of writing). The Windows port of FE2 is glFrontier, it does not require the DOS version to run. Version & patch history Initial UK release (October 1993) The initial UK release was supplied on 1 or 2 x 3.5" Double Density (DD) floppy disks. The first disk containing the game and installer and the optional second disk containing 5 alternate starting scenarios. This was considered a rushed release and the game contains a number of bugs including: Passenger bug. Wormhole bug. Bribe bug. ELITE bug. Mining bug. Imperial ship bug. Cemiess negative price bug. Despite these issues some FE2 veterans still consider this to be the optimum version as it was believed the wormhole bug enhanced the game. This is not a recommended version, as later versions have most of these bugs fixed. Most full priced retail version included a manual, quickstart guide, a gazetteer (a list of notable systems) used in conjunction with the systems map and 'Stories of life on the frontier', a collection of short stories set in the FE2 galaxy. Mining bug patch (October 1993) A patch created by Steve Critchlow that fixed the mining bug that would cause a crash after leaving an unattended MB4 mining machine in a system. This is a file replacement patch, once downloaded the zip archive is extracted into the game folder replacing a single file. This patch is only recommended for the initial UK release. This patch is available from: First Encounters (courtesy of the Wayback Machine). Frontierverse. Internet Archive. CD release (March 1994) The CD release has most bugs fixed, with only the bribe bug remaining. Distributed on a single CD. This version included all the FE2 documentation. This is a recommended version. International release (August 1994) The worldwide release has most bugs fixed, with only the bribe bug remaining. Distributed on 1 or 2 x 3.5" Double Density (DD) floppy disks. This version included all the FE2 documentation. This is a recommended version. Digital release (June 2001) Also known as the shareware release, it was distributed as a zip archive. This was an official distribution via the Elite Club website. This version is fully patched and includes the copy protection codes. This is a recommended version and probably the easiest to obtain. This version does not include complete documentation, however it is complemented with a version of the manual in html format, and a separate copy protection document, available from Elite Club. This version can be obtained from: Elite Club (game, manual and copy protection, courtesy of the Wayback Machine). FrontierAstro. Frontierverse. Life on the Frontier (game, manual and copy protection). Retail media Due to the age or the media and the drives required to read the media, it is recommended to rip floppy and cd-rom media to image files, to save wear and tear on media and the mechanical drives. The floppy disks should be ripped to a DOSBox staging compatible .ima or .img image format. The cd-rom can be ripped to a data only .iso image format as there is no cd audio on the cd. Game management It is recommended to use a DOSBox game management strategy or similar strategy you may have developed. The DOS game folder is: D:\Games\DOS\Frontier Elite II The recommended game management folders for the DOS version are: cd - for any cd images. fdd - for any floppy images. hdd - the folder use as the emulated DOSBox hard disk conf - to store DOSBox and HOTAS configuration files. docs - for documents.. The Windows port, glFrontier has an installation folder, and a separate setup folder as shown below. The setup folder is used to store any setup files, e.g. HOTAS config or docs. You may wish to try a similar setup: D:\Games\Win\glFrontier D:\Games\Win\glFrontier setup HOTAS config Only the Joystick is supported by the DOS version. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 2 axes. When using a physical controller with 4 axes or less, the game should be able to correctly identify the 2 joystick x and y axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controller is detected by DOSBox. [6][7][8]. The physical axes to Windows axes were configured as follows: Physical axis Stick & throttle Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Note: There is no HOTAS config for glFrontier, discussed below. DOSBox config This is using a configuration compatible with DOSBox Staging v0.83.0-RC1. [cpu] core = simple cpu_cycles = 25000 cycleup = 500 cycledown = 500 [voodoo] voodoo = off [mixer] reverb = small chorus = light [mt32] model = cm32l romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 [joystick] joysticktype = 2axis timed = off swap34 = on deadzone = 0 [dos] xms = off [autoexec] @echo off # mount a "D:\Games\DOS\Frontier Elite II\fdd\*.img" -t floppy mount c "D:\Games\DOS\Frontier Elite II\hdd" # mount d "D:\Games\DOS\Frontier Elite II\cd\frontier.iso" -t cdrom mixer master 100 /noshow c: cd frontier autotype -w 1 y 1 call frontier.bat exit The following zip file contains an example DOSBox Staging config. It should be changed to match your hardware and personal preferences. Due to the revised defaults with this DOSBox version, most settings are now personal preference or optimal settings, such as sound or joystick settings. Only those settings that differ from the DOSBox Stagiing v0.83.0-RC1 default config are shown above. The cpu is set to simple for increased compatibility. It is suggested by fan sites and an earlier DOSBox guide to set cpu_cycles to at least 20000. To prevent any speed issues this has been increased slightly to 25000 cycles. Voodoo emulation isn't required and is disabled. The mixer and joystick settings are a personal preference and suitable for my joystick hardware (see HOTAS config). The game supports Roland or Adlib/Sound Blaster sound. The default Sound Blaster settings are appropriate. The optimum Roland sound settings use the CM32L device as described in List of MT-32-compatible computer games. The game requires EMS memory and requires XMS memory to be disabled, as described in the DOSBox Staging wiki, Game does not run properly or at all because EMS is not set. EMS is enabled by default. XMS must be disabled in the [dos] section. The autoexec has example mount commands for mounting installation floppy disk images, a hard disk folder and a cd image of the game. As there are multiple installation floppies a wildcard is used to mount all floppy disk images. As the shareware version of the game is used, the autotype commands automates the config menu selection when the game is run. After waiting 1 second, y accepts the shareware agreement and 1 selects Roland CM32L sound (2 could be used to select Adlib/Sound Blaster sound). Installation Retail floppy/CD The retail floppy/CD images should be installed using DOSBox. The first installation floppy and CD has an installer utility to copy files to an appropriate hard disk folder. The install utility is run with: install c Where c is the emulated DOSBox hard disk. The CD install requires an additional language selection during installation. Shareware The shareware version can be downloaded and the contents extracted using Win10/11. The extracted files and folders should then be copied into the DOSBox hard disk folder. Patching Only the initial UK release requires patching, however using an alternative pre-patched release is preferrable. If you wish to use the patch on the initial UK version: Download the patch zip archive and extract the contents, which should be a single file. Copy this into the appropriate FE2 installation folder replacing the existing file. Running & configuration The cd and floppy version is run from DOSBox with the following command: C:\FRONTIER> frontier.exe The digital/shareware version is run from DOSBox with the following batch file: C:\FRONTIER> frontier.bat The digital/shareware version requires confirmation of the shareware licence by selecting Yes. All version require a sound selection, there is a choice of: 1. Roland CM32L sound board. 2. Adlib / SoundBlaster compatible sound board. 3. PC internal speaker. 4. No sound. It is recommended to select 1 or 2, whichever is preferred. Autotype The autotype command in the DOSBox config assumes the shareware/digital version is used and automates the shareware licence confirmation and selection of Roland CM32L sound. Quitting Ctrl-C quits the game. Documentation The following documents are available digitally: Original retail documents Manual, pdf download. Internet Archive, Frontier Elite II Manual. The Gazetteer, pdf download. Internet Archive, Elite II Frontier The Gazetteer PC. Life on the Frontier, Frontier Universe Fiction, Frontier: Elite 2, The Gazeteer. Quick start card, pdf download. Internet Archive, Frontier Elite II Quick Start Card. Life on the Frontier, Frontier Universe Fiction, Frontier: Elite 2, Misc, FE2 Quick Reference Card (PC). Stories of Life on the Frontier, pdf download Life on the Frontier, Frontier Universe Fiction, Frontier: Elite 2, Stories of Life on the Frontier. Galaxy map, jpg image Life on the Frontier, Frontier Universe Fiction, Frontier: Elite 2, Misc, FE2 Galaxy Map. Digital/shareware documents Manual, zip download. Elite Club, Downloads, FRONTIER: ELITE II - Manual (HTML format). Life on the Frontier, Downloads, FE2 Manual Copy protection codes, txt download. Elite Club, Downloads, FRONTIER: ELITE II - Copy protection codes. Strategy guides & FAQs The Secrets of Frontier Elite, Tony Dillon, pdf/rar download Internet Archive, Frontier Elite 2 Guide PDF. FRONTIER (ELITE II) Game Info, compiled by Christoph Tietz, txt download. Jades (Wayback Machine), Frontier FAQ. Tutorials Frontier Fundamentals, JimPlaysGames, YouTube video tutorial series. Mods Most mods are of the save game variety allowing an advantageous starting position, or cheat based mod, increasing funds or changing game parameters (reducing space requirements of equipment, etc). One notable exception is the control mod, which adds manual control of left/right lateral thrusters and top/bottom thrusters. This allows for manoeuvres including a vertical takeoff from a planet spaceport or circle strafing an enemy during combat. Created by Andrea Villa, this enhancement to FE2 is available from: FrontierVerse, Control mod. Further information The following sites provide additional information on FE2 as well as patches, mods and utilities to enhance gameplay.: FrontierAstro. First Encounters (courtesy of the Wayback Machine). Frontierverse. Life on the Frontier. glFrontier Created by Tom Morton, glFrontier is a highly re-engineered/reverse engineered Windows port of the Atari ST version of the game. It utilizes code from the Hatari emulator and the SDL library, to support OpenGL graphics. As it is based on the Atari ST version there are no textures giving the game a very 'clean' look. glFrontier @ 1920x1080 glFrontier does suffer from significant glitches and issues and it is left to personal preference as to whether glFrontier or the DOS version of FE2 is used. There are currently three glFrontier releases: The original glFrontier by Tim Morton. A later Win32 release, GLFrontier-win32 from Kochise. The GLFrontier-Extended from Brett Wilson that adds Android support and touch screen controls. As glFrontier is reversed engineered from the Atari ST version, the DOS version is not required to run glFrontier. Obtaining The original glFrontier can be obtained from the following sites: GLFrontier Project Page (courtesy of the Wayback Machine). FrontierAstro. SpaceSimCentral (requires registration). The Win32 release, GLFrontier-win32 can be obtained from: The GLFrontier-win32 GitHub repository. GLFrontier-Extended can be obtained from: The GLFrontier-Extended GitHub repository. Running The original glFrontier will often fail to setup the window or screen resolution properly resulting in an immediate crash. The game may need to be restarted multiple times until it is successful and the intro movie begins. GLFrontier-win32 and GLFrontier-Extended seem to employ a more robust setup that fails less often. GLFrontier-win32 seems to have particular problems with saving progress. At present compatibility options don't seem to solve this problem. Command line options The following command line options are supported across all versions: Usage: frontier [options] Where options are: --help or -h Print this help text and exit. --fullscreen or -f Try to use fullscreen mode. --nosound Disable sound (faster!). --size w h Start at specified window size. Note: the usage should state: glfrontier [options] Additional in-game commands These are glFrontier commands only: F11 Toggle fullscreen. Ctrl-E Toggle hardware GL / original software renderers. Ctrl-M Toggle mouse grabbing. F Toggles some debug info & fps readout. Ctrl-Q Quits the game. Joystick issues According to the code in the glFrontier project, there doesn't seem to be any support for joystick or HOTAS devices despite the Joystick control option present in the in-game options menu. Example video Example video showing the digital/shareware version of FE2 with joystick support and the Control mod applied. glFrontier @ 1920 x 1080 Finally... Credit and thanks for the FE2 information goes to: Frontier Developments for the digital/shareware release of FE2 and supporting documents. George Hooper for the First Encounters fan site. Robin Sharrock for the Frontierverse fan site. The creator/maintainer of the FrontierAstro fan site. The creator/maintainer of the 'Life on the Frontier' fan site for info and hosting documents. The Internet Archive for hosting patches, documents and the Wayback Machine. The DOSBox Staging wiki maintainers for FE2 game issues and solutions. Tony Dillon for The Secrets of Frontier Elite. Christoph Tietz for compiling the FE2 FAQ and the Jades fan site for hosting it. JimPlaysGames for the Frontier Fundamentals video series. Andrea Villa for the Control mod. Credit and thanks for the glFrontier information goes to: Tom Morton for glFrontier. Kochise for GLFrontier-win32. Brett Wilson for GLFrontier-Extended. FrontierAstro and SpaceSimCentral for hosting glFrontier. Good hunting/trading/mining/piracy!

  • Flight of the Intruder: Intruding into Staging

    A guide to running the Rowen & Spectrum Holobyte developed, 1990 sim, Flight of the Intruder in DOSBox Staging. Based on the book and film of the same name, Flight of the Intruder (FotI) is a sim of the naval carrier aircraft F-4 Phantom II and A-6 Intruder based in the Vietnam theater during the war. In 1990 there was little to choose from graphics-wise between the Amiga and PC, with the introduction of VGA although the Amiga still retains superior sound. As a DOS only sim DOSBox Staging is used. This game was considered the spiritual successor to the original Falcon (from Spectrum Holobyte) before the release of Falcon 3.0. Version & patch history The versions and patches released for FotI are listed below. Initial release The initial release was in July 1990 and distributed on 3 x 5.25" floppy or 3 x 3.5" floppy disks. There is no version listed for the game in the credits but is believed to be version 1.0, given the subsequent version numbering. The first disk is used to install/run with CGA graphics, while the remaining two disks are used to install the EGA/VGA version. Version 1.1 A re-release occurred in August 1990 and was again distributed on 3 x 5.25" or 3 x 3.5" floppy disks. The version is listed at the end of the credits. Like the initial release the first disk is the CGA version while the remaining two disks allow the EGA/CGA version to be installed. There are no release notes accompanying this version. Update disk (version 1.2) An update disk was released in December 1990 on a single 3.5" floppy, which updated the game to version 1.2. The version is listed at the end of the credits. The update was applicable to the EGA and VGA versions. There were no release notes accompanying the update disk. This is a recommended update for versions 1.0 and 1.1. Version 1.2 Releases occurred throughout the 1990's with version 1.2 release on cd-rom in May 1995. The minimum spec also being raised a 386 processor and VGA graphics only. The game is first run from the cd, with the game installed to the hard disk as part of running the game. The game can be played later from the cd-rom or hard disk. The version is listed at the end of the credits and there are no release notes detailing changes or enhancements. Digital release The game was re-released digitally on the gog.com platform in 2024. The digital edition uses version 1.2. Retail media Due to the age or the media and the drives required to read the media, it is recommended to rip floppy and cd-rom media to image files, to save wear and tear on media and the mechanical drives. The floppy disks should be ripped to a DOSBox staging compatible .ima or .img image format. The cd-rom can be ripped to a data only .iso image format as there is no cd audio on the cd. A digital edition of the game is available on gog.com. Game management It is recommended to use my DOSBox game management strategy or similar strategy you may have developed. The recommended game management folders for the DOS version are: cd - for any cd images. fdd - for any floppy images. hdd - the folder use as the emulated DOSBox hard disk conf - to store DOSBox and HOTAS configuration files. docs - for documents.. HOTAS config Joystick, throttle and rudder pedals are supported. The game supports either a stick and throttle scheme or a stick, throttle and rudder scheme. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controller is detected by DOSBox. [6][7][8]. The physical axes to Windows axes were configured as follows: Physical axis Stick & throttle Stick, throttle & rudder Joystick x-axis DX_X_AXIS DX_X_AXIS Joystick y-axis DX_Y_AXIS DX_Y_AXIS Throttle DX_Z_AXIS DX_Z_AXIS Rudder N/A DX_XROT_AXIS DOSBox config The DOS version is configured to run under the latest released DOSBox Staging version, v0.83.0-RC1 (at time of writing). [dosbox] vmem_delay = 500 [cpu] core = simple cycleup = 100 cycledown = 100 [voodoo] voodoo = off [mixer] reverb = small chorus = light [sblaster] sbtype = none oplmode = opl2 [joystick] joysticktype = 4axis timed = false swap34 = true deadzone = 0 [autoexec] @echo off # mount a "D:\Games\DOS\FLight of the Intruder\fdd\disk*.img" -t floppy mount c "D:\Games\DOS\FLight of the Intruder\hdd2" mount d "D:\Games\DOS\FLight of the Intruder\cd\intruder.iso" -t cdrom mixer opl 1000 /noshow mixer master 100 /noshow d: intruder.exe pause exit The following zip file contains an example DOSBox Staging config. It should be changed to match your hardware and personal preferences. Due to the revised defaults with this DOSBox version, most settings are now personal preference or optimal settings, such as sound or joystick settings. Only those settings that differ from the DOSBox Stagiing v0.83.0-RC1 default config are shown. The vmem_delay is set to improve the timing issues within the sim. The credits scroll too quickly without this setting, with it the sim is slowed to a better pace. The cpu is set to simple as it is optimised for, and provides better compatibility with older real mode games. Voodoo emulation isn't required and is disabled. The Sound Blaster settings emulate an AdLib Music Synthesizer Card as described in the DOSBox Staging wiki Sound cards. The mixer and joystick settings are a personal preference and suitable for my joystick hardware. The autoexec has example mount commands for mounting installation floppy disk images, a hard disk folder and a cd image of the game. The Adlib sound is extremely quiet in-game, possibly due to the game expecting the Adlib audio to be played through amplified speakers (according to the FotI manual). In order to hear the Adlib audio, the master volume is restored to 100% and the OPL volume is increased to 1000%. Note: It is recommended to increase this volume in increments from 100% until a suitable OPL volume is found, to prevent a volume that may damage speakers. In this example config the cd version of the game is run. Floppy release The floppy release includes the CGA, EGA and VGA versions of the game. The CGA is run/installed from a single disk. The EGA/VGA versions are installed from the remaining two disks. Installation and patching are dependent on version. Installation The CGA version is installed onto a hard disk by copying the contents of the CGA disk into a suitable hard disk folder. The EGA and VGA versions must be installed from the remaining two floppy using the DOS installer app (install.exe). Patching Only the EGA and VGA versions can be patched to version 1.2. The patch was distributed as a separate floppy update disk. The image of this disk should be mounted in DOSBox and the update utility (update.exe) run from within DOSBox. Running The game is run from the installation folder (the default is intruder) with: C:\INTRUDER> intruder.bat CD release CD menu The CD release uses a unique combined installation and running process. When the game is first run from the cd, it installs on the hard disk, before running the game. When subsequently run from the CD, the hard is checked for the game folder and files and if they exists the game is run. This means the game can be run from the CD or directly from the hard disk folder created by the installation process. To run the game from the cd: D:\> intruder.exe And directly from the hard disk: C:\INTRUDER> intruder.bat Configuration All configuration is performed in-game. THe sound source can be selected from the File menu and the optimum setting is Adlib. The Control menu allows the selection of graphics, sound and control settings as shown below: Documentation Theater map The following documents are available for this sim in pdf format: Manual. Special installation instructions and addendum. Quick reference (keyboard command & cockpit layout). Map. They should be obtained as they are essential to use the sim, which differs significantly from modern aircraft sims. Example Video Finally... Credit and thanks to John Novak and the rest of the DOSBox Staging team. Good hunting!

Drop Me a Line, Let Me Know What You Think

Thanks for submitting!

© 2023 by DarkenedRoom.. Powered and secured by Wix

bottom of page