Sbob
SOH-CM-2024
OK, let's dive into this beast. Wayyyy back when FS2K was still "state of the art" in terms of freeware and FS2002 was well on it's way to becoming M$'s red headed step child in the FS line, Kirk Olsen released one of the most advanced freeware aircraft the community had seen. The mighty F-16 Viper. The (pre-GMAX) 3DO pushed the limits for what was possible back when VCs were still a novelty. The dynamics were even more advanced for FS9 because Kirk purposely modeled a computer controlled fly-by-wire cockpit, and it took some getting used to. You didn't fly the plane, you constantly updated the flight computers with the joystick and rudder inputs (ie, "suggestions").
Did it work? Well, mostly yes. The original flight dynamics took advantage of the new SDK for FS2004, which really didn't address fly-by-wire cockpits. Just ask the now gray haired Airbus fan boys who were up in arms back in 2004-5. The Viper also had to deal with other problems. In FS, airplanes with small wings weren't supposed to go fast or be aerobatic.
What this meant was that the Viper was twitchy beyond all get-out. Even if you took your time and built up your experience level in it, the Viper just never felt "right". I think a lot of this was due to the original Viper download, which was geared toward the Thunderbirds. The plane handled slick and twitchy because that was what you wanted for an air show. Later variants would come out with stores on the pylons in both the single-seat C model and dual cockpit D. The 3DO continued to get better with non-US variants that featured things like larger tail pods, drag 'chutes, conformal fuel tanks, and the big avionics spine. Still, the flight dynamics didn't change much, if at all.
That novel virtual cockpit was a lot of fun, until you looked inside the Panel folder to see what was going on.
To me, what it always looked like was that Kirk and his team would find problems during the coding and layout and just start throwing kitchen sinks at them until it worked.
Its an A+ for effort and, at best, a C- for efficiency. Meaning, its a bear to figure out what's going on with that VC. I'll get into what we can do about it in a later post.
So, let's keep things simple in this first post. One of the big drawbacks to the Viper happens when you try to fly it in cold conditions. Give it a minute or two after you take off and you'll see the airspeed in the HUD and the back-up ASI drop to zero. Oops, you just froze the pitot tube. There are two ways to fix this, either add a Pitot Heat switch to the 2D panel or let the flight computers deal with it and make the following change:
Open the Aircraft.cfg file and find the {electrical] section. It should look like this-
[electrical]
;BusType, MaxAmpLoad, MinVoltage ;BusTypes:0=MainBus,1=AvionicsBus,2=BatteryBus,3=HotBatteryBus,4-7=Generator/AlternatorBus(1-4)
max_battery_voltage=24.0
min_battery_voltage=24.0
max_generator_alternator_amps=400.0
generator_alternator_voltage=28.0
flap_motor = 0, 5 , 17.0
gear_motor = 0, 5 , 17.0
autopilot = 0, 5 , 17.0
avionics_bus = 0, 10, 17.0
avionics = 1, 5 , 17.0
pitot_heat = 0, 2 , 17.0
additional_system = 0, 20, 17.0
marker_beacon = 1, 2 , 17.0
gear_warning = 0, 2 , 17.0
fuel_pump = 0, 5 , 17.0
starter1 = 0, 20, 17.0
light_nav = 0, 5 , 17.0
light_beacon = 0, 5 , 17.0
light_landing = 0, 5 , 17.0
light_taxi = 0, 5 , 17.0
light_strobe = 0, 5 , 17.0
light_panel = 0, 5 , 17.0
See it yet?
pitot_heat = 0, 2 , 17.0
All you need to do is change that first 0 to a 1 -
pitot_heat = 1, 2 , 17.0
Now, you can fly above FL 200 or the Korean country side in winter with no hassles.
I like this fix better than adding a switch because it "feels" a little more authentic from the Sim's point of view.
Its also much quicker.
Speaking of Korea, there are many repaints available for the Viper and some nice ones feature the WP tail code.
Those planes fly out of Kunsan/Gunsan AB (RKJK) which is included in the stock scenery but its very simple.
BTW, Kunsan was officially renamed Gunsan when South Korea issued corrections to the english spelling of many of their words several years ago.
To keep it simple, just call it RKJK.
I spent years off and on trying to find some scenery or at least an AFCAD for RKJK.
MAIW did some great scenery for Osan but never did anything with Kunsan.
I found the one and only FS9 AFCAD files for Kunsan last weekend by mistake.
Head over to Flightsim.com and download pacafai2.zip or pacbases.zip and you'll find the FS9 AFCAD for RKJK.
The first zip has an AFCAD with a more "fighter-like" feel and some basic buildings included.
That first AFCAD also includes the odd long taxi way going north with a small apron.
That apron is the civilian airport.
You can tweak those parking spots with AFCAD2 or just leave them be.
ANYway, that's enough for today. In the next post I'll write about some of the competition to the Viper (KBT's F-2, Lago's F-16, and Dean's F/A-18C and D) and why you may want them installed along with the Viper.
The Viper has been around for a LONG time, if you have any insight or ideas on how to make it better, please drop a post or twelve in this topic.