I was looking a little deeper into the gauges. Is it normal for the Manifold Pressure and RPM gauges to be off by as much as what is displayed? Looking at the popup I get a different reading then the guage.The RPM gauge shows: <Position X="152" Y="154"/><Item Value="0" X="84" Y="298"/><Item Value="15" X="152" Y="7"/><Item Value="26" X="282" Y="224"/>So if I read this right I see X=152+152=304 Y=154+154=308.152 would be verticle(center of width) at 7 pixles from the top so this number is correct.This would mean eigther the 1st, 3rd or both are off by a small amount.I think I have a more accurate calculation.X= 0+ 97= 97 Y=308-35=273 (RPM 0)X= 0+152=152 Y= 0+23= 23 (RPM 15)X= 304- 43=261 Y=308-92=216 (RPM 26)Let me know what you thik. I'm going to pluig in the numbers and see what happens.My numbers seem to be a little high so far. Hmmm. I just noticed that the image is not 304x308. It is 304x304 making the numbers off.

ok here is my more accurate RPM gauge.<Element> <Position X="152" Y="152"/> <Image Name="RPM_Needle.bmp" PointsTo="East"> <Axis X="45" Y="9.5"/> </Image> <Nonlinearity> <Item Value="0" X="84" Y="292"/> <Item Value="7" X="7" Y="147"/> <Item Value="15" X="152" Y="7"/> <Item Value="23" X="286" Y="143"/> <Item Value="26" X="282" Y="222"/> </Nonlinearity>Added a little more accuracy to the manifold pressure gauge. You would need to change this for both engines in the file.<Element> <Position X="150.5" Y="151"/> <Image Name="manifold_needle_L.bmp" PointsTo="East">

Any more from Carenado on this....The temp gauges and such?I noticed the up-date on there page..."You don't need this patch if you downloaded the package after July 1st, 2009 0300 GMT"But the temp gauge doesn't match the numbers you guys are using?And I can't get FireFox to allow me to modify the XML.Jeff

Any more from Carenado on this....The temp gauges and such?I noticed the up-date on there page..."You don't need this patch if you downloaded the package after July 1st, 2009 0300 GMT"But the temp gauge doesn't match the numbers you guys are using?And I can't get FireFox to allow me to modify the XML.Jeff

The temp gauge code has to read Fahrenheit instead of Celsius. No need to change the numbers, as it turns out.The autopilot code has been accepted by Carenado and should be released in an update.

The temp gauge code has to read Fahrenheit instead of Celsius. No need to change the numbers, as it turns out.The autopilot code has been accepted by Carenado and should be released in an update.

Go Bert!!. Thanks for all your investigative work here. Hope to see the patch from Carenado soon

The temp gauge code has to read Fahrenheit instead of Celsius. No need to change the numbers, as it turns out.The autopilot code has been accepted by Carenado and should be released in an update.

Thanks again for your work Bert!

The temp gauge code has to read Fahrenheit instead of Celsius. No need to change the numbers, as it turns out.The autopilot code has been accepted by Carenado and should be released in an update.

Thanks Bert....Jeff

(L:TRIMAP,bool) 1 ==if{ (>K:AP_PITCH_REF_INC_DN) }and(L:TRIMAP,bool) 2 ==if{ (>K:AP_PITCH_REF_INC_UP) }and<Area Left="342" Top="62" Width="84" Height="81"> <Cursor Type="Hand"/> <Click> 0 (>K:AP_ALT_HOLD) (A:AUTOPILOT ALTITUDE LOCK) 0 == if{ 0 (>K:AP_ATT_HOLD_ON) } </Click> </Area>

Something still seems to be wrong with this code. Every time I turn of ALT hold while NAV hold is on I loose my NAV hold. causing me to turn on my NAV hold again. This is causing the pitch hold to start again so you get stuck in an endless loop unable to use the pitch. Anyone else getting this ?

Something still seems to be wrong with this code. Every time I turn of ALT hold while NAV hold is on I loose my NAV hold. causing me to turn on my NAV hold again. This is causing the pitch hold to start again so you get stuck in an endless loop unable to use the pitch. Anyone else getting this ?

OK, lets get the exact sequence that is causing you trouble...If I turn on the AP, turn on NAV, turn on ALT, turn off ALT (either directly or using the rocker switch),NAV stays on... This is sitting on the tarmac...

OK, lets get the exact sequence that is causing you trouble...If I turn on the AP, turn on NAV, turn on ALT, turn off ALT (either directly or using the rocker switch),NAV stays on... This is sitting on the tarmac...

ok I just started a flight from KHOU on the active RWY 17Set the GPS for KDFWNav/GPS is set to GPS.I take off and everything works fine. Hit the Nav button on the Autopilot. Autopilot responds like it should. Using the rocker the pitch control works.I climb to say 3000 and level off and turn on ALT hold. If I hit the rocker then Both ALT and NAV on the autopilot turn off automaticaly. I believe the same thing happens if you press the ALT button however let me go back and check.ok If I have NAV and ALT turned on then turn off ALT NAV also turns off. If I turn NAV back on pitch control does work again. For some reason NAV hold keeps turning off. That's the problem.

ok I just started a flight from KHOU on the active RWY 17Set the GPS for KDFWNav/GPS is set to GPS.I take off and everything works fine. Hit the Nav button on the Autopilot. Autopilot responds like it should. Using the rocker the pitch control works.I climb to say 3000 and level off and turn on ALT hold. If I hit the rocker then Both ALT and NAV on the autopilot turn off automaticaly. I believe the same thing happens if you press the ALT button however let me go back and check.ok If I have NAV and ALT turned on then turn off ALT NAV also turns off. If I turn NAV back on pitch control does work again. For some reason NAV hold keeps turning off. That's the problem.

Ok, try something:Disable the AP annunciator//gauge14=PA34S3!RadioAnuncios, 319, 446 ,192, 65We know it has a bug, in that the NAV and ALT displays are in the same spot...Tell me if the AP behaves better then.. :(

Ok, try something:Disable the AP annunciator//gauge14=PA34S3!RadioAnuncios, 319, 446 ,192, 65We know it has a bug, in that the NAV and ALT displays are in the same spot...Tell me if the AP behaves better then.. :(

It still occures if you comment that gauge out from the VC.Also I noticed if you have NAV on and you press ALT then NAV turns off.I don't see a reason this is setting a toggle on the buttons we didn't change. unless its because it isn't formatted as a clickevent like the others.

It still occures if you comment that gauge out from the VC.Also I noticed if you have NAV on and you press ALT then NAV turns off.I don't see a reason this is setting a toggle on the buttons we didn't change. unless its because it isn't formatted as a clickevent like the others.

OK, I think I see the issue... when ALT is engaged, it also engages the Wing leveler which turnsoff HDG or NAV.. not so good and I have no idea how to change this either :(But I believe you are correct: "Click Event" does not engage the Wing Leveler, but assigning the value with >K etc does...

"Click Event" does not engage the Wing Leveler, but assigning the value with >K etc does...

I've found a brute force coding method that solves it... do you want to test it?

While watching the "Cylinder head temp" yesterday after applying the new patch....I noticed as I raised the flaps on take-off....the "Ammeter" was moving when you use the flaps?Any body else seeing this?Jeff

I've found a brute force coding method that solves it... do you want to test it?

I'll give it a shot.