VonS

Great opening reports gents - looking forward to more. An excellent initial entry Raine - I particularly like the interlude about Mr. Cust (reminds one of the clumsy Mr. Toad from Wind in the Willows). Happy DiDing all, Von S

Hello, I am assuming that the AI increases/decreases mixture often while flying, in conjunction with reduction of throttle - depending on altitude. This is (maybe) one of the reasons why they drop speed more quickly since they reduce both power and throttle to the engine at the same time. Possibly try choosing "auto-mixture" if there is such a setting in the in-sim menu - might help to stay in formation more easily with a large flight - instead of manually toggling with mixture at different altitudes. Also worth experimenting with, if you prefer manually to tweak mixture - is to turn off one of the magnetos while you reduce throttle - that might be another trick worth exploring, to reduce speed more quickly. Don't forget to turn the magneto on again once you have decelerated. I need to find more time to fly WOTR -- from memory, I remember also turning off the battery when flying, and only turning it back on before landing, etc. Flaps I tend to avoid using but instead use the one-magneto-on trick when landing - helps to cut power noticeably. Other little oddities that I remember doing - no need to fly at more than 85% mixture, even when flying low - doesn't add any power and only wastes fuel. You might however want to set to 100% (rich) when landing - if you are worried that your engine will conk out. Cheers, Von S

Hello, recommended is to scroll towards the bottom of the following post - where you will find two links to performance tips for the Hurricane and Spitfire in WOTR - much of the info. is applicable to the BF-109 too. Cheers, Von S

And so it begins - nice to see more mature WWI pilots (such as the crew from The Blue Max) and some hailing from exotic regions, for DiD IV - will see if I can find enough free time perhaps to join once "1916" rolls in gents' - currently still busy with work and all that jazz. Be careful with those under-powered crates if flying some of the early war FMs for maximal enjoyment in 1915. Looking forward to reports of aircraft barely taking off and (very) long hauls to the front, particularly when the winds are in the opposite direction. And keeping my fingers crossed for a dogfight or two between the early Morane Parasol L and Pfalz A.I early war variants - congratulations to all, beforehand, if you manage to overtake and/or land hits on your opponent in such scenarios. Happy DiDing all, Von S

A good compromise therefore with the guns mod. may be to increase the various gun range entries by a value of anywhere from 10 to 30 meters or so above current values - which should keep the actual max. shooting ranges (for the AI) fairly close to distances specified/estimated in the initial version of the guns mod. Thinking out loud here but hope that the info. is of help. Cheers all and a happy new year to all fellow WOFFers/WOTRers, Von S

Since there is no official sub-thread "wish list" for WOTR - permit me gents to use this one (briefly) as an ad hoc wish list --- here's wishing that WOTR will eventually get the early Mk.I Hurricane (with fabric-covered wings, two-bladed prop., no self-sealing tanks, and about 1000 HP). Possible also is that there was no WEP power option on the early Mk.I (c. 1937 to 1939), but I will let the WW2 specialists do further research into that. The early Mk.I would fit nicely for Battle of France scenarios, obscure pre-WW2 conflicts, as well as for situations having the occasional early Mk.I available for BoB too, for variety. Cheers all and happy WOTRing in early WW2 'crates (also happy holidays to all WOTRers/WOFFers), Von S

Brief update to this thread: a small FM Addon Package (Ver. 1.1) has been included for BH&H2 under this post. The package includes the Benz-powered (early) Alb. D.1, as well as the SPAD 17 (300 hp). For the WOFF UE/PE version of the addon package, see instead this post under the same thread. Cheers all, Von S

Brief addendum to this stimulating thread - those looking for my FM packages for BH&H2 are best off checking over this link, since the link contained in the first post of this thread is to the main page for my WOFF UE/PE-only FM package. The link included in this particular post takes you to the support thread for all of my WOFF-related packages, where you may also find the WOFF UE/PE-era FM tweaks ready for download, as well as other WOFF/WOTR enhancement packages and GPU tuners, etc. Cheers all & happy WOFFing, Von S

Yes, this has been a vexing problem in the FE/FE2 series owing to the nature of the TW sim. engine - WOFF has some random engine unreliability thrown in which is a nice addition (and engine cutoff in negative Gs), but ROF probably has even more realism in that department (with over-revving damage and other engine problems) - although I think that we have overall better FMs than those other two sims (lack of dangerous, sustained spins in WOFF, too much turbulence over-amplification in ROF, etc.). If I ever stumble on some way of introducing engine unreliability into the FE series, I will of course post here --- ideally, I would like to introduce such a feature, if possible, using one of the general ini files that would include parameters for all aircraft --- since it would be cumbersome to implement such tweaks per data ini file. Cheers all, Von S

Correct, that is the SVA5 variant that Laton did many years ago. The Balilla had slightly worse performance than the SVA5 (about 10 kph slower top speed and slightly slower rate of climb). Surprising, however, is that the Balilla seems to have been produced longer than the SVA5 - well into the 1920s. Happy flying all, Von S

For those who are interested in flying the Ansaldo, there is an old model from 2009 by Laton available for FE/FE2 - the tweaked FM/data ini for it is available in my big ver. 9.9 FM update pack. A few yrs. back Mike Dora (I think?) came up with a fix that got rid of a white patch/square near the propeller hub on that Ansaldo too - all possible fixes were included in the data ini tweak available in the relevant FM update pack. The Ansaldo was one of the fastest WWI aircraft (230 kph top speed near SL, or thereabouts) but, as Crawford has indicated, not the most maneuverable. Since this is turning into a wish list for new aircraft for FE2 - here are a few that I would (ideally) like to see, eventually, somewhere in the production line: Fokker D.I (with inline engine and the vertical tail fin that sits in front of the round comma-shaped rudder) Fokker D.V (yes that one, possibly used in small numbers in combat) Fokker D.VI (maybe, an interesting variant but if I had to choose between the D.VI and D.V, I would go with the D.V since it has a nice spinner and interesting wing shapes/arrangement) Pfalz Dr.I (yes I know that there is an A-team one available, and I've tweaked the FM for that one in my FM update packs --- but that model is old and somewhat blocky-looking) On the Entente side, the only one that pops to mind and that I would like to see is the Morane-Saulnier Type I (with scalloped trailing edges on wings, and with the Vickers M.G. -- the one used largely by the Imperial Russ. Air Service, even more so than the earlier Type N). Anyway happy flying all (also happy holidays to fellow FE2-ers if I don't post again before the new year), Von S

@Dornil, speaking from experience in FE2 data inis only -- empty mass is empty historical weight in kg, for the aircraft. Have never bothered to check if mass fraction values in FE2 data inis add up to 1 x empty weight since most of those fraction values were left in stock form in my data ini FM tweaks. Having said that, you will notice that smaller mass fraction numbers, for components, make those components more fragile and easier to destroy. High mass fraction numbers function as bullet-proofing but I don't recommend tampering with mass fraction numbers to achieve such effects - you are better off implementing structural factor, also MaxG values, per aircraft components, if you want to induce limitations or limits (also to narrow down limits) prior to structural damage happening. (As far as I remember, numbers and data entries plugged into different aircraft components, panels, wings, etc., take priority over more general data sections such as "[AircraftData].") Too bad there isn't a one-size-fits-all data ini tweaking manual for the TW sims - but it is what it is. Also take note that the flight engine in FE2 models air density and a few other things (possibly) differently than SF2 does (for example, an F4U Corsair with a top speed of about 750 kph in SF2, dropped into FE2, will have a top speed of about 880 kph -- moral of story, data inis between FE2 and SF2 are not interchangeable -- and it is easier to modify FE2 data inis for SF2 than it is to back-port data inis from SF2 into FE2 -- requires more work to go backwards to FE2). Cheers all, Von S

Thank you Stephen for the lovely N. 21 - this one will nicely complement the N. 21 in Geezer's beta pack and I will carry over the FM modifications from that one that I did a while ago, when I find time, to your model as well. The good thing about the Ojcar FMs is that they are very tweak-friendly and it doesn't take too much time to bring the specs. up to historical peculiarities. Always nice to see fresh models coming out for FE2. @Crawford, thank you for that info. regarding 110 hp upgrades for the N.21 -- this has got me thinking about a few possibilities now -- maybe I will upgrade Geezer's N.21 to the 110 hp variant (since if I remember correctly some of his sub-variants of the N. 21 carry the Vickers - been a while since I checked but will look into it) --- and I will tweak Stephen's N.21 around a 90 hp or so variant, since it carries the Lewis. Good times ahead in FE2 where the only limit is our imagination, time constraints, and of course the limitations of TK's sim. engine. Cheers all, Von S

Unfortunately no data.ini for dummies guide available, as far as I know - but you might also find this thread and the responses there helpful, regarding yaw instability corrections, rudder tweaks, etc. As well, there is a "doc" file available on CombatAce (for SF Wings over Vietnam), about 50 pages in length, and that contains lots of info. about data inis - click here for that file. In terms of those values you've asked about, here's a snippet, with comments, from the Alb. D.II file for FE2: [AircraftData] EmptyMass=673.0 ---> value in kg, empty weight of aircraft //EmptyInertia=1409.22,2044.98,2815.56 EmptyInertia=564.0,439.6,921.1 ---> these are best not tampered with, since changing these values impacts things like acceleration/deceleration in dives, inertia when looping, etc. (reducing these numbers gives a lighter, floating FM feeling with smaller numbers more suitable for wooden aircraft, and so on; very general rule of thumb is that the inertia values, in the x,y,z string/axes of values, should be of the following sizes - x larger than y by about 10-20%, y smallest, z largest, larger than x by about 30-40% or so - such proportions were tested for WW1 aircraft in FE2 - no guarantees that such ratios work well in SF2 for jet-age stuff) ReferenceArea=24.5 ----> total area, in meters, for the aircraft, including from front to back of fuselage, and from wingtip to wingtip ReferenceSpan=8.5 ----> reference span in meters, from wingtip to wingtip ReferenceChord=1.75 ----> highest value for chord width of wings, in meters, should be used as reference if applying chord values to wing/stab sections and whatnot; the value may change to a slightly smaller number, depending where the chord value is used in what wing section, for left/right stabs, etc., but ideally should never exceed the value included for "ReferenceChord" CGPosition=0.00,0.00,0.00 -----> center of gravity position for aircraft (x,y,z string/axes), best left alone unless you are having trouble with take offs with aircraft too nose-heavy, etc. (this is a helpful value to tamper with on WW1 aircraft, to get their tails up while accelerating to take off --- otherwise best left alone) NOTE: tampering with "CGPosition" to get aircraft to take off/land more smoothly is the crude approach to that problem -- the more "professional" approach is to manipulate "CL0MachTableData" values (usually a series of four, five, or six numbers) located in the LeftStab and RightStab sections of a data.ini file --- recommended is not to touch those table data values if aircraft land/take off well --- since manipulation of those numbers alters pitch up/down capability of elevators, etc. Cheers all, Von S

If you note carefully, the following values are different in those two data inis: CLmax=0.29084 AlphaStall=17.50 AlphaMax=18.73 AlphaDepart=22.23 StallMoment=-0.002 StallDrag=0.0227 Easiest way to create a more spin-prone FM is to lower those alpha stall/max/depart values. Of further significance is to pop in a stalldrag value (Capun's data ini has one, the other data ini doesn't). Another interesting bit of info.: those stallmoment values of negative 0.002 are close to no stallmoment value at all - slightly nose-down, mushy stalls when a negative no. is placed there - a nastier, nose-up stall if a positive value is there instead. We have some nicely spin-prone aircraft in FE2 courtesy of toggling and tweaking of the entries listed above. General suggestions: default TW stallmoment value (in FE2) = -0.02 (mushy, nose down stall) never exceed value for harsh, nose-up stalls (have tested this, AI do not like when it goes above this number) = 0.02 recommended values for mushy, nose-down stalls = -0.005 to -0.015 recommended values for harsher, nose-up stalls (such as for WW1 aircraft, also "Widow Makers" (F-104s) and other jet-age pocket rockets) = 0.005 to 0.015 values closer to zero are of course gentler in either range of numbers (positive, nose-up, or negative, nose-down) For more spin-prone wings, check alphastall/max/depart values, also CLmax values, for tip/middle/root sections of wings (also doesn't hurt to check such values for the left/right stab entries too). To induce very spin-prone aircraft, avoid alpha-related values higher than about 13.00 or 14.00. For example: AlphaStall=11.00 AlphaMax=13.00 AlphaDepart=13.50 One more (obscure) tip: the "Chord" values that are included in some data inis, per wing tip/middle/root sections, while not central to spin characteristics, may be manipulated somewhat for a slightly different FM feel. Chord values are in meters, by the way. I see that the chord value used in those entries you've quoted in this thread is "1.11." If you want a narrower chord and more spin-related oddities, pull that value down to about 0.95 or so. Changes in chord of about +/- 0.2 (20 cm added or removed) do impact (in subtle ways) how things like lift, drag, also stall behavior, work. Recommended however is to leave chord values alone if not comfortable tampering with them, and to manipulate alphastall/max/depart values instead, by values of about 2.00 - until you get desired and/or historical, textbook-recorded stall results. It's possible to get good/realistic FMs in the TW series but it takes time. Avoid tweaking "CLmax," by the way, unless comfortable with that - because it can improve wing lift too much, into unhistorical values/ranges - particularly for jet-age stuff. And yes, the AI will "honor" all data ini values implemented in said files - as far as I've been able to see in FE2, there will be no cheating by the AI (except maybe when landing but that's not a major concern). Cheers to all from your friendly neighborhood WW1 aircraft FM factory , Von S

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