Jump to content
Sign in to follow this  
33LIMA

CA-WW1 - the Roland Walfisch

Recommended Posts

Spotting for the Gunners in the LFG Roland C II!
post-66801-0-94807500-1398711576.jpg
 
In an air war notable for the sheer variety of planes of all shapes and sizes that made it to the front, the LFG Roland C II must be one of the most distinctive, if not also one of the most attractive. 'Truely, this aircraft is a whale!' was the reaction of one of the German procurement people who came to see what they'd be getting for their reichsmarks, giving the Walfisch its enduring nick-name. But it was also one of the most advanced aircraft of its day, a compact, fast, streamlined single-bay two-seater general purpose aeroplane in a world where other such machines were bigger, slower or ungainlier…and mostly, all three.
 
'The best German aircraft now' was reportedly the verdict of RFC ace Albert Ball, who frequently came up against (and shot down) the type in the summer and early autumn of 1916. However, though sometimes encountered in sizeable formations in this its heyday, the Roland was produced in comparatively small numbers and its front-line service career was over by about mid-1917. Speedy in the air, it was slow and expensive to make. Its thin wings tended to warp in the harsh conditions of front-line airfields and visibility for landing was poor, resulting in many crashes or hard landings. But still, it was a notable performer for its time, whose capabilities generally matched its good looks.
 
Many of us will know the type from the 1960s Airfix 1/72 kit, helpfully moulded in light blue plastic in imitation of the distinctive finish initially carried by the Roland. It made up into a nice model, with decent crew figures instead of the dreaded 'goggled alien' of earlier Airfix WW1 kits.
 
post-66801-0-15113500-1398883648.jpg
 
One day, I will make this kit again, notwithstanding that newer versions are available. In the meantime, I can fly the Roland in simulators. I don't yet have the Rise of Flight Roland, seen here escorting my DFW C V in a recent mission...
 
post-66801-0-63077600-1398884095.jpg
 
...but I do have and like the First Eagles versions from the A Team Skunkworks. Though they have a 'Spandau' machine gun for the observer, instead of a 'Parabellum', there are a couple of interesting variants, including this one with a captured Lewis Gun fitted to fire ahead over the propeller arc, which was tried in real life:
 
post-66801-0-16021300-1398979977.jpg
 
But for this mission I chose Wings Over Flanders Fields. Having flown the Roland in Over Flanders Fields, I was keen to see how I made out with this machine in the latest incarnation of this sim, with Ankor's self-shadowing mod and the new AI and landscapes of WOFF.
 
The campaign
Creating a new pilot, I tabbed throught the available German 'Bomber/recce' squadrons flying in September 1916 till I found one that flew the Roland in the British sector - WOFF still provides a better representation of the RFC order of battle, and would benefit in particular from the addition of French two-seaters more suitable for either 1916 or 1918 than the Morane L (really a 1914-15 type) and the licence-built Strutter (gone from the front by mid-1918).
 
I ended up with Feldflieger Abteilung (Artillerie) 240, based at  in Flanders. I believe the 'Artillerie' indicates that we specialise in observing for the artillery and can correct their fire using radio transmitters, one of the major jobs for two-seaters in WW1, along with photo or visual reconnaisance and to a lesser extent, bombing. Here's our roster and our operational area.
 
post-66801-0-42755100-1398711843.jpg
 
Even without tabbing to the Intelligence summary, I knew that the deadliest foes we could expect to face in our sector would be DH-2 'pusher' fighters and the more modern French Nieuport scout, both types used by several RFC squadrons. With the British fighters apt to patrol up to ten to twelve miles on the German side of the Lines, I knew also that we must be prepared to meet them in the air, whatever our task would be.
 
The mission
It's 12 September 1916, and our assigned task for this morning is artillery observation. Down to the south west we must go, from our airfield at Houplin down to the trench-lines. There are no less of six of us on this operation, with myself leading the full flying strength of the staffel. When I draw an 'art obs' mission in OFF or WOFF, I generally fly to the front and orbit near any friendly artillery barrage in progress, as if I was directing the fire. It's not possible actually to call down fire onto ground targets (although after this mission I'm no longer so sure, of which, more later). If there's no artillery fire going on, I regard my radio transmitter (or the battery's receiver) as having 'gone dark' and do a bit of recce work, so that the taxpayers still get their money's worth.
 
post-66801-0-94376100-1398711955.jpg
 
We have an escort, but I wasn't going to put much faith in the two obsolete Fokker Eindekkers we'd been allocated. For all I knew they were the last ones at the Front, still able to beat up a BE2c but well outclassed by any fighter we were likely to meet. My own flight would serve as my escort. I would do the virtual artillery-spotting. Knowing that formation-keeping in WOFF was considerably improved over OFF, I knew my comrades would be able to keep up quite well as I circled over the front. Anyone trying to shoot down the spotter - me - would have to get through them, first. At least, that was the theory.
 
Here we are, lined up opposite the sheds and ready for the 'off'. I had chosen a camouflaged skin from those available in WOFF, but the rest of the flight are in the original, distinctive and rather racy light blue. I checked my controls and started up. Then I called up the Tactical Display (TAC), set its target type to 'aircraft', checked its range was suitably low (I left it at half a mile) and turned the TAC off again: it was now ready to padlock air targets, when turned on again. I didn't expect to do too much (if any) dog-fighting on this mission but if I had to break formation and fight individually, I decided I was going to make good use of my forward-firing MG, relying on the observer to cover my tail. Which is more or less how it came to pass.
 
post-66801-0-81274300-1398712053.jpg
 
But that lay in the furture. I roared off the airfield and tried some gentle turns before setting course for the Front and throttling back to allow my flight to catch up. I found the ailerons deceptively light and the rudder heavy. It was easy to under-bank and slip outwards, or worse still, over-bank and find yourself in a nasty side-slip, if you didn't give her plenty of top or bottom rudder. This was nearly to be my undoing.
 
post-66801-0-76775500-1398712198.jpg
 
But that, too, lay in the future. For now, I watched my flight catch up from astern. One of them took several minutes, during which time I saw two aircraft fly past overhead - the two Fokkers, I supposed. This was the only time I saw them, as it turned out.
 
post-66801-0-12592900-1398841905.jpg
 
At at last we were all in a nice diamond formation. I opened the throttle wide and I began to climb, maintaining forward pressure on the stick to stop my tail heavy plane's nose from rising too much. All around us, thin clouds loomed, slipped past below, beneath or beside us, then loomed ahead again.
 
post-66801-0-35778900-1398712392.jpg
 
post-66801-0-60870600-1398712458.jpg
 
I spent a little time admiring and exploring my plane, inside and out, between navigating and scanning the skies. Visibility downwards was, as expected, not good, but in every other direction, I had a superb view, unobstructed by the usual high-mounted biplane upper wing.
 
post-66801-0-14453500-1398712777.jpg
 
post-66801-0-14914100-1398712774.jpg
 
Looking behind, the sight of my flight tucked in behind me inspired confidence…to much, perhaps, I thought, remembering Albert Ball's opinion that such formations were easier to surprise as the aircrew tended to feel a false sense of security and relax.
 
post-66801-0-87627400-1398712775.jpg
 
post-66801-0-19808200-1398713003.jpg
 
 
On we went. Climb rate was less than stellar and we were not far above five thousand feet as we came up the the trench-lines. Our Fokker escorts were nowhere to be seen and I decided I wasn't going to hang about looking for them. I was at a respectable height for artillery observation and was now at the Front, where lay our targets. I leveled off and throttled back slightly. I had arrived at the war.
 
post-66801-0-59275000-1398712778.jpg
 

Approaching the area over the Lines where we were tasked with spotting for the Gunners, I turned on the Tactical Display to get a navigation check. Instead, I got a surprise. In fact, I got two surprises.

 

post-66801-0-03305100-1398970403.jpg

 

First, knowing that I was headed roughly in the direction of my target area, I was startled to notice that the pale blue line showing the path to my next waypoint, instead of pointing up, straight ahead, had slewed around to my left rear. If that wasn't strange enough, the text displayed beneath the TAC itself was telling me that it was high time to go home. In fact, not even home - to the nearest airfield. Had I inadvertently skipped a waypoint? No, I was fairly sure I had done no such thing. My true objective still lay ahead.  Who's leading this mission, anyway - me or the Tactical Display? Pilots in the German Air Service may often be mere NCOs but while I may have to take orders from my commissioned observer - my own alter ego, anyway - I'm certainly not at the beck and call of an on-screen visual aid. Sod that, I thought. On we go.

 

Actually, the TAC was trying to be helpful. Looking behind, the reason for the device's caution was not hard to see. An aircraft was slicing into our formation from our left rear. And though I didn't notice it at the time, three other aircraft were below and behind us to the right.

 

post-66801-0-26253400-1398971068.jpg

 

My initial reaction, seeing just the one presumed enemy attacking, was that I'm not going to break formation and get distracted from my objective for the sake of one aggressive Englishman. Unfortunately, those on the right of my formation didn't agree that staying together and meeting the enemy with massed fires was the best bet. That side of my formation broke up rapidly, as Rolands wheeled off and after the Nieuport. All very commendable perhaps and it certainly seemed to put off the foe-man, who turned away.

 

post-66801-0-10024400-1398971295.jpg

 

I now had a decision to make, and I needed to make it immediately, before the passage of time removed one of my options. I could hold my course to the objective, with what looked to be two remaining flight-mates. Or I could turn us back to join the battle, keeping my formation, if not intact, then together; and resuming my progress to the objective when the battle had been won.

 

Keeping to my present course seemed to comply with the Master Principle of War - Selection and Maintenance of the Aim...but at the expense of one nearly as important - Concentration of Force. Incidentally, contrary to what John Keegan said in 'The Face of Battle', these principles, far from being thought old-fashioned, were taught at Sandhurst in the late 1970s.

 

Anyhow I had read too many accounts - Trafalgar, for one - of forces that are (or get) split up, then being defeated in detail, even by numerically weaker enemies. So I turned back to join the fight. By this point I had realised there was more than one enemy aircraft. I picked up one who lay ahead and gave the attack order, so that the others would pick their own targets. Mine, I recognised as a Nieuport Scout. He was manouevring a few hundred feet below, to my half-right.

 

post-66801-0-09980200-1398971843.jpg

 

I made a series of swooping attacks on him, allowing my observer a crack as I whizzed past. While I kept up my speed and most of my height, the tightly-turning Nieuport was able to turn in under my attacks most of the time. He in his turn was prevented from having a determined go at me by the presence nearby of at least one other Roland.

 

post-66801-0-68236500-1398972074.jpg

 

post-66801-0-12977800-1398972554.jpg

 

After a few more passes I got behind him and stayed there long enough to get in several good bursts from not too far out. He stopped manoeuvring and settled into a steady glide earthwards, emitting a spluttering trail of grey smoke. I watched as he piled up into the mud behind me. Got him!

 

post-66801-0-91891900-1398972075.jpg

 

post-66801-0-32826900-1398972508.jpg

 

But the fight wasn't over yet!

...to be continued!

Share this post


Link to post
Share on other sites

In the air and on the ground...

 

post-66801-0-93339400-1399058517.jpg

 

Having knocked down one of the Nieuport Scouts that had diverted my formation from its assigned task of spotting for the Gunners, I was naturally elated. But I had lost a lot of what altitude I'd started with. Now of all times, I didn't want to be the next one for the chop! So I began a full-power climbing turn, in the general direction of our side of the Lines and comparative safety.

 

Looking around, I took stock. The air combat seemed to have petered out. Some distance behind me, I could see three or four planes slowly closing up on me - hopefully members of my six-aircraft flight. But while most of the aircraft seemed to be in the distinctive light blue Roland factory finish, one was not. An Englishmen had not given up and was hunting us again! I turned around and went for him, ordering my two flight-mates to attack as I did so. Individually our two-seaters might be pushed to handle a nimbler Nieuport. But as with the last combat, I hoped that one or the other of us would get in a good crack at him, while he was occupied with the rest of us.

 

post-66801-0-09095500-1399058879.jpg

 

And so it came to pass! The Nieuport was soon on the defensive, with our Rolands rolling and swooping all around him. And once again, it fell to me to finish the fight. A single and rather slow-firing fixed MG fired from a comparatively cumbersome two-seater is not the most effective killer of fighter planes. And with my Roland's comparatively effective ailerons, more than once I found myself over-banked, with the wings near the vertical and side-slipping rather than turning. Twice I barely managed to level her before hitting the ground, recovering at literally tree-top level.

 

post-66801-0-73608400-1399058981.jpg

 

post-66801-0-04856300-1399058983.jpg

 

But in the end I got into a good position on the Nieuport, who was again handicapped by having to deal with several Rolands who were all out to nail him. And down he went. Two kills! And in a single mission! I checked the time and my location - I wasn't going to let a sloppy combat report cost me confirmation of my double victory!

 

post-66801-0-65834100-1399059065.jpg

 

post-66801-0-10150600-1399059068.jpg

 

My next problem was that I was suddenly alone again. The other Rolands had disappeared, as if by magic. Looking to the south, I finally spotted a single distant aircraft hearing east, which might have been one of them. I circled for a while, gaining some height, in the hope some of my flight might rejoin me. In the end, still alone, I turned my machine to the west, determined to complete my mission, even if I had to do so on my own.

 

post-66801-0-31637900-1399059162.jpg

 

And that mission was artillery observation - using morse code and a radio transmitter to adjust the fire of friendly artillery batteries onto ground targets. WOFF doesn't simulate this process but happily - whether put there by the WOFF campaign system or not -  I could see that there was an artillery barrage already in progress in my objective area. So as I used to do in OFF when flying an 'art obs' mission, I headed that way, intending to loiter over the barrage and thereby simulate as best I could the task of spotting and correcting the fall of shot.

 

post-66801-0-88802500-1399059163.jpg

 

As far as I could make out, the barrage was falling into a beaten zone which was across and roughly diagonal to the line of the enemy trenches. I orbited the shelling, watching the bombardment hit home but also keeping a wary eye out for enemies in the air, not least any sign that my observer might be tracking one.

 

post-66801-0-03659100-1399059246.jpg

 

What I did see, was on the ground. A long track or narrow road ran roughly north to south, close behind the enemy trenches being bombarded. And on the road, I saw that there were two groups of enemy Motor Transport, trundling along. I watched them for a while, mentally urging the artillery to shift its fire onto these tempting new, soft-skinned targets. Of course, no such thing could happen, as even WOFF doesn't support telepathy.

 

post-66801-0-45470500-1399059358.jpg

 

Or perhaps it does! As I watched, artillery rounds suddenly bracketed the MT convoy. Some of the trucks stopped, while others continued along. Then more artillery fell, this time right amongst the northernmost group of vehicles. As the smoke cleared, I could see a column of dark smoke rising, as one of the trucks burned. Others seemed to have been immobilised!

 

post-66801-0-66138900-1399059398.jpg

 

post-66801-0-42982100-1399062219.jpg

 

Our Gunners were not done yet. Further salvos clobbered the southernmost group of vehicles, producing another column of smoke from a burning truck.

 

post-66801-0-11475100-1399059562.jpg

 

post-66801-0-61301200-1399059563.jpg

 

If I hadn't seen this with my own eyes, I would not have believed it. I presume that telepathy can be ruled out here. So, maybe it was a complete co-incidence that there happened to be an artillery bombardment at approximately the position of my own objective. Perhaps it was just a further co-incidence, that there was MT on the move close by. And perhaps it was yet one more co-incidence, that soon after I noticed the trucks, our artillery engaged them. But however it happened, short of providing a fully functioning system for calling down and correcting artillery fire, WOFF could not have done a better job of creating a believable impression that I had completed my artillery-spotting mission in this most satisfactory fashion. It was a magical moment!

 

post-66801-0-06389200-1399059627.jpg

 

Mission well and truly accomplished, I thought to myself! Time to call it quits and go home. I swung around the nose of my trusty Roland until she was headed east once more. The skies around me looked to be empty and devoid of either succor or threat.  I suddenly felt rather alone and vulnerable. I very much wanted now to make it home, with our two aerial victories and a successful shoot under our proverbial belts.

 

post-66801-0-60814100-1399059932.jpg

 

I need not have worried. Soon, in a shallow full-power dive to pick up speed, our machine was back over friendly territory, with the Lines falling away behind us.

 

post-66801-0-22132800-1399059934.jpg

 

Not long after, we were joining the circuit over Houplin, still on our own and quite unmolested. Despite the Roland's reputation for cracking up on landing, I got her down without any particular drama and trundled happily up to the sheds.

 

post-66801-0-93619400-1399059935.jpg

 

post-66801-0-20994100-1399059938.jpg

 

In my excitement and my anxiety to find out what fates had befallen the others, I neglected to check the detailed debriefing screen. But the initial debrief and squadron information screen told the tale. Of our six machines, three had made it back to base. Two of the three Rolands which didn't, had been destroyed and their crews killed. The two victories and the successful shoot had been team successes; without the others, they would likely never have come my way. But the team had paid a high price. It was a sobering moment, set against the satisfaction of a job well done.

 

post-66801-0-59613500-1399061657.jpg

 

post-66801-0-05302800-1399061659.jpg

 

As missions go, this was one of the very best two-seater sorties I have flown in any WW1 sim. The air-to-air combat was dangerous and exciting. And even if it was a complete fluke which never happens again, the sight of that artillery fire, arriving just as it might have done, had I called it in by radio, smashing up that road convoy, was one of those classic moments of pure simming immersion and delight that I will not forget in a long time. Simply brilliant!

 

post-66801-0-06182700-1399060796.jpg

Share this post


Link to post
Share on other sites

Man, really enjoying your mission posts!  A great evening's entertainment thus far :)

 

H

Share this post


Link to post
Share on other sites

Thanks Harry. Glad if I can convey some of the incredible fun and immersion available to us from PC simulation in all of its many guises, free of the real hazards of being shot down, knocked out or lost with all hands!

  • Like 1

Share this post


Link to post
Share on other sites

Well, your mission reports were so compelling, and the screen captures for WOFF so impressive, that I went and bought the thing.  I'm loving the immersion and the beautiful experience of it all, but in a way, I wish it was more difficult to fly.  I've been playing RoF for about six months now, and although I'm still a noob, I have really enjoyed the feeling of accomplishment, especially battling with the earlier planes and getting them into the air and back down again in one piece.  Now that I'm flying missions and getting the occasional victory, it feels very satisfying :)

 

WOFF 2 and RoF morphed together would be perfect :)  Let's see what RoF comes up with in the single player department next year.

 

Cheers, and keep those mission reports coming!

 

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