VonS

And, yes, one more even smaller update to this thread - the FrankenBHAH Enhancement Hardcore Addon Ver. 1.15 for the BH&H2 Enhancement Package (not for the WOTR Package) is now included under this post. Install directions may be found in the "Read Me" file that accompanies this very small addon. In short, the Hardcore Addon makes for more challenging regular flying, and dogfights, in BH&H2 (more engine failures, more wiry opponents, etc.). EDIT: see top post of this thread for relevant download link(s), etc. Cheers all, Von S

Hello fellow FE2 fliers, The FE2 forums are somewhat sleepy so I hope everyone's doing well. Brief update to this thread. The modder working on the Bleriot is busy currently with a variety of other duties - and I have been busy with my FM and other FPS optimization packs for the WOFF series of sims. by OBD, over the last few months - but I hope to be able to find some free time by the new year to tweak the FMs for one or two other aircraft that I never got to, for my big FM update pack for FE2 (specifically the Sopwith Snipe that I began FM tweaks for but never completed). Will update this thread again, regarding the Bleriot, in a few months - should there be any further progress with the Bleriot. Cheers all and a big thank you to all modders for making FE2 one of the most customizable WW1 flight sims, Von S

And one more small update to this thread - the FrankenMiniTuner Ver. 1.2 (add-on) to the WOTR and BH&H2 Enhancement Packages is now included under this post. Install directions included there. The MiniTuner helps to squeeze out a bit more FPS when loaded after the base Enhancement Packages - JSGME-friendly versions of the MiniTuner are included both for BH&H2 and WOTR in the relevant zipped file. EDIT: see top post of this thread for relevant download link(s), etc. Cheers all, Von S

All fixed now - installer-friendly versions of those two packages have been uploaded. Cheers, Von S

Handsome screenies gents' - been a while since I posted under this thread, so here are a couple (taken during testing of the WOTR Enhancement Package Ver. 1.0). Cheers all, Von S

Very brief update to this thread that the older WOTR GPU Tuner Patch has been superseded by an improved and more extensive WOTR Enhancement Package Ver. 1.0. Link available in the post above. Cheers all, Von S

Very brief update to this thread that the FrankenBHAH Enhancement Package for BH&H2 has been upgraded to Version 1.1 (link available a few posts above this one). EDIT: see top post of this thread for relevant download link(s), etc. Cheers all, Von S

@OP, as far as I can tell from flying in WOFF of any recent iteration, and also from some of the comments I've read on SimHQ - historical wind drift directions are modeled in WOFF. Speaking of winds in WOFF, default values give lots of "vertical winds" (no jokes please ) in bad weather - so, to compensate and give yourself more of an obvious feeling of horizontal winds and horizontal wind drift, make sure to keep the vertical winds setting in JJJ's excellent MultiMod either set to low at all times or no higher than moderate (and make sure always to have horizontal winds at the default/full setting in the MultiMod). The turbulence values may be tweaked to taste (low, moderate, full). I've cooked up a variety of simulation.xml files that, in conjunction with the MultiMod, provide further subtleties to winds in the WOFF PE/UE eds., but those files are not recommended for BH&H2. For BH&H2, recommended simply is to use the MultiMod settings instead. Also, those who are enjoying my FrankenBHAH Enhancement Package (for smooth FPS and other benefits) in BH&H2 will notice slightly different intervals between large turbulence bumps. Have extended the default no turbulence interval from 5 secs. to 10 or 12 secs. in the simulation.xml file included in my Enhancement Package (makes for more realistic, occasional turbulence that way I think - instead of having more constant, hyper-turbulent rumbles à la RoF). For a good comment on winds in WOFF, here is an older post by weather and clouds expert BB. For recommended wind settings via the MultiMod, and as per season (spring/summer, autumn, winter), I recommend the info. in this pic. that I posted a while back. Happy flying (in smooth and windy conditions), Von S

@OP, the Fokk. D.VI is an entertaining one indeed. By the way, the D.VI was introduced with the PE (Platinum Edition) add-on pack, sometime in 2019. If you upgraded from WOFF UE directly to BH&H2 - then, yes, the D.VI will be new to you. Happy flying, Von S

We usually manage to intercept at least half of a flight - if the other fellows get too close to the lines we (I and my AI flight) often don't follow them across the lines. Depends also on wind speed and direction, and how fast the enemy's machines are, and what their starting alt. is. I also usually assign my pilots a veteran role, and at least at the Ltn. level - when signing them up. Rookies and novices have to follow the leader always - the AI leader is another can of worms entirely because they may evaluate differently at times and not pursue an enemy flight, etc. Lots of variables at work. Also, if you are in a crate with a poor(er) climb rate, the enemy flight may be too far away to pursue by the time you climb high enough. Cheers all, Von S

Hi michaleen, the mods. folder should be called "MODS" (without quotation marks) - and should be created by the user in the main WOTR folder (home folder for WOTR where all of the other WOTR-related folders are located; same rules apply for WOFF). "Once activated via JSGME" means that mods. are loaded and operational in WOTR/WOFF after they have been loaded through JSGME. JSGME has a split window (two-window) view which shows offloaded mods. in the left window, and loaded mods. in its right window. All mods. that are available for WOTR/WOFF, once unzipped (or installed, since some are available only as exe installers, instead of zip files) -- should be placed in the MODS folder in order to be seen by JSGME. JSGME should itself, when unzipped, be placed in the main WOTR (or WOFF) home folder, in the same directory level where the user-created MODS folder is located. For more info. and a download link to JSGME (version 2.6, which is the last version) - check this page and also the WOFF/WOTR JSGME tutorial here. Good luck with your WOTR install and tweaks, Von S

@OP, might I recommend the two performance-oriented links (for aircraft in WOTR Phase One) located towards the bottom of the following post. Might help out with optimal prop. RPMs, fuel mixtures, etc., since there are more things to juggle in the cockpit in WOTR than in WOFF. Good revs., acceleration and climb rates to you, Von S

Many thanks for this model Stephen - great to see more modding happening for FE2. Cheers all, Von S

FM Upgrade Package for BH&H2 now available at the following link. (Upgrades the previous, ver. 6.5 FM pack that is available for WOFF UE/PE.) EDIT: see top post of this thread for relevant download link(s), etc. Cheers all, Von S

Hello fellow FE2-ers, Just a quick note for those running FE2 on Intel-based Macs (either in a WINE program or directly in Win7, 8.1, 10, etc. in Bootcamp) -- that you might find the info. in the following post (regarding WOFF/WOTR and the latest M1, ARM-based Macs) helpful. In short, for now - recommended is to keep flying FE2 only on Intel-based Macs, in versions of Windows no later than Win10. No guarantees at this point that Win11 can be effectively "shoehorned" onto Intel-Mac hardware, nor any guarantees as to how well FE2 may run in Win11, if at all. Furthermore, the latest ARM-based Macs only support ARM-based vers. (not the x64 branch) of Win11, and only via virtualization (no direct bare-metal Win11/ARM installs available for latest Macs so far -- the point is ultimately an irrelevant one I suppose since FE2 will never be "translated" to run as an ARM-based application anyway -- and I doubt that it would run stably using the x86/x64 virtualization layer that is found inside ARM-based Win11 installs anyway). Happy flying all, Von S

Re-copying my post from SimHQ here -- for those who do not frequent SimHQ but are running WOFF/WOTR on Intel-chip Macs. ----- Thanks Pol for this info. - also recommended is that Mac WOFFers (and WOTRers) for the time being stick either with WINE (skin/bottler) installs, or Win10-in-Bootcamp installs, of any recent vintage of WOFF (UE and later eds.). Will be a while before I test WOFF in Win11 on a Mac - for starters, I will try testing a standalone/clean install of Win11 with TPM disabled, so that I can "shoehorn" Win11 onto my Intel Mac hardware. For those on Macs and curious to experiment, recommended is to check over info. for how to disable TPM in Win11, as well as how to make a Win11 ISO. VERY IMPORTANT NOTE: Currently, the latest (M1 chip, ARM-based) Mac hardware only supports Win11 (and only the ARM variant of Win11) in virtualization software such as Parallels. Currently there is no Mac-hardware-installable version of the ARM-based Win11 available - only via virtualization - and support is still undetermined even regarding the virtualized version, on Macs. Previous Win versions that are x86/x64-based may only be installed up to the latest Intel-chip-based generation of Macs. This means that the x64 version of Win11, that is still the (common) branch of Win, going forward, and that may still support your various Win-based flight sims., on your Mac hardware - is installable (unofficially) only on Intel-based Macs, but will obviously never be installable on ARM-based (M1 and later generations of) Macs. Macs have now moved back to their own, proprietary processors, ARM-based -- and so Mac flight-simmers are unofficially back in the "dark ages" of Mac gaming, of the pre-Intel Mac era -- those old enough to remember should at this point think of PPC-era Macs ("Power PC" processors such as the 603, 604, 604e, etc., used also in some IBM servers I think and typical of beige-box computing of the 1995 to 2005 period). I would rather be a Mac unsupported, Intel sinner than a disenfranchised armchair simmer, huffing and puffing as to why his hissy-fitting Hisso SPAD-on-ARM chip's prop - isn't spinning. Cheers all and happy tweaking of unsupported (x64) Win11/legacy Mac hardware combos., Von S Further edit: According to the unofficial WineSkin continuation project page, for Macs, it seems that there will be support for some x86/x64 programs in WineSkin on ARM-based Macs, but it requires WINE engine WineCX20.0.4 (or later, the cx by the way probably referring to the "CrossOver" WINE project code) -- also required is installation of "Rosetta2" -- the other min. requirement is macOS ver. 11.x.x. Rosetta2 allows ARM-chipped Macs to run Mac-Intel-built programs (but not necessarily Windows-native Intel programs, which is of course a major problem if you want to install Win/Intel-based flight sims. on latest-generation Macs). Keep in mind that this is all obscurely experimental and I don't recommend betting on Windows flight-sim. stability, for now, if ever, on such obscure WINE/Win11 combos. - or even betting on loading your flight sims into a virtualized ARM-based Win11 install on the latest Macs and then hoping that the x86/x64 virtualization layer available inside the ARM-based Win11 environment will maybe support your flight sims. Much safer for now is to keep WOFFing in WINE on Intel Macs, or in Win10 in Bootcamp on Intel Macs.

Available in the package under this post (also available there is a Pfalz D.III and D.IIIa). Cheers, Von S

I'm getting the strange feeling, from the latest posts, that older Edge (html/Trident-based) is working fine, but newer Edge/Chredge (Chromium-based) is experiencing hiccups with CombatAce - may be speculation from my end but perhaps something worth looking into. Good luck all and hope that you experience smooth connecting with CombatAce soon, Von S

No trouble accessing the site from my end - on the older Edge (HTML/Trident based), Firefox (extended support release), Pale Moon (fork of an older ver. of Firefox). I recommend re-setting/re-starting your router and/or cable modem - also clearing cache/passwords/history in your desktop web browsers, as per the good advice posted in posts above mine. Also, if you are using the newer Edge/Chredge (Chromium-based) - or upgraded to it recently from the older Edge - double-check settings in the upgraded Edge (might be the case that the problem is there, somewhere, in the settings - since I noticed on my laptop that some settings were changed once Edge rolled over to Chredge in my ver. 2004 Win10 install). On my desktop computer, on the other hand, I've locked down my Win10 Bootcamp partition to ver. 1809 of Win10 - so I still have the older Edge there (older and newer Edges by the way can co-exist in Win10 but it requires some settings tweaks as per this post, and others). Good luck with the tweaks, Von S

No worries Wilches - all fixed now. The Breguet XIV (French/Fiat and USAS/Liberty variants) and Junkers J.I packages may be found for download under the initial download location for those models, under this post (near the top of page 26 of this thread). Happy flying all, Von S

Bumping up this thread, and to mention that the download links on pages 26 and 27 (hosted on a third-party website) to the Breguet XIV and Junkers J.1, kindly uploaded by Wilches - are no longer working. (Smaller attachments may be posted directly in posts here on CombatAce, by the way - less hassle and no broken links that way.) Cheers all, Von S

Hello gents, another trick worth trying, if you're too lazy to re-install everything onto another HDD/SSD, is to open the Windows registry and drill down into the following folder: HKEY_CURRENT_USER/Software/OBD Software/Wings Over Flanders Fields Once there, double-click the entry called "OFFPath," then change the info. in the "Value data:" section to point to the correct drive where you have moved/copied over your previous WOFF install, and click "OK." The entry I have, for example, under "Value data:" is: C:\OBDSoftware\WOFF\OBDWW1 Over Flanders Fields This would be the relevant entry to change, depending on where you have moved your WOFF install. Have never experimented with this on my rig. since WOFF is on my C drive (and is always in the C drive when installing in a WineSkin/Bottler), but it's worth a shot and might save you from doing an entire re-install. If successful, the same info. would apply when copying WOTR to other drives too. Cheers all and happy tinkering, Von S

Hi Julio, as far as I know Geezer never released a large pilots pack officially, especially some of those WW2 pilots that he modeled. He did allow that the WW1 pilot with a mustache be released (available at the following link, with the BE2a: https://combatace.com/forums/topic/87403-tweaked-flight-models-and-realism-pack-for-fe2/?page=8&tab=comments#comment-780396). and also that the WW1 pilot with the green scarf covering the face be released - that one will be included in the Bleriot XI model, when it is finally/hopefully completed. Happy flying, Von S

Hi Dresam, I've been away from flight simming since about late June, after the ver. 1.3 AI/DM update for RoF was released, partly because of work-related duties. So I haven't been as active on the forums as previously. Hope you are enjoying flying FE2. Greetings, Von S

@OP, make sure that the "enable 3rd party missions" option in the WOFF sim. menu is toggled "on" - if you have loaded Bletchley's mission and defense mission packages via JSGME. Otherwise oddities may result while flying. Also, Bletchley's missions result in many more lone-wolf missions assigned, from what I've read, than stock missions. The only other thing I can think of is to make sure that you are loading the correct third-party missions for BH&H2 - called "Bletchley's Mission Types (BH&H II Version 1)" and "Bletchley's Defence Mission Types (BH&H II Version 1)." Both are located under this link: https://thatoneplease.co/generalWOFF.html If running WOFF UE/PE instead, download the package called "WOFF UE Mission Mods (Version 3.1)." For the record, I don't fly third-party missions so I can't help with other details/oddities regarding them. Happy flying, Von S