Jump to content
Sign in to follow this  
33LIMA

BE12 twosome - #2, Wings over Flanders Fields

Recommended Posts

Second time lucky? Flying the BE12 in Wings over Flanders Fields

Shot11-17-14-21-58-04.jpg

 

This time up, having met a heroic but early end in my First Eagles BE12 campaign, I'm checking out the same experience in WOFF. No need to worry about editing files this time tho, for the BE12 is one of the new planes included in this latest version of OBD Software's popular WW1 airwar sim. 'Latest' not for long, though, as a new iteration, WOFF 2.0, is about to hit the virtual shelves, as a payware upgrade and expansion, with the emphasis on Home Defence against Zepps and Gothas: http://simhq.com/forum/ubbthreads.php/topics/4018110/WOFF_v2.0_Screen_Shots__!#Post4018110

 

As in FE, I created a new pilot, finding that I could enlist in the same squadron from the same date - 19 Squadron, RFC, from 1st September 1916, just days before Boelcke and his 'cubs' from Jasta 2 burst onto the scene. WOFF bases us at Fienvillers/Candas, to the north-west of Cappy and further behind the Lines, than in FE.

 

19 Sqdn 1.JPG

 

And here's my pilot logbook, a much better presentation than FE's pilot stats screen (better than how most other combat flight sims have done this, come to think of it).

 

19 Sqdn -3.JPG

 

Not so good is the accuracy of this page, describing my mount, which emphasises the BE12's brief and almost accidental fighter role and says it was at the front in April 1915, a whole year or more too early. The data in the panel looks more like it applies to the BE2c; for example the BE12 has a 150hp RAF4 engine, not a 90hp RAF1 and the armament is also wrong.

 

19 Sqdn -2.JPG

 

Here's the squadron roster for my first campaign mission. Perhaps WOFF is trying to break me in gently with a patrol behind my own lines. And while I've selected 'always lead', I'm leading just myself, for oddly, I'm on my own in B Flight while A Flight is well up to strength, and flying top cover, for just little old me. Obviously, this squadron believes very strongly in looking after its new pilots. Naturally, I did not consider for a moment the possibility that they might be using me as bait for the wily Huns.

 

19 Sqdn briefing 1.JPG

 

And here's the briefing itself, confirming this rather odd arrangement:

 

19 Sqdn briefing 2.JPG

 

No doubt, the CO knows best. Ours not to reason why, and all that. Off to the airfield I went, finding myself lined up next to A Flight. Losing no time, I started up, checked the controls and as soon as the others began to move off, opened her up.

 

Shot11-17-14-21-45-17.jpg

 

The WOFF BE12 is not a bad replica, tho the nose is I think a little slender. Unfortunately it has not yet been updated like the WOFF BE2c and thus still has its interplane struts visibly too far inboard. Hopefully WOFF 2.0 will effect some improvement.

 

With little thought for such things, I banked around and turned my mind to the task at hand: to wit, a solo patrol behind our own trench lines, with A Flight covering me from somewhere on high. Nothing to it. Or so I thought...

 

Shot11-17-14-21-46-41.jpg

 

...to be continued!

Share this post


Link to post
Share on other sites

It's a long way to Tipperary the objective

 

Shot11-17-14-21-48-16.jpg

 

Gaining height with my single-aircraft B Flight, I looked around for A Flight. I quickly spotted them forming up and scudding around just above the deck. AI-led flights in WOFF, having taken off, spend rather a long time flying around rather aimlessly at low level like this, before something finally triggers them to climb up and head off on the mission itself. Avoiding this rather tedious routine is one reason I prefer always to lead a flight. In this unusual case, I was in a  flight on my own, to which the others were to provide top cover. So I spent a while following them around while slowly climbing to my own assigned 5,000 feet.

 

In the end, I got fed up waiting for them to come out of their 'take off, form up and potter around' routine and headed off down to the south-east, towards the Lines near the town of Albert, whose chuch tower's tottering Virgin Mary's fall was supposed to herald the end of the war.

 

Shot11-17-14-21-55-18.jpg

 

I had selected 'historical weather' and wasn't surprised to find it rather murky, with lots of low cloud and generally poor visibility in most directions at any one time. Despite this, as is my wont I kept the Tactical Display set to short range (to avoid the AWACS radar effect). It can be hard to spot other planes in WOFF at the best of times with visual aids off or minimised and today seemed unlikely to be an exception.

 

Shot11-17-14-22-03-16.jpg

 

While following A Flight around, I had tried to pick up and set a recognisable vector to a genuine mission waypoint on the Tactical Display. But I cycled too far ahead and couldn't get back so having spashed out on my own, I relied instead upon the in-flight map, to navigate.

 

Shot11-17-14-21-57-24.jpg

 

With no 'warp' facility, I went onto 2x time acceleration to cover the long leg to my objective area - I can fly this without autopilot and besides, any faster, it's a stutter-fest. I popped back into real time every so often, to double-check my surroundings, but I saw no flak and no other aircraft, A Flight included.

 

Nearing the limit of my patrol, things were still quiet and I began to fear that this was going to be one of the rather high percentage of my WOFF missions that encounters no enemies. In some frustration, I turned on labels. At least I might discover if A Flight was looking likely to join the party.

 

Shot11-17-14-22-10-06.jpg

 

Instead, the labels which now appeared were for a Halberstadt scout, from Jasta 4. He was about 5 miles away, at ten o'clock and slightly high. I mentally kicked myself for not switching first to 'dot mode' labels and avoiding this unrealistic revelation. The Hun was the other side of some clouds and with labels off, quite invisible. No friendly flak bursts in sight over there either, despite being well on our side of the Lines…where incidentally, Hun scouts should not often be. Maybe he was lost in the bad weather!

 

I continued on my course for a while, turning the labels on and off. The range seemed to be winding down, but slowly. Had the enemy detected me via some from of superior AI vision? Hard to say, but likely, if as seemed possible, he was now heading unerringly my way, despite the intervening clouds.

 

I decided I would do what I would have done, had I not seen the enemy aircraft - continue to the limit of my patrol, then if A Flight didn't show, break off and fly north, just my side of the lines, looking for trade. Another flick of the labels revealed that the Hun, steadily drawing closer, was 'fighting 19 Squadron' (or words to that effect).

 

Shot11-17-14-22-11-15.jpg

 

That was the limit of my patience! I was not going to fly another boring 'milk run' while the others had all the fun! So I turned towards the enemy and impatiently closed with him, flicking labels on and off again. Then, there they were - two Halberstadts, not one, to my direct front, slightly higher and on a reciprocal course. No sign of 19 Squadron...except for me...

 

Shot11-17-14-22-12-40.jpg

 

Shot11-17-14-22-12-50.jpg

 

They flashed past above me and then turned, even as I turned into them.

 

...to be continued!

Share this post


Link to post
Share on other sites

'Heavy-handed Hans flies Halberstadts' *

 

Shot11-17-14-22-15-30.jpg

 

The fight didn’t begin immediately. I lost a bit of height in my turn and the Halbertstadts, though turning too, kept their height advantage, rather than dropping down after me. I kept turning into them to deter an attack from the rear. After a while, one of them disappeared somewhere, how or where I have no idea. I kept turning and watching, toggling padlock on and off, deliberately trying to drag the other Halberstadt down with me, down over my own side of the Lines. And down he came!

 

Shot11-17-14-22-15-55.jpg
 
He dropped right down to my level in an attempt at a firing pass; and a proper dogfight developed. He was nimbler but I happily accepted losing altitude in my turns and my big BE12 refused to stall out, giving me several shots at the Hun. That big airscoop on my nose, the lack of a proper centre-line gunsight and my single Vickers's low rate of fire inhibited my shooting but I still got some hits.

 

Shot11-17-14-22-16-40.jpg

 

Shot11-17-14-22-16-33.jpg

 

The Halbertstadt's movements became more sluggish and he started layng a fine trail of white smoke or vapour. Switching to the side-mounted gunsight view for better accuracy at the expense of field of view - and keeping bursts short to avoid a stoppage - I managed to stay behind him longer and get closer each time I fired.

 

Shot11-17-14-22-21-15.jpg

 

Shot11-17-14-22-21-04.jpg

 

Fortunately the second Hun never showed up again because I was by now fairly well target fixated, knowing I should look behind but totally determined to get my man, despite the friendly AA fire that was now bursting around the both of us.
 
At one point my target climbed up away from me and extended the range further when I pulled up too hard and lost airspeed - and ground. But a slower climb put me back on his tail as he fled east and once again I had him. A few more bursts and he lost much of his forward airspeed and began a steady but wings-level descent. I broke away and watched from above, finally clearing my own tail. I expected the Hun to force land. But about a hundred feet up, he suddenly nosed down into an ever-steepening spiral and hit the ground near a hedgerow. Got him!

 

Shot11-17-14-22-22-48.jpg

 

Shot11-17-14-22-23-57.jpg
 
I wasn't in the mood for a long flight back to my own airfield so after checking the map, I decided to land on a nearby base which lay just to my west, south of a nearby river. I turned away from the smoking remains of my foe and within a few minutes I was slipping down to land.

 

Shot11-17-14-22-25-18.jpg

 

Shot11-17-14-22-29-16.jpg

 

I taxied up to the sheds and switched off, hopeful of a hot drink in my host's officers' mess and that they would have seen and could thus confirm my recent splendid triumph.

 

Shot11-17-14-22-30-36.jpg

 

Shot11-17-14-22-32-16.jpg
 
Mission over, I filled in a victory claim form and gave a pretty good description of the fight, lacking only the time. When I submitted the claim, a message warned me my named witness wasn't flying at the time, which was strange, as he was definitely up there with A Flight - who  admittedly weren't around anyway.

 

19 Sqdn debriefing 3.JPG
 
The full debrief shows no sign of A Flight having been in action, so perhaps that 'fighting 19 Squadron' label indicated the Huns were actually hunting (rather than fighing) me. Evidently, through the wondrous powers of AI vision, they had spotted me from way beyond the distance that their aircraft (as opposed to labels) became visible to me, for they appeard to have been making a bee-line for me the whole time. I haven't a clue what happened to the second Hun. Perhaps our AA fire had damaged him or scared him away, for it was firing all around us, friend and foe, for much of my dogfight. If so, I forgive the gunners for not alerting me to the presence of the enemy aircraft, earlier.

 

The debrief wrongly records me as landing on my home airfield but hopefully, the Powers That Be will at least get the victory confirmation right!

 

19 Sqdn debriefing 2.JPG

 

* from the RFC song:

 

Heavy-handed Hans flies Halberstadts

In handy Halberstadters for a flight our Hans does start.

His C.O. says 'Oh dash it!

For I fear that he will crash it!'

See how heavy-handed Hans

Ham-handles handy Halberstadts!

Share this post


Link to post
Share on other sites

Wonderful stuff!  Thank you for a highly enjoyable read, 33Lima!

 

H

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