Sign in to follow this  
Guest wrdekler

Aeroworx B200 Black Panel Fix.

Recommended Posts

I know from a number of other posts that some of us have made an attempt to copy/install/import the Averoworx Super King Air B-200. For some this seems to have been without a hitch. For some of us, black 2D panels have been a problem. The following worked for me to solve the problem and I thought it might be of some use to someone else.Assumption:All applicable gauges are installed in either the gauge folder, or panel folders of the panels in question. This is a must!1. In each of the six panel.cfg files, disable the first two gauges of Window 0 as follows://gauge00=awx.b20!shared_2d, 0,0,1,1,bg//gauge01=awx.b20!sounds, 0,0,10,10,12. In each of the six panel.cfg files, replace the "ident=x" lines of windows 1,2,3,4, and 5 with some other shortcut. I used the "Toggles.CAB" Icons on my main panels which use to be available in the AVSim or FlightSim libraries. It is quite possible that by simply disabling these lines would serve the same purpose (// before the line), but of course you will no longer have a simicon of any kind to act as a hotspot. My edits for this were as follows.[Window01]ident=10002 //5[Window02]ident=10003 //6[Window03]ident=10004 //7[Window04]ident=10008 //8[Window05]ident=10124 //9Edited as above will negate any action by the first five semicons in the Aeroworx Sim-Icons displayed in the upper left location of the panel. The remaining semicons work normally in bringing up secondary panels. This is academic if you used third party icons as I did as they replace these five functions. All secondary panels can also be brought up either with the applicable shift + number keys, or the top toolbar views>Instrument Panel>. My assumption is that the keyboard and view functions will work if you do not use panel hotspot/semicons but I have not tried this.3. In window 10 and 11 of the Panel.cfg files, Replace the torque gauges with the FSX Baron gauges:gauge10=KingAir!torque1, 942,381,108,108gauge11=KingAir!torque2, 821,382,108,108//gauge10=awb2002!awb200_right_torque, 942,381,108,108,picifr//gauge11=awb2002!awb200_left_torque, 821,382,108,108,picifr4. In Windows 10 and 11 of the Panel.cfg files Replace the Vertical Speed Gauge with the FSX Baron Gauge:NOTE: You DO NOT need to do this in the "panel.an" or "panel.anvc" panels.gauge32=KingAir!vsi, 602,561,177,167//gauge32=awx.honeywell!VSI, 602,561,177,167,picifr5. If you use the windowed display rather than full screen, lower the Sim-Icons slightly in the upper left display of your monitor:gauge32=KingAir!vsi, 602,561,177,167The following is a copy of Window 10 and 11 of my "Panel". I think that "Panel.em", "Panel.emvc", and "Panel.vc" are the same, but you may or may not need to edit gauge numbers and/or location/size parimeters.[Window10]file=pic_vfr_tcas.bmp size_mm=1280,960position=7visible=1ident=1gauge00=awx.b20!EADI, 300,562,200,195,picvfrgauge01=awx.b20!EHSI, 299,762,200,195,picvfrgauge02=awb2001!awb200_pic_vfr_ifr_toggle, 196,429,256,117,picvfrgauge03=awb2001!awb200_pic_cp_vfr_toggle, 923,405,357,70,picvfrgauge04=awb2002!awb200_airspeed, 160,584,124,124,picvfrgauge05=awb2002!awb200_turnslip_pic, 51,679,84,84,picvfrgauge06=awb2002!awb200_rmi_pic, 155,725,137,137,picvfrgauge07=awb2002!awb200_altimeter_pic, 511,583,133,133,picvfrgauge08=awb2002!awb200_dme_pic, 507,879,134,56,picvfrgauge09=awb2002!awb200_left_itt, 689,489,87,87,picvfrgauge10=awb2002!awb200_right_itt, 787,489,87,87,picvfrgauge11=KingAir!torque1, 688,584,89,89gauge12=KingAir!torque2, 788,583,89,89//gauge11=awb2002!awb200_left_torque, 688,584,89,89,picvfr//gauge12=awb2002!awb200_right_torque, 788,583,89,89,picvfrgauge13=awb2002!awb200_left_prop_rpm, 688,679,88,88,picvfrgauge14=awb2002!awb200_right_prop_rpm, 788, 677 ,88,88,picvfrgauge15=awb2002!awb200_left_n1, 689,773,89,89,picvfrgauge16=awb2002!awb200_right_n1, 788,772,89,89,picvfrgauge17=awb2002!awb200_left_fuelflow, 688,865,90,90,picvfrgauge18=awb2002!awb200_right_fuelflow, 787,864,90,90,picvfrgauge19=awx.b20!altalert, 1094,608,147,74,picvfrgauge20=awb2002!awb200_fast_erect_vfr, 96,616,44,44,picvfrgauge21=awb2001!awb200_simicons_h, 0,20,334,28,picvfrgauge22=awb2002!awb200_MasterWarn, 332,382,37,27,picvfrgauge23=awb2002!awb200_MaterCaution, 387,376,38,27,picvfrgauge24=awb2002!awb200_top_annunciator, 895,301,263,78,picvfrgauge25=awb2002!awb200_top_annunciator_test, 1171,329,31,28,picvfrgauge26=awb2002!awb200_gyro_slave, 50,784,88,86,picvfrgauge27=awb2005!awb200_comm1, 903,652,108,116,picvfrgauge28=awb2005!awb200_nav1, 902,783,108,117,picvfrgauge29=awb2002!awb200_whiskey, 988,3,80,52,picvfrgauge30=awb2002!awb200_commch_switch_vfr, 925,536,57,70,picvfrgauge31=KingAir!vsi, 508,731,146,137//gauge31=awx.honeywell!VSI, 508,731,146,137,picvfrgauge32=awb2005!awb200_xpdr, 902,914,108,117,picvfrgauge33=awx.b20!eadi_dim, 170,891,46,51,picvfrgauge34=awx.b20!nd, 1032,693,252,177,picvfrgauge35=awb200_reg!regnum, 454,521,83,31,picvfrgauge36=awx.b20!hdgcrs_popup_click, 44,884,99,69,picvfrgauge37=awb2002!eng_toggle, 511,401,357,69,picvfrgauge38=awb2001!awb200_kln90b_popup, 1104,898,149,56,picvfrgauge39=awb2001!awb200_pi, 1024,141,2,2,picvfrgauge40=awb2001!awb200_ap_vc_toggle, 529,330,300,64,picvfrgauge41=RKG_fuelstat!FuelStatusSq_turbine, 960,100,130,100gauge42=RKG_speed!TAS_GS_S, 965,200,120,65gauge43=RwyInfo!V1, 1000,270,55,20gauge44=Extra-300!GPS Display Toggle, 10,720,20,20gauge45=cessna208!ATC-Display-Toggle, 10,740,20,20gauge46=cessna208!Map-Display-Toggle, 10,760,20,20 gauge47=cessna208!Checklist-Display-Toggle, 10,780,20,20gauge48=Toggles!Toggle02_Icon, 10,780,20,20gauge49=Toggles!Toggle03_Icon, 10,800,20,20gauge50=Toggles!Toggle04_Icon, 10,820,20,20gauge51=Toggles!Toggle05_Icon, 10,840,20,20gauge52=Toggles!Toggle06_Icon, 10,860,20,20gauge53=Toggles!Toggle07_Icon, 10,880,20,20gauge54=Toggles!Toggle08_Icon, 10,900,20,20gauge55=Toggles!ToggleSx_Icon, 10,920,20,20gauge56=Cessna208B_XML!marker_beacon_lights, 354,522,89,30gauge57=Cessna208B_XML!switch_nav_gps, 610,508,32,57[Window11]file=pic_ifr_tcas.bmp size_mm=1280,960position=7visible=0ident=2gauge00=awx.b20!EADI, 350,367,240,233,picifrgauge01=awx.b20!EHSI, 349,607,240,233,picifrgauge02=awb2002!awb200_pic_ifr_vfr_toggle, 266,250,256,108,picifrgauge03=awb2002!awb200_airspeed, 182,382,150,150,picifrgauge04=awb2002!awb200_rmi_pic, 174,552,167,167,picifrgauge05=awb2002!awb200_turnslip_pic, 51,499,98,98,picifrgauge06=awb2002!awb200_altimeter_pic, 604,380,164,164,picifrgauge07=awb2002!awb200_dme_pic, 602,739,163,68,picifrgauge08=awb2002!awb200_left_itt, 819,267,108,108,picifrgauge09=awb2002!awb200_right_itt, 939,266,108,108,picifrgauge10=KingAir!torque1, 942,381,108,108gauge11=KingAir!torque2, 821,382,108,108//gauge10=awb2002!awb200_right_torque, 942,381,108,108,picifr//gauge11=awb2002!awb200_left_torque, 821,382,108,108,picifrgauge12=awb2002!awb200_left_prop_rpm, 820,496,108,108,picifrgauge13=awb2002!awb200_right_prop_rpm, 941,495,108,108,picifrgauge14=awb2002!awb200_left_n1, 822, 610 ,108,108,picifrgauge15=awb2002!awb200_right_n1, 941,609,108,108,picifrgauge16=awb2002!awb200_left_fuelflow, 821,722,108,108,picifrgauge17=awb2002!awb200_right_fuelflow, 941,721,108,108,picifrgauge18=awb2002!awb200_left_oil_press, 820,833,108,108,picifrgauge19=awb2002!awb200_right_oil_press, 939,832,108,108,picifrgauge20=awb2003!awb200_pic_cp_ifr_toggle, 916,160,357,70,picifrgauge21=awb2002!awb200_commch_switch, 1105,337,66,73,picifrgauge22=awb2002!awb200_psync, 725,881,40,40,picifrgauge23=awb2002!awb200_psync_sw, 685,879,17,38,picifrgauge24=awb2002!awb200_fast_erect, 106,423,50,50,picifrgauge25=awb2002!awb200_MasterWarn, 389,137,48,35,picifrgauge26=awb2002!awb200_MaterCaution, 457,130,48,34,picifrgauge27=awb2002!awb200_top_annunciator, 1070,41,318,93,picifrgauge28=awb2002!awb200_gyro_slave, 49,624,106,104,picifrgauge29=awb2005!awb200_comm1, 1080,468,129,138,picifrgauge30=awb2005!awb200_nav1, 1080,625,130,141,picifrgauge31=awb2001!awb200_simicons_h, 0,20,334,28,picifrgauge32=KingAir!vsi, 602,561,177,167//gauge32=awx.honeywell!VSI, 602,561,177,167,picifrThe following is a copy of Window 10 and 11 of my "Panel.an". I think that "Panel.anvc"is the same, but you may or may not need to edit gauge numbers and/or location/size parimeters.[Window10]file=pic_vfr.bmp size_mm=1280,960position=7visible=1ident=1gauge00=awb2001!awb200_pic_vfr_ifr_toggle, 155,422,336,87,picvfrgauge01=awb2001!awb200_pic_cp_vfr_toggle, 923,405,357,70,picvfrgauge02=awx.b20!altalert, 1094,608,147,74,picvfrgauge03=awb2001!awb200_simicons_h, 0,20,334,28,picvfrgauge04=awb2002!awb200_MasterWarn, 332,382,37,27,picvfrgauge05=awb2002!awb200_MaterCaution, 387,376,38,27,picvfrgauge06=awb2002!awb200_top_annunciator, 895,301,263,78,picvfrgauge07=awb2002!awb200_top_annunciator_test, 1171,329,31,28,picvfrgauge08=awb2005!awb200_comm1, 903,652,108,116,picvfrgauge09=awb2005!awb200_nav1, 902,783,108,117,picvfrgauge10=awb2002!awb200_whiskey, 988,3,80,52,picvfrgauge11=awb2002!awb200_commch_switch_vfr, 925,536,57,70,picvfrgauge12=awb2005!awb200_xpdr, 902,914,108,117,picvfrgauge13=awb2002!eng_toggle, 511,401,357,69,picvfrgauge14=awb2008!awb200_adi, 286, 575 ,216,209,picvfrgauge15=awb2008!awb200_vsi2_pic, 518,702,127,127,picvfrgauge16=awb2002!awb200_airspeed, 147,568,129,129,picvfrgauge17=awb2008!awb200_altimeter2_pic, 518,550,125,126,picvfrgauge18=awb2008!awb200_hsi, 288,788,210,180,picvfrgauge19=awb2008!awb200_ts, 153,859,118,118,picvfrgauge20=awb2008!awb200_rmi_pic, 136,703,142,144,picvfrgauge21=awb2008!awb200_gs, 29,935,95,65,picvfrgauge22=awb2008!awb200_left_itt, 692,489,81,81,picvfrgauge23=awb2008!awb200_right_itt, 791,489,81,81,picvfrgauge24=KingAir!torque1, 692,583,81,81gauge25=KingAir!torque2, 791,583,81,81//gauge24=awb2008!awb200_left_torque, 692,583,81,81,picvfr//gauge25=awb2008!awb200_right_torque, 791,583,81,81,picvfrgauge26=awx.b20!nd, 1032,693,252,177,picvfrgauge27=awb2008!awb200_left_proprpm, 693,678,81,81,picvfrgauge28=awb2008!awb200_right_proprpm, 792,678,81,81,picvfrgauge29=awb2008!awb200_left_n1, 693,773,81,81,picvfrgauge30=awb2008!awb200_right_n1, 792,773,81,81,picvfrgauge31=awb2008!awb200_left_fuelflow, 692,866,81,81,picvfrgauge32=awb2008!awb200_right_fuelflow, 791,866,81,81,picvfrgauge33=awb2008!awb200_gpsnavbar_vfr, 67,686,60,145,picvfrgauge34=awb2008!awb200_top_annun_adi_vfr, 289,527,215,46,picvfrgauge35=awb2008!awb200_fast_erect_vfr, 32,852,46,46,picvfrgauge36=awb2008!thelrb, 84,648,12,12,picvfrgauge37=AWX.TCAS!TCAS, 507,845,144,142,picvfrgauge38=awb2001!awb200_pi, 1085,106,1,1,picvfrgauge39=awb2001!awb200_kln90b_popup, 1104,898,149,56,picvfrgauge40=awb2001!awb200_ap_vc_toggle, 535,331,300,64,picvfrgauge41=RKG_fuelstat!FuelStatusSq_turbine, 960,100,130,100gauge42=RKG_speed!TAS_GS_S, 965,200,120,65gauge43=RwyInfo!V1, 1000,270,55,20gauge44=Extra-300!GPS Display Toggle, 10,720,20,20gauge45=cessna208!ATC-Display-Toggle, 10,740,20,20gauge46=cessna208!Map-Display-Toggle, 10,760,20,20 gauge47=cessna208!Checklist-Display-Toggle, 10,780,20,20gauge48=Toggles!Toggle02_Icon, 10,780,20,20gauge49=Toggles!Toggle03_Icon, 10,800,20,20gauge50=Toggles!Toggle04_Icon, 10,820,20,20gauge51=Toggles!Toggle05_Icon, 10,840,20,20gauge52=Toggles!Toggle06_Icon, 10,860,20,20gauge53=Toggles!Toggle07_Icon, 10,880,20,20gauge54=Toggles!Toggle08_Icon, 10,900,20,20gauge55=Toggles!ToggleSx_Icon, 10,920,20,20gauge56=Cessna208B_XML!marker_beacon_lights, 415,500,90,20gauge57=Cessna208B_XML!switch_nav_gps, 645,485,30,55[Window11]file=pic_ifr.bmp size_mm=1280,960position=7visible=0ident=2gauge00=awb2002!awb200_pic_ifr_vfr_toggle, 149,200,404,102,picifrgauge01=awb2003!awb200_pic_cp_ifr_toggle, 916,160,357,70,picifrgauge02=awb2002!awb200_commch_switch, 1105,337,66,73,picifrgauge03=awb2002!awb200_psync, 725,881,40,40,picifrgauge04=awb2002!awb200_MasterWarn, 389,137,48,35,picifrgauge05=awb2002!awb200_MaterCaution, 457,130,48,34,picifrgauge06=awb2002!awb200_top_annunciator, 1070,41,318,93,picifrgauge07=awb2005!awb200_comm1, 1080,468,129,138,picifrgauge08=awb2005!awb200_nav1, 1080,625,130,141,picifrgauge09=awb2001!awb200_simicons_h, 0,0,334,28,picifrgauge10=awb2005!awb200_xpdr, 1079,783,130,138,picifrgauge11=awb2006!sp1_autoign_left_sw, 276,900,32,52,picifrgauge12=awb2006!sp1_autoign_right_sw, 322,900,32,52,picifrgauge13=awb2006!sp1_inverter_sw, 224,899,33,51,picifrgauge14=awb2006!sp1_avionics_sw, 132, 908 ,30,35,picifrgauge15=awb2006!sp1_oxmic, 70,894,41,60,picifrgauge16=awb2008!awb200_adi, 342,367,256,250,picifrgauge17=awb2008!awb200_vsi2_pic, 617,520,150,150,picifrgauge18=awb2002!awb200_airspeed, 177,362,150,150,picifrgauge19=awb2008!awb200_altimeter2_pic, 615,339,149,148,picifrgauge20=awb2008!awb200_hsi, 346,622,246,213,picifrgauge21=awb2008!awb200_ts, 182,706,141,141,picifrgauge22=awb2008!awb200_psync_swa, 660,860,52,79,picifrgauge23=awb2008!awb200_rmi_pic, 166,524,167,167,picifrgauge24=awb2008!awb200_gs, 35,799,113,79,picifrgauge25=awb2008!awb200_left_itt, 825,265,98,98,picifrgauge26=awb2008!awb200_right_itt, 945,265,98,98,picifrgauge27=KingAir!torque1, 825,379,100,100gauge28=KingAir!torque2, 945,379,100,100//gauge27=awb2008!awb200_left_torque, 825,379,100,100,picifr//gauge28=awb2008!awb200_right_torque, 945,379,100,100,picifrgauge29=awb2008!awb200_left_proprpm, 827,495,99,99,picifrgauge30=awb2008!awb200_right_proprpm, 947,495,99,99,picifrgauge31=awb2008!awb200_left_n1, 826,609,99,99,picifrgauge32=awb2008!awb200_right_n1, 945,609,99,99,picifrgauge33=awb2008!awb200_left_fuelflow, 826,723,99,99,picifrgauge34=awb2008!awb200_right_fuelflow, 946,723,99,99,picifrgauge35=awb2008!awb200_left_oil_press, 825,836,100,100,picifrgauge36=awb2008!awb200_right_oil_press, 945,836,100,100,picifrgauge37=awb2008!awb200_top_annun_adi, 341,311,256,55,picifrgauge38=awb2008!awb200_gpsnavbar, 84,507,68,167,picifrgauge39=awb2008!awb200_fast_erect, 38,698,54,54,picifrgauge40=awb2008!thelrb, 100,454,16,16,picifrgauge41=AWX.TCAS!TCAS, 603,690,172,167,picifrgauge42=awb2001!awb200_kln90b_popup, 1222,738,231,47,picifrgauge43=awb2001!awb200_kln90b_popup, 1231,828,222,76,picifrgauge44=awb2001!awb200_nd_popup, 1233,513,73,218,picifrgauge45=awb2001!awb200_ap_vc_toggle, 693,84,300,64,picifrgauge46=Extra-300!GPS Display Toggle, 5,505,25,25gauge47=cessna208!ATC-Display-Toggle, 5,530,25,25gauge48=cessna208!Map-Display-Toggle, 5,555,25,25gauge49=cessna208!Checklist-Display-Toggle, 5,580,25,25gauge50=Toggles!Toggle02_Icon, 5,605,25,25gauge51=Toggles!Toggle03_Icon, 5,630,25,25gauge52=Toggles!Toggle04_Icon, 30,505,25,25gauge53=Toggles!Toggle05_Icon, 30,530,25,25gauge54=Toggles!Toggle06_Icon, 30,555,25,25gauge55=Toggles!Toggle07_Icon, 30,580,25,25gauge56=Toggles!Toggle08_Icon, 30,605,25,25gauge57=Toggles!ToggleSx_Icon, 30,630,25,25You will note that I have a number of third party additional gauges which you may or may not have in your panels. Just ignore them, or add them accordingly if anything turns you on.I hope this is of some use to somebody.Happy Flying:RTHEdit: One thing to add:If you press Shift plus the number 1, you will still get the black screen (cycle between an outside view and the black screen). I don't know why one would want to do this in FSX as you can press the F9, F10, F11 and F12 keys and get about any view you want. However, if you will go to the top toolbar and select views>instrument panel>main panel>normal>PIC VFR View or PIC IFR View you will have your panel back without the black area.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I just noticed in step 5 of my original post, that I copied the line for the VSI in one of the panel.cfgs, not the line for the simicons. It should have read as follows:"5. If you use the windowed display rather than full screen, lower the Sim-Icons slightly in the upper left display of your monitor:gauge21=awb2001!awb200_simicons_h, 0,20,334,28,picvfr"The second perimeter was edited from "0" to "20".From the six panel selections, this selection was the "Panel" . The gauge number may be different for some of the other five panels.Respectfully:RTH

Share this post


Link to post
Share on other sites

In the PIC Fuel Panel, the fuel gauges also read zero all of the time.I replaced them with the default King Air gauges and they seem to work reasonably well.If I am interpreting correctly, the Aux/Main select switch is then negated and useless. The Gauges are indicating a composite of both sets of tanks. This was my choice.An alternate would be to edit the aircraft.cfg file (fuel). Unless I am mistaken, this would essentially be about the same thing.In any case, this gives one at least a somewhat representative gauge reading of fuel quantity.[Window03]gauge01=Kingair!Fuel_Quantity_Left, 111,79,144,129gauge02=Kingair!Fuel_Quantity_Right, 394,77,131,123//gauge01=awb2003!awb200_left_main_fuel_qty, 111,79,144,129,picfuel//gauge02=awb2003!awb200_right_main_fuel_qty, 394,77,131,123,picfuelHappy flying:RTH

Share this post


Link to post
Share on other sites

Thanks RTH. I missed flying the Aeroworx B200 since moving to Vista and FSX. Your work is much appreciated.Regards,

Share this post


Link to post
Share on other sites

Thanks for all this info rhodges!Have you also got the autopilot to work? When I use the switches in the VC next to the PIC chair I can set all the options. For example, switch on AP, FD and HDG. Nothing happens however...thanks,Wanne.

Share this post


Link to post
Share on other sites

Good Morning Wanne (or afternoon, evening, or whatever depending upon your location in the world).In answer to your question, "Have you also got the autopilot to work?", I am afraid the answer is yes and no. Works great for me, but I am not sure this will be pleasing to you.First of all, I have to confess that I seldom fly with a VC panel. As an oldtimer CFI of past years, I identify with J3 Cubs, Cessna 120's, 140's, 195's and a Luscombe or two among other such antiques. About the most sophisticated things I ever had the pleasure of flying real world was an Apache, Myers 200, VTail Bonanza or Comanche. Therefore, Eye Candy does not mean near as much to me as funcionality. To be able to "virtually" fly everything in FS gives me great pleasure, but I guess the same old mentality is there. For what it is worth, here goes:I thought I had changed the brakes and hydraulics sections of the aircraft.cfg, but this old memory was remembering the wrong bird. That was the Gulfstream V (Another One of my favorites).With (or probably without) the modifications I included in my original post, the Autopilot problem to which you refer is unique to the Panels that include the VC provisions. If you select a VC included panel, the Autopilot does not word in either the 2d mode, or VC mode. If you choose the "NO VC" liveries, the autopilot works flawlessly as near as I can tell and that was all I looked at until I got your reply. However, you did get me curious.After reading your reply, the first thing I tried was progressively disabling VC gauges in the "Panel.VC". I would have thought that this would have made it just like the "Panel", but apparently there is another difference somewhere. That having failed, I tried the following:1. I disabled the existing "panel.vc" (Renamed it).2. I then copied my working "panel" to my desktop and renamed it "Panel.vc", and moved it back into my Aeroworx Aircraft folder.3. I then copied all of the "Vcockpitxx" windows from the original (renamed) "panel.vc" into my new "panel.vc".Now, this is where the results may or may not be acceptable to you: The Autopilot now works fine in THE 2D MODE ONLY with a VC provided panel. I get no response at all in the VC Panel mode relative to Autopilot settings. If you are a VC panel puriest, my suggestion would be to open a secondary window for the Autopilot Window, then use your Virtual Cockpit, but make all Autopilot activations with the Autopilot window. If you have multiple monitors I would hope this would not be a biggy to you. Likewise for opening and closing the secondary Autopilot window on a single monitor.I did not check any farther than this as like I said, the VC isn't really my thing. There may or may not be other issues. As with the 2D Panel I noticed that the torgue gauges needed to be replaced. Probably the same thing is true of the VSI. There may be others, but if what I have done interests you at all, this should be a dandy starting point.Note that the modifications above which were required for the "panel.vc" will also be required for the "panel.anvc" and "panel.emvc" as well if you fly birds with those panels.Good Luck and Happy Flying:RTH1585368CFI

Share this post


Link to post
Share on other sites

Good evening rhodges (from the Netherlands),thank you for looking into this problem and the detailed answer!I normally prefer the VC over the 2D panels as I use TrackIR hardware. However, I wouldn't mind flying the B200 in 2D for the time being. I started using Flightsimulator (Sublogic) on my Amiga so I'm certainly accustomed to using them. :)Sadly, things aren't still working very well. When I use the 2D analogue B200's the autopilot switches (shift 7) work... but ALT or ALT select doesn't. The green letters appear in the ap window, but the plane doesn't react. Some other settings work fine, HDG for example.Well, it did work one time but after restarted the session the plane didn't react to this setting anymore... very strange.I hope that I can further look into this next saturday, but I'm afraid that I'll have to wait for the 3.0 version. regards,Wanne.

Share this post


Link to post
Share on other sites

Hello Again Wanne:I am sorry to hear that it is not working for you. I am presently flying from KLWB to KCVG with the Autopilot engaged, and with the VC Panel. So far I have seen no problem with the exception of as expected, several panel gauges are not working, but I assume they could be replaced as they were on the 2D panel.First guess, I know nothing about TrackIR, but would be suspicious that it is related to that linkup if it is associated with your autopilot. If there is a way to disable it temporarily and try without it, it might be worth a try just to see if it works.My reason for saying this is that I tried to replace the radio panel with the Bendix stack which I personally prefer, including the Autopilot Panel. The Autopilot then would not respond for me either.One other odd thing. I have also discovered that if I try to resize the autopilot on my second monitor, when I try to activate anything, I get an error message and FSX shuts down. If I leave the size alone, I can move it anywhere I want it and it responds flawlessly with no problems.I Haven't a clue as to why it is not working for you with the exception of the above suggestion. I would bet that if I could get it to work, you sure could though, but it does take patience and quite a bit of time (plus trial and error in my case). I am totally a monkey and bananna man who has to keep pressing keys until I get a bannana. I claim to be an authority on nothing.Good luck:RTH

Share this post


Link to post
Share on other sites

In the event that anyone might be interested in this scenario, I finally got the Bendix Radio Stack to work. As might be expected, the Aerowax panel Radios are linked to the EADI, EHSI, and altalert in such a way that if one is disabled, some of the others don't work. I replaced the EADI and EHSI with the FSX Kingair gauges, and the King Radio Stack including the AP panel work fine now. My final panel.cfg for the "Panel" is included below. The other panels would need to be edited in similar fashion, including window 11 of the "Panel".I realize this is probably ridiculous to some, but I like to have everything that is possible and practical on my main panel and personally prefer the Bendix stack. She flys like a dream IMHO. The only things remaining that I have not been able to get to work in FSX are the Position, Beacon, and Strobe lights. Landing lights and the tail illumination seem to work fine.For what it is worth:Happy flying:RTHWindow10 (In Brackets which this post format will not allow)file=pic_vfr_tcas.bmp size_mm=1280,960position=7visible=1ident=1gauge00=KingAir!attitude, 300,562,200,195//gauge00=awx.b20!EADI, 300,562,200,195,picvfrgauge01=KingAir!hsi, 299,762,200,195//gauge01=awx.b20!EHSI, 299,762,200,195,picvfrgauge02=awb2001!awb200_pic_vfr_ifr_toggle, 196,429,256,117,picvfrgauge03=awb2001!awb200_pic_cp_vfr_toggle, 923,405,357,70,picvfrgauge04=awb2002!awb200_airspeed, 160,584,124,124,picvfrgauge05=awb2002!awb200_turnslip_pic, 51,679,84,84,picvfrgauge06=awb2002!awb200_rmi_pic, 155,725,137,137,picvfrgauge07=awb2002!awb200_altimeter_pic, 511,583,133,133,picvfrgauge08=awb2002!awb200_dme_pic, 501,875,176,85,picvfrgauge09=awb2002!awb200_left_itt, 689,489,87,87,picvfrgauge10=awb2002!awb200_right_itt, 787,489,87,87,picvfrgauge11=KingAir!torque1, 688,584,89,89gauge12=KingAir!torque2, 788,583,89,89//gauge11=awb2002!awb200_left_torque, 688,584,89,89,picvfr//gauge12=awb2002!awb200_right_torque, 788,583,89,89,picvfrgauge13=awb2002!awb200_left_prop_rpm, 688,679,88,88,picvfrgauge14=awb2002!awb200_right_prop_rpm, 788, 677 ,88,88,picvfrgauge15=awb2002!awb200_left_n1, 689,773,89,89,picvfrgauge16=awb2002!awb200_right_n1, 788,772,89,89,picvfrgauge17=awb2002!awb200_left_fuelflow, 688,865,90,90,picvfrgauge18=awb2002!awb200_right_fuelflow, 787,864,90,90,picvfr//gauge19=awx.b20!altalert, 501,875,176,85,picvfrgauge20=awb2002!awb200_fast_erect_vfr, 96,616,44,44,picvfrgauge21=awb2001!awb200_simicons_h, 0,20,334,28,picvfrgauge22=awb2002!awb200_MasterWarn, 332,382,37,27,picvfrgauge23=awb2002!awb200_MaterCaution, 387,376,38,27,picvfrgauge24=awb2002!awb200_top_annunciator, 895,301,263,78,picvfrgauge25=awb2002!awb200_top_annunciator_test, 1171,329,31,28,picvfrgauge26=awb2002!awb200_gyro_slave, 50,784,88,86,picvfr//gauge27=awb2005!awb200_comm1, 903,652,108,116,picvfr//gauge29=awb2002!awb200_whiskey, 988,3,80,52,picvfr//30gauge30=awb2002!awb200_commch_switch_vfr, 925,536,57,70,picvfrgauge31=KingAir!vsi, 508,731,146,137//gauge31=awx.honeywell!VSI, 508,731,146,137,picvfr//gauge32=awb2005!awb200_xpdr, 902,914,108,117,picvfrgauge33=awx.b20!eadi_dim, 170,891,46,51,picvfr//gauge34=awx.b20!nd, 1032,693,252,177,picvfrgauge35=awb200_reg!regnum, 454,521,83,31,picvfrgauge36=awx.b20!hdgcrs_popup_click, 44,884,99,69,picvfrgauge37=awb2002!eng_toggle, 511,401,357,69,picvfr//gauge38=awb2001!awb200_kln90b_popup, 1104,898,149,56,picvfrgauge39=awb2001!awb200_pi, 1024,141,2,2,picvfrgauge40=awb2001!awb200_ap_vc_toggle, 529,330,300,64,picvfrgauge41=RKG_fuelstat!FuelStatusSq_turbine, 960,100,130,100gauge42=RKG_speed!TAS_GS_S, 965,200,120,65gauge43=RwyInfo!V1, 1000,270,55,20gauge44=Extra-300!GPS Display Toggle, 10,720,20,20gauge45=cessna208!ATC-Display-Toggle, 10,740,20,20gauge46=cessna208!Map-Display-Toggle, 10,760,20,20 gauge47=cessna208!Checklist-Display-Toggle, 10,780,20,20gauge48=Toggles!Toggle02_Icon, 10,780,20,20gauge49=Toggles!Toggle03_Icon, 10,800,20,20gauge50=Toggles!Toggle04_Icon, 10,820,20,20gauge51=Toggles!Toggle05_Icon, 10,840,20,20gauge52=Toggles!Toggle06_Icon, 10,860,20,20gauge53=Toggles!Toggle07_Icon, 10,880,20,20gauge54=Toggles!Toggle08_Icon, 10,900,20,20gauge55=Toggles!ToggleSx_Icon, 10,920,20,20gauge56=Cessna208B_XML!marker_beacon_lights, 354,522,89,30gauge57=Cessna208B_XML!switch_nav_gps, 610,508,32,57gauge58=Bendix_King_Radio!Bendix-King Radio Audio, 885,465,398,60gauge59=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 885,525,398,100gauge60=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 885,625,398,100gauge61=Bendix_King_Radio!Bendix-King Radio ADF, 885,725,398,100gauge62=Bendix_King_Radio!Bendix-King Radio Xpndr, 885,825,398,60gauge63=Bendix_King_Radio!Bendix-King Radio AP, 885,885,398,75//gauge63=Bendix_King_Radio!Bendix-King Radio DME, 885,885,398,75

Share this post


Link to post
Share on other sites

Hello rhodges,I've done some more testing and I found a way to have the autopilot react to the altitude setting: it only works when FSX is running in windowed mode! May I suggest that you upload the modified panels to the AVSIM library? Wanne.

Share this post


Link to post
Share on other sites

Good morning Wanne:Ummmmm???I sure will consider your suggestion, although the sections of the panel.cfg I previously included in this thread should be sufficient information if someone is willing to dig up the third party gauges. Being that you and Ken were the only persons that replied to this post, I am not sure there would be enough interest to make much difference (Thank you for your interest). I probably am making something more complex than it is, but I guess I fear that there are a few hoops to jump through in order to upload the panel (and I hate a hassle with a passion). I am not too sure how to handle the third party additions, give credit where credit is due, etc. Permission from Aeroworx might be another consideration being that the prime ingredients are payware. In some cases, I have gauges that I have had for years and just copy them as updates are applicable for new versions of FS or new planes. In most cases I probably have the original downloads on CD's or DVD's but would have to look them up in order to include them along with identifying the proper contributor.I feel reasonably safe in modifying for my own personal use and would be happy to email what I have done to anyone wanting to examine or implement in the same way. My address is rthodgestoo@verizon.net.I will give it some thought and dig into it.Respectfully:RTH

Share this post


Link to post
Share on other sites

Hello:In the event that anyone has followed this scenario and is flying the Aeroworx but has not yet gotten the lighting to work properly, I thought you might be interested in this:I finally got the strobe, beacon and Nav Lights to work on the Aeroworx KingAir. My edited portion for the light section of the aircraft.cfg is attached below. Remember that title of the section, "Lights" needs to be in brackets NOT parenthesis, but the format for forum posts does not allow the brackets.Reasonably simple except for one item. I simply replaced the lights with the MSFS Default Kingair lights where applicable. (Compare the two aircraft.cfg's) .The only problem child was the navigation light on the tail. As near as I can tell, the Aeroworx model did not have one, although I did not go back to FS9 and check. Somewhat academic as the tail flood lights were more than ample anyway, but I added it anyway. The problem I had was that for some reason it would not let me simply add the light as "Light.20 =". However, when I put it in the position of "Light.2 =" (The same position as the default KingAir aircraft.cfg location, it worked fine (After a bit of trial and error repositioning). Then of course all numbering below that had to be edited to the next highest number.Edit: One odd item that surely is no biggy. The Tail flood light switch turns the lights on in the off position, and visa versa. All other light switches work, including landing, and taxi lights which are quite bright.The only two things that don't quite play fair to my knowledge are the backcourse Autopilot provisions, and conventional starting for the bird. I tried the default Kingair section of the aircraft.cfg for the autopilot and it had no affect. Backcourse still will not engage. I don't think it is me, because I switched to a MSFS default aircraft and it worked fine.The engine starting is still a hit or miss situation near as I can tell. I tried increasing the bleed air number in the aircraft.cfg but it had no affect, although the following did happen: When you are about to give up and you turn the engine start switch off, the engines start (at least some of the time). The weird thing though, is you can't get them to quit, and stay off. Once started, if you ever turn the battery back on and move the condition lever to a feed position, they start running again whether you want them to or not. Kind of amusing really.Happy flying:(Lights) PUT LIGHTS IN BRACKETS!Light.0 = 3, 0.54, -27.34, 3.21, fx_navred ,Light.1 = 1, -5.35, 0, -0.31, fx_beacon ,Light.2 = 3, -30.00, 0.14, 12.00, fx_navwhi ,Light.3 = 3, 0.54, 27.34, 3.21, fx_navgre ,Light.4 = 2, 0.84, -27.01, 3.19, fx_strobe ,Light.5 = 2, 0.84, 27.01, 3.19, fx_strobe ,Light.6 = 1, -24.23, -0.14, 12.53, fx_beacon ,Light.7 = 4, 5.520, 1.200, 4.495, fx_awxb200_cpLight.8 = 4, 5.520, -1.200, 4.495, fx_awxb200_picLight.9 = 10, -1.60, 0, 4.49, fx_awxb200_cabfLight.10 = 10, 2.15, 0, 4.49, fx_awxb200_cabmLight.11 = 10, -4.10, 0, 4.49, fx_awxb200_cabbLight.12 = 8, 2.8, -17.95, 3.5, fx_awxb200_icelLight.13 = 8, 2.8, 17.95, 3.5, fx_awxb200_icerLight.14 = 9, -23.55, -1.0, 6.55, fx_awxb200_logoLight.15 = 9, -23.55, 1.0, 6.55, fx_awxb200_logoLight.16 = 8, 2.97, -9.8, 1.98, fx_awxb200_icesLight.17 = 8, 2.97, 9.8, 1.98, fx_awxb200_icesLight.18 = 7, 1.08, -26.81, 3.17, fx_awxb200_reclLight.19 = 7, 1.08, 26.81, 3.17, fx_awxb200_recr

Share this post


Link to post
Share on other sites

TrackIR shouldn't have any effect on whether gauges work or not. One thing that has been succesful for me when I have trouble with gauges is to remove the 2D panel completely, or at least remove the troublesome gauges from the 2D panel. I don't know what it is, but sometimes the gauges between the 2D and VC conflict with each other, and since I fly exclusively from the VC, I don't need the 2D gauges anyway.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

Share this post


Link to post
Share on other sites

The problem I have been having with this panel is that in the lower left corner and on the right side, too, I get this flashing area that is very annoying, like you can see inside the panel.Any idea on what is causing this? It's just too annoying for me to fly with it that way. Thankfully, I've got the AFG 300 to use in the meantime.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

Share this post


Link to post
Share on other sites

Good morning Thomas:This may sound like I am arguing with you, so please do not take it that way. No offence is intended. It is just a difference in our preferences and I concede that yours as well as many others may be far superior to mine.If I read the combination of this plus your previous reply correctly, (No. 12 & 13), I am afraid I may not be of much help. In your previous post you mention that at least in some cases you "remove the 2D panel completely," and "since I fly exclusively from the VC, I don't need the 2D gauges anyway." Your sig also includes: "I like using VC's:-)". From this, if I am understanding correctly the flashing is in your VC panel???? If I may ask, does this glitch show up in any other panels besides the Aeroworx Kingair? If so, it may be a hardware issue, not the panel.I am afraid my personal preference in panels is just the opposite, and I pretty nearly fly exclusively with 2d panels. In fact, in some panels I edit out the VC portion of the aircraft.cfg so that my selection of aircraft is not quite so full. I fully realize that I may have to make an adjustment in my preferences at some point in the future as VC's seem to be the rage now days, but old habits and old preferences die hard for an old man.That being said, in the Aeroworx KingAir, I have not seen the problem you describe at all (including in the VC panel). The problem I had as a number of other posts address, was a black 2d panel. As I stated in the beginning of my original post, remming gauge 00 and 01 solved that problem. You might try that to see if it makes any difference.You probably are not interested in this being that all edits I made were to the 2d panel, but if so, I would be happy to email you a copy of my final panel or panels if your account will accept the size. They do take a while even with High Speed service. The service of one party to whom I emailed them kept denying them due to an exceeded quota on that end. We might start with only the panel.cfg, and leave the rest out, that is reasonably small and simple. If the flashing was gone, possibly you could start there with any modifications you prefer, or just ignore the 2d panels. I seriously doubt that this is what you want or that it will do anything for you, but for what it is worth, my email address is rthodgestoo@verizon.netGood luck:RTH

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this