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

Not in the Library

J

John Pirnie

Charter Member
Lets put it this way.
Within the program what file has the listing of the eighteen planes that is consider the Library?
I have searched every file that I can thing of and have found both planes in four files, but still the game tells me that they are not in the Library.



:isadizzy:Can anyone tell me why my PTO install tells me when I double click the EXE to start the game that the b24d_liberator and the b25d_mitchell tells me that they are not in the library.
They are in the lineup and they do fly.
Thanks JP:salute::salute:
 
John,

My guess is that if this is an install you added lots of planes to, it may be a random error message you get because you haver more than 100 planes. CFS 2 is fickle & sometimes throws you these messages...

Or it could be your Quick Combat index is screwed up, but you mention these planes are there & you are able to fly them. Can you select & fly them in free flight, or quick combat, or both?
 
UncleTgt said:
John,

My guess is that if this is an install you added lots of planes to, it may be a random error message you get because you haver more than 100 planes. CFS 2 is fickle & sometimes throws you these messages...

Or it could be your Quick Combat index is screwed up, but you mention these planes are there & you are able to fly them. Can you select & fly them in free flight, or quick combat, or both?
Click to expand...


Yes, I can fly in every think with no problem. You figure?
JP
 
JOHN............

..open those planes in window explorer and check the sound files. They may be aliased to planes you no longer have. As the line goes in the movie "Casablanca" "............round up all the usual suspects."
 
Fibber said:
..open those planes in window explorer and check the sound files. They may be aliased to planes you no longer have. As the line goes in the movie "Casablanca" "............round up all the usual suspects."
Click to expand...

Both planes had an aliase sound file.
I put in a sound file for both planes and still the d-25_mitchell said that it was not in the library.
The b-24_liberator was ok.
You figure?:isadizzy::isadizzy:
Thanks away
JP
 
John..........

...I am not a sound guru, but did you use the same sound file for both planes, and did the Liberator work after you put in the new sound file? Others here will know better but I think that using a four engine startup for a two engine plane maybe can cause some problems. Find a sound file for the A20 and try it, should work.
I personally made a centralized sound file and can change sound aliases very quickly. Also saves disk space.
 
John,

please excuse me if I bring up something rather silly, but the standard Microsoft file/folder names for their stock CFS2 aircrafts do not include the dash in the aircraft model name.

I mean this:

B24_Liberator or B25_Mitchell instead of: B-24_Liberator or B-25_Mitchell

this because, according to older DOS filename writing rules, special characters (- + = § ! ? % & ^ > < \ / , ; : .) and blanks could not be used when assigning a filename or naming a folder. Special characters are used in command lines and programming languages, a filename wrongly read by the operative system could have led to serious troubles.

This was a great limitation back then but, even if longer names and some special characters were allowed from the release of Windows 95 onwards, when I got CFS2 I noticed immediatedly the great care taken by MS programmers to avoid special characters and blanks in the entire program folder/file structure.

Since I noticed in the names you wrote for the aircrafts CFS2 reports as "missing", those dashes are included, and the aircrafts are obviously stock ones, I wouldn't want that those names are the culprits for your troubles since the simulator is looking for different, albeit slightly, filenames and cannot find them.

Consistency in folder names must be met also in the Quick Combat file, otherwise all type of hell can break loose with CFS2!

Cheers!
KH :ernae:
 
kelticheart said:
John,

please excuse me if I bring up something rather silly, but the standard Microsoft file/folder names for their stock CFS2 aircrafts do not include the dash in the aircraft model name.

I mean this:

B24_Liberator or B25_Mitchell instead of: B-24_Liberator or B-25_Mitchell

this because, according to older DOS filename writing rules, special characters (- + = § ! ? % & ^ > < \ / , ; : .) and blanks could not be used when assigning a filename or naming a folder. Special characters are used in command lines and programming languages, a filename wrongly read by the operative system could have led to serious troubles.

This was a great limitation back then but, even if longer names and some special characters were allowed from the release of Windows 95 onwards, when I got CFS2 I noticed immediatedly the great care taken by MS programmers to avoid special characters and blanks in the entire program folder/file structure.

Since I noticed in the names you wrote for the aircrafts CFS2 reports as "missing", those dashes are included, and the aircrafts are obviously stock ones, I wouldn't want that those names are the culprits for your troubles since the simulator is looking for different, albeit slightly, filenames and cannot find them.

Consistency in folder names must be met also in the Quick Combat file, otherwise all type of hell can break loose with CFS2!

Cheers!
KH :ernae:
Click to expand...
kelticheart, I am not sure what you mean by all this?
JP
 
JOHN........

......what Kelti is explaining to you is that in the titles you posted there are dashes between the "B" and the number. Such as B"-"25 or B"-"24. This is not right for stock planes. Look in the a/c config folder and you should see something like this;
[fltsim.0]
title=B-24D Liberator
sim=B24D_Liberator
model=
panel=
sound=
texture=
The first one is the title YOU gave the plane. The second one "sim" is what the game is looking for to recognize the plane. Make sure the folder in the game a/c folder and this "sim" match exactly.
 
John,

Backup your current mdlnames.txt file in the main CFS2 folder. Next, open the mdlnames.txt file in notepad and delete the following two lines:

"B25D_Mitchell"=North American B-25D Mitchell
"B24D_Liberator"=Consolidated B-24D Liberator

Next look in the folder named INFO and find descript.dat or just descript. Make a backup and then open it in notepad and delete the following lines:

# B25D_Mitchell
U.S. medium bomber (CFS2 object). When selected from the Aircraft list, you can add waypoints to make this plane fly from waypoint to waypoint. When selected from the Infrastructure list, this plane is just scenery and won't move, but can be damaged and destroyed. For detailed information on this aircraft, see the CFS2 Pilot's Handbook or Help.

# B24D_Liberator
U.S. heavy bomber (CFS2 object). When selected from the Aircraft list, you can add waypoints to make this plane fly from waypoint to waypoint. When selected from the Infrastructure list, this plane is just scenery and won't move, but can be damaged and destroyed. For detailed information on this aircraft, see the CFS2 Pilot's Handbook or Help.

You won't need any of this stuff unless you plan on building missions with these items as airfield infrastructure.

Finally, look at the collection of native files in the main CFS2 folder and search out these six files:

AIRWAY_INDEX
ICAO_INDEX
INDEX_FILE
LAT_INDEX
STR_INDEX
WAYPOINT_INDEX

Delete these files. The sim will rebuild your database library later on the next startup.
 
bearcat241 said:
John,

Backup your current mdlnames.txt file in the main CFS2 folder. Next, open the mdlnames.txt file in notepad and delete the following two lines:

"B25D_Mitchell"=North American B-25D Mitchell
"B24D_Liberator"=Consolidated B-24D Liberator

Next look in the folder named INFO and find descript.dat or just descript. Make a backup and then open it in notepad and delete the following lines:

# B25D_Mitchell
U.S. medium bomber (CFS2 object). When selected from the Aircraft list, you can add waypoints to make this plane fly from waypoint to waypoint. When selected from the Infrastructure list, this plane is just scenery and won't move, but can be damaged and destroyed. For detailed information on this aircraft, see the CFS2 Pilot's Handbook or Help.

# B24D_Liberator
U.S. heavy bomber (CFS2 object). When selected from the Aircraft list, you can add waypoints to make this plane fly from waypoint to waypoint. When selected from the Infrastructure list, this plane is just scenery and won't move, but can be damaged and destroyed. For detailed information on this aircraft, see the CFS2 Pilot's Handbook or Help.

You won't need any of this stuff unless you plan on building missions with these items as airfield infrastructure.

Finally, look at the collection of native files in the main CFS2 folder and search out these six files:

AIRWAY_INDEX
ICAO_INDEX
INDEX_FILE
LAT_INDEX
STR_INDEX
WAYPOINT_INDEX

Delete these files. The sim will rebuild your database library later on the next startup.
Click to expand...

Thanks, I will try that.
JP

Well, I tried all that and it did not work!
John
 
JOHN.....

...try replacing the stock plane with the B-24 Guys version of the B-24 and see what happens. Nicer plane. I just noticed that my stock B-24 wasn't appearing at all. Changed it and now it does and flies.
 
Fibber said:
...try replacing the stock plane with the B-24 Guys version of the B-24 and see what happens. Nicer plane. I just noticed that my stock B-24 wasn't appearing at all. Changed it and now it does and flies.
Click to expand...

Sorry Fibber, That did not do the trick either.
Yes I can fly both planes, yes they work just fine but, I still get the message that they are not in the library.
:salute::salute:
 
Check if the following files contain references to b24d_liberator and the b25d_mitchell (you can open the files with Notepad). The files are located in the root folder of CFS2:
cfs2.cfg
qc.mis
 
Well John, unless someone can come up with a solution, you'll just have to put this one on the gremlins of incorrect installations and do a full sim reinstall to rid yourself of the annoyance completely. This kinda stuff always comes down to something we've done wrong and/or missed in a previous installation.

Starting over is not as hard as is may sound. I've done it many times. Just rename your current sim's folder to whatever, e.g. "Combat Flight Simulator 2.0". Then run the setup disk and let it create a new Combat Flight Simulator 2 folder. When it finishes, copy anything you want to keep from the old to the new -- save all the scenery for last. Don't get in a rush to do it all as quickly as possible because that's how further mistakes are made. Just take your time and start with the add-on aircraft and ships first. When these are finished, run the sim to test for any errors. Then move on to add-on effects, objects/infrastructure and weapons and test again. If it the board is still all green, you can dive into the add-on scenery from the old install. By following these measured steps you have a better chance of identifying the sources of any issues quicker.
 
bearcat241 said:
Well John, unless someone can come up with a solution, you'll just have to put this one on the gremlins of incorrect installations and do a full sim reinstall to rid yourself of the annoyance completely. This kinda stuff always comes down to something we've done wrong and/or missed in a previous installation.

Starting over is not as hard as is may sound. I've done it many times. Just rename your current sim's folder to whatever, e.g. "Combat Flight Simulator 2.0". Then run the setup disk and let it create a new Combat Flight Simulator 2 folder. When it finishes, copy anything you want to keep from the old to the new -- save all the scenery for last. Don't get in a rush to do it all as quickly as possible because that's how further mistakes are made. Just take your time and start with the add-on aircraft and ships first. When these are finished, run the sim to test for any errors. Then move on to add-on effects, objects/infrastructure and weapons and test again. If it the board is still all green, you can dive into the add-on scenery from the old install. By following these measured steps you have a better chance of identifying the sources of any issues quicker.
Click to expand...

Yea, I think your right bearcat. that is the right thing to do.
John
 
Just a thought & if it has already been suggested, I apologize. Do the MIA aircraft have a panel folder. Sometime 'empty' folders are removed by 'clean-up' programs if they don't contain a text or other file. All you need to prevent this is a text file named 'Dummy' or whatever.

Never mind, if the panel file was missing, the aircraft would not show up @ all. I think that Sander is on the right track. Try renaming your 'quickcom' file & replacing it with an empty one.
 
You must log in or register to reply here.
Back
Top