Flying campaigns

[highpockets]

I have installed all 4 of Talon's campaigns into a single, clean PTO install with the proper add-ons. I am trying campaign flying for the first time in all these years. Always flown just missions. I have flown 3 missions in the USMC Aces campaign, but none of the other campaigns show up on the campaign screen. I thought I could jump from one campaign to the other if I wanted to. All the campaign missions are loaded into the campaign file and I have run the cleanout of filelistdat and the CDP files.
Some guidance please.
Thanks

[_486_Col_Wolf]

Check to see if the campaign CMG files are loaded into the campaign folder for all 3 missing campaigns.

[highpockets]

I checked already. they are there.. ???

[highpockets]

Maybe I will recopy them into the campaign file

[_486_Col_Wolf]

Are you adding a new pilot for each campaign you want active?

[Shadow Wolf 07]

Are you using the expanded Country.cfg in your install?

[highpockets]

Col Wolf
Its does not even give me an option. The only one I had was the USMC Aces. No 44FG, no USMC'43, no USMC SBD., no P-38-38 \All of theres were in the solomons '43 D/L of talons. USMC ACEs was separate.
Shadow Wolf
Only using the standard county.cfg. Talon did not instruct otherwise.

[Rami]

Highpockets,

Something is rotten in Kingwood...but I can't figure this one out. What more have you done to try and correct this?

[highpockets]

Rami

_486_Col_wolf had it right. Dummy did not add a different pilot name for each set of campaigns
Sorry I had you all scratching your heads.

[_486_Col_Wolf]

It's always the simplest things that get overlooked. Happy Hunting!

[highpockets]

Just discovered problem with two A/C. Got to that out now.

[Shadow Wolf 07]

Check your Sound aliases.

[highpockets]

Shadow Wolf
I have.
I have added several A/C to Talon's install and they all work just fine except FGD2 SBD5_ Dauntless_ Guad 43. In free fight it does not show any selection in bomb loads but I can fly it. The FDG2 SBD5 Dauntless_ Guad does and flies. The Dauntless_Guad works in the missions in USMC aces. The Dauntless Guad_43 is called out in the USMC'43 missions and does not work.Checked the .dp files on both and they look the same. However the Copley P-38G_Lighning is not anywhere? have been here before, just need to sort it out.
I am doing some more working today. i need to learn about these issues so I don't have to keep coming back! There were JMK ships that were not showing and I know about the missing dummy texts in those panel and sound models.
At least I learned that.
Sorry for the blah balh.
Thanks for your help. I know you and others are "watching the store"

[Shadow Wolf 07]

Sounds like you've done everything I can think of. Note: on the JMK ships, open the dp and scroll down to the bottom to Misc Data and change the unit family from 7 to whatever family of ships it belongs to: ie, cruisers are a 5. The category should also conform to the type of ship. Again, for example: carriers are unit family = 7 and category 13, merchant ships are 5,19. Check your stock ships for the correct fam and cat, Usio built all his ships as carriers. That may help.

[UncleTgt]

Shadow Wolf
I have.
I have added several A/C to Talon's install and they all work just fine except FGD2 SBD5_ Dauntless_ Guad 43. In free fight it does not show any selection in bomb loads but I can fly it. The FDG2 SBD5 Dauntless_ Guad does and flies. The Dauntless_Guad works in the missions in USMC aces. The Dauntless Guad_43 is called out in the USMC'43 missions and does not work.Checked the .dp files on both and they look the same. However the Copley P-38G_Lighning is not anywhere? have been here before, just need to sort it out.
I am doing some more working today. i need to learn about these issues so I don't have to keep coming back! There were JMK ships that were not showing and I know about the missing dummy texts in those panel and sound models.
At least I learned that.
Sorry for the blah balh.
Thanks for your help. I know you and others are "watching the store"

Highpockets,

Did you give us a clue in this post? Talon says "FDG2 SBD5 Dauntless_Guad_43" (note the underscore before _43), but you wrote "they all work just fine except FGD2 SBD5_ Dauntless_ Guad 43" No underscore before 43?

Looking at Talon's Solomons 43 zip, it seems the intention was for you to fly David Copley's P38G in the P38 Campaign. Make sure DCC's P38G folder name matches the name Talon uses (P-38G_Lightning) for those missions & it should show up.

[highpockets]

Shadow Wolf & Uncle Ttg
The ships worked ok in other missions once I corrected the panel and sound files. I think the problem is ME. I have somehow not followed the proper instructions from Talon's readme. I have gone through it again earlier but I am again. His instructions are to D/L "this" and "transfer that" to" this" etc etc. Somewhere in there I think I must have missed a step. One of the D/L A/C is KM_p40f_v1 and it works just fine!
I will post my soulution when I find it.

[highpockets]

Talon's P-38G_lightning shows "A/C initialization failure on P-38G_lightning" and
"Error loading mission file".
player_aircraft_string= P-38G-13 Lightning
[fltsim.0]
title=P-38G-13 Lightning
sim=P-38G
panel=
model=
sound=
texture=
kb_checklists=
Model= P-38G
mission unit 3952= p-38g_lightning
sound and panel aliased to P-38F_lightning
I have not idea what I am missing here. I have redone this about 6 times

[Sarg Willy]

A we bit of conflict there , model = ----Plus---- Model = p38-g check the aircraft model folder and use the correct name -- delete the one you don,t have

[highpockets]

Sarge Willy
I should have qualified what I was posting. the "model=" is in the air.cfg.
The two folders inside "model"folder in the main A/C folder match to P-38g as I think they should.

[Fibber]

... on a quick glance here take a close look at what you have in the mission call.

Talon's P-38G_lightning shows "A/C initialization failure on P-38G_lightning" and
"Error loading mission file".
player_aircraft_string= P-38G-13 Lightning
[fltsim.0]
title=P-38G-13 Lightning
sim=P-38G
panel=
model=
sound=
texture=
kb_checklists=
Model= P-38G
mission unit 3952= p-38g_lightning
sound and panel aliased to P-38F_lightning

Do you see any difference there? The failure has a underscore in it, when the mission "player aircraft string" and the title have none! Also, mission and sound and panel aliasing are underscored. THIS will give the plane "failure to initialize" message. Has happened to me a lot in the past. They ALL have to read the same.
All lines have to agree or "plane no go Joe!!"
Adjust them, then have a HAPPY NEW YEAR!!!!!!

[highpockets]

Fibber
I thought the title in the air.cfg and the player_aircraft_name_ string were supposed to match and the main A/C Folder name and the mission A/C name should match.That is how they appear:

[unit_type.4]
type_id=3952
unit_family=1
name=P-38G_Lightning


"title_string"=Solomons P-38 001
"summary_string"=Today you will be flying a P-38G from Fighter2.Your mission is to protect B-17's attacking a Japanese Cruiser at Buin.There will be P-40s joining you.Your goal is 2 kills but stay with the bombers even after you reach your goal,
"objective_string"=P-38'S arrived in the Solomons in December 1942 and are used for escorting bombers,ground attack and intercept.
"intelligence_string"=The B-17s got no hits on the cruiser.
"player_aircraft_name_string"=P-38G-13 Lightning
"airfield_string"=SI HF- Fighter II 6L
I guess my old eyes are not seeing.

[Fibber]

....they are but what the game is telling you is that somewhere you have the underscored a/c installed somewhere (or not)and it has something wrong with it OR in one of the cfg's it is written with the underscore. Had that problem also and it was a PIA to find. Look through the P-38 cfg's and see if there is a mismatch with the underscore in there somewhere.
Sometimes it can be a misplace comma , period, dash, whatever that will give that message.
Happy proof reading!

ADDENDUM: look closely at plane title and what the game calls for. See any difference? NO underscore in the title but the "unit type" you posted has a underscore.

[highpockets]

Oh boy!!! Thanks Fibber.
Won't be much going to bed around here with all the fireworks, so probably be "proof reading".

[highpockets]

Fibber
My biggest problem is understanding the structure of the mission file and what could be wrong in it, if anything.. I may have to get out Cody's guide!

[Captain Kurt]

Highpockets

I know it all seems confusing, but don't get wrapped around the wheel.

The mission is calling for the P-38G_Lightning. The mission looks for the aircraft folder name, not what is inside the aircraft folder. Simply name the P-38G folder in the CFS2/AIRCRAFT folder to P-38_Lightning and the missions will load. You could put a completely different aircraft, say an Fw190, in the P-38_Lightning folder and the mission would load it. Weird, huh?

Now Free Flight is completely different. It looks for the name in the aircraft.cfg file, and not the aircraft folder name. So it would find the Fw190 you put in in the folder and not the P-38G_Lighting.

So anyway, to solve your problem just rename the P-38G folder to P-38G_Lightning and you can fly the campaign.