Jump to content

VonS

+MODDER
  • Content count

    956
  • Joined

  • Last visited

  • Days Won

    2

VonS last won the day on January 27 2021

VonS had the most liked content!

Community Reputation

1,409 +1000 Reputation

4 Followers

About VonS

  • Rank
    WWI Flight Sims on a Mac

Profile Information

  • Gender
    Male
  • Interests
    WWI aircraft & flight-sim enthusiast, particularly my fully modded First Eagles 2 installs.

    FE2 "DiD Missions" thread available at:
    https://tinyurl.com/FE2did

    WoFF tips & tweaks available under the WoFF "casual campaigns" thread (particularly the first few, and last several, pages of that thread):
    https://tinyurl.com/WOFFcc

    FlightGear tips available at:
    https://tinyurl.com/FGtipsVonS

Networking

  • Website
    https://tinyurl.com/FE2onMacs https://tinyurl.com/WOFFonMac

Recent Profile Visitors

14,497 profile views
  1. New in FE2

    FE2 is still alive and well - more obscure than RoF and WoFF - although that may be a good thing. Let us know what kind of "augmentation" you are interested in - and perhaps some of the FE2 specialists will pitch in with good info. If interested in FM modifications/integrations of (and into) FE2 - suggested is to begin with this post, in particular the bottom link of that post that outlines what aircraft packages many of my FM tweaks correspond with. For terrain editing, placement of targets, modification and/or installation of airfield objects, and other misc. objects, I would recommend contacting Stephen1918 (he has developed many excellent aircraft models for FE2, as well as several, important airfield objects). Geezer is also an encyclopedia of FE2-related knowledge (terrain/airfield and aircraft modding and development) - but I don't think that he mods anymore for FE2 (or at least hasn't posted here in a couple of years). Cheers to you & good flying in the FE2 skies.
  2. Still playing

    @toot, the general rule of thumb is that the physics/world model in SF2 (i.e., winds, atmosphere, flight dynamics, etc.) is best suited to jet aircraft and to some extent to fast(er) prop aircraft - let's say with a minimum speed of 400 kph or so. The simulated "world" in FE2 on the other hand caters much more effectively to slow(er) flying, and showcases better the flying (and fighting) characteristics of pre-WWI, WWI, and inter-war era aircraft of, for example, the 1920s (think "barnstorming"). To give an example of the different atmospherics and physics, an early 1950s (late model) F4U-5 Corsair has a historical top speed in the 750s kph in SF2, while, when dropped into FE2, it goes into the 880s kph. Recommended also is to check over this thread regarding swapping of aircraft from FE2 to SF2, and vice versa - sometimes such swapping works, but often it doesn't. Furthermore, FE2 has higher-quality terrains (smaller-sized terrain pieces, as far as I know) and more subtle fog effects, I think, than SF2 - such things help with immersion because most aircraft in FE2 fly fairly low - on the other hand, use of such terrains in SF2 would probably result in an FPS hit, and is not really needed for jet aircraft scenarios where everyone is usually flying high and at great speed. Cheers,
  3. Still playing

    Indeed a shame - hardly any regular posts in the FE2 forums anymore. Hope everyone's doing well - haven't seen names like Geezer, Crawford, and others in these forums for years. Fully-modded FE2 is still my go-to sim for single missions with variety, and for tight-knuckle flying and dog-fighting - I'd say better than modded RoF, and also easier to set up and quicker to get into than the WoFF series (although the latter is definitely the gold standard for full-blown campaigning). Come to think of it, the WoFF forums on SimHQ have also largely dried up over the last couple of years. And DiD IV, the latest Dead is Dead campaign being run in WoFF (on their CombatAce forums) is pretty much literally DiD too (compared with DiDs II and III from several years back). Perhaps newer generations of simmers have mostly gravitated to multiplayer; or tablet/phone games have saturated the game market. I hope to return more regularly to FE2 in the future - there are a few aircraft that I haven't tweaked the FMs for, and I still want to try to introduce (if possible) realistic turbulence into the sim. Also, there's something wholesome and relaxing about tinkering with FE2 - the virtual equivalent of an old, wooden hangar or quaint WWI aircraft factory. Was busy for a while with AI mods for RoF (an exercise in frustration considering that RoF is so locked-down); and also re-discovered FlightGear in the meantime, a very nice, free sim for monoplane simulation and civilian flying - but be selective when choosing aircraft to fly in it. Some of the FMs are questionable, particularly for multi-wing aircraft. Recommended there is to stick to large airliners like the 707, 747, DC-10, also single-wing, small aircraft such as Pipers, Cessnas, Tecnams, gliders, and so on. (Thinking to myself: sure would be nice to introduce the live weather and advanced weather systems from FlightGear into FE2 - i.e., METAR system, also moisture formation, storms, and so on - although that would require some way of having an open connection to the internet, from within FE2, to siphon in live weather data per whatever location you're flying through in FE2 at any given moment, etc.) Cheers all,
  4. One more post for this thread - been tinkering further with FlightGear and have come up with a few more tweaks for the "additional settings" section of the main menu that should help with FPS/graphics quality on AMD-vid cards. Also tweaked the Yasim FMs for the Grumman American AA-1 and SIAI-Marchetti S.205(R) a wee bit in the meantime - to change the former into the early ver. of the AA-1, and the latter into a WACO S-220. More info., as well as all relevant files, are included in the "addons" package that's linked to under the illustrative pics. below. Pic 1 - Re-colored the Standard AA-1 Livery for a Bit More Retro Styling Pic 2 - Re-colored Some of the Stock Interior Panels, and Seats too, for More of a 1960s' Look Pic 3 - Section of a 1960s' Pamphlet About the S.205(R) Import (Rebranded as the WACO S-220 and Up-engined to 220 HP) Pic 4 - Yes, I Enjoy "Flying" the S.205(R)/S-220 in FlightGear (Feels Like a Sports-Car Version of the Piper PA-28 and Looks the Part); Custom Livery not Included FlightGear_Addons_VonS.zip [For my other FlightGear FM tweaks package, see this post above.] Happy flying, Von S
  5. Let me thank you for your stellar tales in DiDs II, III, and IV Raine. I often go back to re-read them and encourage you when convenient to compile a "best of" pdf collection of your pilots' exploits. I wish you good health and happiness, rest and recuperation, and hope that you will continue in some way to be connected with WoFF/WoTR in the future. All the very best to you.
  6. @OP, something similar occasionally happens to me if moving the WOFFKeys.xca file from computer to computer, so that it is no longer recognized in WoFF. For the Logitech stick, it's important to double-check that its correct identification is always in place in the relevant xca file. The full path to the file is: C:\Users\YourName\AppData\Roaming\OBD_Games\OBDWW1 Over Flanders Fields\WOFFKeys.xca Once you open the WOFFKeys file, drill all the way down until you get almost to the bottom of the document, to the joystick section. Then search for the device type name indicated below and make sure that it is identical (or, if not identical, change to the info. below and then save the file) - the joystick should then be recognized in WoFF (i.e., all inputs will be registered, including programmed keys on the joystick and x/y/z axes). <Device Type="Logitech Extreme 3D Pro USB"> Cheers,
  7. Glad you like the post Mue; FlightGear has definitely grown on me in terms of its monoplane offerings (and realistic weather/winds simulation), especially with its latest stable release. For those interested in this thread - have now also included FM tweaks (and slightly re-colored textures) for the Eastbourne Monoplane of 1913 in the attached package located at the bottom of the first post, as well as representative pics. More technical information about the Eastbourne can be found at this informative link that includes several pages on the (obscure) monoplane extracted from the May 1913 ed. of Flight Magazine. Happy flying (in FE2/SF2, as well as in FlightGear),
  8. Recently I had an opportunity to re-install FlightGear (stable ver. 2020.3) on my 2013 Mac Pro and was pleasantly surprised - with no crashes, decent FPS for the most part, and various other improvements that were incorporated over the years. I had dabbled briefly in FlightGear a couple of times before (around 2013, and again around 2020) - but eventually removed the flight simulator from my hard drive on both of those occasions. Since my particular setup(s) are with dual AMD video cards, I thought I would post some (illustrative) tips below, as well as representative pics of the sim when at best, or very good, settings. You will also find, at the very bottom of this post, a zipped file that contains a few tweaked Yasim FM files for the MS.406, MC.72 floatplane, Deperdussin Racer and Bleriot XI, also the Eastbourne Monoplane of 1913, available via the default aircraft hangar in FlightGear. (Couldn't resist tinkering with a few of the FMs since I will this time keep FlightGear on my hard drive - makes for a good, free flight simulator.) For command line entries and tips that should be plugged into the "Additional Settings" option of FlightGear - please see the "Read Me" file that I have included with the zipped FMs that are at the bottom of this post. On a broader note, it's important to tweak the rendering, shaders, and LOD range settings in FlightGear - to get the best experience on your AMD video rigs (be it a dual or single AMD setup). The frequencies, by the way, on my dual FireProD700s have been OC-ed, via MSI Afterburner, from a clock/memory of 850/1370 to 1024/1380 MHz. Be sensible with the rendering options - particularly with the maximum number of scenery and aircraft tiles - anything above a value of 1900 or so is both useless and an FPS hit. Take note as well of cloud density and visibility values. Anything beyond a visibility of 35 km or so is questionable since it does not widen further the cloud carpet but is, once again, an FPS hit. Pic 1 - Sensible/Best Rendering Choices for AMD Video (in FlightGear) Next we look at the shader options that also require careful thinking and tweaking. Take note that "landmass," "urban," also "water" - give different visuals if they are set to the maximum level (of five). I personally prefer how the landscape/terrains look with those three settings at a value of four - with crisper graphics - but tweak according to taste. Also worth noting is that I always run the LOD value on my rig(s) at "-1," via the excellent little program "ATISetLod" that is available under the top post of this thread. Pic 2 - Sensible/Best Shader Options for AMD Video (for crisp and fairly realistic graphics) Also important is to tweak the LOD range settings to get a good balance between visual quality and decent FPS, with no stuttering or crashes. Focus in particular on the maximum distances for the detailed, rough and bare scenery ranges - I decided eventually on cutoffs of 3, 17.5 and nearly 45 km. Other cutoffs worth considering are 2.5, 15, and 40 (or so) km, as well as 3.5, 20, and 50 km. Anything beyond the latter values will, again, most likely not make much of a difference with the visuals but will contribute a noticeable FPS hit. Take note also of the "high detail" and "AI/MP interior" values. I'm getting good results with values of 250 - 260 pixels for those options; also good are values of 300 (or so) pixels. Those two values may be tweaked to taste, for the most part - but, again, be sensible since they may impact on FPS. Pic 3 - Sensible/Best LOD Range Values for AMD Video Last, let's not forget to tweak our custom FlightGear profile (in our AMD settings panel) as best we can, to minimize stuttering, pausing, or crashes. Take note in particular how the shader cache is set to "On," not to "AMD Optimized," and how, even though I have enabled CrossFire mode, frame pacing is set to "Off" (which eradicates stutters on my rig in FlightGear - had tried with frame pacing "On" and was not pleased with the results). If you have only a single AMD video card, experiment with leaving the CrossFire option on (set to "AFR compatible"), or turning it off entirely. Pic 4 - Good AMD Settings for a Custom FlightGear Profile Recommended also, if having any instability with FlightGear on AMD video, is to stick with the "Pro" variant DLLs (drivers) for AMD, instead of the consumer/Adrenalin ones. I particularly like the ver. 19.x.x Pro series of drivers, as well as the venerable ver. 17.x.x ones (the latter of which I have installed on the 2013 Mac Pro). To find links to the Pro 19.Q3 DLLs (the last version of the Pro DLLs to support CrossFire, by the way), see this page. Below follow several representative pics with the settings illustrated above applied - FlightGear provides a nice selection of aircraft with usually very good monoplane FMs, especially for tricycle-gear (small) civilian aircraft such as Cessnas, also for airliners like the (classic) Boeing 707. For multi-wing contraptions on the other hand and more realistic/historical FMs for biplanes, triplanes, and the odd multiplane, the gold standard(s) remain heavily-modded First Eagles 2 and RoF, as well as recent iterations (UE edition onwards) of the excellent WoFF series. FlightGear_SelectFMs_VonS.zip [Updated Feb. 3, 2024: package now includes FM tweaks for the Eastbourne Monoplane.] [For my additional tweaks package for FlightGear, see this post below.] Happy flying, Von S
  9. Hi Tonci, I had a post from yrs. ago regarding that topic (I also think that Burning Beard, Buckeye Bob, and other BB's commented on the topic with excellent info.) - but I can't track down the post now since it was in some obscure thread on SimHQ that got buried by other posts and info. On that note, I'll just copy out from some of my "flight notes" that I have in front of me here, for the WoFF series. ----- Engine Types Management (Simplified) - very early rotaries on Bristol Scout, Fokk. E.I, Pfalz. A.I two-seater, Morane Parasol Type L (early variants before 1916) at 100% power, fine adjustment and blip for limited control - Gnome rotaries on Camel, DH.2 at 80 or 100% power, fine adjustment and blip for limited control - (somewhat) early rotaries such as on later series of Fokk. Eindeckers (the II and III), also the Pfalz E.III, Parasol Type L beginning with 1916, etc. at 60, 80 or 100% power, fine adjustment and blip for limited control - all other rotaries (mid-war, late-war, etc.) at 40, 60, 80 or 100% power, fine adjustment and blip for limited control - early inlines to about Alb. D.III and SE5, full throttle range but no fine adjustment (always full rich) - later inlines from about Alb. D.V and SE5a Hisso onwards, full throttle range and fine adjustment available Realistic Fuel Consumption Tips - either use the Orbyx "fuel mod" available with JJJ's MultiMod for WoFF, or, if you prefer a static solution, set fuel to about 40% for approx. two hrs. max. flight as mostly historical (avoid 50% since it sometimes crashes WoFF, or at least did crash it during the WoFFue era) - from Aug. 1918, for Germans, elites get 20% fuel supply since rations - less important German units from Aug. 1918 get only 10% fuel supply ----- Cheers,
  10. Hi Tonci, for BH&H2-compatible mods, best is to check over Becker's excellent mods-compatibility post at this link. RJW's "Custom Consolidated Airfields and Facilities" mod(s) are must-haves and are compatible with BH&H2. Also worth checking out are BuckeyeBob's cloud/weather mods (those I think are listed under Becker's post, and available also on Sandbagger's website where RJW's facilities mods are hosted too). In terms of my FM mods, make sure to use with BH&H2 only the ones that are indicated to be BH&H2-compatible in that package (I've organized things by folders so it is easy to figure out what is compatible - for example, my older WoFF UE/PE FM mods are all in a separate folder and may be disregarded). The "FrankenBHAH Enhancement Package" is a terrain/FPS-tuner package tweaked to eradicate screen tearing and to improve FPS whenever possible, in BH&H2. There are also various realism tweaks included in that package. If you want to run the enhancement package, the recommended order in which to load it via JSGME is as follows: Step 1: Base Enhancement Package (ver. 1.1) Step 2 (optional): Hardcore Addon (ver. 1.15) Step 3 (optional, load only if not installing 1.15): Hardcore "Compensatory AI" Addon (ver. 1.16) Step 4 (optional, always load after 1.1, 1.15/1.16, etc.): FrankenMiniTuner ver. 1.2 If you are interested in the mods listed immediately above, recommended is first to install only the base package 1.1 and mini-tuner 1.2, for FPS improvements and smoothness - and to leave the addon 1.15 and/or addon 1.16 for later, once you become more familiar with WoFF (because addons 1.15 and 1.16 include some modifications to AI routines and chances of such routines in WoFF BH&H2; those addons also increase chances of engine breakdown, fire, etc., and further remove you from the stock WoFF experience). To find all of those various mods, simply scroll up/down through the posts in that support thread where I also posted info. about the dual-CPU X79 build. In terms of Bletchley's mods - I don't know if they are compatible with BH&H2. Hopefully someone will see this thread and comment on those other mods. The "Historically Populated Airfields" mod by JJJ (ver. 1.5) works for the most part, as far as I know, only if you are also using JJJ's Java-based "Mission Editor" for BH&H2. Standalone, I don't think it provides full results - namely, historical aircraft types (static models) at airfields, depending on period of war. Regarding those other terrain mods you've mentioned - largely a hit-and-miss situation - some may be compatible, others may not be - best is to experiment slowly with those (I think that most of those terrain mods were made for WoFF UE, possibly not even updated for WoFF PE). Cheers,
  11. Hi Tonci, have PM-ed you a message with various tips and suggestions regarding what AMD GPU DLLs to try out on your rig. Hopefully one of those versions of DLLs, at least, will resolve that textures oddity for you. Cheers,
  12. Brief update to this thread - instead of opening a separate post, I thought that it would be best to bump this particular thread up with fresh(er) technical info. regarding WoFFing on AMD-vid cards. Those who are sometimes troubled by flashing and/or dark terrain tiles in WoFF on AMD video might wish to have a gander at this article located at the bottom of the WoFF FM and other mods. support thread, wherein I outline an X79 server build and a few tips/tricks that might help to resolve any oddities if WoFFing on AMD GPUs. Will also update regarding this under the relevant AMD thread on SimHQ if I have not already done so. Cheers all & good WoFFing to you,
  13. BHaH-Two WoFFing on a Dilwe Dual-CPU-Socket X79 Motherboard with Dual Overclocked AMD RX 580s, for Kicks and Giggles Recently, on a lazy winter's afternoon, I had the good fortune of finding two new/unopened Intel Xeon E5 2690 v.2 processors (3.0 GHz; 3.6 GHz TurboBoost; 10-core) on Ebay and decided that, for 37-38 USD a piece, they were a wholesome buy. My original intention was to "upgrade" the single Intel Xeon E5 1650 v.2 (3.5 Ghz; 3.9 GHz TurboBoost; 6-core) sitting in my 2013 Mac Pro (my standard WoFFing machine), but I then decided that it was better to "build" a computer around the two Xeons that I found, for kicks and technical handiwork. The general idea was to create an office server/work computer setup - which would also fit well with WoFF BH&H2, considering that flying an Eindecker in WoFF is hardly leisure but instead very rewarding and hard work. Armed with such ideas, I then picked my way through various components, deciding that I wasn't interested in exceeding about 800-900 USD for the entire build. Various parts included the Corsair computer case (4000 D) with good ventilation, a Corsair 850 Watt PSU, etc. (No tacky LED lights for me or brown/beige Noctua fans.) For the computer and video graphics themselves, I decided on a dual-CPU X79 board and happily found mounds of rather cheap, single-CPU Chinese ones being offered on Amazon. Not to be maximally cheap, I decided on the ever-so-slightly higher-tiered (?) Dilwe brand (X79 dual LGA 2011 socket; EATX-sized motherboard). And, at any rate, the dual-CPU-socket offerings were not as plentiful as single-CPU mobos. The dual-CPU board I picked supports a maximum of 128 GB of DDR3 RAM at 1866 MHz but I went instead with a modest 32 GB (1600 MHz) of budget RAM (TeamGroup rebranded Micron chips) and a 1 TB NVMe M.2 (Kingston) SSD, also with two passive Supermicro heatsinks, and so on and so forth. For the video cards, being pleased with a dual team red (AMD) setup in the 2013 Mac Pro (two 6 GB FirePro D700s), I chose again a dual AMD setup (two 8 GB RX 580s this time around) for the custom build, even though it is generally suggested that WoFFing is safer on the team green side of the fence (nVidia). Luckily, the RX 580s were also Dilwe brand (making for a good fit with the Dilwe motherboard). And I found the Dilwe name attractive for some reason, possibly reminiscent of fridges and other gadgets from the 1950s. Several cables, fans and modifications later, over the span of a few days, I found myself in a position finally to test the Dilwe Dual-Xeon monstrosity couched in an elegant Corsair case. Installing Windows was no problem; neither was tweaking the somewhat limited options in the BIOS, but a few tips follow below (and no, I did not flash/upgrade the BIOS nor will I do so - not interested at all in bricking this strange build). Suggestions: - switch to legacy BIOS and format your drive to MBR (not GPT), for maximal smoothness of installation (of Windows); UEFI does work but I preferred the legacy/MBR route (if installing Linux, the latter will do its own formatting prior to installation) - disable such options as extended synchronization, pci-e clock/power management, and precision clock timers in the BIOS (helps to give a more responsive system and apparently minimizes GPU throttling) - set latency timers at least to 64, possibly 128, in the BIOS (default is 32); I went with 160 and haven't noticed any peculiarities so far Pic 1 - Initial Five-Fan and Mostly Passive Heatsink Setup The only other main area of concern, after having installed Windows and organized/tweaked settings, was how to keep the dual Xeons cool at idle. Initially I went with a five-fan setup (three intake on the front; two outtake, with one at the back and one at the top). The setup was perfectly sufficient to keep the two GPUs cool that way for most tasks - you could even turn off the GPU fans with no risk (with the fine program Fan Control) - but CPUs still remained quite hot at idle. The worst idle temperatures were with thermal paste applied between the passive heatsinks and processors (around 70 degrees Celsius). Better idle temperatures (of 55 to 60 degrees Celsius) were attained by placing thermal pads between the passive heatsinks and processors (never mind the general consensus that paste is better than thermal pads) - and by going to a six 120 mm fan setup (by adding an extra intake fan at the top of the case). I also oriented some of the fans differently, with the bottom two fans up front working as intake fans, also the two fans at the top of the case. The back fan remained an outtake fan; and the top side fan on the front was also reversed to function as an outtake fan - giving two nice exhausts on the top sides (front and back) of the case. Pic 2 - Final Eight-Fan Setup and Orientation for Improved Cooling I could have left things alone at that point but then decided to custom-install two small, unassuming (and gray) Noctua fans (1600 RPM, 92 mm) to each of the passive heatsinks, through the miracle of some zip ties and wire clips. This finally gave me splendid results (with idle CPU temperatures in the 30s Celsius - see included pic., overview of temp. nos. via the excellent program HWiNFO). The eight fans in total, surprisingly, are not that noisy, especially with the case fully closed and the included dust filters attached. Also helpful was that I had - before the final arrangement of fans - sandwiched two 1mm copper plates between each of the Xeon CPUs and their heatsinks, also "framing" the copper plates with four strips of thermal pad for good measure. Pic 3 - HWinNFO Allows for a Quick Overview of Temps. in the Taskbar (Details are Temps. for CPUs 1 and 2, Packages 1 and 2, Top and Bottom of Mobo, SSD, and GPUs 1 and 2; Choose Heads-Up Colors as per Taste in HWiNFO) The two RX 580 GPUs were easily overclocked via MSI-Afterburner from stock numbers of clock 1284/memory 1750 MHz to clock 1415/memory 2095 MHz. Numbers of 1420/2100 MHz and higher give the occasional crash and are not worth the risk. CPU overclocking is not possible with locked multipliers on this generation of Xeons; furthermore, it is also not possible to BCLK overclock the system bus on the Dilwe X79 mobo (or most such mobos). Pic 4 - Nice and Stable OC on the RX 580s Aside: I did in the meantime manage to overclock the bus to 103 MHz on the 2013 Mac Pro for a small performance boost and it runs well with no higher temperatures noted (to OC slightly your bus on a 2013 Mac Pro, download the obscure and outdated program called "setfsb.exe," choose as clock generator the profile called "ICS932S421BGLF," etc. - do track down other details regarding the program via Google before attempting the tweak, and also worth remembering is to download ver. 2.2 of the program, not 2.3, since 2.3 doesn't allow for the bus to be changed on a 2013 Mac Pro). Other information worth sharing, regarding WoFFing on dual AMD setups, is to point, in your AMD profile, to the WoFF.exe, not to the CFS3.exe run-time (even though it sounds counter-productive). On older versions of WoFF, and also on single AMD video-card setups, feel free in most cases to point to the CFS3 run-time instead. Pic 5 - Point BH&H2 to the WoFF.exe (not to CFS3.exe) if on a Dual AMD Setup Further, if enabling crossfire in your WoFF profile in the AMD settings, make sure to disable crossfire in the "global settings" profile in the AMD settings program - having crossfire enabled in both global and individual program profiles will cause random black tiles/textures in WoFF (a common complaint regarding AMD vid. and WoFF, and that has appeared on the WoFF SimHQ threads, occasionally, over the years). Pic 6 - It's Important to Disable Crossfire in your "Global" AMD Settings Profile (To Minimize Risk of Texture Corruption) By making sure to enable crossfire per program, but not globally - if you have multiple AMD cards installed - you will get rid of any texture corruption effects. Last, it doesn't hurt to experiment with various versions of the AMD DLLs (drivers) that you install. For example, the latest AMD DLLs (as of this writing) work fine on the Windows 10 22H2 install that I have on the Dilwe X79, but crossfire is not present (and hasn't been present) as an option since about the ver. 20.x days of the AMD DLLs. To be on the safe side, I have installed the Radeon Pro Software for Enterprise (version 19Q3) and it works fine, with no noticeable drop in FPS in WoFF BH&H2, and also supports the crossfire option (version 19Q4, for example, does not). On a broader note, if you are having any other troubles with the Adrenalin/consumer versions of the AMD DLLs and your WoFFing - go with the Pro DLLs instead. Pic 7 - Detailed BH&H2 AMD Settings for Your Convenience I happily recommend the AMD Pro DLLs 19Q3 for your WoFF/AMD combinations on later iterations of Windows 10, such as 22H2 - just as good, if not better, than the venerable ver. 17.x.x DLLs that go well with Win10 ver. 1809. The link to the correct drivers is: https://www.amd.com/en/support/kb/release-notes/rn-pro-win-19-q3 Overall, while I am not terribly interested in dipping further into the hobby of custom-building PCs for myself, I am quite pleased with the outcome of the Dilwe X79 (one-off) project. A few quick bench tests in CPU-Z (see included pic.) indicate that, on average, the Dilwe is giving me the multi-threading power of three 2013 Mac Pros - but will most likely also use three times as much electricity as the Mac Pro (e.g., the Dual-Xeon Dilwe X79 idles at around 93-94 Watts, at best, while the 2013 Mac Pro idles at around 46-47 Watts). Pic 8 - Quick Benchmark Results The experiment was a nice way to put two Xeon processors to good use, with the end result being a stable server/work computer as well as the occasional hosting hardware for a campaign or two (or three) of power-WoFFing. BH&H2 1.37 therefore moves to my Dilwe Dual-Socket X79 with its pair of OC-ed RX 580s, while I will keep my FrankenWoFF install (PE terrains and aircraft backported to WoFF UE 4.18) on the 2013 Mac Pro. Pics 9, 10, 11 - BH&H2 1.37 on the Dilwe Dual-Xeon X79 (LOD set to -1 via the Program ATISetLod; Pics also Include a Variation on Xjouve's Ver. 1.1 Water Mod, etc.) Finally, worth considering for these DIY obscure computer builds are any bottlenecking issues that might emerge; easiest to avoid those problems is by choosing processors, motherboards, and video cards of roughly the same, or similar, generations. From what I could research the best choice of GPU, for example, for the X79 server mobo that I picked up, as well as for the ver. 2 generation of E5 Xeons I found, was either the AMD RX 580 8GB or nVidia's GTX 1060 6GB card. Minimizing of possible bottlenecks should help, theoretically, to minimize any FPS drops and stuttering nuisances in your WoFF install. Good current and retro WoFFing to all (on single or dual-socket CPU mobos; obscure, well-known, and everything in between),
  14. Hi Alpenman, those files that begin with an underscore are Mac OS files that are sometimes arbitrarily generated in various folders of my mods packages as I work on them. I usually turn off the setting to view invisible files, in the Windows 10 partition on my Mac Pro, so I did not spot those files earlier (typically they show up as visible files so I delete them before uploading my mods packages; this time they remained invisible for some reason). Have now removed all Mac-related files and have re-uploaded the RoF mods package. While those Mac indexing files don't alter the way the AI/DM mods work - I recommend re-downloading the package (the link is in the first post of this thread) - for the sake of improved cosmetics. The PWCG "ModulationsVer3" file is fine by the way (doesn't contain any Mac-related files), so that one was not re-uploaded. Cheers,
  15. Hi Alpenman, Recommended is to check over the following two posts on the IL2 forums, regarding AI takeoff fixes for RoF. As far as I know, the problem is present in PWCG 3.x.x but not in the older 16.3.1. I have included the takeoff fix tip in my AI mods, by the way. The only other thing that I can think of is that the AI doesn't like stronger winds so it might help to reduce wind speeds too in the PWCG menu, if all else fails to resolve that takeoff problem. https://forum.il2sturmovik.com/topic/83819-possible-fix-for-squadron-mates-not-taking-off-during-career-missions/ https://forum.il2sturmovik.com/topic/84205-ai-not-taking-off-and-acting-weird/ Cheers,
×

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