|
Post by tiger1972 on Aug 31, 2010 7:16:10 GMT -5
Hello...I just purchased as demo worked fine for me. I am using the new fix pack 1.1.4. I have read the manual but I am having a few problems.
1. I have setup several aircraft configurations for various planes using (example filename B752_N752DL.cfg for my posky 757-200). In my aircraft.cfg my atc id = N752DL and in the [General] Section my atc model = B752. In the FCOM inside FS9 plane is showing correctly as B752 N752DL but when you click on the characteristics button it shows it as volume class medium (characteristic cfg is listed as large) and none of the other info listed is correct. Am I naming everything right so that the FCOM picks the correct .cfg configuration file?
I am having this problem with all planes that I have made config files for.
2. In the Admin dispatch, none of the aircraft configurations that I created show up in the drop down list. The only ones that show up are the default ones installed by FSCaptain.
3. I am also having the problem (which just started recently) when creating a new aircraft config and placing the new name in the box, it doesn't take and tries to save everything as new airplane...If I copy and rename an existing .cfg file I can then edit it and everything sticks.
|
|
|
Post by FS1TR on Aug 31, 2010 17:14:59 GMT -5
The name of the FSCaptain cfg file and the Type inside that file must be the same as the atc_model in the FS aircraft.cfg file. Therefore, if the atc-model = B752, the FSCapttain cfg file must be B752.cfg and the Type must be B752.
|
|
|
Post by tvieno on Aug 31, 2010 17:38:43 GMT -5
With #1, fs1tr is correct. What ever is in the atc_model= field has to be the name of the cfg file. Best bet is to delete your b752_N752DL file or any B75* file and let the program create a generic one with the proper name. Then afterwards, go in and change whatever info that needs to be changed.
I think, with #2, you have to have the FCOM gauge installed in the airplane for it to be in the pull-down menu.
I have noticed the same thing with #3. I just let the program create the airplane config and I manually enter the info that I want changed. Seems to be the only way with this program.
|
|
|
Post by tiger1972 on Sept 1, 2010 13:47:33 GMT -5
Still can't get the FCOM to use the right load map to load the plane I'm using and the characteristics are all wrong in FCOM....Why when importing a load map of a plane does it omit Station0. I just had this scenario happen
Plane has 6 load stations (Station0, Station1, Station2, Station3, Station4, Station5). Administrator Load Map imports only 5 of those 6 (omitting Station0). I changed this in the administrator to have 6 stations with Station0 (from aircraft.cfg) as Station1 (In FSCaptain administrator. Fire up the plane and it gives me an error saying doesn't match load map. What gives?
Also another issue I'm having is in the FCOM changing the ETE constraint does nothing. I set it to 2 hours and all the flights it is giving me is 3 hours, 4 hours, etc....ETE constraint does not appear to work.
|
|
|
Post by Dutch Owen on Sept 10, 2010 10:40:52 GMT -5
I'm not sure what your problem is with the load map. Any further info you could give might help.
With the ETE constraint -- that does not apply to scheduled flights, only to charter flights. Is this the problem? If you have a constraint of 2 hours you should never see a *charter* flight longer than that.
Dutch
|
|