Jump to content

Recommended Posts

img00118-2.thumb.JPG.9531d02de3c7b712ee1c28d7961963f2.JPG

 

Okay so the Rolling Thunder campaign was never my favourite campaign from the series, in fact might be the most bland. The main reason for this was most probably the fact that there is no forward line of troops and tank columns to fight it out, and gain or lose ground after each mission.

 

Rolling Thunder for real
The campaign namesake this is based on was one of the most disastrous and misguided campaigns in the history of aerial warfare. What was hoped would be a few weeks of bombing missions to get North Vietnam back to the negotiating table to stop them trying to invade the South, turned into 3 or so years of bombing targets selected by Washington. Or to put it another way pussy footing around bombing things that did nothing more than improve North Vietnam's resolve to continue on its agenda and also allow it to build up its defenses with the help of the Soviet Union and China.
So, 3 years of bombing targets – many times the same targets over and over, and never achieving the desired US strategy.

 

img00118.thumb.JPG.a0fa1d8e5bde48449119f53a486ee9ff.JPG

 

Rolling Thunder in game
In the Strike Fighters game engine this translates to what seems like a string of single missions and yes you don’t have much of an objective other than to try and not get shot down.
However, unlike auto generated Single missions, Campaign missions are more content filled and almost always include strike packages and flights that help you do your job (If you at least meet your timings). Not only that all the units have their markings and decals as they should.

Like history there are no SAMs until mid 1965 and the MiG regiments are limited in number. One great thing about TKs games is the use of "dates", so the game engine can just plonk in the correct objects (Guns/SAMs/MiGs) depending on the date you are flying. This also includes getting rebased and upgraded to better aircraft during the campaign.

img00143.thumb.JPG.7f6c5c585a7681abdacb3f9e245cc75e.JPG

 

Vietnam Gold
Like most things in Strike Fighters World, mods can really help and I am using the Vietnam Gold mod with a variety of my own changes. This comes with quite a fearsome atmosphere with a ton of guns shooting at you with purple stuff, red stuff and grey puffy stuff. A major benefit is a bigger variety of targets and not just the sodding comms building again.

 

Gameplay
Feb 24 1966 and I am flying from Da Nang in an F-100D (1964 version) for the 416th “Silver Knights”. I don’t know what it is about the F-100D that I like because it is outclassed by pretty much all the MiGs.  

The Lang Chi Electric Power plant is my target (a welcome addition from gold pack I think) – and I need to be on target for 09:10 on the dot.

img00123.thumb.JPG.8ad86e0cb07eacd79fb5cbd24cb29de9.JPG

 

 

I am maxing out the M-117s here – there are plenty of them available. The SF2 Super Sabre also allows TERS to carry 4 on the inner pylons by default but with extra drag.

img00124.thumb.JPG.c9e3359e4fc228c62b22a3f5adfb7052.JPG

 

How to get there hmmm. Those that played Wings Over Vietnam will know various routes into the North to minimise exposure to the SAMs, some of which had a 90% plus probability of kill if you were not flying at about 5ft off the ground. Luckily the SAMs in SF2 and this pack allow you to fly a bit more as they tended too back then!
With a target near Yen Bai I can use the highlands as cover and cross in over South NVN where there are little to no SAMs.

img00125.thumb.JPG.8e46b2d6630987ba6b31e37f2dab0e9c.JPG

The Square box waypoint (the Initial Point /IP) is also the spawn point if you use Alt N, so can be moved around if you don’t have time to fly there.

Waypoint 3 is fixed as a rendezvous with other flights. If SF2 had been developed, it would have been nice to change the waypoint details for the flights like in Falcon so you could move the fixed waypoint for all flights.

Another thing that could have been improved was seeing your actual target area before flying. If you consider Jack Broughton spent all night memorising features etc before going on a mission you can understand the point of just marking the actual target with Padlock or a red dot!

As you can see only 2 MiG regiments active with MiG-17F and MiG-21F-13.
 

First Lt Eldon Atterbury is my wingy today. If you do take time to nurture the pilots their stats do improve (if they survive)


img00127.thumb.JPG.322c44eeda6bd0d8a19756ffcf78730b.JPG

 

Let's go then

img00131.thumb.JPG.67879f579f0a5ab41dbebf7f1298b37b.JPG

 

As we fly towards the target other flights are also on route to their targets.

img00133.thumb.JPG.8724808d9deea633d710983842ba6721.JPG

 

After a while several fights occur

img00135.thumb.JPG.381fbe7b66e7b9155df7f81e53b9dcf4.JPG

img00140.thumb.JPG.9a4b9d91d849cff372f829067987a08b.JPG

 

Due to meticulous planning we reach the target just fine and we roll in from above the cloud base

img00144.thumb.JPG.5453f3aabc3f35a0869cfd769f1c26f0.JPG

 

 

I hit the target but get peppered by a lot of triple A

img00153.thumb.JPG.0c93c76eaeae963411f9f123afabc5c7.JPG

 

Phew heading out but think my Wingy is a bit lost.

img00157.thumb.JPG.2ba82fda41323131d7ce04dcc425ab0b.JPG

 

 

Try to search, but no sign of him and no beeper! so off home alone

img00158.thumb.JPG.e19a8c4dc5cb10b1eeabe7a41e9b9326.JPG

 

 

Mystery solved, a MiG-21F-13 gunned him down and I had no idea that was in the area!  If only all Vietnam mysteries could be solved so easy!

img00161.thumb.JPG.feed01f6149d4f3ba9593d1e528f8a8e.JPG

 

I then went on to fly A-4C/Es for the US Navy in which you get to take off from Carriers in the Gulf on Tonkin

img00179.thumb.JPG.503870df6619b2d7e38e479f30af737f.JPG

img00182.thumb.JPG.3297586013373fc144e50d71aae01179.JPG

 

Mr SAM is always happy to see you

img00188.thumb.JPG.de1ab332c3e6d554c2d7117f0e9597ad.JPG

 

This thud was just lucky!

img00189.thumb.JPG.ddf315249bce1b79c1a24c12e2c1e0d4.JPG

 

This thud was not so lucky

img00191.thumb.JPG.1fde337126d07c3e4e73e1e31105631d.JPG

 

What are all those blotches

img00177.thumb.JPG.1c049a6879b56bed65b25f4e3c2b190a.JPG

 

So still quite intense flying through all the anti air and check 6 for those MiGs as always!

img00170.thumb.JPG.58208ab6a14534c75eb8e85649e7dfe4.JPG

 

 

 

 

 

 

 

 

 

 

 

  • Like 11

Share this post


Link to post
Share on other sites

Green Hell 3.5

On further examination I think I'm already using the 'Gold' Vietnam air & ground expansion, with Green Hell 3.5 & it's enhancement package over the top, so "it's as good as it's gonna get". In any case I can't remember the last time I flew standard SF2 Vietnam, that's how good the A-G expansion is.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By VonS


      View File SF2 Cold War Prop and Flogger FM Tweaks
      Hello SF2 Flyers,
      For the post-WW2 prop. high-performance aircraft, several tweaks have been applied to the data inis, ranging from lift values for wings and wing tips to the engine section, prop. rpms, flight control section, gears section, flaps, also empty weight, inertia values, ceilings, engine sounds, rudder reversal effect fix, aileron/elevator/rudder sensitivity and movement, etc., depending on the type tweaked. Tweaks are not as extensive as for my FE2 work - but I've tried to get them into the "90% realistic enough" category for SF2 since these high-performance types are difficult to precision peg to within a km or two of historical stats., in contrast to the slower-moving FE2 types. Also included with this package are my minor data ini tweaks for several Flogger types, such as the MiG-23 S, early M, ML, P, MLA, late variant "98," and export variants MF and MS.
      Many thanks to the original FM modders for the late prop. types, including Baffmeister, Wrench, Cocas, MontyCZ, Charles of A-Team, Coupi, Paolopanz, and others I may not have mentioned here. The data inis are for SF2 installs only, tested at hard FM settings (no guarantees that the AI can land them nicely, although they fly them just fine). The Me109 G5 and H0 are variants on the stock G10 package provided on CombatAce (to install simply copy the relevant aircraft folders, rename as per my included folders, and drop in the relevant files). P-47 Sprint upgrades are variants on the ETO P-47D Bubbletop model and PTO P-47D Razorback model linked to above. Also included with this package are three sounds for a Pratt-Whitney, Centaurus, and Me109 either Benz or Hisso powered (sound works good for both). Links to the relevant aircraft that correspond with these data ini tweaks are located in the included "Read Me" file with the package. Please go through the Read Me for more thorough info. regarding these FM tweaks.
      Happy flying,
      Von S 
      Submitter VonS Submitted 04/15/2019 Category ini File Edits  
    • By VonS
      Hello SF2 Flyers,
      For the post-WW2 prop. high-performance aircraft, several tweaks have been applied to the data inis, ranging from lift values for wings and wing tips to the engine section, prop. rpms, flight control section, gears section, flaps, also empty weight, inertia values, ceilings, engine sounds, rudder reversal effect fix, aileron/elevator/rudder sensitivity and movement, etc., depending on the type tweaked. Tweaks are not as extensive as for my FE2 work - but I've tried to get them into the "90% realistic enough" category for SF2 since these high-performance types are difficult to precision peg to within a km or two of historical stats., in contrast to the slower-moving FE2 types. Also included with this package are my minor data ini tweaks for several Flogger types, such as the MiG-23 S, early M, ML, P, MLA, late variant "98," and export variants MF and MS.
      Many thanks to the original FM modders for the late prop. types, including Baffmeister, Wrench, Cocas, MontyCZ, Charles of A-Team, Coupi, Paolopanz, and others I may not have mentioned here. The data inis are for SF2 installs only, tested at hard FM settings (no guarantees that the AI can land them nicely, although they fly them just fine). The Me109 G5 and H0 are variants on the stock G10 package provided on CombatAce (to install simply copy the relevant aircraft folders, rename as per my included folders, and drop in the relevant files). P-47 Sprint upgrades are variants on the ETO P-47D Bubbletop model and PTO P-47D Razorback model linked to above. Also included with this package are three sounds for a Pratt-Whitney, Centaurus, and Me109 either Benz or Hisso powered (sound works good for both). Links to the relevant aircraft that correspond with these data ini tweaks are located in the included "Read Me" file with the package. Please go through the Read Me for more thorough info. regarding these FM tweaks.
      Happy flying,
      Von S 
    • By VonS
      Hello gents',   Thought I'd post some speculations and observations on the FM aspects of some things in FE2 and SF2 that I've recently been tinkering with. This might be an interesting post for those who like to follow these technical threads.   I was recently installing more aircraft into my small SF2 install - something I wanted to get to last year but had no time - and I decided to install a couple of the late prop aircraft too, particularly the SeaFury and F4U-5 variant of the Corsair. Overall pleased with the handling of the types, I tweaked a few things such as desensitizing the rudder on them, and also giving them slightly heavier aileron feel - since those late model prop aircraft were fairly heavy, about 4500 kg on average.   Further testing involved flying and inspection of the [FlightControl] and [Engine] sections...couldn't get much beyond about 500 kph near sea level or at alt. in the types...so I commented out the MaxSpeedSL entry for the FlightControl, and tweaked prop speeds to close to historical, within the 2000 to 3000 rpm range, also pushed up the value for the SLPowerDry entry for the Engine, usually by a noticeable amount, and then tested further.   Some of the things I've noticed, in terms of SF2 specifically (but this post is relevant to FE2 too):   a) WEP power is not modelled realistically, since you can keep running it without engine damage   b) WEP power doesn't give much of a boost, if at all (although I've only tinkered with the SeaFury and Corsair so far)   c) a better way of simulating, however simplistic it is, the potential of WEP power, is to manipulate the AltitudeTableData numbers instead (for example, I plugged in values ranging from about 1.05 to 1.35 around the 6000 m alt. band, which should be where the Corsairs benefitted the most from max. throttle)   d) after manipulation of the AltitudeTableData, it's best to get rid of the WEP entries entirely, and set up "throttle gradients" instead under the engine sections, such as:   ThrottleRate=0.65
      IdleThrottle=0.12
      CruiseThrottle=0.45
      MilThrottle=0.70
      MaxThrottle=1.00   The numbers above I've plugged in, for example, for the Corsair. The space between Military throttle and Max throttle would be where "WEP power" would theoretically in this case be engaged, somewhere around the 0.85 mark for the band I've selected above. For this to work somewhat realistically, the player should restrict themselves to about 85% throttle max. except in extreme situations, depending of course on where military and max throttle are set. Also important for this to work is to make sure that the max SL speed under the FlightControl section is left uncapped (commented out) - otherwise artificial barriers are set up that cannot be bypassed by more than about 20-30 kph.   Speed caps work beautifully in SF2 for the jet engines, but, at least from my experience, don't work that well with the late prop planes since you can then never hit top max. recorded historical speeds, not even at alt. - and not at SL either. Also noticeable in the example above is that I've increased the throttle rate from the default of about 0.25. Historically, late prop aircraft would have had better acceleration than early jet planes (not better top speeds, but faster acceleration to their own max speed). By the 1960s/70s, jet engines should surpass the props even in acceleration.   I then re-tested by dumping the modified Corsair into my FE2 install. In SF2 it can get into the 760s kph, as historical, using the engine and throttle values I've included in my graded throttle settings above, while in FE2 the same tweaks push the top speed into the 880s kph - a difference of about 120 kph for top speeds, across FE2/SF2.   This is why it's not a good idea simply to transfer data inis from one of the sims to the other. I'm assuming that the discrepancy in top speeds means that TK went with calculations to give less air resistance in FE2 (maybe FE as well?) - to fit better with the more fragile and maneuverable WWI aircraft types. One thing that remains constant between FE2 and SF2 is that, at least from my observations, the WEP modelling is not very realistic - there was no high alt. band where I could push the top speed beyond, for example, a reasonable top speed that may have been possible at near sea level (such as 500 or 600 kph).   Some preliminary conclusions, to be tested further:   a) speed caps at sea level should be kept in place in FE2, as done in the data inis in my FM packs, since they fit better with the lower top speeds of the early aircraft anyway, and mach limits should also be kept fairly low (I have them set at 120% of the "top speed" of the WW1 aircraft....this allows for realistic dive speeds that I haven't been able to push beyond about the 460 kph mark even on the late war types such as the SE5a)   b) flying late WW2 and early Cold War prop aircraft in FE2 is not recommended, but FE2 may be good for "Golden Age" stuff, as Geezer speculated upon in another thread (can't remember the link for that now), in other words for aircraft that don't have a top speed higher than about 350 or 400 kph   c) the difference between top speeds at alt and at sea level are modelled just fine for the jet engines in SF2, since caps on SL speeds, and Alt speeds, work fine for those (have seen this in some Flogger tweaks that I did for my mini-SF2 install); in other words, SF2 respects the wet/dry mach values and alt table entries beautifully for jet-age stuff   d) I think that the MaxThrottle value in SF2, for the prop aircraft, could use some more tinkering/testing...I've set it at 1.00, but will try other values of 1.20, 1.50 etc., to see if this creates more realistic differences between regular power and WEP, or some kind of "accordion" effect   e) as it stands, I'm enjoying the SeaFuries and Corsairs but only with SL speed uncapped and giving historical top speeds not at alt. but near sea level (this is a compromise of sorts since, at alt, they still make about 600 kph and sometimes a bit more - so I'm not terribly irritated by not attaining 740 kph at 7000 m alt or so, for example, in the SeaFury, as recorded for that plane)   f) a couple of pics included below of the AI in SF2 now losing control of their F4U-5 Corsair during a scrap, and doing several back flips (too much throttle applied perhaps?); he then bails out of the otherwise undamaged plane; so, overall, I'm liking the realism of some of the haphazard maneuvers they now make, and also the increased speed at which these late prop fights now happen, even on the deck   g) anything that I find of further use in the SF2 data inis, and if relevant to FE2, I will tinker with more to bring even more realism into FE2 (the lockout speed trick implemented for control surfaces in the alternative Morane-Saulnier type N data ini posted under the FM thread for FE2 is an example of things discovered while combing through the SF2 files)   Happy flying,
      Von S   

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..