Baron airspeed indicator error

[zfehr]

Old question, still no answer. The TAS adjustment knob on the IAS gauge for the default Baron moves the wrong direction... not very useful. Has anyone ever posted a fix for this or does someone know how to fix it? Also, does anyone doing the beta testing for FS-ACOF know if this gauge is fixed in the new version... if it isn't, bring it up so it gets fixed!!!

Only used the word fix four... no five times!

Zane

Athlon XP2000+
ECS K7S5A Motherboard
PNY GeForce 4MX420 64MB PCI
512 PC2100 DDR
WinXP Home
CH Products USB Yoke and Pedals
Game Commander2/FSNavigator/MyTraffic Sp2

[zfehr]

Bump... try again.

Somebody?

[FS2002tipster]

I've forgotten why now, (post in a forum many months ago) but I've never used that adjustment knob.

If you can define exactly what you mean by "moves the wrong direction", I'll take a look in the gauge code and see if it's an easy fix.

http://www.flightsim.com/dcforum/Use...f7187467a2.jpg

http://rtw2003.tripod.com

[zfehr]

Hello there,

Thanks for the response. The problem with the Baron airspeed gauge is that the calibration bezel rotates the wrong direction. i.e. when you are at 10,000 feet at standard temperature you should be able to set the 12 o'clock porton of the bezel to 10, in the region of the gauge approximately 6 to 9 o'clock if you are indicating 180 knots the outer portion of this should read about 198 knots (that would be your true airspeed at that altitude for those conditions). At present the knob will only allow adjustments that go in the opposite direction... would only be useful if you were going be flying below sea level. I have looked at the gauge with the xml editor within FS Panel Studio but couldn't figure out what to change. Hopefully you will recognize what one would have to do to make it rotate the other direction.

Best of luck,

Zane

[FS2002tipster]

I couldn't figure it out I'm afraid. I changed the limits and all sorts. I just couldn't get it to register the opposite way.

Rob Barendregt and Arne Bartels are the XML gauge wizards that I know of. Might be worth trying to get hold of them.

http://www.flightsim.com/dcforum/Use...f7187467a2.jpg

http://rtw2003.tripod.com

[Captain_Slarty]

havent tried it, but if we look at the code.

<Help ID="HELPID_GAUGE_TAS_CALIBRATION" />
- <Area Right="9">
<Cursor Type="DownArrow" />
<Click Event="TRUE_AIRSPEED_CAL_DEC" Repeat="Yes" />
</Area>
- <Area Left="9">
<Cursor Type="UpArrow" />
<Click Event="TRUE_AIRSPEED_CAL_INC" Repeat="Yes" />
</Area>

try changing the uparrow and downarrow around ??

Joe.

http://homepage.ntlworld.com/captain...s/coolskul.gif

System - >
3gig Intel + .. Size DOES matter

[FS2002tipster]

Unfortunately that just swaps the + and - in the tooltip but doesn't have any actual affect on the register.

I'm obviously missing something somewhere. The gauge logic is reasonably easy to construct, but the syntax in XML is a nightmare, particularly if you're unfamiliar with C++.

http://www.flightsim.com/dcforum/Use...f7187467a2.jpg

http://rtw2003.tripod.com

[zfehr]

Thank you for trying. I've been looking at it again with the tools within FS Panel Studio and so far nada... only mess it up!

Hopefully someone with more gauge savvy will pick up on this thread. And MICROSOFT should FIX IT in the upcoming version.

Zane

PS I'd love it someone would take the Baron HSI gauge and make a copy of it that used information from NAV 2 only. You could then have a two HSI panel (what I'm used to seeing). Nice to fly with.

[FS2002tipster]

[font size="1" color="#FF0000"]LAST EDITED ON Mar-09-03 AT 00:26AM (EST)[/font][p]LOL - I've only just finished version 2 of my Baron Panel (it's at simviation.com if you want a look).

I suspect it wouldn't be difficult though. In the case of my panel there isn't a square inch of space left on it though so something else would have to go.

Btw - I re-did the boot and prop de-ice switches so they actually have an effect in FS2002 rather than the dummies that Microsoft provided.

http://www.flightsim.com/dcforum/Use...f7187467a2.jpg

http://rtw2003.tripod.com

[wsieffert]

I believe the two TAS BMP should be reversed in numbering:

Presently:

Airspeed_TAS.bmp /1024 240 on left to 100 on right
Airspeed_TAS.bmp /640 240 on left to 100 on right

To:

Airspeed_TAS.bmp /1024 100 on left to 240 on right
Airspeed_TAS.bmp /640 100 on left to 240 on right

The bipmap may also have to be rotated or numbers aligned to match the 0deg position.

W. Sieffert