Jump to content
33LIMA

Sopwiths Over Flanders Fields 3

Recommended Posts

Tripehounds!

 

Shot10-04-16-22-43-00.jpg

 

There can't be many aircraft prototypes that have been looped on their maiden flight. But I do know of one that was - three times in rapid succession, a few minutes into the flight. It was the Sopwith Triplane, courtesy of the Sopwith Aviation Company's famous test pilot, Harry Hawker, who gave his name to the firm when it was effectively reconstituted to avoid a crippling tax bill, post-war.

 

The Tripe or Tripehound, as it was known, served only with the Royal Naval Air Service and (apart from one machine) not with the Royal Flying Corps (though the Aéronavale had a few, for a while). And it equipped few squadrons, lasting longest with  'Naval 1', which was fully operational with the type in early 1917 and didn't give them up for Sopwith Camels until about November the same year.  But the Tripehounds certainly made a big impression, on friend and foe alike. They say that imitation is the sincerest form of flattery, and the success of the fast-climbing and highly-manouuvrable Sopwith Triplane spurred a German 'triplane craze', with many plane makers rushing to develop prototypes, of which only the famous Fokker Dr.I saw significant combat service. I don't believe the two ever met in combat but you can see them in a fairly leisurely mock dogfight in this HAFU video. The Sopwith reproduction is in the 'Black Maria' markings of ace Raymond Collishaw, leader of the famous 'black flight' of 'Naval 10'.

 

https://www.youtube.com/watch?v=yDFeiknDa88

 

For this campaign in the Sopwiths over Flanders Fields series, I've opted to fly with pioneer Tripehound squadron 'Naval 1', starting in May 1917 for no better reason than at that stage, we've moved to la Bellevue, closer to the front - I fly my Wings over Flanders Fields missions in real time, so I appreciate the shorter transit flights! My pilot is Richard Collishaw, possibly 'Naval 10' ace Raymond's (imaginary) brother. As usual, having ticked the 'always lead' option, I'm in charge of 'B' Flight, with 'A' Flight AI-led and no 'C' Flight.

 

Tripe1.jpg

 

My first mission is a run up to the lines to the east-north-east, responding to a ground observer report of enemy air activity in the sector. There's four of us in 'B' Flight (all with proper naval ranks, like 'Flight Sub-Lieutenant') and 'A' Flight is putting up another five Tripehounds, to assist us in an unspecified fashion.

 

Tripe2.jpg

 

And here we are, lined up and ready to go. The dire weather of 'Bloody April', replicated in WoFF when you have 'historical weather' selected, has happily given way this early May day, to blue skies with but a scattering of small clouds. Several (but not all) 'Naval 1' Tripehounds carried the two small white bars seen on mine and some other machines in this line-up; the kites with the white fins display a variation that is common on Sopwiths.

 

Shot10-04-16-22-38-09.jpg

 

I check my controls while my 130 HP Clerget rotary engine fires into life, then it's off we go!

 

Shot10-04-16-22-39-04.jpg

 

Once well off the ground, I throttle back (which in rotaries, if I recall right, was either via a 'blip switch' which cut the ignition, or a variant which did so for some cylinders). This gives me time to admire the weather, my mount and the scenery, all of which WoFF reproduces very nicely, thanks in no small measure to Ankor's DX9 mod. A thing of the past is the exaggerated 'wide-angle lens' external view, for one thing.

 

Shot10-04-16-22-39-43.jpg

 

The view from the 'office' is just as good. You can't see it in the picture below, but it includes an animated propeller-driven pump mounted on the right-hand centre section strut. I'm glad the WoFF riggers have fitted a square pad to protect my virtual pilot's head from the breech of the Vickers Gun; it blocks the view much less than Sopwith's patent 'flattened doughnut' padded windscreen, as fitted to the WoFF Pup and Strutter.

 

Shot10-04-16-22-41-30.jpg

 

One thing I quickly find that I don't much like about my Tripehound is that she is determined to roll to the left. At all engine speeds, quite a lot of aileron deflection is needed to keep her level. This is uncomfortable in transit and will undoubtedly be awkward in combat. But there's no point dwelling on it. When the others get into 'V' formation on either side, I open her up and swing around in a climbing turn to the front. What will await us there - if anything - we will find out, soon enough.

 

Shot10-04-16-22-39-51.jpg

 

To be continued!

Share this post


Link to post
Share on other sites

We find company, over the lines!

 

Shot10-04-16-22-42-09.jpg

 

Reflecting further on my Tripehound's tendency to roll left - not seen as strongly or at all in other rotary-engined sim aircraft I've flown, including the Rise of Flight Triplane - I notice that with stick central, the ailerons on both sides are somewhat depressed, which effect is visible in the picture above. I really must have a word in the ear of my rigger when I get back to la Bellevue, I decide.

 

Looking back, I can see that the flight-mates on my right are keeping up reasonably well, as we climb towards the lines.

 

Shot10-04-16-22-41-54.jpg

 

To my left, the other two chaps are edging somewhat ahead, leading me to wonder if I had echelon formation selected, rather than 'V'. I can't change this in flight, so it'll have to do.

 

Shot10-04-16-22-49-01.jpg

 

About half-way to the lines, I see a formation of five aircraft as they emerge from under my nose, passing below and ahead of us, moving from left to right. They pay us no heed, and are not being fired upon by our own gunners, so I'm confident that they are the five machines of 'A' Flight. Where they're going, and what they intend to do when they get there, I am less sure of.

 

Shot10-04-16-22-45-17.jpg

 

We're approaching ten thousand by the time the shelled area becomes visible, ahead and right. In the pic below, you can see the little prop whizzing around on the strut-mounted generator or pump to my right. It's said that the Sopwith Triplane was evolved from the biplane Pup so that the more slender wings would give the pilot a better view, and overall, in this it succeeds quite well.

 

Shot10-04-16-22-49-41.jpg

 

We arrive at the front pretty well on track, over the town of Arras itself, which gave its name to the battle for which 'Bloody April' was fought the month before. Some buildings are still standing, but much of the town has been smashed by shellfire.

 

Shot10-04-16-22-50-50.jpg

 

Shot10-04-16-22-51-21.jpg

 

Reaching the area where enemy aircraft have been reported, I see nothing of them. The skies around use seem clear, above and below. So I begin a wide turn to the right, intending to orbit the area for a while, to see if anyone else comes along to provide us with a bit of company and generally keep us entertained.

 

Shot10-04-16-22-53-29.jpg

 

As we come around, I look behind and right to check if the two fellows on that side are still keeping up. They are, but I am more interested in the more distant aircraft I can now see directly behind, and apparently coming after us. This isn't terribly friendly behaviour, I tell myself.

 

Shot10-04-16-22-55-15.jpg

 

I turn the formation around to confront him. He seems to be on his own, but he keeps on coming. In fact, it's an Albatros D.III scout. If he really is on his own, he's either very hot or very silly, taking on three of the best fighting machines we have at the front. Evidently, he hoped to catch us by suprose from behind, but though he can now see that we've spotted him, the Hun isn't deterred. Well, if he wants a scrap, that's exactly what he's going to get, very soon now.
 

Shot10-04-16-22-55-34.jpg

 

...to be continued!

Share this post


Link to post
Share on other sites

Tussles over the trenches

 

The Hun is slightly above me as I turn into him, so I only get in a few rounds from my single Vickers Gun as he flashes overhead...

 

Shot10-04-16-22-55-44.jpg

 

...and then goes down in a left hand turn, before pulling up level a few hundred feet below. I can see clearly his white tail and red fuselage.

 

Shot10-04-16-22-55-49.jpg

 

But he's not on his own. There are at least two Huns, probably three or more. My flight-mates are now going for the first Hun, whom the tactical Dpsilay - turned on briefly for padlocking purposes - tells me is 'Historical Ace' Paul Kemp. Rather than risk a collision by joining a conga line, I aim to swing in behind them all, and cut in on the second Hun.

 

Shot10-04-16-22-56-03.jpg

 

This fellow also has a white tail, so it looks like I'm up against Jagdstaffel 2, by now named after its first leader, the late Oswald Boelcke. Soon, we're having a merry old tussle, and I'm wishing I had tried to use the CFS3 trim keys, while I had the time, so that I had full sideways movement of my joystick, instead of having to use a fair proportion of it to counter my Tripehound's strong roll to the left.

 

Shot10-04-16-22-56-43.jpg

 

Still, I manage to outmanoeuvre the V-strutter and get in behind him.

 

Shot10-04-16-22-56-59.jpg

 

He's fast, and my single gun lacks the killing power of his twin Spandaus. But I think I've landed some hits, for he stops evading and dives away in a gentle turn. It's a bad move, for the Hun machine hasn't been invented that can out-dive a .303 round.

 

Shot10-04-16-22-57-08.jpg

 

Suddenly, the tables are turned! The Hun with the red fuselage has somehow escaped the attentions of the other Tripehounds and the first I know of it is when his rounds are whacking into my machine. In a momentary panic, I roll right and shove the nose down hard, desperate to get out of that withering fire.

 

Shot10-04-16-22-58-07.jpg

 

Meanwhile, the second Hun makes good his escape, passing underneath me and away. Von Seel I think was his name, another Historical Ace, with his own skin and individual marking in WoFF.

 

Shot10-04-16-22-58-35.jpg

 

My clumsy manoeuvre does the trick, and the red Hun is now engaged again by my flight-mates and driven off. I use the opportunity to extend from the scrap in a gentle dive to build up speed...

 

Shot10-04-16-22-59-16.jpg

 

...then, finding that everything still seems to be working and that nothing has fallen off, I pull back up and around, to get back into the fight. I've had a close shave but am rather cross to have been thwarted in my effort to clobber the second Albatros. It's time to give that red Hun a taste of his own medicine!

 

Shot10-04-16-22-59-29.jpg

 

...to be continued!

  • Like 1

Share this post


Link to post
Share on other sites

Back in business - briefly!

Shot10-04-16-23-02-12.jpg

 

Heading back into the dogfight behind and above me, the first Hun I met was the V-strutter with the black ‘S’, who, I thought, had run for it, after his friend Red Fuselage shot me off his tail. We had a quick head-on pass then he disappeared behind and began to turn.

 

Shot10-04-16-22-56-26.jpg

 

Instead of going after him, I left him, continuing to climb away, up to where my three flight-mates were scrapping with two other Huns.

 

Shot10-04-16-22-59-43.jpg

 

One of these fellows was Red Fuselage, so I singled him out for some special attention, with artillery fire, raking ground targets beyond him, providing a dramatic backdrop.

 

Shot10-04-16-23-00-29.jpg

 

But I quickly broke off, when I saw another Triplane - just visible behind the tip of my left middle plane - cutting in onto his tail.

 

Shot10-04-16-23-00-41.jpg

 

Looking around for Black ‘S’ instead, I saw the third Albatros, above me. This had the later Jasta 2 marking of a halved black and white tailplane, but the rest of him was pale blue – it was Hermann Frommherz’s ‘Blaue Maus’. Of course, this sort of information was unknown to my virtual alter ego in May 1917, but the bright colours marked the Hun out as someone who didn’t feel the need for camouflage and concealment, and perhaps therefore something of a hot shot. Or perhaps his sky colour was intended as a form of camouflage, ahead of his time!

 

Shot10-04-16-23-01-04.jpg

 

Shot10-04-16-23-01-14.jpg

 

Either way, it wasn’t long before he was rolling over, to get onto my tail.

 

Shot10-04-16-23-01-24.jpg

 

He didn’t make it. Instead, another Triplane was onto him in a flash. He twisted and turned but the Sopwith easily out-manoeuvred him and hot shot or no, down he went.

 

Shot10-04-16-23-01-40.jpg

 

As I watched, the pale blue Albatros glided down and made a respectable forced landing, managing not to turn over despite the rough ground.

 

Shot10-04-16-23-03-37.jpg

 

As I returned my attention to the skies above, I came unstuck. I was evidently now over enemy territory, and low to boot, for my machine came under sustained ground fire from the trenches below. The grey pencil-lines of the tracers lanced up all around me, and for the second time, rounds whacked into my Triplane.

 

Shot10-04-16-23-04-13.jpg

 

I jinked like a hare to get out of the lines of fire, swinging around to the west as I did so. Behind me, our gunners continued to pound unseen targets amidst the enemy trenchlines. The MG fire from below soon tailed off, and I was not pursued from the air, thank goodness.

 

Shot10-04-16-23-04-49.jpg

 

No damage was visible (bullet holes aren’t, with high-resolution aircraft textures enabled, on my version of WoF) but my motor didn’t seem to be pulling so strongly any more. Confident my four comrades could handle the one or two remaining Huns - probably all the better without a disabled flight leader to worry about - I got back across into friendly territory without further incident.

 

Shot10-04-16-23-05-30.jpg

 

Preferring to avoid the risk of a forced landing if my motor packed up, I headed for a conveniently-sited friendly aerodrome just on our side of the lines, outside the shelled area.

 

Shot10-04-16-23-06-53.jpg

 

My Clerget rotary kept going and I was able to get down in one piece. Parked aircraft on WoFF airfields generally seem to be the same as the one you’re flying, regardless of what’s really based there, hence the other Tripehound in front of the hangar.

 

Shot10-04-16-23-08-40.jpg

 

The mission results screen in WoFF is one of the big improvements over previous versions of the sim, as you can see from the one below for this mission.

 

Tripe3.jpg

 

I had shot down nothing and got few hits, so it was a rather poor show on my part. I was flying the more manoeuvrable aircraft, but the enemy all seemed to be very experienced pilots, with at three current or future aces amongst them. So I was quite glad that as a flight, we had come out on top, with no losses or casualties, and one victory credited to Maynard, one of my flight's  two 'Historic Aces' (an unfortunate abbreviation in WoFF, as to the RFC it meant 'Hostile Aircraft', until replaced by 'Enemy Aircraft' about 1916).

 

I am very new to the WoFF Triplane and I think I need a bit more experience to get the best out of her. Strangely enough, in a 'Quick mission' in the Tripehound featured below - one of Naval 10's famous 'Black Flight' - I didn't experience the pronounced tendency to roll left, so perhaps my old Saitek cyborg is due replaced at last!

 

Shot10-08-16-23-10-25.jpg

 

But having now faced off against the foremost planes and pilots Germany can put up against me and returned battered but unvanquished, I’m feeling pretty confident, and looking forward to the next scrap!

  • Like 3

Share this post


Link to post
Share on other sites

Good action report, 33LIMA! I've always been more than a little partial to the Tripehound. As I recall, Naval 1 had a pair of "twin Vickers" Tripes for testing, starting in July of 1917. Do you get a chance to try them out in WoFF?

Share this post


Link to post
Share on other sites

Thanks, guys! No, Silberpfeil, I haven't tried WoFF's 2-gun Tripehound yet! I see that Jon Guttman, in Osprey's 'Naval Aces of WW1 Part 1', says there were six of these, and that Naval 10's Collishaw got a DFW in one of them, N533, on 7 July.The extra firepower would be very welcome, but if WoFF models the real-life performance penalty, I wouldn't want to sacrifice better climb and manoeuvrability for it!

 

Anyhow, there are no prizes for guessing which WoFF Sopwith comes next!

 

Shot06-26-16-00-38-52.jpg

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