Jump to content

Recommended Posts

Hi Robert..TBH i cannot nail down what the difference was,for me it just felt right, it felt like my hand fitting comfortably in a glove rather than me squeezing it in..BTW in no way im a dismissing WOFFs FM,s ,i just like what Gav,s achieved

The rudder issue that Gav mentions is a definite difference.But as in my above post JSGME at this moment is killing my FPS,so until i cure that little problem im going to fly with WOFF,s stock DVa Fm...cheers  

Share this post


Link to post
Share on other sites

JSGME hurting your fps is a new one to me.  I just move folders in and out manually for now and I don't have any trouble.

 

Thank you for the feedback!

Share this post


Link to post
Share on other sites

JSGME hurting your fps is a new one to me.  I just move folders in and out manually for now and I don't have any trouble.

 

Thank you for the feedback!

Your welcome Gav,thank you for your FM file,ive just used it to freeflight around my airfield..i felt so in control just to add,Ive noticed (at least on my system) that if i click on the x in the top corner of JSGME my Mods still load..if i click on the close button on JSGME yes they still load BUT i have a 15-18 FPS drop..i tried this 4 times to be sure and everytime it dropped my FPS.So i just click the x and everythings spot on..thank you once again Gavagaidrinks.gif.pagespeed.ce.9olfNKsCP-.gif

Share this post


Link to post
Share on other sites

Guys, I'm sorry again...

I explored the files I uploaded (with gavagai's Mod) and the file structure was not correct to be used via JSGME.

I'm afraid neither Bucksnort's (Hellshade's D.V FM) is.

There is folder missing (OBDWW1 Over Flanders Fields)...so JSGME is not installing the FMs in the right place.

Meaning I was having a placebo effect all night yesterday, trying to test, at last, gavagai's FM... :blink:

I have also updated my original post... 

 

Alb D.Va 680kg 190hp_gavagai.7z

Edited by elephant

Share this post


Link to post
Share on other sites
Meaning I was having a placebo effect all night yesterday, trying to test, at last, gavagai's FM...

Well, here's an honest man!

elephant, I have such placebos sometimes, when I want to shade parts of my skins very subtly

in Photoshop. I often brush over that part several times, thinking I'm getting there - just a bit

slowly - until I realise: the layer is not activated. Mwahahahaaa!!!

 

(OT: 'Placebo' had some nice songs - like 'Slave to the Wage'...)

Edited by Olham

Share this post


Link to post
Share on other sites

Guys, I'm sorry again...

I explored the files I uploaded (with gavagai's Mod) and the file structure was not correct to be used via JSGME.

I'm afraid neither Bucksnort's (Hellshade's D.V FM) is.

There is folder missing (OBDWW1 Over Flanders Fields)...so JSGME is not installing the FMs in the right place.

Meaning I was having a placebo effect all night yesterday, trying to test, at last, gavagai's FM...

I have also updated my original post... 

 

Hey Guys,

 

I was finally able to log back into CombatAce, but it may be temporary.  My son already has an account here and when I also created one it let me in long enough for my first post but then blocked me as they don't allow two accounts from one IP address.  So they put a fix in temporarily but I may not be able to stay. 

 

Just wanted to say quickly that the JSGME that I posted is for a JSGME executable and Mods folder installed in the "OBDWW1 Over Flanders Fields" folder where the WOFF/CFS3 executables, Ankors Shaders Mod, etc are also located.  If you've got JSGME installed at the root directory of WOFF then it won't work.  It sounds like Hellshade already has that path covered in his post, but Hellshade's won't work if your JSGME/Mods install is with the game executables. 

 

That could also be the difference between Adger's and RJW's tests.  The folder structure will depend on how you installed JSGME and the location of your MODS folder.

 

Cheers!  (this may be my last post)

 

B.

Edited by Bucksnort

Share this post


Link to post
Share on other sites

All mods should be written for the MODS folder right in the WOFF folder - not anywhere "deeper".

I have changed the ini for the shaders, which were also written for a "deeper" directory path.

I eliminated that one line which addressed the mod, and now it works fine where it should be.

Maybe you guys could just do the same?

Edited by Olham

Share this post


Link to post
Share on other sites

Hey Guys,

 

I was finally able to log back into CombatAce, but it may be temporary.  My son already has an account here and when I also created one it let me in long enough for my first post but then blocked me as they don't allow two accounts from one IP address.  So they put a fix in temporarily but I may not be able to stay. 

 

Just wanted to say quickly that the JSGME that I posted is for a JSGME executable and Mods folder installed in the "OBDWW1 Over Flanders Fields" folder where the WOFF/CFS3 executables, Ankors Shaders Mod, etc are also located.  If you've got JSGME installed at the root directory of WOFF then it won't work.  It sounds like Hellshade already has that path covered in his post, but Hellshade's won't work if your JSGME/Mods install is with the game executables. 

 

That could also be the difference between Adger's and RJW's tests.  The folder structure will depend on how you installed JSGME and the location of your MODS folder.

 

Cheers!  (this may be my last post)

 

B.

I always have my MODS folder under the "WOFF" folder and when I download mods from anyone I make sure the correct Folder structure is in place for that mod. If the mod isn't defined properly by the modder, I create it so it will work. In my case all the mods are activated fine. Just thought I would set this straight.

Share this post


Link to post
Share on other sites

Well, I get to stay!

 

Just got a note back from CombatAce and they have adjusted my account to allow my son and I to both participate.

 

I've told Gav this already, but just for the record I really like his Alb D.Va FM.  I hope he'll share more FM's with us!

  • Like 1

Share this post


Link to post
Share on other sites

Just thought id Add that Pol has mentioned That they are looking at the Alb FM,s..."No promises but we are looking into the Albatros FM to see if there are other areas we can improve." to quote Pol directly.

THATS why OBD deserve all the credit they receive IMO,they DO listen to us and any improvements that need to be made will be...Just to add from above postings GAV,s Fm must have been put in the right place by me.Because I noticed a significant difference in flight.


Nice one..Glad your Back Bucksnortt,i used it aswell and i have to admit i really like Gavs FM...Get your Other FM,s posted Gav :biggrin:

Share this post


Link to post
Share on other sites

Good to hear, Buck! I LIKE this place!

Share this post


Link to post
Share on other sites

I will try your suggestion. I know my xfm is in the right place as I validated it before trying the mod. I always look to see the files have been implemented when I activate a mod in JSGME, before using them in WOFF. I'm anal that way. I guess it's my project mgmt background (due diligence).

 

best regards

Gavagai;

 

Thanks for the suggestion of trying the slip turn. I used spot view instead of f3. I can now see the difference. when flying the stock xfm and trying a side slip with full rudder counter to ailerons the craft cannot be held in the a straight side slip approach. It want to keep turning. Your xfm on the other hand makes side slip properly possible.

 

I also tried it in a slip turn and now can see the difference in that yours will hold much longer in a tight turn before reaching stall speed.

 

I guess what I was lacking was the visual confirmation that I needed. I wasn't feeling it before hand.

 

You have achieved some nice improvements in the handling sir. As for how the DVa should really handle I don't know. I would surmise that a side slip should be possible and your xfm makes it so.  I now feel that the devs should look at this and make a judgement call if possible.

 

Best Regards;

Share this post


Link to post
Share on other sites

The tighter turn is from 2 things:

 

1. the reduced loaded weight to 914.5kg

 

2. A more efficient L/Dmax compared to the default.  The CLmax on the default Albatros is also very low, which is what made me suspicious.  The CLmax of the Goettingen 174 airfoil is publicly available data, around 1.41.  The CLmax of the WOFF Albatros D.Va is only 1.14.  I don't know if that was a typo or not, but it is similar for all of the Albatros scouts, so it seems not to have been a mistake.

 

I don't think the turn is excessively good, however.  Just yesterday I found it a chore to keep up with a Spad 7 in a flat turn, and then the AI Spad I was chasing entered a climbing turn that I could not follow.  As always, more feedback is welcome.

 

-----------------

 

When I have more time I'll post a jsgme of the FMs I have adjusted and find satisfying.

Share this post


Link to post
Share on other sites

What is a "slip turn", guys?

Share this post


Link to post
Share on other sites

What is a "slip turn", guys?

Olham;

 

think of it as rudder in opposite direction of ailerons in a turn! (left turn, left aileron, right rudder). You probably do it instinctively and just don't know the term.

Share this post


Link to post
Share on other sites

So is it safe to use your wing rudder moddifications (corrections) in other models as well (D.V early and uprated)?

Or the wing strenght is a factor to be considered? (D.V more vulnerable than D.Va)

 

I have flown a few fights and I like the result (the plane seems more flyable)... :angel:

Sometimes there are obvious mistakes like the one you described above (typo) or the wrong weights used in Albatrosse,

deriving from older versions of OFF and being perpetually repeated.

 

The tighter turn is from 2 things:

 

1. the reduced loaded weight to 914.5kg

 

2. A more efficient L/Dmax compared to the default.  The CLmax on the default Albatros is also very low, which is what made me suspicious.  The CLmax of the Goettingen 174 airfoil is publicly available data, around 1.41.  The CLmax of the WOFF Albatros D.Va is only 1.14.  I don't know if that was a typo or not, but it is similar for all of the Albatros scouts, so it seems not to have been a mistake.

 

I don't think the turn is excessively good, however.  Just yesterday I found it a chore to keep up with a Spad 7 in a flat turn, and then the AI Spad I was chasing entered a climbing turn that I could not follow.  As always, more feedback is welcome.

 

-----------------

 

When I have more time I'll post a jsgme of the FMs I have adjusted and find satisfying.

 

 

I hope you'll expand your research-fine tunning to other planes too.

Share this post


Link to post
Share on other sites

Did anyone cast an eye on the AI behaviour, when using an FM mod?

Did they still behave well, and could they still achieve anything?

Share this post


Link to post
Share on other sites

Olham,

 

The AI behavior seems OK.  No crashing during takeoff or landing.  I did see a collision during normal navigation, but that happened now and then with the default FMs, too (I am a terrible flight leader I guess).

 

In dogfights the AI does fine.  However, some of its defensive maneuvers are more limited because it can no longer use the rudder to yaw so wildly. 

Share this post


Link to post
Share on other sites

Okay, thank you, gavagai.

Next weekend I may be able to test both the D.V and D.Va mods.

Until then I will fly both aircraft as vanilla FMs, to get a feel for the default ones.

I never flew the D.Va much even in OFF - never lived that long. :grin:

Edited by Olham

Share this post


Link to post
Share on other sites

Olham,

 

The AI behavior seems OK.  No crashing during takeoff or landing.  I did see a collision during normal navigation, but that happened now and then with the default FMs, too (I am a terrible flight leader I guess).

 

In dogfights the AI does fine.  However, some of its defensive maneuvers are more limited because it can no longer use the rudder to yaw so wildly. 

 

 

 

Just wanted to add that ive done 5 campaign missions using Gav,s FM and everything's running how it should,Takeoffs and landings are fine,AI seems fine...Have you thought of approaching Pol,or Winder Gav? and seeing if you can put a JSGME version of your FM,s over at Sim hq? I cant see this being a problem as there are other mods that change the sim (Aris clouds mod,77-scouts news mod Etc) then people can choose to use or not use them.Just a thought Bud.You could add them here aswell the only reason i mentioned Sim hq is because i believe that there are people over there that dont know about Combat aces OFF\WOFF forum and so would miss out.

Edited by Adger

Share this post


Link to post
Share on other sites

Regarding FM changes, you can do a lot to the FMs and the AI will still fly fine.  The warnings against doing this seem like a bit of a red herring.

 

Now, for horse power, changing it does nothing (same is true of RPM).  Aircraft performance in WOFF seems to be a function of the max sea level airspeed, the weight, and the LDmax (lift/drag). "170hp" is just a generic designation for the Mercedes D.III power output in the Albatros D.III or D.V.  Primary sources indicate 175 PS @1450 rpm, with the max rpm in level flight at around 1500 rpm.

 

Now, regarding weight, there is a Windsock document that has the OAW Albatros D.Va coming in at over 950kg.  We also have a primary source that says 914.5kg.  So, I went with the primary source for my WOFF FM.  That same Windsock document doesn't convert correctly between metric and imperial units, fwiw.  They say 5km = 15250ft.

 

The other big difference you can feel in the FM I made is the rudder response.  No more hockey skids to the point of flying sideways through the air.  I also reduced the roll rate slightly to feel more like the Rise of Flight Albatros D.III.  Every account I have read of the Albatros describes mediocre roll performance, and with all the subjectivity that comes along with it, it seemed appropriate to make that change.

 

Incidentally, the WOFF FM leaves out the 2 degrees of lower wing dihedral in the Albatros V strutters.  I was very surprised that they missed this.

 

-------------------

 

Now, having argued myself silly at the Rise of Flight forums over the Albatros airspeed, it is great that I can finally tinker with the FM in a WW1 flight sim.  However, WOFF is not free of the same problems.  Just like Rise of Flight, the Entente rotary scouts are pretty fast.  118.5mph for the Camel, 110mph for the Nieuport 17, 116mph for the Nieuport 24, etc.  As Pat Wilson says, FMs will never be perfect, but they shouldn't be obviously wrong.  The idea is to make the relative performance of the aircraft credible.  So, one of the first things I did was to slow down the rotary scouts (including the Dr1, ahem).  For example, all of the more detailed sources have a max airspeed of about 107mph for the Nieuport 24, but there is one figure out there that says 116mph and WOFF went with that one.  That ends of skewing the whole balance in 1917 when your Albatros is slower than 116mph.

 

Just to clarify some things.

 

Adding 2 degrees to the lower wing will not achieve what you think it will. We missed it because it will make no real difference in sim.  The *.xfm txt file does part of the job - RexH's code interprets the data as required by the sim.

For example the Gyro makes little difference to inline engines as he deals with it differently.

 

Regarding breaking AI - it's not a red herring, we do not make daft statements for no reason .  The AI are trained on every FM.  RexH designed the AI and new FM changes so he should know.  AI may break at various places, including when damaged, altitude, different formations or in rare situations etc, odd manoeuvres or other strange behaviour. The fact it's OK well lucky :)

 

Just because some sources say x and 1 says y doesn't make the 1 wrong obviously but I am not going to get into a debate - also sometimes we chose to go various for all sorts of reasons, or because it makes sense to the AI or other reasons.

The Merc engine was upgraded and improved all along for sure, we do not have many variants of each craft unfortunately.

 

For every stat one way there are others another way, we think the balance is pretty good but yes you may not.

Edited by Polovski

Share this post


Link to post
Share on other sites

AHH FM,s the bane of all flight sim discussions..Nice post IMO Pol it lets us at least know about a Developers side of things..I think at least whats important to ME is the comments regarding The AI are trained on EVERY fm and That Rex Hanover designed the FM and AI so he should know.. and also the the AI May break in places (damaged,rare situations,Etc) just about nails my decision to Keep flying with Vanilla WOFF fm,s at this time..IM not going to lie I did see a difference in Gavagai,s DVa FM,and i did like it..especially the Rudder turns..But I also believe that if Yourself,Winder and Rex believe that there,s something that,s drastically wrong with ANY fm,you would en devour to Fix it..Cheers

Share this post


Link to post
Share on other sites

AHH FM,s the bane of all flight sim discussions..Nice post IMO Pol it lets us at least know about a Developers side of things..I think at least whats important to ME is the comments regarding The AI are trained on EVERY fm and That Rex Hanover designed the FM and AI so he should know.. and also the the AI May break in places (damaged,rare situations,Etc) just about nails my decision to Keep flying with Vanilla WOFF fm,s at this time..IM not going to lie I did see a difference in Gavagai,s DVa FM,and i did like it..especially the Rudder turns..But I also believe that if Yourself,Winder and Rex believe that there,s something that,s drastically wrong with ANY fm,you would en devour to Fix it..Cheers

 

Adger;

 

What  I find interesting through all of this discussion and playing with the FM's is that we all come at it with differing opinions as to "what should be", but none of us are definitive experts basing our opinions on actual flight experience with the crafts in question. Therefore our opinions are only subjective.

 

I agree with you that the Devs will ultimately make changes to the FM's if they can do so and if it is deemed warranted.

 

This discussion thread and the modification of FM's is valuable for critiquing and analysis and may focus the devs attention to looking more closely to determine if changes are warranted.

 

I am happy to have followed this thread as it has allowed me to learn a considerable amount about FM's and how they work and having Pol give a discourse on it as well is very useful in helping me understand how things are integrated in WOFF.

 

Best Regards;

 

 

Share this post


Link to post
Share on other sites

Just to clarify some things.

 

Adding 2 degrees to the lower wing will not achieve what you think it will. We missed it because it will make no real difference in sim.  The *.xfm txt file does part of the job - RexH's code interprets the data as required by the sim.

For example the Gyro makes little difference to inline engines as he deals with it differently.

 

Regarding breaking AI - it's not a red herring, we do not make daft statements for no reason .  The AI are trained on every FM.  RexH designed the AI and new FM changes so he should know.  AI may break at various places, including when damaged, altitude, different formations or in rare situations etc, odd manoeuvres or other strange behaviour. The fact it's OK well lucky :)

 

Just because some sources say x and 1 says y doesn't make the 1 wrong obviously but I am not going to get into a debate - also sometimes we chose to go various for all sorts of reasons, or because it makes sense to the AI or other reasons.

The Merc engine was upgraded and improved all along for sure, we do not have many variants of each craft unfortunately.

 

For every stat one way there are others another way, we think the balance is pretty good but yes you may not.

 

Hi Pol;

 

Thanks for the generic discourse on the whys and wherfores that affected the decision making process for your FM's. I appreciate it because it gives me a deeper understanding of what your folks had to do to get where we are with WOFF, and just how intricate and interlinked the AI logic is to the FM's. I always thought they were separate and independant.

 

Now what I am going to say is not a criticism of how things are or a request to make a change, but just an observation I have made in testing Gavagai's FM against the stock FM.

 

I noted that flying the stock FM in spot view while approaching to land, it was impossible for me to put the DVa into a side slip.  I was able to do it quite successfully with Gavagai's FM.

I recognize that I do not have any technical knowledge to validate whether the DVa could actually do a side slip, but I suspect it would have been possible. That said, I am not asking for a change to the stock FM, just making an observation to report back to the devs in case it is something they may not be aware of or could benefit from.

 

Best Regards to you all and keep up the great support. You guys are the best!

Edited by rjw

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By CaptSopwith
      Howdy Gents,

      Hope you are all doing well. I am finally getting a chance to sink my teeth into OTT and I'm enjoying immensely. As noted by Pol and Winder, the system requirements are quite a bit higher than before. I'm wondering what your target FPS is these days. I have a beefy gaming rig (specs below) and I'm finding that with the scenery and terrain detail dialed in at 3 and the visibility set to 100km, I'm consistently in the mid to low 30s. Traditionally with a new game, I set most of the settings on max (the joys of getting a new gaming rig when I turned 40 lol). After reading over the release notes for OTT, I realized that perhaps my fps philosophy has been incorrect - I keep aiming for a high FPS and with an older engine like CFS3 combined with the wizardry of OBD, I'm not sure I'm viewing these games settings with the right mindset.

      With all that rambling out of the way, I wanted to ask: What is a good average fps for your adventures in WOFF these days? Do you aim for a high fps or do you look for a smooth fps even if its lower. I'm really curious to hear about your experiences. I'd be delighted to hear from Pol or Winder as well - what targets do you aim for when you are doing your final tests before a release? Rick, I know that you are not only playing WOFF, but you're also recording - which is an insane load on a system! What fps do you look for? Thanks in advance for sharing them and any tweaks and settings that you've had some luck with.

      Cheers!

      Intel (11th Gen) i9-11900KF @3.50GHz
      RAM: 32GB
      nVidia GeForce RTX 3080 (10GBV RAM)
      WOFF installed on SSD
      Monitor: 2560x1440 at 144Hz
    • By VonS
      INSTALLING WOFF BHAH 2 IN (CLASSIC) WINESKIN ON A MAC AND/OR THEN TRANSPLANTING THE ENTIRE INSTALL TO WINDOWS 10 BOOTCAMP (info. added May 3, 2021)   Directions below should be followed, first to install WOFF BH&H 2 in WineSkin on a Mac, and then (optionally) to transplant the OBDSoftware\WOFF folder to Windows 10 in Bootcamp. This will allow for a BH&H 2 install to co-exist with previous WOFF installs in Windows, and also makes use of the same settings/keys file, to minimize installation and tweaking hassle for us Mac-heads.   The steps below assume that you already have an older version of WOFF running in WineSkin on your Mac - because such an older install in WineSkin is necessary to have for the full installation, and testing, of BH&H 2, to complete itself (otherwise the install will fail). These steps also assume that you are familiar with the installation steps, instructions, jargon, etc., located under the long WOFF-on-a-Mac post that is available under the WOFF threads on SimHQ.   (Those who do not have a previous version of WOFF installed in classic WineSkin, which is necessary for all of the steps below to be completed, are recommended instead to try either a direct install of BH&H 2 in Win10 on the Bootcamp side/partition of a Mac, or to try installing BH&H 2 into newer WINE wrappers available via the unofficial and newer WineSkin fork available at https://github.com/Gcenx/WineskinServer.)   STEP ONE: go to https://sourceforge.net/projects/wineskin/ and download the latest classic, wineskin winery (ver. 1.7 as of this writing), via the green "download" button there   STEP TWO: double-click on the program; in the menu that opens click on the plus sign to the left of "new engines available," and in the list that then opens choose WS9Wine1.7.7, download it, and then - when you're back in the main menu - choose "create new blank wrapper" (now wait about 3-4 minutes for your Mac to make the custom wrapper; once finished, the wrapper will be placed in an Applications folder that has been made inside your user folder on OS X and/or macOS)   STEP THREE: double-click on the wrapper once again and choose "install software" in the main menu; then "choose setup executable" in the next window that opens and locate your exe file for WOFF BH&H 2 that you purchased; now let the wrapper do its thing to install the game   STEP FOUR: once installed, the wrapper will go back to the main menu and you can click "quit" (it may also prompt you to locate the program before it drops to the main menu, the program in this case being the exe file of the game that was just installed - best thing at this point is just to leave this alone and close that window, if it doesn't drop to the main menu automatically)   STEP FIVE: once the wrapper has quit, don't double-click on it but "right-click" it and choose the option in the popup menu on OS X and/or macOS that says "show package contents" (this will open the wrapper's folder and should list something like a contents folder, the alias to its c drive, and an app/icon called WineSkin); double-click on the app named WineSkin and you will open the main menu window again, of the wrapper; and choose "advanced"   STEP SIX: under the advanced menu, to the right of the box called Windows EXE (that contains a file path), click on "Browse"; this will open up your finder on OS X and/or macOS, and then you can scroll to your desktop or downloads folder on your Mac; look for the latest patch for WOFF BH&H 2 that you should have downloaded separately, from the official WOFF website, and choose that updater exe installer (click "choose"); then you're back in the WineSkin advanced menu with the proper file path for the update patch's exe now listed in the box near the top of the window; now quit that WineSkin preferences window and go back to the main WineSkin app that you previously created - and then double-click on the main WineSkin app icon so that a window opens and which will allow for an installation of the latest update patch to happen (follow directions that pop up in the relevant window, to install the WOFF BH&H 2 update patch); once the process has completed, quit the main WineSkin program again, if it does not close automatically   STEP SEVEN: right-click on the main WineSkin wrapper once again, choose "show package contents," and then double-click once more on that secondary WineSkin icon/wrapper mentioned in STEP FIVE above; under its "advanced" menu, to the right of the box called Windows EXE (that contains a file path), click on "Browse"; this will open up your finder on OS X and/or macOS, and then you can scroll into the "drive_c" of the wrapper into which you installed WOFF BH&H 2 and then patched it to its latest version; in "drive_c" look for "OBDSoftware\WOFF" and scroll into there, and keep scrolling until you find "WOFF.exe," and choose that (click "choose"); then you're back in the WineSkin advanced menu with the proper file path for the game's exe now listed in the box near the top of the window; now close that secondary WineSkin wrapper window   STEP EIGHT: copy or move the now updated OBDSoftware\WOFF folder that resides in that WineSkin wrapper to your desktop; the WOFF folder is found by right-clicking on the main WineSkin wrapper and choosing "show package contents"; the package is located within the "drive_c" folder, by the way   STEP NINE: now locate the WineSkin wrapper for your earlier edition of WOFF, double-click on it and select "show package contents," and navigate to the relevant "drive_c" directory to locate the OBDSoftware\WOFF folder that corresponds with that older variant of WOFF; rename that folder to something like OBDSoftwareOld\WOFF and move it to your desktop; now copy over, to that location instead, the fresh OBDSoftware\WOFF folder that corresponds with BH&H 2, from your desktop   STEP TEN: copy and replace the OBDSoftware\WOFF\OBDWW1 Over Flanders Fields\campaigns\CampaignData\Pilots folder in your fresh BH&H 2 folder (that should be in the older WineSkin wrapper by now, as explained in the previous step) with the same folder from OBDSoftwareOld\WOFF that is now on your desktop (this is an important step; otherwise, BH&H 2 will not open in WineSkin unless this older Pilots folder transplant is done)   STEP ELEVEN: now close all unnecessary WineSkin windows and double-click the main WineSkin wrapper icon for your earlier edition of WOFF but that now contains the newer OBDSoftware\WOFF folder with the transplanted CampaignData\Pilots folder; allow BH&H 2 to open; recommended is to fly one quick combat mission or one of the other instant missions available, to allow all necessary files to populate successfully in your install; congratulations!, you now have a successful WOFF BH&H 2 install running in (classic) WineSkin; you may now quit WOFF BH&H 2   STEP TWELVE: optional at this point, if you like, is to copy the now functioning and tested WOFF folder that resides in your BH&H 2 WineSkin install (the one located at OBDSoftware\WOFF), to a Windows 10 partition on your Mac, or perhaps to another Mac (or Windows machine) where you already have an older version of WOFF installed; there will be no need to un-install that older version of WOFF that resides in Windows; simply rename that older version to something like WOFF UE or WOFF PE, in order to run BH&H 2; if you want to run the older version of WOFF again, rename the newest WOFF folder to something like WOFF BH2, and the older one simply to WOFF, and the old version then becomes functional; both installs will coexist happily, and will also use the same keys/settings located under AppData\Roaming\OBD_Games\OBDWW1 Over Flanders Fields (recommended, however, is to map extra keys for Lewis gun loading/reloading into the older WOFFKeys.xca file that you have, for full, functional use of that gun in BH&H 2)   NOTES: Don't forget to swap back your older OBDSoftware\WOFF folder into your WineSkin WOFF wrapper, on your Mac, if you will not be running BH&H 2 in WineSkin but only in Windows; or, make a copy of your functional WineSkin install instead, place the older WOFF folder into that wrapper, and enjoy running multiple versions of WOFF that way too, directly in OS X/macOS (recommended is to give the multiple WineSkin wrappers different names, to avoid confusion, if you choose such a setup); no guarantees that the instructions posted above will result in a stable install of WOFF BH&H 2 on your Mac, but there is a fine chance that careful following of the instructions will result in a good install   ----- ADDENDUM: WOFF BHAH2 BOTTLING (Brief Illustrated Tutorial; info. added May 4, 2021)
      Please find included below some tutorial pics. for how to install/extract WOFF BH&H2 into an empty WineSkin bottler that should first be optimized for WOFF BH&H2 bottling and that runs well on Mac OS X versions 10.5 to 10.12 (for macOS versions 10.13 and higher, recommended instead is to see the unofficial WineSkin port for Macs at https://github.com/Gcenx/WineskinServer). Bottler not supplied for download here; recommended is to make your own either via classic WineSkin, and then to install BH&H2 as specified in the pics. below, or to install/bottle via a newer WineSkin as per the link given immediately above.
      The "BH&H2 Bottler" in my case, on my Mac Mini, has been set to Windows 7 compatibility, with WINE Wrapper version 2.6.2, and WINE Engine WS9WINE1.7.7. No WineTricks have been installed because this wrapper ONLY installs WOFF BH&H2, and individual patches for BH&H2, into ready and transportable form, but does not serve up a functional, running BH&H2 install within the wrapper itself.
      To set up a functional, running install of BH&H2, proceed to look carefully over the final illustrated instruction set provided below, and as well do read over the more thorough installation directions located under this relevant WOFF-on-Mac post (above) or the longer one on SimHQ that also covers installation info. regarding WOFF UE/PE before focusing on BH&H2.
      NOTE: Successful transporting of a functional, running install of BH&H2 onto a Win10 partition on your Mac (should you choose not to run BH&H2 in WineSkin) - requires that you also, already have an older version of WOFF installed on the Win10 partition/drive, since that older version has created the necessary Windows registry files for WOFF, as well as other necessary folders that contain keyboard/joystick customizations for WOFF, etc.
      Happy bottling, transporting, and flying of WOFF BH&H2,
      Von S 
       
      Classic WineSkin Main Window - Use "Install Software" button to install BH&H2 and all relevant update patches

       
      Right-Click Maneuver - After BH&H2 has been installed and patched, right-click and choose "Show Package Contents," to display directories

       
      Navigating to C Drive - Double-click on the "drive_c" alias to enter the c drive main level directory

       
      Locating the "OBDSoftware" Folder - The relevant folder will be located inside the main level, c drive directory (see further explanations provided on the pic.)*

       
      * Recommended is to keep a copy somewhere on your Mac of such a bottled, patched, but non-functional WineSkin wrapper with BH&H2 installed and patched inside it - this way you may patch/update the bottled version whenever new patches come out, and then carefully follow the same procedures as explained in the pic. immediately above this note, in order to be able to fly the latest version of BH&H2 either in WineSkin wrappers or in your Win7/8.1/10 Bootcamp partitions.
    • By VonS
      Hello fellow WOFFers,
      Thought I’d open this separate thread for a future mods-compatibility list for the ver. of BH&H 2 (WOFF) that will be released soon. Becker is welcome to make use of this thread for his long mods-compatibility list that is currently hosted on the WOFF threads over on SimHQ. I will also use this thread to update regarding my FM mods., GPU Tuner Patch, etc., in the future and time-permitting.
      For convenience and simplicity, I encourage everyone who is a member/user of CombatAce to post mods-related questions for BH&H 2 WOFF under this thread, since it will be easier to find mod-compatibility info. that way. While most WOFF-related mods. are available via Sandbagger’s site for WOFF addons, this thread will hopefully prove helpful for compatibility questions, info. regarding release of new mods. not hosted on Sandbagger’s site, etc. - and ideally will become a centralized hub for mod-related topics since there are too many mod-related threads over on the SimHQ forums for WOFF and it becomes confusing/discouraging to navigate for new WOFF fliers who might wish to load up quickly on WOFF goodies and fly.
      OBD, feel free to delete this thread if you will be posting a separate stickied thread for mod-compatibility questions, etc.
      For those interested in downloading my FM tweaks packages for the Ultimate and Platinum Eds. of WOFF, as well as GPU Tuner Patches for the Platinum Ed., including for WOTR Phase One, and the small FM tweaks package for WOTR Phase One - please see the link included immediately below. Those WOFF-related packages are not compatible with the latest, BH&H 2 edition unless otherwise indicated in this thread. I am currently busy with work and other duties, so my limited modding time will be devoted only to First Eagles 2 for the foreseeable future.
      Tweaks Packages for Previous Eds. of WOFF, etc.
      EDIT: to find my previous and current mods packages for WoFF/WoTR, click on my propeller icon here on CombatAce to go to my main profile page. Once there, click on the "about me" tab to find all relevant info. and mod download link(s).
      Cheers all,
      Von S 
×

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