|
Post by Pete on Sept 11, 2013 16:07:52 GMT -5
hi, i am also having problems with my new aircraft not showing up in the dispatch window, in fact there is only 7 showing out of about 20 planes...anyway i have followed all the tips shown in this section of forum, and still no joy. i have unistalled and reinstalled to no effect please help someone.
here is some of the cfg file of the aircraft;[fltsim.0]
title=MJC8Q400_BTI
sim=MJC8Q4
model=
panel=
sound=
texture=BTI
kb_checklists=
kb_reference=
atc_id_color=0xffffffffff
atc_id=YL-BAH
ui_manufacturer=Bombardier
ui_type=MJC-8 Q400
ui_variation=Air Baltic
ui_createdby=Majestic Software
description=Majestic Software Dash-8 Q400 Air Baltic
atc_heavy=0
atc_airline=Air Baltic
atc_flight_number=
[fltsim.1]
title=MJC8Q400_BER
sim=MJC8Q4
model=
panel=
sound=
texture=BER
kb_checklists=
kb_reference=
atc_id_color=0xffffffffff
atc_id=D-ABQG
ui_manufacturer=Bombardier
ui_type=MJC-8 Q400
ui_variation=Air Berlin
ui_createdby=Majestic Software
description=Majestic Software Dash-8 Q400 Air Berlin
atc_heavy=0
atc_airline=Air Berlin
atc_flight_number=
|
|
|
Post by Pete s on Sept 11, 2013 16:32:15 GMT -5
so sorry for post, i am an idiot, just noticed the new patch up, thank you so so much...fantastic every thing works fine now, thank you.
|
|
tanj
Trainee
Posts: 25
|
Post by tanj on Dec 28, 2013 10:41:16 GMT -5
Hello,
the Airbus Extended A321 and A321 Neo don't show up in the Dispatch list. Using the new 1.5.0 function it says that atc-id is blank or unset, however that is incorrect.
|
|
|
Post by Dutch Owen on Dec 28, 2013 12:07:31 GMT -5
Could you copy out for us the relevant ID portion of the aircraft.cfg for one of these airplanes please?
Thanks Dutch
|
|
tanj
Trainee
Posts: 25
|
Post by tanj on Dec 29, 2013 7:23:51 GMT -5
|
|
|
Post by Travis on Dec 29, 2013 9:02:10 GMT -5
Tanj, Try adding these four files to your \FSCaptain\Aircraft folders and then re-run your Admin. Airbus configurations.zip (2.04 KB)
|
|
tanj
Trainee
Posts: 25
|
Post by tanj on Dec 29, 2013 12:01:34 GMT -5
Hi Travis,
that's much better, thank you! Airplanes are now selectable.
|
|
|
Post by Travis on Dec 29, 2013 14:29:27 GMT -5
Tanj,
Super! We'll make sure those files are in the next release....
|
|
|
Post by tamsini on Jan 4, 2014 11:12:09 GMT -5
Is there any WORKABLE 100% fullproof way to this "Aircraft Type" nonsense? I cannot believe that after a year and deciding to give it another try, nothing has changed. This is a fundamental part of this program and it is ridiculously flawed. Tons of people have the same issue and yet bits and pieces of possible solutions exist.
What can a user do to make it work if you cannot fix it within the program.
|
|
|
Post by Travis on Jan 4, 2014 13:34:23 GMT -5
Tamsini, In brief, what's not working for you? Let us know and we'll get it fixed. This area is working very well in my opinion, but as aircraft developers come out with unique changes (the QW Avro/RJ and Aerosoft Airbus Extended being the most recent, and the RealAir Dukes before them), we have to adapt to their changes. (Checking this thread, there's only two verified problems in the past year, both fixed with updated configuration files - hardly what I'd call "ridiculously flawed."). Then, sometimes our adaptations end up breaking something that has worked for other Captains. There's no sheriff in town enforcing all developers to a standard, so it's a Wild West situation. We do the best that we can - so if you have a problem, let us know and we'll try to fix your problem. To close out, the biggest issue is some developers don't use the standard attributes and data in the aircraft.cfg file as they should - as was intended by ACES. I do not want what I just wrote here to come across as harsh. If it does, then please accept my apologies as my writing must not be up to its task.
|
|
|
Post by Travis on Jan 4, 2014 13:46:40 GMT -5
For the duke on both models they used: atc_model=Duke [snip] It's just an question of either not understanding or not caring about what the atc_model directive defines. It should be used to designate the aircraft's ICAO code. So for the piston Beech it should be: atc_model=BE60 For the Turbine Beech there's no separate icao designator, I suggest using atc_model=BE61 Hello Svilen-from-last-year! For my new-to-me Turbine Duke, I chose the ICAO value for the "Royal Turbine Duke": BT60. Because when I fly it... I feel like a King!
|
|
|
Post by ericmay on Jan 8, 2014 20:04:16 GMT -5
Hey there, under flight dispatch the only aircraft that show up are the default ones from FSX.
My other addons, such as FeelThere ER-145 show up in aircraft characteristics, but not dispatch.
FSCaptain says my ATC_ID is not defined or blank, however a look at the .cfg shows this is not the case.
There is a lot of information on this post, but I am clueless as to which actually works.
Thanks
|
|
|
Post by Travis on Jan 9, 2014 10:15:59 GMT -5
Eric, The 145 comes in two versions -LR and -XR and I checked to see that I modified my atc_model value for the -XR to be the proper type - E45X. That's my long-winded explanation to essentially say, "my system's not like yours." If you could zip and email both of us your ERJs' "aircraft.cfg" files (the ones in the \SimObjects\Airplanes\ folders) and your latest ADMIN logs in \FSCaptain\Data\Logs\ we'll have it sorted out. What I have are two files in \FSCaptain\Aircraft - a E145.cfg and a E45X.cfg... plus I have load maps for them in \FSCaptain\Aircraft\Maps
|
|
|
Post by ericmay on Jan 9, 2014 22:24:01 GMT -5
Thank you for your quick reply, I will get you the files this weekend when I am off.
|
|
|
Post by kenkosan596 on Mar 6, 2014 23:41:55 GMT -5
I am try to fly with my new Carenado BONANZA A36, but can't find in Aircraft type on Flight Dispatch. The reason is indicated as ATC_ID not defined or blank in aircraft.cfg I tried to solve to add some number after atc_id= in the aircraft.cfg, but didn't work. Please advise me to solve this issue.
The following is the its aircraft.cfg data;
//********************************************************* // CARENADO BONANZA A36 FSX // Copyright ゥ Carenado 2011 - All Rights Reserved //*********************************************************
[fltsim.0] title=BONANZA A36 WHITE sim=A36 model=2P panel= sound= texture= kb_checklists=A36BONANZA_CHECK kb_reference=A36BONANZA_REF atc_id= ui_manufacturer="Carenado" ui_type=BONANZA A36 ui_typerole="Single Engine Prop" ui_createdby="Carenado" ui_variation=White description="Bonanza A36 Carenado" atc_heavy=0 atc_airline= atc_flight_number= atc_id_color=0000000000 visual_damage=1
[fltsim.1] title=BONANZA A36 STRIPES sim=A36 model=2P panel= sound= texture=STRIPES kb_checklists=A36BONANZA_CHECK kb_reference=A36BONANZA_REF atc_id=N9874Z ui_manufacturer="Carenado" ui_type=BONANZA A36 ui_typerole="Single Engine Prop" ui_createdby="Carenado" ui_variation=Stripes description="Bonanza A36 Carenado" atc_heavy=0 atc_airline= atc_flight_number= atc_id_color=0000000000 visual_damage=1
[fltsim.2] title=BONANZA A36 DEEP GREEN sim=A36 model=1P panel= sound= texture=DEEPGREEN kb_checklists=A36BONANZA_CHECK kb_reference=A36BONANZA_REF atc_id=N4527T ui_manufacturer="Carenado" ui_type=BONANZA A36 ui_typerole="Single Engine Prop" ui_createdby="Carenado" ui_variation=Deep Green description="Bonanza A36 Carenado" atc_heavy=0 atc_airline= atc_flight_number= atc_id_color=0000000000 visual_damage=1
[fltsim.3] title=BONANZA A36 JAL sim=A36 model=2P panel= sound= texture=JAL kb_checklists=A36BONANZA_CHECK kb_reference=A36BONANZA_REF atc_id=N8295L ui_manufacturer="Carenado" ui_type=BONANZA A36 ui_typerole="Single Engine Prop" ui_createdby="Carenado" ui_variation=JAL description="Bonanza A36 Carenado" atc_heavy=0 atc_airline= atc_flight_number= atc_id_color=0000000000 visual_damage=1
|
|