On my other post on F-111 and Falcon 4:Red Viper, there are some limitations with the F-111 in Red Viper.
By default you get the f-16 pit. You can install Aeyes freeware 2D F-111 pit. This gives you the following 2D cockpit views:
Straight ahead:
Down:
Right:
If you look out over the wing you get a weird looking F-16 wing:
The install procedure I think I followed was run the Aeyes installer for that cockpit and removed the existing 16_ckpit.dat file from the C:\MicroProse\Falcon4\art\ckptart\F111 folder.
There is a download on my site of some Australian F-111 skins in DDS format suitable for Falcon 4: Red Viper. I didn't create them. The low-vis came from an archive called skins-of.zip created by HPt (Harold Pot) on this thread on GlobalFalcon.org, the SEA camo came from an archive RAAF_F111-mr6sqn.zip (that didn't contain a readme.txt). I've since found a link on OpenSkins linking to "Mike Rivers's 6Sqn F-111C" and a broken link on this OpenSkins page to more F-111 skins by Mike Rivers. The skins appear to be his. I've updated the author details in the zip. Thanks to Ranger on the Free Falcon forums I now have the Photoshop PSD files for Mike Rivers's F-111 skins that includes layers for SEA and low-vis. The file with the PSDs is now in my downloads page.
Thanks to the authors of these skins. I've simply renamed the files from 2229.dds to 1101.dds to match the proper DDS file for Red Viper's F-111. Both skins and install instructions are in the zip, short movie of the SEA camo in being used in Red Viper is at the bottom of this page.
I believe (I don't have OF installed) the DDS file name (1101.dds) is the same for the F-111 in Open Falcon, so you can also use these files with Open Falcon. To check, view the DDS file checking the DDS file you are replacing is the same aircraft by use DDSView.
For a 2D F-111 cockpit suitable for Red Viper see Aeyes freeware 2D F-111 pit at http://www.cockpits.nl/
Touchbuddy is a free Windows application that allows you to enter keyboard inputs via a touchscreen. It allows you to create your own interfaces that look like cockpit panels or any other interface you can imagine and when you press the touchscreen it can send a keystroke to your application. When you touch the screen you can have the image under your finger change, so (for example) you can have toggle switches change position. There are several community made profiles available for Falcon 4, Lock On, ARMA and Winamp from the Touchbuddy website and there is a developer kit to make your own. The application supports embedding ActiveX applets like PDF readers for accessing maps and manuals in-sim and also has the ability to show cockpit information from Lock On.
Here is a sample video from the Touchbuddy website showing a touchscreen being used with Lock On:
That profile uses very simple buttons. Simon Cookman's profile for Falcon 4 provides interfaces that look like real panels complete with toggle and rotary switches:
Touchscreens can be very expensive, especially once you go beyond the small 10" or smaller touchscreens coming out of China intended for cars. But you can buy "touch panels" much more cheaply, saving up to 80% over larger touchscreens of 19 inches (assuming you have a 19" LCD monitor), because you are only buying the touch part of the touchscreen without the LCD display unit. You put the touch panel over an existing LCD monitor either fitting it between the plastic bezel and LCD screen or placing it on top of the bezel of your LCD monitor. I have a 15 inch Touchkit touch panel I bought on Ebay and I've just taped mine to a 15" LCD using black electrical tape. Electrical tape - is there anything it can't do? The touch panel consists of a 3mm thick glass panel, a small controller connected via ribbon cable to the panel and a USB cable to your PC:
Touchbuddy is an excellent app but there is a problem with some games/sims. Touchbuddy generates a left mouse click input when you press the screen. This means in games that use the left mouse button to fire a weapon - for example Armed Assault, Touchbuddy doesn't work correctly. You press the screen and you fire your weapon. There are ways around this. You can use Touchbuddy in client/server mode. That is, running the touchscreen and Touchbuddy off a second PC with the second PC sending just the keystrokes over the network to the other PC running the Touchbuddy client. This works very well. I've also read of people running Touchbuddy in a Virtual Machine to send keystrokes to the host running the virtual machine, unsure how exactly they do this.
Using a Touchscreen for Falcon 4.
In response to a forum post on Frugalsworld, I tried out using the touchscreen to press the buttons in the cockpit of Falcon4:AF. That is use the touchscreen as a fully clickable cockpit. That worked reasonably ok, the ICP was easy to press as were the toggle switches in the side panels, but the MFD buttons are very small on a 15" screen running at 1024x768 and that was problematic. I would occasionally press the wrong button. On a larger screen I think it would be ok.
Here is a video of me using the touchscreen in Falcon 4:AF with the default pit:
On using a Touchscreen as your primary monitor for Falcon 4 I had an issue using a touch screen with rotary switches. For example in Falcon the rotary switches require a right mouse click to turn the rotary switch in an anti-clockwise direction. With some touch screens like the screens using the latest Touchkit drivers a right mouse click is supported by holding your finger on the screen for a short duration. But this is the problem I had - when you first press the screen you still generate a left mouse click that has to be undone. So it works like this: You press and hold the screen. You first generate a left mouse click, then by holding your finger down you generate a right mouse click. You continue to hold your finger on the screen you generate another right click. What this means is that using the rotary switches you initially switch the wrong way and it takes a couple of seconds to do two or more switches back the other (correct) way.
I don't use the 15" screen for Falcon like this normally, I just tried it to see how it would work.
