VonS

I voted for "meh" because I tend to use it only on occasion, and strictly as a desperate, defensive maneuver - if I have enough speed - both in the earlier and later WW1 'crates. Recommended is to "lean the loop" to one side, near the top of your loop - as Mikael Carlson does on his Dr.1 - this will give you better control and also help to get away from your opponent more quickly than a regular loop will - also helps to maintain a bit more energy if you go with the "diagonal loop" (let physics - the torque and energy - pull you out of the problem ). Generally speaking, I would go instead with a split-s to get away quickly from something, or stall into a spin to drop alt. quickly and disappear from the AI's sight, before coming up again behind their tail. Cheers all and happy looping, Von S

Hello again fellow FE2-ers, Please find included below some of the latest developmental pics. from the Bleriot XI (6-cyl. Anzani powered). Swambast has been doing magnificent and detailed work on the 3D model. He is currently busy with other duties, and I will be taking a modding break during the summer - but we hope to collaborate further on the Bleriot XI over the next few months and eventually to get to the stage where I can apply an already-tested FM to this particular model. Will post here again in a few months once more things are completed. For the most part, the external model is now largely complete - we still need to look over and complete the rigging/warping wires for the wings, also some details regarding the wheel assembly - and to look over details for the cockpit (both for internal and external cockpit views). Then the FM-application stage will follow. Eventually, we hope to have a completed model ready, which our excellent skinners can as well have fun with once it is released. Cheers all and happy flying, Von S

Thanks Menrva for the clarification. I was confusing the "large address space" hack with true 64-bit. Apparently SF2, while 32-bit, received the large address space tweak some time ago, to allow access to more than 3.25 approx. GB of system memory - FE2 never received such a tweak officially, I think, but the tweak may be applied using the "4GB Patch" available on the internet. Thus my confusion and thinking that SF2 is 64-bit, which it never was. An old, relevant thread here: https://combatace.com/forums/topic/80572-4-gb-patch/ What I've always wondered is if the large address space tweak to a 32-bit app gives us an approximation of a "48-bit app" - interesting link below for those who like such questions: https://www.quora.com/Why-are-there-no-48-Bit-operating-systems EDIT: Apparently, SF2 is "large address space aware" since the May 2012 patch, by default. For FE2, recommended instead is application of the "4GB Patch" (link included to that in my "Read Me" notes for my big FM/realism update pack for FE2 - but can also be found using a Google search). Cheers all, Von S

As far as I know gents - SF2 is a 64-bit program already (edit: see follow-up post two posts below this one). FE2 on the other hand is 32-bit. (No problems running FE2 on my 64-bit Win10 install, by the way - so, theoretically, all should be well in this Win11 thing that some may upgrade to.) Happy flying, Von S

I'm assuming that a fresh (future) patch from OBD will iron out further oddities in BH&H2 gents - but, in the meantime, for those who like to tinker - look over the following two entries under the "Airfield" section of the simulation.xml file (that is located in the main "WOFF" folder of your BH2 install): min_descentAngle_deg="4.5" max_descentAngle_deg="6" Perhaps tweak those two, default values to smaller numbers, to facilitate smoother landings at less steep angles (I recommend something like 2.5 for "min_descentAngle" and maybe 5 or so for "max_descentAngle" - worth a try - do however make a backup of your stock simulation.xml file before trying out such tweaks, or even better, make your tweaked simulation.xml file JSGME-ready and load it that way). Those still running the UE/PE editions of WOFF are recommended to check over some JSGME-friendly, modified simulation.xml files available here (as always, read directions in the download post, as well as in the included "Read Me" file, for more thorough info.). Happy WOFFing, Von S

Nice write-ups Lima, interesting to see a version of WOFF before I began WOFFing. By the way, fences are deadly to about version 4.18 of WOFF (UE). The 4.21 or 4.22 patch that disables SweetFX compatibility also tones down fence (and tree) deadliness. The PE addon (ver. 5.0.x) included a few other subtleties regarding trees and fences, which are continued in the BH&H2 edition. I spend most of my time in my backport of PE aircraft/terrains into 4.18 since I prefer SweetFX color saturation in WOFF to what ReShade can do (ReShade is really the only option after the ver. 4.21 patch) - and I keep a stiff upper lip when crashing into trees or fences. Happy flying, Von S

Different winds/turbulence simulation.xml files (JSGME-friendly) available for WOFF UE/PE, at the link below the included pic. These simulation.xml files provide different winds and turbulence settings that work in conjunction with similar settings available in JJJ's MultiMod for WOFF. Set choices first in the MultiMod, before loading the relevant, complementary simulation.xml file, via JSGME - for all effects to be implemented properly. The relevant simulation.xml files provide several other tweaks too, including greater chance of random engine failure, greater chance of flamers, more varied gradations of AI (particularly for veteran and novice AI, etc.). Detailed info. and installation instructions are included in the "Read Me" document that is in the package. NOTE: These modified simulation.xml files are only for WOFF UE/PE. For tweaked simulation.xml files for BH&H2 instead, please see the FrankenBHAH Enhancement (and Addon) Packages included in relevant posts in this thread. Happy flying, Von S WOFFuepe_TweakedSimulationFilesVer1.0_VonS.zip

Just a brief update to this thread that the links to Xjouve's terrain meshes, water mods., land cover mods., global layer mods., etc. (that are compatible with WOFF UE/PE/also BH2), and originally available under the WOFF threads on SimHQ, are no longer functioning. Xjouve seems to have disappeared from WOFF modding and those links have likely expired in the meantime - I hope he's doing well. EDIT: Xjouve updated the broken links earlier this year, 2022, so recommended is to double-check relevant links occasionally on the SimHQ WoFF threads for continued functioning of said links. Cheers all, Von S

Setting observer/gunner accuracy to a value of 4, 4.5, or 5 - in JJJ's wonderful MultiMod - also helps to give more varied reactions. Sometimes gunners are excellent that way, sometimes average. I'm getting good, varied results with a value of 5, also 4.5. (Also set rear gunners to "less accurate" in the workshop settings in WOFF.) As well good to try is to reduce the AI guns' effective/precise shooting range to about 300 m (via the MultiMod). In terms of tracers, if you load one of JJJ's tracer mods. via JSGME, you will see tracers coming from rear gunner positions too. Cheers all, Von S

@OP, I recommend checking over this response regarding MP in the TW sims (in short, not possible, but the post contains good technical details): https://combatace.com/forums/topic/88806-thoughts-on-multiplayer-in-fe2/?tab=comments#comment-717069 Happy flying (in single player), Von S

Yes, the MS-N had a Hotchkiss M.G. with a side-loading tray (for clips carrying 30 rounds, I think). Several British MS-Ns replaced the Hotchkiss with a Lewis, instead. The MS-I on the other hand carried a Vickers. Cheers all, Von S

A fine idea. As far as I know, while that exact option is not yet possible - it is (in the UE/PE vers. of WOFF) possible to list, manually, extra witness names in the witness box. Simply place a comma after the first witness you choose in the witness box, and then type out any other witnesses who are available from the pull-down witness list. In order to do this, manually click on the witness box after choosing your first witness from the pull-down list. Also recommended is to use a comma to separate multiple witness names, rather than a semicolon (since a semicolon, it has been rumored, created oddities at times such as perpetual postponement of claims going through, etc.). Have not tried this in WOFF BH2 yet, but I am assuming that the witness box is "clickable" there too. I also leave a space after the comma, for good measure, and not to upset the claims system, in my backport 4.18 install. While this isn't exactly what you are asking for - theoretically, including a multiple witness list will "hit home" every time, with at least one of those witnesses being relevant if you have multiple claims listed. Cheers all and smooth claiming systems to you ("next time you must have witnesses"), Von S

Yes, we have one in FE2 - a fine model and you will find two FMs available for it in my FM pack for FE2 - one is for the Type N Bullet, the other modifies it to the specs. for the Type I, for the eastern front. The FE2 MS-N was the one, in modified form, that was experimented with in WOFF, by the way - unfortunately the original modder who created the MS-N has not logged in here for more than a decade. So it will probably be simpler, for those with skinning/modding talents, to begin from scratch with the MS-N, for WOFF. Cheers all, Von S

Yes, that sounds about right - have also sent you a PM with more info. The ver. 2.0 is by the way the lighter package with more 1 MB sized files; package ver. 1.0 contains more of the larger, 5 MB sized clouds. I am using ver. 2.0 since ver. 1.0 gave me a bigger FPS hit - although these things vary by rig. so perhaps you are getting better results with the bigger, ver. 1.0 pack. EDIT: Ver. 1.0 contains about six or seven larger (5 MB) cirrus and stratus-type clouds, while Ver. 2.0 reduces those same files to 1 MB in size. Cheers all, Von S

@Redwolf, I agree - I am only running FPS-friendly mods. in BH&H2 and will avoid the long list of (almost every) mod. that I am running in FrankenWOFF 4.18. Don't want to risk having FPS too low in BH&H2 and have managed, so far, to maintain them at about 70 FPS or so - with my FrankenBHAH Enhancement Package installed. @Dornil, the cloud mod. packages are at this link: https://thatoneplease.co/skyWOFF.html The relevant package is called "Clouds Mod (Version 1.0 and 2.0)." @Both, I will double-check my clouds pack mod. and will post info. in about 15 mins. - I think that I manually extracted the cloud files I wanted from that package and then made a custom JSGME folder for my own WOFF installs. EDIT: The 1MB-friendly cloud pack is the "Ver. 2.0" folder; "Ver. 1.0" has larger textures that impact on FPS somewhat. Cheers, Von S

Cloud mod. compatible in my BH&H2 install - I use the "1 MB" package - increases quality of clouds but doesn't give an FPS hit as do the 2 MB clouds. Stock clouds are a mix of 512 KB and 1 MB, by the way. I also recommend the Gecko improved water textures pack linked to somewhere under the mods. threads on SimHQ - recommended are the 2 MB water textures - improves quality of water but no FPS hit as with the higher (4 MB, etc.) water textures. I'm also running Olham's rivers mod. that makes the stock river a bit more blue - seems compatible so far. I've also been running the light, standalone airfields mod. (from the WOFF UE-era), not the full consolidated airfields package, in BH&H2 - and it seems okay so far, with no FPS hit. More info. on that in this post: https://combatace.com/forums/topic/95914-woff-bhh-2-mods-compatibility-lists-mod-faqs-etc/?tab=comments#comment-783382 Cheers all, Von S

I also don't know of any demos ever released for the modern TW series of sims. I wouldn't be surprised if that "demo" contains a trojan. The official TW series are available here: https://store.thirdwire.com/store_w7_all.htm#ShowMore And here: https://store.thirdwire.com/store.htm Cheers all, Von S

Hi Dresam, that is strange that selection boxes and arrows are non-functional in your ReShade install. I unfortunately don't have any advice on that - beyond perhaps re-installing ReShade once more, to see if that gets rid of the problem. Hopefully others who have had similar experiences with ReShade will post here with possible solutions to such a problem, of non-functional arrows/boxes in the ReShade menu. Ver. 1.2 of the RoF AI package seems okay so far in further quick combat tests. I have yet to test it further in campaign mode, over the next couple of months - and will keep a record of typical AI behavior in campaign mode. Hopefully it will be an improvement over 1.1 - although I did not fly too many campaigns in 1.1. A final ver. 1.3 of the AI pack will be released maybe much later this year, towards the end of summer, or fall - no earlier - since I want to do more extensive testing with 1.2 than I did with 1.1. I am currently spending more time in FE2 (and my FrankenWOFF 4.18 install) - since I prefer the immersion of FE2/WOFF - but I will try to find more time for campaigns in RoF too . It is most likely that ver. 1.3 will further improve on 1.2 - but I doubt that much more can be done with the AI in RoF than has been possible already in ver. 1.2. I will have a better picture of what to do in a final version of the RoF AI package in a few months. Greetings, Von S

Hi Dresam, from your explanation it seems that ReShade is loading properly but no preset file has been created, or selected, in it - therefore the message that is constantly seen at the top of your FE2 screen. Recommended is to press the "Home" button on your keyboard while in FE2 and while ReShade is running - this will open up the full ReShade window with various preferences present. Then search for the relevant preferences tab to load the appropriate preset file (there should be a "+" sign to the right of a box that contains the presets directory path - click on that plus sign to open another sub-window that will allow you manually to navigate to the FE2 preset file, and then to select it and to click "Save"). You may then close the ReShade preferences window and - ideally - no warning windows will be present anymore at the top of your screen while flying FE2, or any other sim. That floating window, when present, indicates that no preset file has been created, or that an existent preset file has not been chosen and saved, for ReShade to be able to open it and apply the necessary settings. Greetings, Von S

Hi Dresam, yes that sounds correct. Point ReShade to the folder that contains the FE2.exe when installing it. Recommended is first to uninstall ReShade if you have installed it incorrectly, and then re-install it again - pointing to the correct folder that contains the simulator's exe. Greetings, Von S

Very brief update to this thread: those interested in recording video/audio in the WOFF (CFS3) runtime and who are running WOFF of any vintage from UE to BH&H2, either on Macs or PCs with AMD-vid. cards, and perhaps slightly older AMD DLLs (such as the venerable ver. 17.x.x), are recommended to check over the following post under the AMD help thread on SimHQ: https://simhq.com/forum/ubbthreads.php/topics/4569175/re-amd-help-and-support#Post4569175 Cheers all, Von S

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 TIP: I recommend loading my "FrankenBHAH Enhancement Package" in WOFF BH&H 2 on Macs. It is JSGME-friendly and improves FPS via my FrankenMiniTuner, among various other improvements worked on in FrankenWOFF 4.18. Please see the "Read Me" file included in the package for more info. The link to the package is (https://combatace.com/forums/topic/92320-fm-tweaks-for-woffuepe/?tab=comments#comment-783155). Also, if loading Reshade and perhaps my shaders preset file for WOFF, in BH&H 2, recommended is to set NoMultisampling to a value of 1 in the two d3d8 configuration files that are included in the package, located under WOFFScenery\Shaders and OBDWW1 Over Flanders Fields. ----- 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.

Just a quick note that I'm getting the following warning from WinDefender when I download the BH&H2 mission ed. from the alternative link above, also from the downloads sections here on CombatAce: Backdoor:Win32/Bladabindi!ml Defender then proceeds to trash/delete the file - so no worries from my end but wanted to give a heads up. Is it perhaps the same false error that was present in earlier versions of the mission ed., since it contains an exe/shortcut to the main JAR file - and is showing up as a backdoor thingy in Defender? (I have Defender on "high settings" by the way, not default - which I set via a little program called "ConfigureDefender.") Cheers all, Von S

Hi Dresam, Maybe double-check that you do not have the same axes linked to pitch/yaw/zoom views in your Default.ini file located under: C:\Users\Username\Saved Games\ThirdWire\FirstEagles2\Controls The relevant entries to check over are included below: CAMERA_ZOOM_IN=MOUSE_BUTTON01 CAMERA_ZOOM_OUT=MOUSE_BUTTON02 CAMERA_PITCH_AXIS=MOUSE_Y-AXIS CAMERA_YAW_AXIS=MOUSE_X-AXIS CAMERA_ZOOM_CONTROL=MOUSE_Z-AXIS Greetings, Von S

Hi Dresam, Sorry can't help with suggestions regarding cockpit zooms/views and TrackIR since I only use padlock view and mouse view. Hopefully someone with experience running TrackIR or open-source imitations of TrackIR will pitch in with some tips in this thread. In terms of ReShade, it does not install into the saved games directory for FE2, but instead, you will find the relevant folders (after a ReShade install has completed) located in the actual game directory for FE2, found at: C:\Program Files (x86)\ThirdWire\First Eagles 2 Having said that, there is one more peculiarity to be aware of for FE2 - as indicated in the included "Read Me" file with the shaders preset package. The peculiarity is that, unlike for SF2, the preset file itself for FE2 does not load into the game directory where the other ReShade-related folders are loaded. Instead, the FE2 preset file is loaded into: C:\Users\Username\AppData\Local\VirtualStore\Program Files (x86)\ThirdWire\First Eagles 2 So, to activate my preset file in ReShade, in FE2, make sure to place "FE2SF2shadersVonS.ini" into the directory location specified immediately above this sentence. To load the ReShade menu while in FE2, by the way, use the "Home" key on your keyboard - the "Home" key will open up other menu settings in ReShade where you will be able to load my preset file, toggle other filters, etc. Greetings, Von S