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

Dreaded fail to initialize again.

highpockets

highpockets

SOH-CM-2025
QC and Free flight failure
New install with only one set of missions. Deleted .cdp and filelist.dat. No joy.
Where to next?
 
Reply...

Jim,

Check the usual suspects...aircraft and ship counts, (include skins in the count) the number of objects in your objects_dp folder, or trace it back to the last thing you installed, remove it, and see if that works.
 
36 a/c including skins, about 600 objects, about 50 ships. I am going back to reinstall again. I may have a corrupted new install.
 
CFS2 failed to initialize

highpockets said:
QC and Free flight failure
New install with only one set of missions. Deleted .cdp and filelist.dat. No joy.
Where to next?
Click to expand...

I've always found that if you OK the "Failed to initialized" and then OK the following failed to start QC/Freeflight message, then click the "Fly now" button again it will work.

Odd that you are getting this on a fresh install though.

cheers,

SW
 
Just my 2 cents, being I have to mess with my mdlnames all the time,
That is where I usually find my problem ???

Dave
 
Reply...

No Dice said:
Just my 2 cents, being I have to mess with my mdlnames all the time.

That is where I usually find my problem ???

Dave
Click to expand...

Dave,

That's precisely why I suggested "the last thing you installed." :very_drunk:
 
Hmm Ok. I didn't think the mdlnames affected the QC or FF. I will give her a try tomorrow before the Super bowl starts--maybe :untroubled:
 
Maybe try this:

Yo HP;

Open your main CFS2 folder.
Locate the single file named: ERROR.log
Open it with notepad, wordpad or MS Word

It should list any "component errors" and hopefully lead you to the source of your problem.
 
HP....

Some quick thoughts here, You say you have a new install with one set of missions.
- What theater did you install to?
-Do all your planes have right sounds or aliased to a plane/sound you do have?

I ask as I kept getting this for awhile. I went through all the added missions and discovered in my ETO install some missions calling for objects I didn't have. I downloaded those converted CFS1 objects and installed.
I also found that I had a aircraft in ETO install that was driving me batty. I won't name the plane because the author I think very highly of. Just say that it lived up to its' name and caused me a lot of grief!:redfire: I got rid of it and the QQ and FF worked. Don't know why but it did. Why the plane was good to have I didn't find it was necessary.

Also, look for and remove the ..._INDEX file and remove, the six of them. This is along with the usual suspects

Now go watch the game!:wavey:.
 
Hey guys, thanks for all your tips. I haven't had time to do more research. This was supposed to be a new install PTO only, with one set of missions to test. All the missions are fine, it is just the QC and FF. I will keep you posted.
Thanks again.:applause:
 
Highpockets,

An issue I encountered was with a ship I installed. However, a fresh install with all stock ships shouldn't create the problem. I found that having a ship DP filename that is different than the ship's folder name caused errors. It was a third party addon and renaming either the DP or folder so the names matched solved the problem. Also as a precaution I made sure the MDL file also had same name as the DP and ship folder name.

I don't recall if this caused an intialization error or not, but I also ran into problems adding a folder name into the descript.dat file (in the info folder) that had spaces in the name. I had to use the underscore instead of spaces to seperate words in the descript.dat folder names, and then corresponding to that used the underscore instead of spaces in the DP and MDL filename and folder name in the ship folder.

An error will also occur when selecting an aircraft in Mission Builder that has a title name longer than 69 characters (including spaces) in the aircraft.cfg.

So here be a few more trouble shooting tips. I hope you get the issue resolved.
 
I will continue to work on it. I don't really need the QC or FF but it is nice to have if you just want to fly for a bit. I did another fresh install, tested it and both worked. Installed the mission/campaign with attendant instructions, A/C , ships etc. Again the missions all worked just fine but got the failed it initialize with QC and FF. I will continue to seek the answer.
Thanks Oglivie. I will check your tips out.
 
You must log in or register to reply here.
Back
Top