Fighterpilot
Members +
Hi chaps how would I go about sorting this error message? I have the zero installed in my aircraft folder.
View attachment 94556
Thanks
Richard
View attachment 94556
Thanks
Richard
-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
-
IMPORTANT DOWNLOADING INFORMATION - ALL MEMBERS PLEASE READ
Please see this thread for updates. Update Thread
SOH ADMINISTRATION
error message help
- Thread starter Fighterpilot
- Start date
Fighterpilot
Members +
Everything seems to be in order with it, yet I still get the error message.
Richard
Richard
bub
Charter Member
Richard,
Usually that's what I do when a plane doesn't show up. The only other thing I can think of would be to get a fresh copy and try that. Something in the one you have may not be right. Also, I don't ever remember getting that error message. This one may be above my meager skills.
Sorry I couldn't help.
Bub
Usually that's what I do when a plane doesn't show up. The only other thing I can think of would be to get a fresh copy and try that. Something in the one you have may not be right. Also, I don't ever remember getting that error message. This one may be above my meager skills.
Sorry I couldn't help.
Bub
yep , Bubs right, that's a good answer nuthin meager bout your skills, plus just d/l http://members.jcom.home.ne.jp/hago/h2/mz-a6m2b.zip ..... loads up just fine, no errors, maybe redownload and try again.
The other options IF you have good sound.cfg and panel.cfg in respective folders is to make sure you have it listed in your mdlnames.txt, in your descript.dat and in your quickcom/qc_plane.qcb
I do not alias any of my sound or panels in any of my aircraft because of this.
CFS2 can be quirky on some of these things.
Once you check all of these, then go to your main CFS2 folder and search for *.cdp. When the list populates, highlight and delete them ALL.
Hit the back button and search for filelist.dat. When the list populates, highlight and delete them ALL.
Hit the back button and search for index. When the list populates, highlight and delete them ALL.
Start CFS2, let it rebuild the indices and see if you now have the Akemi Zero.
Also, make sure that you do not have over 80-100 (varies) aircraft in your aircraft folder, including all the multiple skins as aircraft. CFS2 sees each skin as a separate plane.
If you do have that many, get the over plane limit DLL and put it in your MODULES folder. I think SdC is who created it.
I do not alias any of my sound or panels in any of my aircraft because of this.
CFS2 can be quirky on some of these things.
Once you check all of these, then go to your main CFS2 folder and search for *.cdp. When the list populates, highlight and delete them ALL.
Hit the back button and search for filelist.dat. When the list populates, highlight and delete them ALL.
Hit the back button and search for index. When the list populates, highlight and delete them ALL.
Start CFS2, let it rebuild the indices and see if you now have the Akemi Zero.
Also, make sure that you do not have over 80-100 (varies) aircraft in your aircraft folder, including all the multiple skins as aircraft. CFS2 sees each skin as a separate plane.
If you do have that many, get the over plane limit DLL and put it in your MODULES folder. I think SdC is who created it.
Fighterpilot
Members +
Well I seem to have sorted the problem out. I had various repaints of it but since removing them it seems to be working fine again.
Richard
Richard
kelticheart
Charter Member
Strange error message....
... if only removing repaints resolved it. Chances are that one of those repaints had one or more corrupted files.
Hi Richard, the other possibility is that your aircraft.cfg pointed at the wrong repaint folder name. This in case you had more than one skin installed in the same aircraft folder with an addition to the folder name to identify it.
I mean this, for example:
\model
\panel
\sound
\texture
\texture.1
\texture.2
or
\texture.Sakai
\texture.Iwamoto
etc.
What puzzles me is the type of error message, because in both of the above cases the aircraft simply should have not showed up in Free Flight selection window. In the past, my CFS2 spat out such message only when the aircraft *.mdl file was corrupt.
As Devildog73 rightly pointed out, CFS2 can really be quirky, sometimes.
Cheers!
KH :ernae:
... if only removing repaints resolved it. Chances are that one of those repaints had one or more corrupted files.
Hi Richard, the other possibility is that your aircraft.cfg pointed at the wrong repaint folder name. This in case you had more than one skin installed in the same aircraft folder with an addition to the folder name to identify it.
I mean this, for example:
\model
\panel
\sound
\texture
\texture.1
\texture.2
or
\texture.Sakai
\texture.Iwamoto
etc.
What puzzles me is the type of error message, because in both of the above cases the aircraft simply should have not showed up in Free Flight selection window. In the past, my CFS2 spat out such message only when the aircraft *.mdl file was corrupt.
As Devildog73 rightly pointed out, CFS2 can really be quirky, sometimes.
Cheers!
KH :ernae:
DD...
....there are some batch files to do those cleanouts in a simpler mode. Lets see if this finally attaches here. If not the name is "cleanout.rar" I do not know who did it as there is no name in the "read-me" but it does work and does it all with a click of the mouse. Just wish there was one for the "Index" files.
....there are some batch files to do those cleanouts in a simpler mode. Lets see if this finally attaches here. If not the name is "cleanout.rar" I do not know who did it as there is no name in the "read-me" but it does work and does it all with a click of the mouse. Just wish there was one for the "Index" files.