• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Player aircraft failure in Campaign mode for BoB RAF

Archive1

Charter Member
I have installed the newer version of Battle of Britain - RAF (the full version). In Campaign mode, the first mission (Kenley Sqd #1) displays the Zero as the player aircraft, not the AH_HurricaneMK1_2blade designated and consequently the whole campaign crashes. And the AH Hurri does not appear in the drop down list theoretically available as a replacement for the Zero. The AH Hurri works in the single Mission version, and the aircraft does correctly appear and fly in QC and in Free Flight. So I presume the aircraft is not the problem. I do not understand why it is correctly available in Mission mode, but not in Campaign mode. I have also reviewed all the other aircraft required by this first mission for the BoB RAF campaign and they all seem properly structured (Sound, Panel, etc).

The similar newer campaign versions of the Battle of the Bulge work fine, and the German upgrades also work well, along with the Mosquito campaign upgrades.

What am I missing here? Must be something that I don't get. Why 'no' in campaign mode, but 'yes' in mission mode?
 
It sounds as if your player aircraft is most likely missing a sound or panel alias & the game is ignoring it. Check your hurricane folder & make sure that there isn't a problem in one or both of these files. Off hand, I would wager that one or the other is aliased to the 3-blade hurricane.
 
Wheat:
Thanks for the reply but that can't be the problem. I set the Sound to alias to the M6A2_Zero (which is in the Aircraft file solely for alias use in testing aircraft) and the panel is cleanly entered and contains some of my mods that are in other aircraft without problems. If either of those were the problem I would expect the aircraft not to show up in QC or in Free Flight - but it does, in both. The proper aircraft shows up and flies just fine when the Kenley mission is flown in the Mission section, but not when the same Kenley mission is opened in Campaign mode - I get the Zero...that's what so puzzling. I have also changed all (repeat all) the aircraft called for in the mission, but it still shows the Zero as the player aircraft in campaign mode alone.

Any other ideas? I'm stumped since I've never run into this before.

And as I mentioned - I do not get this problem with other campaigns, just with BoB - RAF (full version).
 
Wheat:
Thanks for the reply but that can't be the problem. I set the Sound to alias to the M6A2_Zero (which is in the Aircraft file solely for alias use in testing aircraft) and the panel is cleanly entered and contains some of my mods that are in other aircraft without problems. If either of those were the problem I would expect the aircraft not to show up in QC or in Free Flight - but it does, in both. The proper aircraft shows up and flies just fine when the Kenley mission is flown in the Mission section, but not when the same Kenley mission is opened in Campaign mode - I get the Zero...that's what so puzzling. I have also changed all (repeat all) the aircraft called for in the mission, but it still shows the Zero as the player aircraft in campaign mode alone.

Any other ideas? I'm stumped since I've never run into this before.

And as I mentioned - I do not get this problem with other campaigns, just with BoB - RAF (full version).

Copy the same mis file from missions to campaigns. It sounds as though the mis file in campaigns is calling for [unit wxyz] (which the zero is designated) and not [unit 1234] which the player aircraft is designated in the mis file. The mis file in the campaign folder will tell all.
 
DD73:
I have copied the mission directlly from the Campaign folder (it's the first mission the Campaign begins with) into the Mission folder. Both the Campaign and Mission call for the same unit "(AH_Hurricanemk1_2bladeCFS") as the player aircraft when I check the code.

player_aircraft=3874

[unit_type.1]
type_id=3874
unit_family=1
name=AH_Hurricanemk1_2bladeCFS

The Zero is only involved as a sound alias, but wrongly appears as the designated player aircraft when the campaign begins and if I alias the sound to a different existing aircraft...I still get the Zero. I think the Zero is called only because alphabeticaly it's the first aircraft in my Aircraft folder (A6M2_Zero). If I substitute some other aircraft for the AH_Hurri, the same thing happens...the Zero shows up as the player aircraft when the campaign begins.
I even cleared both the Campaign and Mission folders and reinstalled the missions and campaigns from scratch.

Dunno. Is a mystery, but thanks for the response.
 
Reply...

Good evening,

I've been busy today settling back in, but I should be able to complete my work tomorrow and have a look at this. Stay tuned...
 
Do you have a 'misc Data' section in the aircraft's DP file &, if so, does it have an aircraft begin service date earlier than the date stated in the campaign and \ or mission?
 
Wheat:I think you've got it!

For the aircraft: "entered_service=11/1/41"

For the mission: "date=1/6/40"

Never, never thought to look at those dates in all the modifications I've worked through. Well done.

Whew! Thought I'd done something stupid. Well, I do lots of stupid things...but...

So, do we fudge and move the aircraft into an earlier date, or what? Maybe just put in an earlier vintage Hurri?

Maybe Rami could get involve here. I certainly respect his opinion too.

-=Archive1-=
 
For What It's Worth

...So, do we fudge and move the aircraft into an earlier date, or what? Maybe just put in an earlier vintage Hurri?...

I ain't
Rami, [He's a LOT more handsome] but I've gotten into the habit of making ALL my aircraft, library objects, etc with an "entered service" date at least 10 years older than they actually existed.

Then I never have the challenge you've described.

This is especially true for buildings and infrastructure - What may work in a WWII scenario will give you fits in 1917 unless that building / water tank / whatever was built before 1910....

Hint Hint
SC
:kilroy:
 
To all: Problem solved. As a test I changed all the AH aircraft used in the RAF campaign to 'entered service=1/1/40' Worked like a charm.

And I think SC7500 is correct...don't know about the handsome bit. Knowing this would have saved a bunch of time over the years fiddling around trying to get things to work that seemingly had no explanation.

Now to check other files.

What happens if you just delete the 'entered service=1234' line? Will have to test and see. Easier than editing each if you can just take them out.

Thanks to all.

Rami: Hope the trip was grand.
 
Reply..

Archive1,

I was following this thread with great interest, because I was looking in the campaign and mission files, and had NO IDEA what the problem was. This thread just goes to show how tricky a beast CFS2 can be, because I am now aware of something that I had no idea about.
 
Rami:
Yep, the code is smarter than we are. Welcome back. Now to look at all those lines of programing in order to anticipate problems with other stuff.
Appreciate your work with all the campaigns, BTW.
 
Back
Top