Engjell Berisha

Thank You guys, only romans rng approach worked, nothing else worked not even the millibars.

I'm creating a PFD, it has a display that shows the kohlsman setting but when it's at 29.92 it displays the letters STD. I can't work out mathematically how to define when this is. I've tried this:(A:KOHLSMAN SETTING HG,inHg) 29.92 - <Althought this yeilds a infinitely small number and not zero as I had hopped>I tried using visible tags but (A:KOHLSMAN SETTING HG,inHg) 29.92 == nor (A:KOHLSMAN SETTING HG,inHg) 29.92 != work.

Do you ever get the failures when the engines are on? If so press SHIFT G.

I know at one time there was a beautiful depiction of what could've been an Eastern Airlines 737-200 on Mr. Cantu's model. I don't recall who painted it but I have searched to no avail and I can not find it for the life of me.Could someone point me in the right direction or perhaps you have it and would email it to me.Here's some screenshots of it.

Only on that panel?

Thank You Ed. The only model that I have seen with visually modeled ice build up on the actual aircraft is the Lotus Sim Albatross, I wonder how this is achieved, is it difficult?

Perhaps I'm too happy and I'm understanding this wrong, does this actually mean you'll see ice form on the aircraft or only feel it? Is there a variable which will tell you how much ice you've accumulated? Which version of FS?

Hu, interesting. Where would I get the patch from mate?

SWEET! It only lets me fly in the winter, I can't understand why but I'm happy enough I suppose. Thank You so much!!!!I'll have to see what if I can find what is casing this.Thank You very, very much mate!

Hello I've been experiencing crashes in the Juneau/Stikine Regions of Flight Simulator for a few months now. It is one of my favorite regions to fly, I have many sceneries installed there and they had been working great up until a few months ago. I don't recall installing any new scenery/mesh in the area or anywhere else at that time. I just started to get crashes there.I can for example start off at PAPG and take off for and fly 040º and after a few minutes the sim will turn all black, and I usually get a error message for a dll and what not. The name of the dll changes most of the time so I can not figure it to be a specific dll. I've tried disabling just about every scenery I have in the area and nothing, I still get the same problems.I have installed the following sceneries:SIRPUltimate Terrain - Alaska & CanadaFreight DogsFSAddon Glacier BayHover Control Outposts - they are like 50 - 100NM out of the are or so but I never get the crashes here.PAFE & PAPG addon sceneriesI'm fairly well rehearsed in addon-scenery and such and I understand the manipulation of the scenery orders well enough and have tried many different orders but none seem to work.I hope some one can help me with this as I really, really miss flying in this area!

That would make sense, because my gauge won't work without it. Thank You Bill.Reading material on entering input is hard to find it seems, would you know if any?Why do I set it to 31? I've seen this in several gauges I learned to use it from and that's the only reason I've continued to do so - because it works.

Actually I think ( (L:char21,enum) chr ) should work but I don't think you can put the spaces, or maybe I'm wrong. I'll test it if I get a chance but I think ((L:char21,enum) chr) or ((L:char21,enum) chr ) should work.What is enteringinput anyway? I've always been told to use it, that wasn't from the gps 500 either it was from a gauge I built.

Nice, brief, but intuitive.Think about making them into PDF's?

Try this, not tested but I think it should work. 'A' (>C:fs9gps:IcaoSearchStartCursor)31 (>C:fs9gps:enteringInput)(L:char21,enum) chr (>C:fs9gps:IcaoSearchEnterChar) Put it in your Update string but you ought to add some clauses to keep it from continuously firing.Or perhaps you could just put it in the click code.I would recommend using L:char21,number as oppose to enum aswell - I read and have been told that enum and bool are better suited to lower numerical computations.Hope that helps.

Hello I've been experiencing crashes in the Juneau/Stikine Regions of Flight Simulator for a few months now. It is one of my favorite regions to fly, I have many sceneries installed there and they had been working great up until a few months ago. I don't recall installing any new scenery/mesh in the area or anywhere else at that time. I just started to get crashes there.I can for example start off at PAPG and take off for and fly 040º and after a few minutes the sim will turn all black, and I usually get a error message for a dll and what not. The name of the dll changes most of the time so I can not figure it to be a specific dll. I've tried disabling just about every scenery I have in the area and nothing, I still get the same problems.I have installed the following sceneries:SIRPUltimate Terrain - Alaska & CanadaFreight DogsFSAddon Glacier BayHover Control Outposts - they are like 50 - 100NM out of the are or so but I never get the crashes here.PAFE & PAPG addon sceneriesI'm fairly well rehearsed in addon-scenery and such and I understand the manipulation of the scenery orders well enough and have tried many different orders but none seem to work.I hope some one can help me with this as I really, really miss flying in this area!

I'm pretty sure this is possible, as I've done calculations with conditional statements in formatted text for things like waypoint index and subsequent information and such.I'll test it when I get a chance. Below is some of the code I used on one of my FMC's:<ScrollY>(L:FMC-FWD-PLN-SCROLL,number)</ScrollY><String>\n\n\{lsp=2.5}%((L:WP_counter,number) 4 + (C:fs9gps:FlightPlanActiveWaypoint) + s3)%((C:fs9gps:FlightPlanIsActiveFlightPlan) (C:fs9gps:FlightPlanWaypointsNumber) s2 0 != and)%{if}%((L:WP_counter,number) (C:fs9gps:FlightPlanActiveWaypoint) + sp1)%{loop}%(l1 (>C:fs9gps:FlightPlanWaypointIndex,number))%((C:fs9gps:FlightPlanWaypointRemainingDistance,nmiles) 0 !=)%{if}\t\{fnt2}%((C:fs9gps:FlightPlanWaypointMagneticHeading,degrees) d360)%!03d! °M\t%((C:fs9gps:FlightPlanWaypointRemainingDistance,nmiles) s0 100 >)%{if}%(l0)%!d! NM%{else}%(l0)%!3.1f! NM%{end} %((C:fs9gps:FlightPlanWaypointETA,seconds) 0 >)%{if}@eta%{else}-------%{end}\n%((L:FplDelete,enum) 1 ==)%{if}\{rev}<\{nr} %{else}%{end}%((C:fs9gps:FlightPlanActiveWaypoint,number) l1 ==)%{if}%( l8 (>L:FlightPlanVS,number) 1 (>L:FlightPlanAltitude,number))\{rev}%{else}\{nr}%{end}%((C:fs9gps:FlightPlanWaypointIdent,string))%!s!%( l8 (L:FlightPlanVS,number) 5000 >)%{if}%( 5000 (>L:FlightPlanVS,number))%{end}\{nr}\t%((A:GPS FLIGHT PLAN WP COUNT, number) 1 - l1 ==)%{if}%((C:fs9gps:FlightPlanWaypointAltitude,feet) s7)%{else}@WaypointAltitude2%{end}%( l1 (C:fs9gps:FlightPlanActiveWaypoint,number) ==)%{if}%%(180 l0 1852 * / l11 (A:Indicated Altitude, feet) - 0.3048 * * 196.85 * 100 / near 100 * s8)%{else}%(180 l0 1852 * / l7 0.3048 * * 196.85 * 100 / near 100 * s8)%{end} %(l8 0 >)%{if}CLB %(l8 abs 0 == !)%{if}%(l8 abs)%!d!%{end}%{end}%(l8 0 <)%{if}DES %(l8 abs 0 == !)%{if}%(l8 abs)%!d!%{end}%{end}%((C:fs9gps:FlightPlanWaypointAltitude,feet) 0 >)%{if}%((C:fs9gps:FlightPlanWaypointAltitude,feet) (>G:VAR4))%{else}@WaypointAltitudeSet%{end} %(45 180 l8 0.00508 * / / abs s10 0 == !)%{if}%(l10)%!5.1f! ° %{end}%((A:GPS FLIGHT PLAN WP COUNT,number) 1 - l1 == )%{if}/ %((C:fs9gps:FlightPlanWaypointAltitude,feet) s6)%!d! FT%{else}@WaypointAltitude%{end}\n%( l1 (C:fs9gps:FlightPlanActiveWaypoint,number) ==)%{if}%( l9 100 / near 100 * (>L:FlightPlanWPAltitude,feet))%{end}%{else}%(l3 ++ s3)%{end}%(l1 ++ s1 (C:fs9gps:FlightPlanWaypointsNumber) < l1 l3 < and)%{next}%{end}</String>

Right-o! Cessna, and a few avionics companies provide high-resolution imagery of there products such.I'm thinking pinned?

http://www.tghaviation.com/ - Here's one I use.

Same here, thanks.

Does anyone know if the Nearest Selected variables work? I can set the select number but I get nothing for the names or lat/lons of the selected.Such as: NearestVorSelectedVorLatitude

Thank You Jan. There isn't a difference between the two values though?

..just wanted to say you guys rule!Teaching me a bunch, thank you!

I'm actually more freeware than it seems you think or than I seem to have been labeled, but I suppose I'm not labeled that way....I'll see what I can figure out from your advice, thank you Jan. Thank You Bill, makes great sense now. Currently I'm just using a clip to make it look decent I may potentially add a mask if needed, this is great fun though - pie & arc rule!Thank You guys!

Just tested, they work now on mine too. Thank You Jan.You're saying Axis is more advisable than pivot correct?Would you be able to teach me/point me in the right directions for creating custom flightplan lines & symbols?

Jan I tried that but it didn't work.Bill, you're the man - again - thank you. The only difference I can tell from my code and yours is that there's no nonlinarity table and you've changed the value it seems to be an angel of 360 from what I can tell.What's the difference between the corrected N1 and the TURB ENG1 N1?EDIT: Bill you said that you hid the other two with the first one and the first one with a mask? How did you hid the other two with the first one?FYI, for whatever odd reason (A:TURB ENG1 N1,perecent) percent will not work, only the corrected [(A:TURB ENG CORRECTED N1:1,percent)] works. I replaced the corrected in bills code with turb eng1 n1 and it didn't work and then I put in the corrected into the initial code I used and it moved just as bills does now. I still don't know the difference between the too but corrected works with pie and turb eng1 n1 won't.