Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Gender
  • Location
  • Interests
    Flying, Computers

Flight Sim Profile

  • Online Flight Organization Membership
  • Virtual Airlines
  1. Tom,YOU ARE THE MAN!!!!The change worked perfectly. I was able to solve another problem code because of you.Thanks again.:)Benny
  2. Hi Tom,What I want to happen is that once the plane reaches lets say 25,000ft, then the counter stops counting away and stays on with the current count. I need this to happen without further clicking to stop this.So the limit will be 25,000ft. Is there any way to limit this by Alt or by a count number say 150?%((A:Indicated Altitude, feet) 501 / int 200 r -)%!d!Thanks,Benny
  3. Hi,I also tried to add 150 > at the end but no luck.Benny
  4. Hi Tom,The code worked perfectly, I just added a ( - ) after the 501 to get the negative altitude to show up. I have 2 strings - one string for the positive and one for the negative triggered by the plus/minus 0 feet. One more question - something I forgot earlier, how do I "cap" off the numbers - what I mean to say is that after it gets to 150 and I want it to stop there, then what do I use to stop?Best Regards,Benny
  5. Hi Tom, It's a different bitmap for every 500 and stays on the entire time from activating until the new bitmap takes over. It's actually a number reduced by 1 as the aircraft climbs, and gains as it descends. The start number for 0-500ft is 200; so at 501 feet, it will appear as 199, etc... I thought about using a string as well but didn't know the code to change it, and maybe bitmaps are easier?Any Ideas on both?Thanks,Benny
  6. Hi all,I'm making a gauge that will trigger a bitmap when the altitude hits every 500ft,(0-500, 501-1000, etc) both up and down in altitude.I'm not to sure where to begin since I could make a gauge like such:(A:Indicated Altitude, feet) 501 < (A:Indicated Altitude, feet) 0 > &But, I would have to make at least 50 entries just for 25,000 ft. There has to be a simpler way.Any help will be greatly appreciated.Thanks,Benny
  7. Thanks Bill,I was down to my last 3 hairs:)The code worked perfectly. I didn't know you could use the K events in the value section - only the click section.I really appreciate the help.Best Regards,Benny
  8. Hi Bill,Well I got a little time to work on this and so far from your suggestion I have the following code:"if (L:HeadingHoldSwitch,bool = 1) then (turn on AP Master andHDG Hold) else (turn on AP Master)"(L:HeadingHoldSwitch,bool) if{ (A:Autopilot master, bool) (L:HeadingHoldSwitch,bool) && } else{ (A:Autopilot master, bool) }The code doesn't seam to work to activate the Heading Hold, even when the autopilot master is activated. Is this code wrong to what you wanted in previous post?Should there also be an "intro" code mixing the (L:HeadingHoldSwitch,bool) with the (A:Autopilot heading lock, bool), and how do I do that? Please helpThanks,Benny
  9. HI,I'm trying to find the code that will make my Heading gauge active (armed)without the AP master being on; so, that the HDG light on my autopilot gauge is on and waiting for the AP master switch be be turned on to initiate the desired turn.I've tried different K codes and (A:Autopilot Heading Lock, bool), etc. I've tried to have it turn on when the panel is loaded but no luck.Any help will be appreciated.
  10. Hi Johann,It looks like you have a type-o >K:TOGGLE_ALTERNATOR1) (L:GEN1,bool) ! (>L:GEN!,bool)(>L:GEN!,bool) should be:(>L:GEN1,bool)1 instead of !Not tested, hope it works.Regards,Benny
  11. Never mind - I just figured it out. I forgot to include the minus at the end after combining them together to find the difference.Benny
  12. Hi all,Does anybody know how to combine these 2 values and get the difference from them?(A:NAV1 radial,radians) (A:Plane heading degrees gyro,radians) - pi +(A:Plane heading degrees gyro,radians) /-/The first one is from actual radial being tracked by the NAV1.The second one is from the "rose" plate (card) that rotates with the heading on a RMI.I'm trying to find the difference in degrees from the actual radial being tracked and the actual course being flown.Thanks,Benny
  13. Hi Bill,I've tried that one but it doesn't fit what the gauge is supposed to do according to the manual. The BC light needs to only come on when you are more than 90 degrees from the localizer, the Glideslope is unavailable, and the localizer is still available. Any ideas?
  14. Hi all,I'm trying to make a Back course gauge that will be indicate that you are more than ninety degrees from the localizer and no glideslope will be available, and you can still capture the back course beam.I have the "no glide slope available, but the 90 degrees from the localizer I can't figure out. I don't know what to use. Please help.Here is what I have so far:(A:HSI GSI needle valid, bool) 0 == (A:HSI has localizer, bool) &&Thanks,Benny
  15. Roman,Both codes worked perfect. Would you mind explaining the following code. I know it has something to do with stacks, but I'm not familiar with it.(A:Attitude indicator pitch degrees, degrees)s1 30 < l1 -40 > & Many thanks,Benny
  • Create New...