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

Flying campaigns

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

....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!:wavey:

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.
 
Oh boy!!! Thanks Fibber.
Won't be much going to bed around here with all the fireworks, so probably be "proof reading". :wavey:
 
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!
 
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? :dizzy:

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.
 
Ok guys--the main CFS2 Talon sim I set up has in the main A/C folder, an A/C folder named "P-38_Lightning" as previously show above. I changed the title in the Air.cfg from P-38G-13 Lightning to P-38G_Lightning and even went into the first mission and changed the player_ name_ string from P-38G-13 Lightning to P-38G_Lightning. In the mission body,The player_aircraft=3952
Did not change the below in the mission body
[unit_type.4]
type_id=3952
unit_family=1
name=P-38G_Lightning
Still failed to initialize
I have looked at this enough over the last two days and unless I still am not following the correct directions,
I think something else is a problem. Maybe the air.file? i don't know how to check that.
I am not an alcohol drinker, but this might drive me there.:very_drunk:
I am going into another install to fly for a while or complete my USMC Aces campaign in this one.
May come back in this install next year.:biggrin-new:
Thanks for ALL the input.:applause:
Happy New Year
 
HP...

....change the a/c folder name to P-38G_Lightening. (enlargement added) All the titles must agree. It appears the folder is named "P-38_Lightening" Not in agreement with the other .air, etc.
 
Fibber
It is as you noted, just a typo on my part.:banghead: Where can I find David Copey's P-38 FGH models conversion to cfs2?
I may have a corrupted D/L file. Talon readme in his Solomons '43 campaign uses his G model.
 
Thanks Rami
I have a strange occurrence that I cannot figure out. Just to test out FF in my Talon's PTO. I installed the P-38H and the P-38G in DDC's aircraft and installed another of his --P-38J Jeanne. The P-38H and P-38J showed up in FF and flew just fine. The P-38G which I have been messing with off and on for a week still would not show up.:banghead:
 
HP........

....just looked at the original file here that Rami posted. If you have the planes installed, straight from there, unless you have the P-38 F installed the "G" plane won't show. The panel and the sound files are ALIASED to the P-38 F!!! Either change the aliases, or put in a panel and sounds in those files.
 
Reply...

Highpockets,

The P-38G model is predicated on use of his P-38F model. The G model is not aliased to the "stock" P-38 F Lightning. It's subtle, but notice the difference...

P-38F_Lightning (DCC version)

P38F_Lightning (Stock version)

The David Copley version has its own panel and sound files. Ergo if you do not include this model, then none of the other (G, H) models will work.
 
:banghead:
No wonder! :redfire:
I did not see the subtleties and the instructions to this dummy were not that clear.:dizzy:
It now works.
All you guys are SURE patient!:applause:
Thanks:wavey:
 
Rami
I had looked at the sound and panel aliases several times and "assumed" it referred to the stock P-38.. You know about the "assume" word.:p87:
 
Reply...

Highpockets,

Forgive me for this, but I deliberately sat on my hands for a couple of days to see if other members or you would have the light bulb go off. :a1310:

I guess next time, I shouldn't wait as long! :wavey:
 
Rami..........

....I couldn't find my original Copley file and it wasn't until I opened the one you referenced that I saw, and remembered, the difference. I have the planes, but I have the Panel and Sounds aliased my own way.
 
Reply....

Fibber,

Not accusing anyone, good buddy. Just trying to increase the knowledge base by trying to let others take the mantle.
 
You must log in or register to reply here.
Back
Top