phjvh

<Element> <Position X="50" Y="80"/> <Polyline Bright="Yes" LineWidth="2" Color="silver"><Point X="-3" Y= "-7"/><Point X= "0" Y="-10"/><Point X= "2" Y= "-7"/><Point X= "0" Y= "-8"/><Point X= "0" Y= "10"/></Polyline> <Rotate> <Value>(A:Ambient wind direction,radians) (A:Plane heading degrees gyro,radians) - (A:Magvar,radians) - pi +</Value> <Delay DegreesPerSecond="20"/> </Rotate> </Element> Hi, A possibility, xml vector (fs9):

Hi, Just Google for aircraft window. Take one and edit in mspaint, proper dimensions etc. et voila!

A last wet pic! Now back to the 767.....

It is a Skyspirit2010 767 with altered aircraft.cfg and air file, so one cannot release. Btw. almost 4 Gb.......

Another observation: Tested the 787 with my 767 panel and had problems with the elec. sys. too. So changed the aircraft.cfg: 1. removed under [electrical] electric_always_available = 1 2. added under [GeneralEngineData] master_ignition_switch=1 Here after no problems anymore, at least with the 767 panel. For fun made a HUD with 767 gauges.

can send you, mail?

With a little bit of artwork (text) you can have a nice overhead. And gauges and functions......

I have been looking too, but didn't find anything better. There are usable bitmaps on google......

You are right with the phenomenon. But there seems to be more wrong. E.g. tried to save cold and dark, but when starting fs again the engines were running?? Why using a 767 overhead with illogical placed gauges etc. etc.? I should contact the authors or rebuild the panel with the proper bitmaps and right placed gauges and functions using as much technical info as possible.

You should have know: 787 and battery....... Joke, what download, what panel?

same as mine maybe only for fsx?

get only:

well, have the dev. rel. version and the button only shows: <ModelInfo /> probably doing something wrong...

Hi, Off topic off course, but downloaded modelconverter 1.3 just for curiousity. where is the "show modeldef" button?

Right, FTR, i use only: <Value>(A:GPS DRIVES NAV1,bool) (A:GPS WP ETE,minutes) 2 < and</Value> for obvious reasons.

Didn't calculate that, but probably "the whole lot" is the amount of minutes to get to the waypoint whatever direction one is moving, so i think you are right. (Time = Distance / Velocity)

My observations ETE minutes: On the ground: "0" when parking brakes are on and "a whole lot" during taxiing. In the air: the amount of minutes to the waypoint and when holding the number increases on the outbound leg and decreases, of course, on the inbound leg. When moving in a circle around the wpt, so distance stays the same, the number of minutes remain even.

Hi, (A:sim on ground,bool) ! if{ (A:GPS WP ETE, minutes) 2 < (A:GPS IS ACTIVE WAY POINT,bool) (A:ELECTRICAL AVIONICS BUS VOLTAGE, volts) 10 > and and if{ 1 } els{ 0 } } els{ 0 } A translation: If airborne (A:sim on ground,bool) !, then the value is "1", when the 3 arguments, (A:GPS WP ETE, minutes) 2 < (A:GPS IS ACTIVE WAY POINT,bool) (A:ELECTRICAL AVIONICS BUS VOLTAGE, volts) 10 > and and, are true. if not, one of the arguments is false, the value is "0". On the ground the value will be "0".

OK, For fun tested your code and this works perfect: <Element> <Position X="0" Y="200" /> <Select> <Value> (A:sim on ground,bool) ! if{ (A:GPS WP ETE, minutes) 2 < (A:GPS IS ACTIVE WAY POINT,bool) (A:ELECTRICAL AVIONICS BUS VOLTAGE, volts) 10 > and and if{ 1 } els{ 0 } } els{ 0 } </Value> <Case Value="0"><Image Name="wpt Alert1.bmp" Bright="yes"/></Case> <Case Value="1"><Image Name="wpt Alert2.bmp" Bright="yes"/></Case> </Select> </Element>

Watch the spaces! and try: <Value> (A:sim on ground,bool) ! if{ (A:GPS WP ETE, minutes) 2 < (A:GPS IS ACTIVE WAY POINT,bool) (A:ELECTRICAL AVIONICS BUS VOLTAGE, volts) 10 > and and if{ 1 } els{ 0 } } els{ 0 } </Value>

Btw. Using ETE reads 0 (<2!), when parking brake or pushback is on. That 's why the alert comes on. Also when using ETE, (A:GPS IS ACTIVE WAY POINT,bool) is Always 1, so you don't need that parameter. Of course one can use (A:sin on ground,bool), but that is extra, unnecessary code. I use (A:GPS DRIVES NAV1,bool), of course only when airborne and have a flawless functioning waypoint alert system. So: (A:GPS WP ETE,minutes) 2 < (A:GPS DRIVES NAV1,bool) and This is part of a lot of other code only working with current on the Av. buses..

Strange, Can you show all code you use in this gauge?

Try to use: (A:GPS DRIVES NAV1,bool) instead of (A:GPS IS ACTIVE WAY POINT,bool)

Hi, Try to use ETE. This works for me: a bell sign before reaching a waypoint. (A:GPS WP ETE,minutes) 1 < if{ (L:waypoint,number) 0 == if{ 1 (>L:waypoint,number) 1 (>L:sign,number) } } els{ 0 (>L:waypoint,number) } Hope it helps,

Sorry, Forgot to say FS9, but i will give it a shot. Thanks