Jump to content

phjvh

Frozen-Inactivity
  • Content Count

    2,240
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by phjvh

  1. How do you lock on one plane? If one moves the mouse, all data are lost.
  2. Thanks for all answers. At least not to do for me.
  3. Sorry, Forgot to mention,HUD, FS9 and only xml. To clarify, i mean a forward looking radar with symbols showing distance and vector. Azimuth and altitude relative to the plane's velocity vector. Personally i think it is hardly possible, but it would be something to chase an AI with my 767..... Btw, with the "normal" TCAS/Radar it is good to do also, but rather difficult to construct carets etc.
  4. Hi, Using Arne's radar gives a good pic of the traffic around in a horizontal plane. Did someone succeed to get an image of the vertical in front of you with say the velocity vector as center?
  5. Thanks!, This one works: %((A:AUTOPILOT NAV SELECTED,enum) 1 ==) %{if} %((A:NAV TOFROM:1,enum) 1 ==)%{if}TO%{else}FROM%{end} %{else} %((A:NAV TOFROM:2,enum) 1 ==)%{if}TO%{else}FROM%{end} %{end}
  6. Hi, I use (>K:AP_NAV_SELECT_SET) to choose between the two modes and (A:AUTOPILOT NAV SELECTED,enum) to read which mode is active. The code i use is: %((A:AUTOPILOT NAV SELECTED,enum) 1 ==) %{if} %((A:HSI TF FLAGS:1,enum) 1 ==)%{if}TO%{else}FROM%{end} %{else} %((A:HSI TF FLAGS:2,enum) 1 ==)%{if}TO%{else}FROM%{end} %{end}
  7. Hi, By coincidence i noticed that the HSI TO/FROM FLAG: %((A:HSI TF FLAGS,enum) 1 ==)%{if}TO%{else}FROM%{end} didn't work when the autopilot is drived by NAV2: (A:AUTOPILOT NAV SELECTED,enum) 2 == With (A:AUTOPILOT NAV SELECTED,enum) 1 == no problems. Is this observation correct?
  8. Ah, That one is for Fr. Bill or another C++ guru to answer. But i think it is possible.
  9. Congrats! Well, if your program gives lat and long values, then you can put those in an xml gauge. Advice: download the gps guide of "Propwash". It is all in there.
  10. Do a search: https://www.google.com/search?hl=nl&safe=off&site=imghp&tbm=isch&source=hp&biw=1000&bih=574&q=embraer+120+panel&oq=embraer+120+panel&gs_l=img.3...3064.18366.0.19478.19.12.1.6.6.0.50.461.12.12.0...0.0...1ac.1.7.img.d3CXk_QGz5I and start cutting, pasting, editing etc.
  11. May be too much space <String>........ if{ (A:NAV DME:1, nmiles) (> L:MyDMEDistance, Number) } (L:MyDMEDistance, Number))%!03d!</String> Should be: ..............(>L:MyDMEDistance,number)....or ..............(>L:MyDMEDistance,number)... ? and i advice to use formattedtext.
  12. It looks like you have some gps background. In that case no transparancy. It is possible to do, but then you need a whole lot of xml.....!!
  13. I get 3 messages with my method: glideslope active, alive and engaged. Same for localizer. To alter this in lights off, amber and green seems not too difficult.
  14. Hi, I use (A:NAV1 CDI,number): -127<-- 0 -->127 and (A:NAV1 GSI,number) -119<-- 0--> 119 to do something similar. Works ok for localizer and glideslope. eg. for copilot voice: "Localizer alive...." . (A:NAV1 CDI,number) abs 90 < if{ (L:approach logic 2,number) 0 == if{ 1 (>L:approach logic 2,number) 1 (>L:localizer alive,number) } } els{ 0 (>L:approach logic 2,number) } etc.
  15. Hi, Try: (A:GPS DRIVES NAV1,bool) ! if{ (>K:TOGGLE_GPS_DRIVES_NAV1) (>K:AP_NAV1_HOLD_ON) } els{ (A:GPS DRIVES NAV1,bool) if{ (>K:TOGGLE_GPS_DRIVES_NAV1) (>K:AP_NAV1_HOLD_OFF) } }
  16. Hi, You can place a rectangle in front of everything with different grades of transparancy. It simulates a dimmer.
  17. hi, Try to use "zorder" in the window section of the panel.cfg: [Window00] .... zorder=0 [Window01] ..... zorder=1 etc. Works for me
  18. A last question: Should you take into account in the code a form of windcorrection? ...and from the Netherlands: Merry Christmas and a Happy New Year!
  19. Hi, This is a very complicated subject! Take into account MTOW (Boeing data), air-temperatures and pressures, weather, runway condition, thrustmodes, powersettings, limits, restrictions, costindex etc. etc. etc. Hundreds of calculations whill finally result in power, attitude and opt/max cruise-altitude with step climbs etc.. Then you will have a reasonable VNAV profile and a "cheap as possible" trip. Quite difficult and it is hard to read my own over 8 year old code....,. Sometimes asking myself: is it worth the effort??
  20. Hi, I use for the symbols: <Visible> (@c:FlightPlanWaypointRemainingDistance,nmiles) 5 < (@c:FlightPlanWaypointRemainingDistance,nmiles) 0 > and if{ (P:absolute time, number) 1 % 0.5 > } els{ 1 } </Visible> and text: %((@c:FlightPlanWaypointRemainingDistance,nmiles) 5 < (@c:FlightPlanWaypointRemainingDistance,nmiles) 0 > and) %{if}\{blnk}%{else}\{nr}%{end}%((@c:FlightPlanWaypointIdent))%!s! Mind that flashing will stop sooner when altitude increases!
  21. Hi, Test this and you wil see what COM frequencies come up. It is not what one expect, but that has to do with "bandwidth"? <Macro Name="BCD">100 * 10000 % int d 10 % r 10 / int d 10 % r 10 / int d 10 % r 10 / int 16 * + 16 * + 16 * + </Macro> <Element> <Position X="52" Y="685"/> <FormattedText X="58" Y="15" Bright="Yes" FontSize="14" Font="Quartz" Color="%('silver' 'gray' (A:CIRCUIT AVIONICS ON,bool) ?)" Adjust="Center" VerticalAdjust="Center"> <String>\{bo}%((A:Com1 active frequency,MHz))%!7.3f!</String> </FormattedText> </Element> <Element> <Position X="52" Y="715"/> <FormattedText X="58" Y="15" Bright="Yes" FontSize="14" Font="Quartz" Color="%('silver' 'gray' (A:CIRCUIT AVIONICS ON,bool) ?)" Adjust="Center" VerticalAdjust="Center"> <String>\{bo}%((L:com frequency,number))%!7.3f!</String> </FormattedText> </Element> <Area Left="50" Right="225" Top="705" Bottom="725"> <Tooltip>COM TEST, %((L:com frequency,number))%!7.3f!</Tooltip> <Cursor Type="Hand"/> <Click Kind="LeftSingle+RightSingle" Repeat="Yes"> (M:Event) 'LeftSingle' scmp 0 == if{ (L:com whole,number) 1 - 118 max (>L:com whole,number) (L:com whole,number) (L:com fract,number) + (>L:com frequency,number) (L:com frequency,number) @BCD (>K:COM_RADIO_SET) } (M:Event) 'RightSingle' scmp 0 == if{ (L:com whole,number) 1 + 136 min (>L:com whole,number) (L:com whole,number) (L:com fract,number) + (>L:com frequency,number) (L:com frequency,number) @BCD (>K:COM_RADIO_SET) } </Click> </Area> <Area Left="50" Right="225" Top="726" Bottom="755"> <Tooltip>COM TEST, %((L:com frequency,number))%!7.3f!</Tooltip> <Cursor Type="Hand"/> <Click Kind="LeftSingle+RightSingle" Repeat="Yes"> (M:Event) 'LeftSingle' scmp 0 == if{ (L:com fract,number) 0.001 - 0 max (>L:com fract,number) (L:com whole,number) (L:com fract,number) + (>L:com frequency,number) (L:com frequency,number) @BCD (>K:COM_RADIO_SET) } (M:Event) 'RightSingle' scmp 0 == if{ (L:com fract,number) 0.001 + 0.999 min (>L:com fract,number) (L:com whole,number) (L:com fract,number) + (>L:com frequency,number) (L:com frequency,number) @BCD (>K:COM_RADIO_SET) } </Click> </Area> If you want to see e.g. 121.121 in the display, you will have to use the L:Var., but that stands for a different com. freq. (125.125) May the @BCD is the problem.
  22. fr. Bill, ah well eh eh, just like the way my gauges look......
  23. Hi, You are completely right, a newer version showed: <Value> (A:Indicated Altitude,feet) (A:Autopilot altitude lock var,feet) - abs 200 > if{ (A:Indicated Altitude,feet) (A:Autopilot altitude lock var,feet) - (A:Vertical speed,feet per minute) / abs (A:GROUND VELOCITY,knots) * 60 / 0.3125 0.625 1.25 2.5 5 10 6 (L:hsi zoom,number) case * int (>L:rangezoom factor,number) (L:rangezoom factor,number) 2 > if{ (L:rangezoom factor,number) } els{ 0 } } els{ 0 } </Value> FYI, have in different subpanels 4 nd's operating...send a not corrected one; bad bad.
×
×
  • Create New...