Jump to content
Sign in to follow this  
33LIMA

The anti-Richthofen squadron

Recommended Posts

Hunting the Red Baron...in a dud aeroplane!

 

Shot11-18-16-22-09-53.jpg

 

You might be forgiven for thinking that the combination in spring 1917 of Britain's leading fighter pilot and the country's greatest fighter plane would have been the combat aviation equivalent of a marriage made in heaven. Far from it, for Captain Albert Ball DSO, MC (and later VC) was not at all impressed with the Royal Aircraft Factory's new Scouting Experimental 5. 'The S.E.5 has turned out a dud... It's a great shame, for everybody expects such a lot from them... it is a rotten machine', was his verdict. He'd been posted as a flight commander to the recently-formed No. 56 Squadron, working up at Colney Hatch in England before deploying to France. 'There were rumours of an anti-Richthofen squadron' wrote Alexander McKee in The Friendless Sky, 'and this was it.' Or as near such a thing as ever existed. "Fifty Six" was certainly something special. Not only was it first to be equiped with the first of the Royal Flying Corps' new types of fighter ('scout') aircraft, intended to match the Hun's Albatros V-strutters; to the squadron was posted an unusually high proportion of especially skilled and/or experienced pilots. Hence likely the rumour, which reached the ears of the great man himself, that the squadron was tasked with bringing an end to the career of Manfred von Richthofen.

 

Such was Ball's antipathy to the S.E.5 that he tinkered considerably with his own machine, adjusting amongst other things seat height, windscreen and armament. Some of these modifications were adopted for all the squadron's machines and those produced afterwards, like replacing the semi-enclosed 'glasshouse' windscreen with a smaller, conventional one and removing the little gravity-fed fuel reserve tank atop the wing centre section. Here is Ball in his modified machine, in typically bare-headed fashion despite the wintry conditions.
 

Ball SE5.jpg

 

Not only that, but on arrival in France, Ball pleaded with RFC boss Hugh Trenchard to be given a Nieuport Scout. 'Boom' agreed, with the proviso it was to be used only for solo missions, with the S.E.5 employed for all flight operations. While as squadron mate and Sagittarius Rising author Cecil Lewis said, the oiginal 150 hp version of the SE was not quite a match for the Albatros, it was, despite Ball's misgivings, a worthy contender in mid-1917 - and, with a more powerful motor, still a front-line fighter at war's end, a year and a half after it first saw action. Ball seems to have warmed to the type, for he scored eleven of his last thirteen victories in the S.E.5, before being killed in one in unclear circumstances during a disastrous series of patrol actions against Jasta 11 on 7th May 1917. Ball's memory lived on, and the S.E.5 went on to carve out an equally illustrious name for itself, in the hands of men like Jimmy McCudden, Arthur Rhys-Davids, 'Mick' Mannock and Billy Bishop.

 

A campaign in S.E.'s with 'Fifty Six' is something any WW1 simmer is likely to fly at least once; and this set of mission reports is from my own latest effort, flown in Wings over Flanders Fields. Now in its Ultimate Edition, with its hugely-immersive single-player experience, WoFF can fairly lay claim to being the ultimate WW1 air combat sim. And it wouldn't be WoFF if it didn't feature both 56 Squadron and the S.E.5. Thus equipped, I decided to start my campaign at the beginning of May 1917, at the point the tide had begun to turn and 'Bloody April' was, at last, behind the RFC.

 

It's good that WoFF features the S.E.5, because it's quite different visually from the 200 hp version we usually get in flightsims, and which didn't appear till late summer 1917. To digress, it's generally stated, based on official rigger's notes, that it was the S.E.5a version which introduced the more powerful 200hp motor, with a visibly-larger frontal radiator. However, in Crowood's Aircraft of the Royal Aircraft Factory, author Paul Hare reveals that works drawings show that the S.E.5a was created after only 23 'true' S.E.5s had been built, by cutting the length of the rear wing spars, reducing considerably the pronounced rake of the original wingtips. The early production S.E.5a retained the 150 hp engine.

 

As well as the early model I'm flying on this campaign, WoFF features S.E.5as with the geared 200hp Hispano-Suiza and the later (and more reliable) ungeared Wolesley Viper engines. A 'Hisso' S.E.5a is seen below, in foul weather over southern England; I think the wingtips should be a little less raked but she's a fine replica and looks much better since WoFF enabled us to lose the former wide-angle lens external view. The Viper engine had more angular edges to the radiator and a noticeably-lower thrust line/prop.

 

Shot07-11-16-23-57-07.jpg

 

The mission

It's 1st May 1917 and the weather is fine. 'Fifty Six' has settled down to the war at Vert Galand in northern France and today, I'm leading 'B' Flight on a Line Patrol up to the north-east, near Arras.

 

Shot11-18-16-22-06-30.jpg

 

'A' Flight has two machines on this show, in addition to my four. You can see one of the others - Rhys-Davids, no less, from his white fuselage marking - taking off to my right front, as I open up the throttle to start my own run. You can also see that painting the upper (and lower) wing roundels well inboard was an unusual feature of the markings of early S.E.'s

 

Shot11-18-16-22-05-09.jpg

 

I'm soon airborne and climbing away. The WoFF S.E.5 is a fine piece of work, and she sounds just as good as she looks.

 

Shot11-18-16-22-05-37.jpg

 

What sort of fighting machine she is, I expect soon to find out...which I will, though not quite as I might have expected...

 

...to be continued!

  • Like 3

Share this post


Link to post
Share on other sites

An unfortunate misunderstanding...

 

We have a moderately long leg to the front so I have plenty of time to get up to our assigned patrol altitude of just over eight thousand feet. In 'V' formation, we begin the climb, with one SE to my right...

 

Shot11-18-16-22-09-32.jpg

 

...and another two on my left...

 

Shot11-18-16-22-10-23.jpg

 

I have plenty of time to look around my nicely-rendered virtual cockpit...

 

Shot11-18-16-22-06-08.jpg

 

...and to admire the dramatic cloudscapes as we plough onwards and upwards, towards the front lines to the north-east.

 

Shot11-18-16-22-13-33.jpg

 

My machine carries a real 56 Squadron scheme, serial B'514 which was flown by Lt Richard T. Leighton. As well as flight and individual aircraft letters (and wheel hubs in flight colours) I have a red dumbell on the rear fuselage. I think the latter is a personal marking, as I think a wide white rear fuselage band was the first official squadron marking, later changed to two thin white bars angled inwards towards the top.

 

In plan view, I reckon the wing-tip profile - which I think is shared with WoFF's later-production SE's - is somewhere in between the sharply-raked tips of the S.E.5 proper and the much more squared-off wingtips of the 5a.

 

Shot11-18-16-22-16-36.jpg

 

Shortly after levelling out at our patrol altitude, like the best laid plans of mice and men things go awry. I realise that I haven't checked to see that my labels are set to display dot mode (which renders distant planes as specks, which would otherwise be invisible until they were rather unrealistically close). I decide I should rectify this. Having forgotten the keystroke to cycle through label types, I foolishly resort to trial and error. First, I manage to turn on text labels. Then, I try Ctrl+L. This turns out to be the (non-reversible) command for my flight to land. My comrades obey promptly, breaking formation and falling away!

 

Shot11-18-16-22-19-33.jpg

 

This leaves me in something of a quandrary. I don't particularly fancy washing out the mission completely, but I don't care much for going on alone, either. But as it happens, my faffing about with the labels helps me make up my mind. For it reveals one or more DFW two-seaters high and right, coming my way. Our AA boys aren't engaging them, so I might have missed them had it not been for the labels, though dot mode might have brought them to my attention soon enough, had I enabled it.

 

Shot11-18-16-22-19-58.jpg

 

It's strange that the Huns are from Flieger Abteilung 208 A, because the 'A' means their speciality is artillery observation, which they would not generally be doing this far behind the lines (the small 's' in their designation I believe means their unit is from the Kingdom of Saxony). But I can't possibly know any of this. What I do know is that these Huns are on our side of the lines and that it's now my job to deal with the blighters.

 

I turn off the labels, pull up my nose and turn gently onto an interception course. The Huns are just specks against the blue, but I can just about make out that there's no less than five of them!

 

This is going to be interesting...

 

Shot11-18-16-22-20-22.jpg

 

...to be continued!

Share this post


Link to post
Share on other sites

Up and at 'em!

 

Shot11-18-16-22-21-57.jpg

 

I turn back west and run ahead of the Huns, climbing as I do so. I find that despite losing speed in the climb, I am still slowly drawing ahead of them. So far, so good. The enemies fly on impassively, maintaining formation. Evidently they are not terribly worried about a single enemy fighting machine, even if it is from the anti-Richthofen squadron.

 

Shot11-18-16-22-22-18.jpg

 

The fact they seem so singularly unworried about me serves only to increase my desire to interrupt their cosy little sight-seeing trip. I decide that I am going to attack from head on, which should give them the wind up, good and proper. So I continue to climb.

 

Shot11-18-16-22-23-55.jpg

 

Looking down from the Huns' viewpoint, it's not hard to see why they appear so unconcerned. My S.E.5 looks rather lonely and insignificant, hardly much of a threat to the impressive Hun phalanx above and behind me.

 

Shot11-18-16-22-24-25.jpg

 

But soon, I'm up at their level, and I turn left into them. It's time to put a stop to their damned impertinence!

 

Shot11-18-16-22-25-48.jpg

 

However, I have turned in too soon, and find myself closing from an angle off their course. So I end up attacking the nearest DFW in a curve, pulling around to the right to keep my sights onto him as he flashes left to right across my nose.

 

Shot11-18-16-22-26-04.jpg

 

I get some hits, but am hit in return as one or more of the enemy observers get me in their sights. A light spatter of blood on the goggles indicates that I have been hit, as well as my machine. This isn't going so well! I tighten my turn and bank away to get out of their line of fire as quickly as possible, nosing down as I go.

 

Shot11-18-16-22-26-12.jpg

 

At this point, I really should have packed it in. But I can't bear the thought of those Huns smugly flying on as they watch me slink away with my tail between my legs. So I reverse my course and come back after the same DFW. If there is a way of attacking without coming into the field of fire of at least one of the enemy observers, I can't think of it, so I just go for him, coming in from the outside of the formation so as not to make it too easy for the beggars.

 

Shot11-18-16-22-26-47.jpg

 

I'm not sure who starts shooting first, but very soon, light pencil lines from tracer fire are criss-crossing the skies between us. Bits fly off my target, and suddenly, he noses down to the left. Got him!

 

Shot11-18-16-22-26-58.jpg

 

I break up and right but collect some hits before I am again out of range. The DFW I have attacked levels out and clearly isn't going down just yet. But I've certainly knocked him out of formation. Now, he's on his own. Not feeling so smug now, are you, I ask him in my mind.

 

Shot11-18-16-22-27-03.jpg

 

The DFW flies to the east, with me in hot pursuit. This is one enemy machine which won't be making it back to Hun-land, if I have anything to do with it.

 

Shot11-18-16-22-27-33.jpg

 

...to be continued!

Share this post


Link to post
Share on other sites

A narrow escape

 

I have already attacked this Hun two-seater twice and he can clearly see that another attack is coming. As I close in to make it, he begins a turn to the left, as if to give his observer a clear field of fire...

 

Shot11-18-16-22-27-40.jpg

 

I cut inside his turn, jink, and then go straight at him. All rather unsubtle, and hits are exchanged on both sides. At about 75 yards, I break low and left.

 

Shot11-18-16-22-27-56.jpg

 

This has the desired effect of taking me quickly out of his line of fire. But on he flies, seemingly no nearer to going down.

 

Shot11-18-16-22-28-54.jpg

 

I come around in a tight turn, looking back at the Hun. I can see now that he is losing altitude, and while he keeps his wings level, he is flying a tad erratically, porpoising slightly every so often.

 

Shot11-18-16-22-29-15.jpg

 

Sensing that another attack will do the trick, I tighten my turn...too much! I promptly spin out, treating the Hun to the sight of my S.E. spiralling earthwards like a falling leaf. The DFW promptly turns away, to make good his escape.

 

 

Shot11-18-16-22-29-24.jpg

 

I chop the throttle, put the controls neutral and apply opposite rudder. Nothing happens, except the spinning continues and the earth rapidly draws closer. I feel a tinge of panic. Have my controls been damaged, leaving me to keep on spinning until I hit the ground? Is this the end, already?

 

Finally, my machine responds to the controls, and I come out of the spin. I keep the nose down to build up speed, then begin pulling up. but at that moment, my engine splutters and the prop spins to a halt. I push the nose down again and try to re-start the motor, but she chugs then comes to a stop again.

 

Shot11-18-16-22-30-09.jpg

 

Now, all thought of knocking down the Hun is gone and my attention turns to finding a decent field for a forced landing. There are plenty to chose from, but many of them are rather small or lined with trees.

 

Shot11-18-16-22-30-41.jpg

 

I am mightily relieved when I see that I am close to an airfield. I turn directly towards it, keeping my nose well down in the turn to avoid another spin, which woud be extremely dangerous at this height.

 

Shot11-18-16-22-31-10.jpg

 

A rather steep, curving approach is the best that I can do, but it seems to go well enough. I see that am coming in rather fast and that I need to be careful not to run into the sheds. The fellows down there will surely not appreciate such a clumsy visitor.

 

Shot11-18-16-22-31-55.jpg

 

My wheels bounce once and then I'm down. I let the speed drop enough then pull back on the stick, so as to dig in the tailskid. This brings me to a halt opposite the hangars, where the ack emmas won't have too far to haul my kite.

 

Shot11-18-16-22-32-19.jpg

 

My S.E. is somewhat knocked about but repairable. As am I, apparently. The debriefing tells me that I'll be in hospital for nearly a fortnight. Hopes that my Hun might have come down after my last attack appear to have been dashed; if he did, it won't be credited to me.

 

56 Sqdn debrief.jpg

 

Not a great start! I should have washed out the patrol after inadvertently send my flight-mates away. Having decided to fly on alone, I shoud not have repeatedly attacked a superior enemy formation. Oh well. At least I came down in friendly territory, didn't completely wreck my machine, and wasn't hurt too badly. I'll soon be back at the front, ready for another crack at the bally old Hun, and this time, I'll be a bit more careful!

  • Like 3

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
Sign in to follow this  

  • Similar Content

    • By VonS
      INSTALLING WOFF BHAH 2 IN (CLASSIC) WINESKIN ON A MAC AND/OR THEN TRANSPLANTING THE ENTIRE INSTALL TO WINDOWS 10 BOOTCAMP (info. added May 3, 2021)   Directions below should be followed, first to install WOFF BH&H 2 in WineSkin on a Mac, and then (optionally) to transplant the OBDSoftware\WOFF folder to Windows 10 in Bootcamp. This will allow for a BH&H 2 install to co-exist with previous WOFF installs in Windows, and also makes use of the same settings/keys file, to minimize installation and tweaking hassle for us Mac-heads.   The steps below assume that you already have an older version of WOFF running in WineSkin on your Mac - because such an older install in WineSkin is necessary to have for the full installation, and testing, of BH&H 2, to complete itself (otherwise the install will fail). These steps also assume that you are familiar with the installation steps, instructions, jargon, etc., located under the long WOFF-on-a-Mac post that is available under the WOFF threads on SimHQ.   (Those who do not have a previous version of WOFF installed in classic WineSkin, which is necessary for all of the steps below to be completed, are recommended instead to try either a direct install of BH&H 2 in Win10 on the Bootcamp side/partition of a Mac, or to try installing BH&H 2 into newer WINE wrappers available via the unofficial and newer WineSkin fork available at https://github.com/Gcenx/WineskinServer.)   STEP ONE: go to https://sourceforge.net/projects/wineskin/ and download the latest classic, wineskin winery (ver. 1.7 as of this writing), via the green "download" button there   STEP TWO: double-click on the program; in the menu that opens click on the plus sign to the left of "new engines available," and in the list that then opens choose WS9Wine1.7.7, download it, and then - when you're back in the main menu - choose "create new blank wrapper" (now wait about 3-4 minutes for your Mac to make the custom wrapper; once finished, the wrapper will be placed in an Applications folder that has been made inside your user folder on OS X and/or macOS)   STEP THREE: double-click on the wrapper once again and choose "install software" in the main menu; then "choose setup executable" in the next window that opens and locate your exe file for WOFF BH&H 2 that you purchased; now let the wrapper do its thing to install the game   STEP FOUR: once installed, the wrapper will go back to the main menu and you can click "quit" (it may also prompt you to locate the program before it drops to the main menu, the program in this case being the exe file of the game that was just installed - best thing at this point is just to leave this alone and close that window, if it doesn't drop to the main menu automatically)   STEP FIVE: once the wrapper has quit, don't double-click on it but "right-click" it and choose the option in the popup menu on OS X and/or macOS that says "show package contents" (this will open the wrapper's folder and should list something like a contents folder, the alias to its c drive, and an app/icon called WineSkin); double-click on the app named WineSkin and you will open the main menu window again, of the wrapper; and choose "advanced"   STEP SIX: under the advanced menu, to the right of the box called Windows EXE (that contains a file path), click on "Browse"; this will open up your finder on OS X and/or macOS, and then you can scroll to your desktop or downloads folder on your Mac; look for the latest patch for WOFF BH&H 2 that you should have downloaded separately, from the official WOFF website, and choose that updater exe installer (click "choose"); then you're back in the WineSkin advanced menu with the proper file path for the update patch's exe now listed in the box near the top of the window; now quit that WineSkin preferences window and go back to the main WineSkin app that you previously created - and then double-click on the main WineSkin app icon so that a window opens and which will allow for an installation of the latest update patch to happen (follow directions that pop up in the relevant window, to install the WOFF BH&H 2 update patch); once the process has completed, quit the main WineSkin program again, if it does not close automatically   STEP SEVEN: right-click on the main WineSkin wrapper once again, choose "show package contents," and then double-click once more on that secondary WineSkin icon/wrapper mentioned in STEP FIVE above; under its "advanced" menu, to the right of the box called Windows EXE (that contains a file path), click on "Browse"; this will open up your finder on OS X and/or macOS, and then you can scroll into the "drive_c" of the wrapper into which you installed WOFF BH&H 2 and then patched it to its latest version; in "drive_c" look for "OBDSoftware\WOFF" and scroll into there, and keep scrolling until you find "WOFF.exe," and choose that (click "choose"); then you're back in the WineSkin advanced menu with the proper file path for the game's exe now listed in the box near the top of the window; now close that secondary WineSkin wrapper window   STEP EIGHT: copy or move the now updated OBDSoftware\WOFF folder that resides in that WineSkin wrapper to your desktop; the WOFF folder is found by right-clicking on the main WineSkin wrapper and choosing "show package contents"; the package is located within the "drive_c" folder, by the way   STEP NINE: now locate the WineSkin wrapper for your earlier edition of WOFF, double-click on it and select "show package contents," and navigate to the relevant "drive_c" directory to locate the OBDSoftware\WOFF folder that corresponds with that older variant of WOFF; rename that folder to something like OBDSoftwareOld\WOFF and move it to your desktop; now copy over, to that location instead, the fresh OBDSoftware\WOFF folder that corresponds with BH&H 2, from your desktop   STEP TEN: copy and replace the OBDSoftware\WOFF\OBDWW1 Over Flanders Fields\campaigns\CampaignData\Pilots folder in your fresh BH&H 2 folder (that should be in the older WineSkin wrapper by now, as explained in the previous step) with the same folder from OBDSoftwareOld\WOFF that is now on your desktop (this is an important step; otherwise, BH&H 2 will not open in WineSkin unless this older Pilots folder transplant is done)   STEP ELEVEN: now close all unnecessary WineSkin windows and double-click the main WineSkin wrapper icon for your earlier edition of WOFF but that now contains the newer OBDSoftware\WOFF folder with the transplanted CampaignData\Pilots folder; allow BH&H 2 to open; recommended is to fly one quick combat mission or one of the other instant missions available, to allow all necessary files to populate successfully in your install; congratulations!, you now have a successful WOFF BH&H 2 install running in (classic) WineSkin; you may now quit WOFF BH&H 2   STEP TWELVE: optional at this point, if you like, is to copy the now functioning and tested WOFF folder that resides in your BH&H 2 WineSkin install (the one located at OBDSoftware\WOFF), to a Windows 10 partition on your Mac, or perhaps to another Mac (or Windows machine) where you already have an older version of WOFF installed; there will be no need to un-install that older version of WOFF that resides in Windows; simply rename that older version to something like WOFF UE or WOFF PE, in order to run BH&H 2; if you want to run the older version of WOFF again, rename the newest WOFF folder to something like WOFF BH2, and the older one simply to WOFF, and the old version then becomes functional; both installs will coexist happily, and will also use the same keys/settings located under AppData\Roaming\OBD_Games\OBDWW1 Over Flanders Fields (recommended, however, is to map extra keys for Lewis gun loading/reloading into the older WOFFKeys.xca file that you have, for full, functional use of that gun in BH&H 2)   NOTES: Don't forget to swap back your older OBDSoftware\WOFF folder into your WineSkin WOFF wrapper, on your Mac, if you will not be running BH&H 2 in WineSkin but only in Windows; or, make a copy of your functional WineSkin install instead, place the older WOFF folder into that wrapper, and enjoy running multiple versions of WOFF that way too, directly in OS X/macOS (recommended is to give the multiple WineSkin wrappers different names, to avoid confusion, if you choose such a setup); no guarantees that the instructions posted above will result in a stable install of WOFF BH&H 2 on your Mac, but there is a fine chance that careful following of the instructions will result in a good install   ----- ADDENDUM: WOFF BHAH2 BOTTLING (Brief Illustrated Tutorial; info. added May 4, 2021)
      Please find included below some tutorial pics. for how to install/extract WOFF BH&H2 into an empty WineSkin bottler that should first be optimized for WOFF BH&H2 bottling and that runs well on Mac OS X versions 10.5 to 10.12 (for macOS versions 10.13 and higher, recommended instead is to see the unofficial WineSkin port for Macs at https://github.com/Gcenx/WineskinServer). Bottler not supplied for download here; recommended is to make your own either via classic WineSkin, and then to install BH&H2 as specified in the pics. below, or to install/bottle via a newer WineSkin as per the link given immediately above.
      The "BH&H2 Bottler" in my case, on my Mac Mini, has been set to Windows 7 compatibility, with WINE Wrapper version 2.6.2, and WINE Engine WS9WINE1.7.7. No WineTricks have been installed because this wrapper ONLY installs WOFF BH&H2, and individual patches for BH&H2, into ready and transportable form, but does not serve up a functional, running BH&H2 install within the wrapper itself.
      To set up a functional, running install of BH&H2, proceed to look carefully over the final illustrated instruction set provided below, and as well do read over the more thorough installation directions located under this relevant WOFF-on-Mac post (above) or the longer one on SimHQ that also covers installation info. regarding WOFF UE/PE before focusing on BH&H2.
      NOTE: Successful transporting of a functional, running install of BH&H2 onto a Win10 partition on your Mac (should you choose not to run BH&H2 in WineSkin) - requires that you also, already have an older version of WOFF installed on the Win10 partition/drive, since that older version has created the necessary Windows registry files for WOFF, as well as other necessary folders that contain keyboard/joystick customizations for WOFF, etc.
      Happy bottling, transporting, and flying of WOFF BH&H2,
      Von S 
       
      Classic WineSkin Main Window - Use "Install Software" button to install BH&H2 and all relevant update patches

       
      Right-Click Maneuver - After BH&H2 has been installed and patched, right-click and choose "Show Package Contents," to display directories

       
      Navigating to C Drive - Double-click on the "drive_c" alias to enter the c drive main level directory

       
      Locating the "OBDSoftware" Folder - The relevant folder will be located inside the main level, c drive directory (see further explanations provided on the pic.)*

       
      * Recommended is to keep a copy somewhere on your Mac of such a bottled, patched, but non-functional WineSkin wrapper with BH&H2 installed and patched inside it - this way you may patch/update the bottled version whenever new patches come out, and then carefully follow the same procedures as explained in the pic. immediately above this note, in order to be able to fly the latest version of BH&H2 either in WineSkin wrappers or in your Win7/8.1/10 Bootcamp partitions.
    • By VonS
      Hello fellow WOFFers,
      Thought I’d open this separate thread for a future mods-compatibility list for the ver. of BH&H 2 (WOFF) that will be released soon. Becker is welcome to make use of this thread for his long mods-compatibility list that is currently hosted on the WOFF threads over on SimHQ. I will also use this thread to update regarding my FM mods., GPU Tuner Patch, etc., in the future and time-permitting.
      For convenience and simplicity, I encourage everyone who is a member/user of CombatAce to post mods-related questions for BH&H 2 WOFF under this thread, since it will be easier to find mod-compatibility info. that way. While most WOFF-related mods. are available via Sandbagger’s site for WOFF addons, this thread will hopefully prove helpful for compatibility questions, info. regarding release of new mods. not hosted on Sandbagger’s site, etc. - and ideally will become a centralized hub for mod-related topics since there are too many mod-related threads over on the SimHQ forums for WOFF and it becomes confusing/discouraging to navigate for new WOFF fliers who might wish to load up quickly on WOFF goodies and fly.
      OBD, feel free to delete this thread if you will be posting a separate stickied thread for mod-compatibility questions, etc.
      For those interested in downloading my FM tweaks packages for the Ultimate and Platinum Eds. of WOFF, as well as GPU Tuner Patches for the Platinum Ed., including for WOTR Phase One, and the small FM tweaks package for WOTR Phase One - please see the link included immediately below. Those WOFF-related packages are not compatible with the latest, BH&H 2 edition unless otherwise indicated in this thread. I am currently busy with work and other duties, so my limited modding time will be devoted only to First Eagles 2 for the foreseeable future.
      Tweaks Packages for Previous Eds. of WOFF, etc.
      EDIT: to find my previous and current mods packages for WoFF/WoTR, click on my propeller icon here on CombatAce to go to my main profile page. Once there, click on the "about me" tab to find all relevant info. and mod download link(s).
      Cheers all,
      Von S 
    • By Kodokushi
      I created a deck to use with the Matric Android app to control WINGS OVER FLANDERS FIELDS: BETWEEN HEAVEN & HELL II.
      Intro
      I'm so new to the game that I still don't know just what I don't know about playing it I have a little bit of flight sim experience in the past but having recently read the remarkable book Marked for Death  byJames Hamilton-Patterson I used google to learn more about WWI flight, found WOFF and jumped in running. I've never been fond of using a keyboard to enter sim commands I'm grateful for this forum, it's been instrumental in helping me get started, my thanks to everyone who has contributed. I'm not affiliated with Matric app in any way, I'm just a guy trying to figure things out The Matric App
      Their Website http://matricapp.com/ All edits are done on the desktop app that is a free download  The mobile app communicates with this desktop app to work with your game (Or photo editor, videos, music, etc. etc. Matric is useful beyond gaming) Google Play Store on Android phone or tablet to get the mobile app.  Cost for the app is scaled based on what you can either afford or how much you value it ranging from $12.99 to $19.99 you choose how much you  pay. I use a Kindle Fire tablet that I found a work around to get the Play Store on How I use Matric in WOFF
      I set up my deck to have everything I didn't have set up already on other devices (you may see buttons you don't need or need more but this is easily editable)  I use SmoothTrack Face Tracking App on my Android phone with Opentrack on my computer so I didn't need the eye movement commands As an aside, I have tried many setups and this is the best inexpensive solution I have found for face tracking I had trouble with my VKB Gladiator NXT Joystick so I pulled an old Logitech Extreme 30 Pro joystick out and started using it.  I think the Gladiator issues are related to some setup I was doing for IL2 and not related to WOFF, I will dedicate the time later to getting it going in WOFF but the Logitech works fine for now. the Logitech has a few commands on it, these are not on my Deck I changed a handful of commands while playing around with setup, please be aware if you download my deck that the following are not standard WOFF commands: Fixed Views Toggle Control+NumberPad5 Select Next Weapon Conrol+NumberPad2 Right Rudder Trim Control+NumberPad6 Left Rudder Trim Control+NumberPad4 Increase Time Compression Control+Semicolon Quality Control If you find an error in my deck, please share it here, I haven't even pushed every button in game yet. Future Plans
      I expect my decks to change quite a bit as I learn. Some buttons will be removed, some changed in look or groupings.  Dedicated decks built for given plane types that have identical or very similar commands, removing commands that do not apply to those planes Move buttons that are needed to access quickly (Combat) in sizing and location to fit my needs as I learn I already have Blip button and unjam guns at the edge of the screen and large in anticipation of needing them quicker I can see moving or copying the Wingman commands to the Weapon and Combat page to access them in the heat of battle without changing pages Decks for realistic flying without any navigation buttons, just the bare basics after I get competent Add maps as pages to decks, they will not be scrollable, but multiple pages that are static maps (images) can be added.  Area around landing field for sure As much of the engagement area as possible as additional pages I hope that some of you here use Matric and contribute your work so that I can implement your improvements into my own setup. If there is another option for this type of tablet based game control that is inexpensive I'd love to hear your experience. For now I can't think of anything that would make me change but I try to keep an open eye as to what is out there. Get my Deck for Free if you have Matric
      Kodokushi WOFF BHAH2 Flanders Field 1.1.2022 Deck • Matric (matricapp.com) Or seach 'Kodokushi' from the desktop Matric app  I plan to date my decks as I update them and will try to keep on top of removing the older decks if they seem obsolete compared to newer efforts  




×

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..