New Package For ETO BoB Campaign

D

Daiwilletti

Charter Member
Given the great posts recently showing the BoB campaign in ETO, I've knocked together a package which I think should improve campaign play.

http://www.mediafire.com/file/7gngezvbo13p2pz/ETO_BoB.zip/file

If anyone would like to test it, the link is here. One of the things is an amended country.xml file so that extraneous nationalities' vehicles and parked aircraft do not show up at airbases and other facilities. But there are a number of other goodies. Tally ho!
 
Grabbing it now and can't wait to check it out! Will start a fresh ETO BoB campaign for it, rather than resume my existing one with the new files. Between this and the update to CFS3-BoB, Christmas has come early!

Quick query - the readme says it's for version 2 of the campaign, not version 1. What I've got is the campaign here, on the ETO campaigns page of MrJMaint's CFS3 site, with update 1 applied - is that what's needed?
 
Daiwilletti said:
The faithful hurribird is a bit dinged up after a scrap over Dover



But landing is fairly routine

Click to expand...

I see your dinged Hurribird, and raise you a complete write-off, pilot included...(different mod I know).

Shot05-11-20-23-38-13.jpg
 
Dawn takeoff, intercept mission. Some of ETO's airbases allow for mass takeoffs. This is controlled by the runway file in the objects folder. Great fun!

 
33lima said:
Grabbing it now and can't wait to check it out! Will start a fresh ETO BoB campaign for it, rather than resume my existing one with the new files. Between this and the update to CFS3-BoB, Christmas has come early!

Quick query - the readme says it's for version 2 of the campaign, not version 1. What I've got is the campaign here, on the ETO campaigns page of MrJMaint's CFS3 site, with update 1 applied - is that what's needed?
Click to expand...

Yes, I may be wrong, I just thought that is how it is described for the Sim-Outhouse download. I hope all goes well, it tests fine on my ETO 1.5.
 
OK thanks - planning to start a test campaign later this evening, after backing up and carefully installing per the readme. I'm guessing that it's not practicable to make this into a mod that could be enabled and if needed, disabled using JSGME, as it involves more than just files being swapped in and out.
 
Another question on the readme if I may!

It says 'Keep the folder and contents of ETO_BoB in a safe place outside your ETO install'. I took a complete copy of my ETO install folder (less only the separate folders in Documents and Appdata) on a backup drive a couple of weeks back so I should have enough to avoid having to install the Expansion all over if I get anything wrong.

But..my CFS3 ETO Expansion install doesn't have a folder 'ETO_BoB'. That's the name of the zip file with this mod. But I don't have anything of that name in my ETO install folder, which is a bit worrying. Am I missing something that should be in there? Or are you just suggesting I keep a safe copy of the mod somewhere before using it? Want to be sure before I kick off installation!

PS on a different tack, I thing I'm going to try to install this as a JSGME mod as that would appear to do most of what's needed, leaving just one or two steps that would need done manually eg deleting the .bdps. Still keen to be sure I'm not missing an ETO_BoB folder.
 
PPS I think I now have this packaged as a JSGME mod. I deleted 'BOB from the names of those four files so that when enabled, they will be backed up when the mod copies them over. So that disabling the mod will restore the backups.

The only thing that this leaves is:


(i) - not understanding the ref to backing up the folder I don't have;

(ii) - not being clear how I do step 5 (checking the fighter bombers I want to fly have 'recon' as a mission their .xdp files. What's a fighter bomber? The obvious ones like the 110C-4b and (IIRC) E-7, that can carry bombs? Or do I need to look atfor example Spit and Hurri .xdp files to see if the tag fighter_bomber exists in their files? TBH I'm not sure I'd miss not being able to fly fighter bombers as I want to fly RAF in the BoB so that means interceptors (or maybe the occasional Blenheim night bomber sortie to sink invasion barges) - not fighter-bombers, a concept that didn't really exist in the RAF in 1940.

(iii) - for step 6, the mod would need the regeneraged .bdp files for each of dozen or so A/C for which the mod provides fresh .xdp files. With the .bdp files packaged in the mod alongside the .xdps, they would be enabled when the mod , no need to delete the old .bdps as they would simply be replaced (unless CFS3 has a way of detecting and objecting to that.
I can enable the mod, copy out the .bdps, run the sim to regenerate them, then copy the regenerated .bdps into a full version of the mod which would install all the required files automatically. Edit - appart from the pair in Appdata - but I'd rather have one manual step to apply (or disable) a mod.
 
Last edited:
OK first test report. This is with the mod packaged for JSGME and then enabled, then the appdata files renamed.

I'm getting a CFS3 error before the animated 'pilot lounging about on airfield' screen. It says 'Cannot load campaign 'nek_ETO.xml' Reason: unknown countryID 'USA'. Could be down to my packaging for JSGME but don't think so.

I do have a file of that name in my campaigns folder which I suspect is part of the base ETO install, and maybe needs deleted because the mod 'eliminates extraneous nationalities' (there's a thought :))

Will rename that file, try again, and report back.

EDIT - just realised I deleted the two appdata files on the old Vista HDD the Expansion is installed on, not the current Win 7 C: drive, fixing now!

Another Edit - deleting the two Appdata files didn't help, got the same error. Deleting the campaign nek_ETO.xml solved that problem. But now, CFS3 CTDs when I exit a mission (QC, Hurricane IIA against Bf110c-4b). Will try again changing one of those A/C at a time for one that was not included in the mod.

Final edit of this post - changing neither A/C to one not I the mod didn't help - CFS3 is still CTD'ing when I try to quit the mission. Will disable the mod and check if ETO is working again, but ATM there's something not right.
 
OK the good news is that the ETO expansion is working again after disabling the JSGME version of the BoB mod, copying back in the nek_ETO campaign file, and restoring my backup versions of the Appdate .xml files uisel and Unlimitedpilots.

The only strange thing I noticed is that Unlimitedpilots.xml had not been regenerated after I deleted it when installing the BoB mod. My renamed backup was there, and there was a regenerated uisel, but no regenerated Unlimitedpilots.


Provided you remember to do the step that JSGME cannot (rename the two files in Appdata - I have left out the fighter_bomber step as I don't plan to fly any) I can't think of any reason that using JSGME to install the BoB mod would of itself cause a CTD. If that's correct, that leaves either a bug in the mod, or in the way I built the JSGME version. Will double-check the latter ASAP. The error due to the presence of the nek_ETO campaign file suggests something wrong there, but not the whole story.
 
Need to Check My ETO Setup

Hi 33Lima, I've just finished my breakfast Downunder, and am now trying to digest the implicaitons of you posts. Just let me check a few things on my CFS3 computer, and I'll get back to you.

But one thing - yes the Readme is referring to the ETO_Bob folder provided as a zip file. Also, not having the new gameBoB.xml renamed as game.xml and renaming the existing one gameSTD.xml would create the nek_ETO error message.

When I refer to backup folder, IIRC when installing ETO, there is a process to backup key files, pathway is the C: drive? I was thinking that would be a good place to put the replaced files. Now off to check my install.
 
33lima said:
OK thanks - planning to start a test campaign later this evening, after backing up and carefully installing per the readme. I'm guessing that it's not practicable to make this into a mod that could be enabled and if needed, disabled using JSGME, as it involves more than just files being swapped in and out.
Click to expand...

Hi 33lima,

Actually I agree the preferred way to do things would be to automate as much as possible. But for the testing phase I just assembled the files that seemed the minimum necessary to minimise nations and keep the spawns interesting.

33lima said:
It says 'Keep the folder and contents of ETO_BoB in a safe place outside your ETO install'
Click to expand...

Yes I am talking about my folder unzipped which is called ETO_BoB
Also a lot of the changes could be compiled in a .bat file but I'm not proficient with compiling bat files - it will take me quite a while to compile one

33lima said:
not being clear how I do step 5 (checking the fighter bombers I want to fly have 'recon' as a mission their .xdp files
Click to expand...

Open up a the ETO_Hur_Mk2 aircraft's .xdp file. The first section of an aircraft xdp file is called General, for general stuff presumably! Within that is the Category="fighter_bomber". This is the pick type used for air.spawns - the spawns call for fighters, fighter_bomber, bombers, tactical_bomber or level_bomber.

Very few fighters have the Category="fighter" so I only referred to fighter_bomber. Anyway, step five is largely obsolete because I threw in those aircraft.xdps which have the mod done already.

But FYI, and in case you feel entused to add the Recon option to other aircraft, here is the deal:

Further down the xdp file, past the General section, is a section called Loadouts. This is where various things like fuel drop tanks, rockets, bombs or cannon pods can be selected for flying a mission. What I do is look for the loadout with a MissionType="Escort". This is for longer range duties and is typically associated with a drop tank loadout. I figure Recon missions are usually longer range.

Check that there is not a "Recon" already included in one of the loadouts. In the xdp I provided you for the ETO_Hurri_Mk2, you will see that I added the Recon Missiontype to the 2 x 45 gal drop tank loadout. The MissionType list for the drop tanks is quite long and there are no gaps in the list:
MissionType="Escort,Intercept,Sweep,Bomber_Intercept,Recon"

If you recall, take a look at the bottom of the bo campaign xml you plan to use, for Allied players. There is a MissionEffects and an OffensiveEffects section down the bottom of the campaign file. You will notice that these missions correspond to the missiontypes listed in the aircraft loadouts section:

<MissionEffects>
<ME MissionType="Intercept" M="3" S="3" P="3" Radius="3"/>
<ME MissionType="Sweep" M="3" S="3" P="3" Radius="3"/>
<ME MissionType="Cap" M="3" S="3" P="3" Radius="3"/>
<ME MissionType="Recon" M="3" S="2" P="2" Radius="3"/>
<ME MissionType="Escort" M="2" S="2" P="2" Radius="2"/>
<ME MissionType="AntiShip" M="2" S="3" P="2" Radius="2"/>
</MissionEffects>

Although it is not explicit, I figure that it helps if aircraft involved in the campaign have all the relevant MissionTypes listed in their Loadouts section, that correspond with the missions listed in the campaign.xml file - it just helps.

.bdps - what are you saying here? I don't understand. Easiest just to delete the .bdps from the aircraft folders for which I've provided alternative xdp files.

33lima said:
It says 'Cannot load campaign 'nek_ETO.xml'
Click to expand...

This means you have not renamed the game.xml file to gameSTD.xml, and placed the gameBoB.xml into the root of the install, and renamed it to game.xml

33lima said:
The only strange thing I noticed is that Unlimitedpilots.xml had not been regenerated
Click to expand...

Ah now this may be an issue. In my version of ETO, D:\CFS3 ETO Expansion, I have an unlimitedpilots.xml in this root pathway, as well as in the AppData pathway. In the package, I should include unlimitedpilots.xml together with the uisel.xml, in the Default folder D:\CFS3 ETO Expansion\defaults.

Just check, I suspect you don't have an unlimitedpilots.xml in your main install?
 
Hi Daiwilletti

I just checked and yes I do have unlimitedpilots.xml in my ETO 1.50 install, date modified is Oct '14 so has been there a while!

I renamed the 'Hur_...' folder in the mod 'Huri...' as the former is what the files are called but the ETO aircraft folder those files are in, has the latter, with the 'i'.

Re bdps, for the mod to work with JSGME needs the revised aircraft's folders to contain a .bdp file as well as an .xdp one. To get these, I enabled with JSGME, deleted the old.bdps, ran the sim so that fresh .bdps were generated, then took copies of the new .bdps. I then disabled the mod with JSGME so it was in a 'clean' state, then copied the new .bdps into it. I could then enable and disable the JSGME mod without having to worry about .bdps, as they are now part of the mod. As far as I can see, JSGME wasn't really designed for mods for games like CFS3 which scatter files liberally around your hard drives (F: for the installs, C: for the rest in my case) so there's still a manual step or two, but I'm more comfy with that as I'm a bit prone to destroying perfectly good installs, if left to my own devices. :)

Anyway I just checked my JSGME version for any mistakes I can find in creating it, and your tip that the game.xml version was implicated led me to the discovery that I had neglected to follow my own instructions and rename your gameBoB.xml to game.xml in the JSGME version. This meant that JSGME was copying over gameBoB.xml into the install folder and leaving the original game.xml in place.

So I'll re-test shortly and report back. Seems I'm quite capable of wrecking an install even with JSGME's help :)
 
OK I'm in business. The JSGME version of the mod is loading both CFS3 and missions with no errors, and is now exiting missions and CFS3 as it should, no CTDs.

Plan to kick OFF an RAF campaign tomorrow and probably write it up as an illustrated after action report, such is my new-found level of confidence :) Unless there is something in particular you would recommend I check out ahead of starting a campaign. Anyway thanks for letting me in on this and being patient!

Shot05-13-20-21-43-49.jpg
 
Great news :applause:! One tip - the hurri 2 has a fearsome anti_ship loadout, so although not perhaps sanctioned by the purists, taking an anti_ship mission with the Hurri is a bit of fun.

Have you noticed that when you are at the mission start screen in the campaign, and looking at available missions generated by CFS3 for a particular frontline sector, that there are three stars against the highest value sorties for the sector? Selecting a 3 star mission and completing it successfully will have more impact on the progress of the campaign. In my version of the Bob (Allied) campaign, intercept missions have the highest value for an allied pilot, however if you select another frontline sector on the campaign map, sweep or even anti_ship are sometimes the highest value (3 star) mission for that particular sector.

There are a few problems with the ground spawns in ETO 1.5 with mrjmaint's updated BoB package. I've included a few modified ground spawns in the hope that you will see more activity as you leave your airfield. The main problem that I remember is that some train spawns had a dodgy speed setting for the second waypoint. Even when there is only one problem with a spawn set, it seems to inhibit any of the spawns from appearing. The same for ship.spawns.
 
Thanks for that. Hope to start the campaign later tonight.

Not really test criteria as such, but you might (or might not!) be interested in my list of things I will be trying to answer/looking for that are probably also applicable to the base campaign, that I'm still not sure about from playing it so far in the original version.

  1. It's very desirable to enable player to choose A/C or sqn at campaign start – any way to enable this eg allocate high opening stock of prestige points? Seem to remember this was possible.
  2. Possible to set a different player flight strength, other than 8? EG 12? Useful if attacker strengths are being increased. But maybe not a good idea, as 8 is enough of a handful for a leader!
  3. Are larger than stock raids spawned? EG 18-30 A/C? (here, raids = bombers, as opposed to escorts)
  4. Are formations closer? Player's? AI's? Both?
  5. Are close escorts (or sweep cover) spawned for raids: in enough strength (=8-24 A/C) and often enough (= majority of raids ARE escorted)?
  6. Are LW jabo raids spawned; and if so, given their rarity, at a relatively low rate, compared to other raids (say 10-20%, tho higher would be ok from October)?
  7. Are (non-jabo) raids spread reasonably well between all four LW dive- and level-bomber types?
  8. Does the LW mount single aircraft recce or 'pirate raid' flights, or just raids by formations?
  9. Are raids spawned to targets in something like historical progression (shipping & ports, then also coastal airfields & RDF, then also inland airfields and industrial targets)?
  10. What are the campaign’s victory conditions eg LW wins if London occupied by 31 October, else RAF wins on 31 October? Or something less obvious?
  11. Could campaign run on beyond 31 October? Best if it was resolved on some basis on or soon after that date, if RAF is not clearly already defeated earlier.
  12. When’s the earliest an invasion of England could happen? Should not be before early September!
  13. Is a counter-invasion of France possible? Completely unhistorical, so threshold best set at a level the RAF player can never reach. Stopping a successful invasion (not just an invasion) should be enough for RAF to win. An invasion which hasn’t occupied London by the time winter weather sets in can probably be considered to have failed, hence some date during Nov-Dec is probably the latest date at which the victory conditions should be resolved and the campaign concluded, allowing a little longer than the official end date of 31 October.
  14. If the campaign can continue into Oct-Nov-Dec, will newer A/C appear - in small numbers only eg Spit II (which was around from early Sept), Hurri II (also from Sept), 109E-7 (from about Aug-Sept), 109F (from Oct)? Better they didn’t appear, than they replaced ALL the older marks at once, which should only happen when the newer marks had widely replaced them, which probably would be early 1941 in most cases.
  15. Is there any particular reason why - if the spawn and era setters are used - this mod can’t be left in place and the ETO can then be played with other campaigns eg for France/attack in west 1940 or for other eras eg SCW?


As for Hurribombers, since these appeared in action over a year after the BoB officially ended, I think I will give then a miss, although attacking targets in and off the coast of France at low level in a MkIIc with 4x20mm cannon and 2x250 or 500 lb bombs would be a lot of fun, if - as in real life - dangerous!
 
Stand Alone BoB Install

Hi 33Lima, that's a great series of questions. A whole lot of ideas spin in my head whilst skimming over the questions and possible responses. I've tried the "reply with quote" option but its not working - possibly the quote is too large.

But as I opened up this post, it occurred to me that really, the best way to fine tune everything needed for a better BoB era campaign play, a stand alone install is the best way to go. Don't get me wrong, I find ETO 1.50 is my most crucial add-on, the great things and massive improvement over stock that it offers. But to get some of the things going (like differentiation of aircraft into fighter groups, not nations) it is much harder when integrating into an already complex set of .bat files.

I've alluded to the need for a .bat file to change country.xml files to suit the different eras. This address aircraft nationalities spawning, and aircraft and vehicle nationalities appearing around facilities due to the quirk of CFS3, distributed allied and axis nationalities amongst facilities along the frontline, and with general ground spawns too (where they are facilities). The trouble is, as I've discovered in this current exercise of "hey lets modify a few files to get the ETO BoB campaigns running more smoothly", that when I modified the country.xml to a simpler range of nationalities, I needed to stop the game.xml from pointing to the NEK_ETO,xml as the default mission file. Then I needed to modify the pilotconstants.xml as it sets the nationalities of pilot nationalities available to select and fly.

So my feeling is we shouldn't try to press ETO v1.50 Era 2 to the nth degree - it is just going to be too hard to get a lot of interesting things done.

Pat Pattle's stand-alone BoB install has provided an excellent sandpit within which to work. He has far to much work on just getting the environment right, it is up to other enthusiasts like us, to make further changes. Alternative campaigns and spawns can be set up which to not muck with the sttings of the base install.

Over the years, I have made 2 or 3 "blended" installs, where I've tried to take the best of Pat's install and the ETO goodies to make a great BoB platform. The trouble is, I always end up corrupting them and have to walk away and start from scratch again.
 
You must log in or register to reply here.
Back
Top