A few great edits have been posted for the Bonanza. Because it can be quite hard to find all this information again in the future, when you might need to reinstall the Bonanza and edit various things again, I thought it would be a nice idea to put them all in one topic for future reference. (Hopefully the upcoming (?) Sp3 patch will make this topic redundant... :( ) Beware, there is NOTHING here that I figured out myself, so that's why I added the name of the one who posted it originally!How to edit a Bonanza xmlSo far these are all xml-edits. So let me first explain how to get that done.1. Go to the folder called Gauges in your FSX folder.2. Create a folder called BonF333. In the Gauges folder there is a file called BonF33.CAB: doubleclick on it and it will open: drag all files from that CAB into the BonF33 you created in step 2.4. If you want to edit a specific xml file, first make a backup of it (for when anything goes wrong) and then rightclick on the original and choose Edit. It should open in Notepad.5. Edit whatever you want to edit. Save the file after editing and that's it. You don't have to make a CAB again of the BonF33 folder because FSX will first look at a folder named BonF33 and only if it can't find it, it will look for the BonF33.CABEDIT 1File to edit: RMI.xml (replace everything in it with the text below)Posted by: Benoit aka bmdExplanation: With this edit the RMI works like the Cessna 206 RMI. But contrary to the Cessna RMI, where there is only one ADF1, in this RMI we have both ADF1 and ADF2. The left selection button switches ADF1 / VOR1 and the right selection button switches ADF2/VOR2.If either NAV1 or NAV2 or both has been selected, the RMI HDG flag appears.=====Start copy below this line=====<Gauge Name="RMI" Version="1.1"><Image Name="RMI_Background.bmp" /><Element><Position X="0" Y="0" /><MaskImage Name="RMI_Card_Mask.bmp"><Axis X="238" Y="218" /></MaskImage><Image Name="RMI_Card.bmp"><Axis X="238" Y="218" /></Image><Rotate><Value>(A:Plane heading degrees gyro,radians) /-/</Value><Failures><SYSTEM_ELECTRICAL_PANELS Action="Freeze" /><GAUGE_GYRO_HEADING Action="Freeze" /></Failures></Rotate></Element><Element><Visible>(L:ADFVOR2,number) 0 == </Visible><Position X="238" Y="218" /><Image Name="RMI_ADF_Needle.bmp"><Axis X="160" Y="21" PointsTo="East" /></Image><Rotate><Value>(A:ADF Radial:2,radians) pi 2 / -</Value><Failures><SYSTEM_ELECTRICAL_PANELS Action="Freeze" /><SYSTEM_ELECTRICAL_AVIONICS Action="Freeze" /><GAUGE_GYRO_HEADING Action="Freeze" /><GAUGE_ADF Action="Freeze" /></Failures><Delay DegreesPerSecond="180" /></Rotate></Element><Element><Visible>(L:ADFVOR2,number) 1 == </Visible><Position X="238" Y="218" /><Image Name="RMI_ADF_Needle.bmp"><Axis X="160" Y="21" PointsTo="East" /></Image><Rotate><Value>(A:NAV2 radial, radians) (A:Plane heading degrees gyro, radians) - pi + pi 2 / -</Value><Failures><SYSTEM_ELECTRICAL_PANELS Action="Freeze" /><SYSTEM_ELECTRICAL_AVIONICS Action="Freeze" /><GAUGE_GYRO_HEADING Action="Freeze" /><GAUGE_VOR Action="Freeze" /></Failures><Delay DegreesPerSecond="180" /></Rotate></Element><Element><Position X="0" Y="0"/><Image Name="RMI_cover.bmp"/></Element><Element><Visible>(L:ADFVOR1,number) 0 == </Visible><Position X="238" Y="218" /><Image Name="RMI_VOR2_Needle.bmp"><Axis X="106" Y="14" PointsTo="East" /></Image><Rotate><Value>(A:ADF Radial:1,radians) pi 2 / -</Value><Failures><SYSTEM_ELECTRICAL_PANELS Action="Freeze" /><SYSTEM_ELECTRICAL_AVIONICS Action="Freeze" /><GAUGE_GYRO_HEADING Action="Freeze" /><GAUGE_ADF Action="Freeze" /></Failures><Delay DegreesPerSecond="180" /></Rotate></Element><Element><Visible>(L:ADFVOR1,number) 1 == </Visible><Position X="238" Y="218" /><Image Name="RMI_VOR2_Needle.bmp"><Axis X="106" Y="14" PointsTo="East" /></Image><Rotate><Value>(A:NAV1 radial, radians) (A:Plane heading degrees gyro, radians) - pi + pi 2 / -</Value><Failures><SYSTEM_ELECTRICAL_PANELS Action="Freeze" /><SYSTEM_ELECTRICAL_AVIONICS Action="Freeze" /><GAUGE_GYRO_HEADING Action="Freeze" /><GAUGE_VOR Action="Freeze" /></Failures><Delay DegreesPerSecond="180" /></Rotate></Element><Element><Visible>(L:ADFVOR1,number) 0 == </Visible><Position X="0" Y="0"/><Image Name="RMI_ADF1_ON.bmp" /></Element><Element><Visible>(L:ADFVOR1,number) 1 == </Visible><Position X="0" Y="0"/><Image Name="RMI_VOR1_ON.bmp" /></Element><Element><Visible>(L:ADFVOR2,number) 0 == </Visible><Position X="0" Y="0"/><Image Name="RMI_ADF2_ON.bmp" /></Element><Element><Visible>(L:ADFVOR2,number) 1 == </Visible><Position X="0" Y="0"/><Image Name="RMI_VOR2_ON.bmp" /></Element><Element><Visible>(L:ADFVOR1,number) 1 == </Visible><Position X="0" Y="0"/><Image Name="RMI_ADF_VOR_1_OUT.bmp" /></Element><Element><Visible>(L:ADFVOR2,number) 1 == </Visible><Position X="0" Y="0"/><Image Name="RMI_ADF_VOR_2_OUT.bmp" /></Element><Element><Visible>(L:ADFVOR1,number) (L:ADFVOR2,number) + 0 ></Visible><Position X="0" Y="0"/><Image Name="RMI_HDG_FLAG.bmp" /></Element><Mouse><Area Left="5" Top="356" Width="88" Height="90"><Cursor Type="Hand"/><Click>(L:ADFVOR1,number) 0 > if{ (L:ADFVOR1,number) 1 - (>L:ADFVOR1,number) } els{ 1 (>L:ADFVOR1,number) }</Click></Area><Area Left="353" Top="358" Width="97" Height="93"><Cursor Type="Hand"/><Click>(L:ADFVOR2,number) 0 > if{ (L:ADFVOR2,number) 1 - (>L:ADFVOR2,number) } els{ 1 (>L:ADFVOR2,number) }</Click></Area></Mouse></Gauge>=====Stop copy above this line=====EDIT 2File to edit: RMI.xml (search and replace as stated below)Posted by: Benoit aka bmdExplanation: As it is said in the pilot's guide the HDG flag appears when there is a problem or when the indicated heading has an error of 5

Edit 4:File to edit: autopilot.xml Posted by: Bert PiekeExplanation: Changes the autopilot HDG function so it will turn tothe heading set by the heading bug:ReplaceAP_HDG_HOLDbyAP_PANEL_HEADING_HOLDEdit 5 (optional):File to edit: vs.xml Posted by: Bert PiekeExplanation: Changes the autopilot preselect knob to mouse wheelactivated turning, and left click to push the knobReplace the existing Mouse section by:

<Mouse>  <Area Left="478" Top="69" Width="175" Height="163"> 	  <Cursor Type="Hand"/>	   <Click Kind="LeftSingle+WheelUp+WheelDown">	  (M:Event) 'LeftSingle'  scmp 0 == if{ (L:VSMODE,number) 0 == if{ 1 (>L:VSMODE,number) } els{ 0 (>L:VSMODE,number) } }		  (M:Event) 'WheelUp'  scmp 0 == if{ (L:VSMODE,number) 0 == if{ (>K:AP_ALT_VAR_INC) } els{ (>K:AP_VS_VAR_INC) } }	  (M:Event) 'WheelDown'  scmp 0 == if{ (L:VSMODE,number) 0 == if{ (>K:AP_ALT_VAR_DEC) } els{ (>K:AP_VS_VAR_DEC) } }   	  </Click>   </Area></Mouse>

And why is Caranado unable to fix these errors themselves rather than attempt to programme all this ourselves?

And why is Caranado unable to fix these errors themselves rather than attempt to programme all this ourselves?

Maybe they will fix these things in a future patch but maybe they like some things as they are, I don't know. But until Carenado has fixed this (or not) it's nice to have the option to do it yourself. Imho. Nothing nicer than a good tweak or edit! :( And btw you can hardly call this programming: it is simply copying text. :( Thanks for the additions, Bert! Keep them coming, please (everyone!). :(

Edit 5:File to edit: adf2.xmlPosted by: Bert Pieke & BenoitExplanation: Change the tooltip information and change the On/Off switch name=====Start copy below this line=====<Gauge Name="Adf2" Version="1.0"> <Image Name="Adf_background.bmp"/><Element> <Visible>(L:ADFON2, number) 0 == </Visible> <Position X="236" Y="15" /> <Text X="272" Y="83" Bright="YES" Length="6" Font="Quartz" Size="50" Color="#ff4200" Adjust="Left" > <String>%((A:ADF ACTIVE FREQUENCY:2, KHz))%!6.1f!</String> <Failures> <SYSTEM_ELECTRICAL_PANELS Action="" /> <SYSTEM_ELECTRICAL_AVIONICS Action="" /> </Failures></Text> </Element><!-- ADF2 ON/OFF --><Element> <Position X="572" Y="95"/> <Select> <Value>(L:ADFON2, number)</Value> <Case Value="0"> <Image Name="ADF_ON.bmp"/> </Case> </Select></Element> <Mouse> <Tooltip ID="TOOLTIPTEXT_ADF2_FREQ"/> <Area Left="226" Top="21" Width="59" Height="61"> <Cursor Type="UpArrow"/> <Click Event="ADF2_100_INC" Repeat="Yes"/> </Area> <Area Left="285" Top="21" Width="28" Height="61"> <Cursor Type="UpArrow"/> <Click Event="ADF2_10_INC" Repeat="Yes"/> </Area> <Area Left="313" Top="21" Width="32" Height="61"> <Cursor Type="UpArrow"/> <Click Event="ADF2_1_INC" Repeat="Yes"/> </Area> <Area Left="354" Top="21" Width="35" Height="61"> <Cursor Type="UpArrow"/> <Click Event="ADF2_RADIO_TENTHS_INC" Repeat="Yes"/> </Area><!-- ADF ON--> <Area Left="578" Top="95" Width="58" Height="60"> <Cursor Type="Hand"/> <Click>(L:ADFON2,number) 0 > if{ 0 (>L:ADFON2,number) } els{ 1 (>L:ADFON2,number) } </Click> </Area> </Mouse></Gauge>=====Stop copy above this line=====Have a good dayBenoit

File to edit: VS.xmlAdd the following within the Mouse section:

<Area Left="20" Top="160" Width="80" Height="40">       <Cursor Type="Hand"/>      <Click> (>K:AP_PANEL_ALTITUDE_ON) </Click>  </Area>

Now you can preselect the altitude and activate it by clickingon the ALT ARM button.Before, you could only start with ALT HOLD and vary the altitude fromthere. This still works, but the above function is handy when you want to seta target altitude while on the ground or while climbing after take-off.If you would like the button to function with the AP turned off, but theFD on, you can make one more edit to the top section of the VS gauge..

<Element><Visible>(A:Autopilot Altitude Lock,bool) (A:AUTOPILOT FLIGHT DIRECTOR ACTIVE,bool) &</Visible>     <Position X="0" Y="0"/>            <Image Name="vs_on_set.bmp" /></Element>

What happened to edits 3 and 4? Did I miss something when I went to the bathroom? :(

File to edit: VS.xmlIf you would like the button to function with the AP turned off, but theFD on, you can make one more edit to the top section of the VS gauge..

<Element><Visible>(A:Autopilot Altitude Lock,bool) (A:AUTOPILOT FLIGHT DIRECTOR ACTIVE,bool) &</Visible>     <Position X="0" Y="0"/>            <Image Name="vs_on_set.bmp" /></Element>

Although the above code works, a better syntax would be

<Element><Visible>(A:Autopilot Altitude Lock,bool) (A:AUTOPILOT FLIGHT DIRECTOR ACTIVE,bool) &&</Visible>     <Position X="0" Y="0"/>            <Image Name="vs_on_set.bmp" /></Element>

:(

Edit 4: File to edit: autopilot.xmlPosted by: Bert PiekeExplanation: Changes the autopilot HDG function so it will turn tothe heading set by the heading bug: Replace AP_HDG_HOLD by AP_PANEL_HEADING_HOLD Edit 5 (optional): File to edit: vs.xmlPosted by: Bert PiekeExplanation: Changes the autopilot preselect knob to mouse wheelactivated turning, and left click to push the knob Replace the existing Mouse section by:

<Mouse>  <Area Left="478" Top="69" Width="175" Height="163">  	<Cursor Type="Hand"/>       <Click Kind="LeftSingle+WheelUp+WheelDown">  	(M:Event) 'LeftSingle'  scmp 0 == if{ (L:VSMODE,number) 0 == if{ 1 (>L:VSMODE,number) } els{ 0 (>L:VSMODE,number) } }     	(M:Event) 'WheelUp'  scmp 0 == if{ (L:VSMODE,number) 0 == if{ (>K:AP_ALT_VAR_INC) } els{ (>K:AP_VS_VAR_INC) } }   	(M:Event) 'WheelDown'  scmp 0 == if{ (L:VSMODE,number) 0 == if{ (>K:AP_ALT_VAR_DEC) } els{ (>K:AP_VS_VAR_DEC) } }    	</Click>  </Area></Mouse>

Hi Bert, I can't get the hdg fix to work...I tried replacing "AP_HDG_HOLD" with "AP_PANEL_HEADING_HOLD" but it doesn't work.Any help would be highly appreciated!

Send me a PM with your email address and I'll send you the complete autopilot file.

Solved! There may be more than one instance of "AP_HDG"_Hold in the gauge... The one that needs changing is:

<Area Left="437" Top="142" Width="108" Height="86">   	<Cursor Type="Hand"/>   	<Click>   	0 (>K:AP_PANEL_HEADING_HOLD)   	</Click>    </Area>

That's what I was doing wrong. Thanks Bert for helping me solve this enigma.Cheers,David DD

Just pulled the Bonanza out of the weeds and was working on these fixes and the edit#2 to fix the heading flag with the new rmi is unclear to me and seems incomplete. Is part of the post missing? I wonder because I also don't see a edit #3.

I believe the post has been cut off.. and whatever was there is lost at sea :(