demyhr

Installation of SP2 also removes the uninstall entry in add/remove programs. Unless you want multiplayer don't install it.

Installation of SP2 deletes the uninstall entry in add/remove programs.

I just noticed that the exterior lights (nav, beacon, strobe) don't work regardless of the realism settings. I uninstalled FSX SP2 and the lights work as expected. Reinstalled (download from Microsoft) and the problem returned.Two questions, does anyone know what the problem is and how to fix it and if not what do I lose if I uninstall SP2?I'm sure this is a not a new issue but I can find no specific details on google or elsewhere.ThanksDavid

I'm trying to reproduce the panel and function of a 1966 C172 G model I used to own in the 80's. The Foster 511 RNAV is the last instrument I need to finish the project. I have modified and coded the Narco Radios and found exact gauges for everything else. It's more a sentimental journey than something serious. I had a lot of good times flying the plane. It had an Avcon Lycoming O-260 180hp engine, Hartzell constant speed prop, flap and aileron seals, remote mag compass, King HSI slaved to compass, Narco MK12 and COM/NAV 11 radios, King DME, King ADF, and the Foster RNAV.While the 180hp didn't make it go faster, I lived in Colorado Springs and the airport I flew out of was 6888 ft elevation and the plane could get off the ground in less than 1200 ft on a 90 degree day at full gross weight. Due to the seals on the flaps and ailerons I could actually slow the plane down with full flaps and power such that the airspeed indicated "0" and still have control, albeit right on the ragged edge of a stall. Flying in the mountains of Colorado was no problem as the plane would reach 18,000 msl which is a fair amount above a normal 172's ceiling. Of course you need oxygen and ifr rating to do that. I regularly would get up to 13,000-14,000 ft going through the passes. I once flew to CA by going straight west and there are areas over northern Nevada where at 10,000 ft you can see no evidence of mankind whatever. needless to say, I tried to stay in radio contact with flight service on that flight. But I digress.I have now got the input to the RNAV working and have a basic idea of the math required to find the offset to the VOR based on the RNAV bearing and distance input. I have tried to couple this to the Bendix/King HSI XML of the FSX Beach Baron. I'm not having much luck getting it working because of my lack of knowledge of the internals of FSX. My relevant code is shown below:Any help with getting this to work would be appreciated. Keep in mind RNAV was used in the 80's (no GPS) with only the input to the RNAV (radial and distance) combined with the tuned VOR radial and the DME distance. I'm hoping to duplicate this operation without resorting to FSX GPS info if possible.Thanks for the help.<!--convert VOR radial to 0-359 degrees--><!--calc angle between nav radial and wp radial --> (A:NAV1 RADIAL,degrees) dnor (L:WP1_BEARING,degrees) - s0 abs dgrd (>L:VOR_WP_ANGLE,radians)<!-- calc distance from WP to plane = sqrt of (a^2 + b^2 - 2*a*b*cosC)a = wp dist from vor L:WP1_DISTANCEb = dme dist VOR to plane A:NAV1 DMEC = angle between nav radial and wp radial L:NAV1_WP --><!-- postfix a^2 b^2 2 a b C cos * * * - + sqrt --> (L:WP1_DISTANCE,nmiles) sqr (A:NAV1 DME,nmiles) sqr 2 (L:WP1_DISTANCE,nmiles) (A:NAV1 DME,nmiles) (L:VOR_WP_ANGLE,radians) cos * * * - + sqrt (>L:DIST_PLANE_TO_WP,nmiles)<!--calc VOR radial from WP in degreesa = wp dist from vor L:WP1_DISTANCEb = dme dist VOR to plane A:NAV1 DMEc =dist from plane to WP DIST_PLANE_TO_WP --><!--postfix BAC = b^2 c^2 a^2 - + 2 b c * * / acos --> (A:NAV1 DME,nmiles) sqr (L:DIST_PLANE_TO_WP,nmiles) sqr (L:WP1_DISTANCE,nmiles) sqr - + 2 (A:NAV1 DME,nmiles) (L:DIST_PLANE_TO_WP,nmiles) * * / acos (>L:TEMP,radians) <!-- Calculate course to fly if s0 < 0 then VOR_OFFSET is negative If s0 > 0 then VOR_OFFSET is positive--> l0 0 < if{ (L:TEMP,radians) /-/ } els{ (L:TEMP,radians) } (>L:VOR_OFFSET,radians)HSI code(>L:VOR_OFFSET,radians)<?xml version="1.0" encoding="utf-8"?><Gauge Name="HSI" Version="1.0"> <Image Name="HSI_Background.bmp" Luminous="Yes" ImageSizes="118,112,186,177"/><Update> (A:NAV1 OBS,radians) (>L:NAV1_OBS,radians)<!-- (A:NAV1 OBS,radians) (L:VOR_OFFSET,radians) + (>L:NAV1_OBS,radians)--><!-- (A:Autopilot heading lock dir,radians) (L:VOR_OFFSET,radians) + (>L:Autopilot heading lock dir,radians)--><!-- (A:Plane heading degrees gyro,radians) (L:VOR_OFFSET,radians) + (>L:Plane heading degrees gyro,radians)--></Update> <Element> <Position X="0" Y="0"/> <MaskImage Name="HSI_Card_Outside_Mask.bmp" Luminous="Yes" ImageSizes="118,112,186,177"> <Axis X="58" Y="57"/> </MaskImage> <Image Name="HSI_Card_Outside.bmp" Luminous="Yes" ImageSizes="106,106,170,170"> <Axis X="53" Y="53"/> </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> <Position X="58" Y="57"/> <Image Name="HSI_Card_Inside.bmp" Luminous="Yes" ImageSizes="70,72,110,114"> <Axis X="35" Y="36"/> </Image> <Clip/> <Rotate> <Value>(L:NAV1_OBS,radians) (A:Plane heading degrees gyro,radians) - </Value> </Rotate> </Element> <Element> <Position X="58" Y="57"/> <Select> <Value>(A:HSI TF flags, ENUM)</Value> <Case Value="1"> <Image Name="HSI_To_Pointer.bmp" Luminous="Yes" ImageSizes="15,8,24,13"> <Axis X="-7" Y="15"/> </Image> </Case> <Case Value="2"> <Image Name="HSI_From_Pointer.bmp" Luminous="Yes" ImageSizes="15,8,24,13"> <Axis X="-7" Y="15"/> </Image> </Case> </Select> <Rotate> <Value>(L:NAV1_OBS,radians) (A:Plane heading degrees gyro,radians) - </Value> </Rotate> </Element> <Element> <Position X="58" Y="57"/> <Image Name="HSI_Needle.bmp" Luminous="Yes" ImageSizes="4,39,8,65"> <Axis X="2" Y="20"/> </Image> <Shift> <Value>(A:HSI CDI needle valid, bool) if{ (A:HSI CDI needle, number) } els{ 0 }</Value> <Scale X="0.173"><!--22/127 = 0.173--> </Scale> </Shift> <Rotate> <Value>(L:NAV1_OBS,radians) (A:Plane heading degrees gyro,radians) - </Value> </Rotate> </Element> <Element> <Position X="27" Y="17"/> <Select> <Value>(A:HSI CDI needle valid,bool)</Value> <Case Value="0"> <Image Name="HSI_Flag_Nav.bmp" Luminous="Yes" ImageSizes="24,13,37,19"/> </Case> </Select> </Element> <Element> <Position X="71" Y="17"/> <Select> <Value>(A:Partial panel heading,enum) 0 != (A:Partial panel electrical,enum) 0 != || </Value> <Case Value="1"> <Image Name="HSI_Flag_Hdg.bmp" Luminous="Yes" ImageSizes="24,13,37,19"/> </Case> </Select> </Element> <Element> <Position X="58" Y="57"/> <Image Name="HSI_Pointer.bmp" Luminous="Yes" ImageSizes="12,9,19,15"> <Axis X="5" Y="44"/> </Image> <Rotate> <Value>(A:Autopilot heading lock dir,radians) (L:Plane heading degrees gyro,radians) - </Value> </Rotate> </Element> <Element> <Image Name="hsi_glide_slope_left.bmp " Luminous="Yes" ImageSizes="4,7,6,11"> <Axis X="4" Y="3.5"/> </Image> <Shift> <Value Minimum="-220" Maximum="120">(A:HSI GSI needle valid, bool) if{ (A:HSI GSI needle, number) } els{ -220 }</Value> <Nonlinearity> <Item Value="0" X="14" Y="57"/> <Item Value="-120" X="14" Y="36"/> </Nonlinearity> <Delay PixelsPerSecond="20"/> </Shift> </Element> <Element> <Image Name="hsi_glide_slope_right.bmp" Luminous="Yes" ImageSizes="4,7,6,11"> <Axis X="0" Y="3.5"/> </Image> <Shift> <Value Minimum="-220" Maximum="120">(A:HSI GSI needle valid, bool) if{ (A:HSI GSI needle, number) } els{ -220 }</Value> <Nonlinearity> <Item Value="0" X="103" Y="57"/> <Item Value="-120" X="103" Y="36"/> </Nonlinearity> <Delay PixelsPerSecond="20"/> </Shift> </Element> <Element> <Image Name="hsi_mask.bmp" Luminous="Yes" ImageSizes="118,112,186,177"/> </Element> <Element> <Position X="103" Y="90"/> <Image Name="HSI_Knob_Right.bmp" ImageSizes="21,21,30,30"> <Axis X="10.5" Y="10.5"/> </Image> <Rotate> <Value>(A:Autopilot heading lock dir,radians) 3 *</Value> </Rotate> </Element> <Element> <Position X="14" Y="90"/> <Image Name="HSI_Knob_Left.bmp" Luminous="Yes" ImageSizes="21,21,30,30"> <Axis X="10.5" Y="10.5"/> </Image> <Rotate> <Value>(A:NAV1 OBS,radians) 3 *</Value> </Rotate> </Element> <Mouse> <Help ID="HELPID_GAUGE_HSI"/> <Tooltip ID="TOOLTIPTEXT_HSI_HEADING_COURSE"/> <Area Left="92" Right="114" Top="79" Bottom="101"> <Help ID="HELPID_GAUGE_HEADING_BUG_ADJUST"/> <Area Right="11"> <Cursor Type="DownArrow"/> <Click Event="HEADING_BUG_DEC" Repeat="Yes"/> </Area> <Area Left="11"> <Cursor Type="UpArrow"/> <Click Event="HEADING_BUG_INC" Repeat="Yes"/> </Area> </Area> <Area Left="3" Right="25" Top="79" Bottom="101"> <Help ID="HELPID_GAUGE_HSI_OBS1"/> <Area Right="11"> <Cursor Type="DownArrow"/> <Click Event="VOR1_OBI_DEC" Repeat="Yes"/> </Area> <Area Left="11"> <Cursor Type="UpArrow"/> <Click Event="VOR1_OBI_INC" Repeat="Yes"/> </Area> </Area> </Mouse></Gauge>

First the goal, I want to create a non-working (hooked to FS9) gauge than simulates a Foster 511 RNAV device. All I want is to simulate the input thumbwheel switches using mouse clicks and vertical sliding mask. The following code segments illustrate I think the basic idea however they don't work. Using Blackbox2 to observe the L:RNAV_WP1_BEARING variable in segment 1 and the G:Var1 variable in segment 2. My question is why do these code segments work differently and what is the trick to getting the number strip to move up and down? A second question is how do I limit the range to 0 to 9 when incrementing/decrementing?I'd really appreciate some help (HINT, HINT Arne Bartels).David1: Will not increment RNAV_WP1_BEARING nor will the vertical number strip (0 to 9) move.<Gauge Name="Foster RNAV 511" Version="1.0"> <Image Name="Foster1_FP.bmp"/> <Element> <Position X="0" Y="0"/> <MaskImage Name="Foster1_FP_Mask.bmp" Luminous="No"> <Axis X="6" Y="27"/> </MaskImage> <Image Name="Bearing_Dec_Wht_strip.bmp" Luminous="Yes"> <Axis X="6" Y="90"/> <Nonlinearity> <Item Value="0" X="0" Y="9"/> <Item Value="9" X="0" Y="171"/> </Nonlinearity> </Image> </Element> <Shift> <Value>(L:RNAV_WP1_BEARING,number)</Value> </Shift> <Mouse> <Area Left="0" Top="18" Right="12" Bottom="36"> <Cursor Type="UpArrow"/> <Click> (L:RNAV_WP1_BEARING,number) ++ (>L:RNAV_WP1_BEARING,number) Repeat="No"> </Click> </Area> <Area Left="0" Top="36" Right="12" Bottom="54"> <Cursor Type="DownArrow"/> <Click> (L:RNAV_WP1_BEARING,number) -- (>L:RNAV_WP1_BEARING,number) Repeat="No"> </Click> </Area> </Mouse></Gauge>2: Will increment/decrement G:Var1 but will not move number strip.<Gauge Name="Foster RNAV 511" Version="1.0"> <Image Name="Foster1_FP.bmp"/> <Update> (G:Var1) (>L:GVar1, number) </Update> <Element> <Position X="0" Y="0"/> <MaskImage Name="Foster1_FP_Mask.bmp" Luminous="No"> <Axis X="6" Y="27"/> </MaskImage> <Image Name="Bearing_Dec_Wht_strip.bmp" Luminous="Yes"> <Axis X="6" Y="90"/> <Nonlinearity> <Item Value="0" X="0" Y="9"/> <Item Value="9" X="0" Y="171"/> </Nonlinearity> </Image> </Element> <Shift> <Value>(G:Var1)</Value> </Shift> <Mouse> <Area Left="0" Top="18" Right="12" Bottom="36"> <Cursor Type="UpArrow"/> <Click> (G:Var1) ++ (>G:Var1) Repeat="No"> </Click> </Area> <Area Left="0" Top="36" Right="12" Bottom="54"> <Cursor Type="DownArrow"/> <Click> (G:Var1) -- (>G:Var1) Repeat="No"> </Click> </Area> </Mouse></Gauge>

Yea Bob, you got the joke!!! I was thinking more along the lines of running the gauntlet of a bevy of senior ladies with whips made of wet noodles. Thank you Andydigital for reassuring me that I have a status. Going around with no status is boring. BTW, if I were to hire a spammer to post hundreds of messages would that help upgrade my status quicker?Back to the real world, I'm still looking for help designing a gauge around the Foster RNAV of the 70's.David.

I recently registered on this forum and have been classified as a "newbie". My question is what must be done to become a full-fledged member? Is there some procedure or ritual I must undergo? If so, how do I go about initiating this procedure? As a "newbie" are there restricted privileges or knowledge that I am not allowed to have until I achieve "Member" status. When do I become eligible for "Member" status? As a 70+ year old retiree of the electronics industry having working as an engineer and manager over 45 years I don't by any means consider myself a "newbie" to technology related endeavors or much else at my age. I have used flight simulators going back to the days of the Z-80 CPM computer and Microsoft Flight Sim since it's first release. So although I may be new to this forum, I'm certainly not a "newbie" to the Flight Sim world or for that matter the the world of real flight having logged over a thousand hours as a private pilot and owner of an older Cessna 172.Maybe you should ask a few questions when registering new members to determine their eventual status. In my case I would consider myself an "oldie" (but goodie) certainly not a "newbie".Seriously, the term "newbie" in my opinion should be eliminated. If it is absolutely necessary to differentiate members by their longevity in the forum I would much prefer "New Member".Regards,David E. Myhr

I've just finished designing an old Narco radio and have found an error in the FS9 SDK docs. Nav frequencies are incremented/decremented in 50KHz steps (108.0, 108.05 etc) contrary to the docs which say 25KHz steps. Com frequencies are incremented/decremented in 25KHz steps (120.000, 120.025, 120.050 etc). The Bendix/King default radios display only 2 digits after the decimal point for COM and NAV. Therefore the Com side cannot display the three digit fractional frequency value and should display .00 .02 .05 .07 and so on. So, a question if I may, what radios are you using? Entering 134.36 into a 720 channel radio should be a forbidden value, if you don't get the fractional sequence mentioned above the radio, in my opinion, is designed wrong. In today's environment real and simulated I think all Com radios change in 25KHz steps (118.000 to 136.975 giving 720 chans) and Nav in 50KHz steps (108.00 to 118. 95 giving 200 chans. Hope this helps.David

I'm trying to design a couple old pieces of avionics. The first is a Narco MK 12 (C I think) NAV/COM. I have done the graphics and now am working on the XML code. I'm by no means an XML expert but I am conversant with programming having made my living for many years programming complex test equipment to test integrated circuits at various companies in San Jose, San Diego and Phoenix. But I digress, I'm working on the Narco XML using other xml radios as a guide. It is going slow due to switching between FS Panel and Fs2004 to debug.The second unit is a Foster 511 RNAV, which I have also got the graphics done, but I haven't a clue where to start the XML. I think I can get the switches/dials coded but how to integrate it into fs2004 so that it actually moves the VOR to a bearing and distance as input by the thumb wheel switch input is a complete mystery. The only RNAV unit I can find is a Narco designed by David Newby Associates as crippleware/payware in 2000 . Newby apparently is no longer supporting his product, having appeared to gone on to the environmental business. Attempts to contact him were fruitless.The goal of all this is to reproduce the panel on the C172 I owned in the 80's. I could use some (actually a lot) of help and if I/we can get it working will post it for public use.David

Thanks for the help, this appears to work fine.Dave

Not sure what happened to my original post, it appears to have been lost in the shuffle.Here's my question. I'm trying to setup the C172 Com/Nav 2 to have glide slope capability coupled to an OBS indicator identical to the Com/Nav 1 OBS. I have set the radios in aircraft.cfg to enable GS and now the challenge is to find a compatible gauge for VOR2. I have found an appropriate gauge in XML format and would like to modify it to work with Nav 2 if possible. My 172 had this dual nav/gs capability and I'm trying to reproduce the panel.Also does anyone know if there is a two channel area nav instrument available.Any help in accomplishing this would be appreciated.Dave

After a several year hiatus I've got time to fool around with FS2004. I'm trying to modify the C72 panel to match the panel the of 172 N1106F I once owned and sold years ago (now in the junk heap after a renter attempted to land in an apartment). The panel had a King HSI with glide slope on nav 1 and a normal heading and glide slope indicator on nav 2. I can get the HSI working nav1 using the Mooney HSI gauge but I can't figure out to get a operable vor heading and glide slope on nav 2.Thanks for any help.Dave