pfflyers

I've always been in the doubters camp. About forty years ago I took a few lessons in a C150, including about an hour of solo touch and go time. To me the sim seems much easier on rookies. After seeing this question in a prior thread I got a chance to ask it of an old friend who is former AF, a current ATP, and a user of FSX. To my surprise he answered yes. He did stress that one would need help from the ground and good weather, but he thought an experinced simmer might pull it off. I'm still skeptical, but you can't completely dismiss the opinion of someone with thirty years of flying experience. So I asked him what were the chances I'd get the opportunity. That's when he LOL'd and said there is no way a member of the cabin crew would ask the passengers if anyone thought they could land the plane. He figured if both the pilots had the fish and there were no deadheading pilots aboard that they already knew about one of the cabin crew would be nominated. He thought liability alone would be enough to prohibit a nonemployee getting into the pilot's seat.

Officially, I'm sure most US carriers encourage crews to do a little 'hands on' once in a while to remain proficient. However, most airlines would want the crew to use autopilot whenever practical because it usually saves fuel. I have a friend that flies for a US airline and he certainly is not prohibited trom taking control when he wants to.

In the sim I like to fly older GA planes and helicopters primarily, so I prefer a gently used cockpit in keeping with the age of those aircraft. As long as we're talking about how developers model their cockpits, I'd like to say to those developers that feel every old plane needs a giant GPS in the middle of the panel that I wish more would offer the option of a 'vintage' vc panel to those of us that prefer old school cockpits.

I have a friend that's a pilot for a US airline. We don't get to talk as often as I'd like, he flies internationally a lot. Whenever we talk I always have a list of questions raised in these type of forums. Hmm... maybe that's why he doesn't call more often. Anyway, just the other night I asked him about this. They have to practice autoland, but seldom use it for real. He told me he normally kicks off the autopilot around the time they turn onto the base leg. One thing I hadn't thought about - he told me that hand flying the whole approach increases the PNF's workload. So, if you want to keep your copilot happy you don't make him work harder than necessary.

I read in another thread a comment from someone claiming to be a RW pilot that many airline's pilot operations manuals actually discourage hand flying and require their pilots to use automation whenever possible. I think this was brought up in the Asiana T7 accident discussion.

It should be noted that (AFAIK) the shockwave light controller gauge only controls shockwave light effects. You can "stack" effects if you want to. When the shockwave controller shuts off the shockwave landing lights you will still have the 'stock' effect in place controlled by your panel switch.

Just wanted to add a post-script. This discussion got me curious as to whether or not I was giving accurate info. Specifically I wanted to see if shockwave provided "switched" and "unswitched" landing light effects - and I think I found that they DO NOT. So, if one installed shockwave landing lights on the wing or fuselage I think they would shut off with the gear retraction assuming one installed the light control gauge (and it worked). I wanted to test this hypothisis, but my shockwave auto switch off thingie seems to have broken. I bought the pack some years and computers ago. I think somewhere along the line a reinstall may not have gone right or it could just be operator error. These questions would probably be easily answered if I could find the documentation that came with the pack, but I can't. In any case, it should be noted that the shockwave effects pack contains way more than just landing lights. I never did get around to really exploring all that's there. Just looking at what's in my effects folder it seems like one could stay occupied for a long time just goofing around with them.

Historic Jetliners Group (HJG) has some freeware Convair 880/990 models available. Their external models and liveries are nice, but they don't do vc's for the most part. Sadly that's a deal-breaker for me these days. I know that many of folks that fly heavies alot prefer a 2d panel, if you're one of them then these are just what you're looking for.

Just to once again attempt to clarify - only the gear-mounted landing lights turn off 'automatically' - the body/wing monted lights respond to your switch inputs. You can have your landing lights on all the time with shockwave lights if you want. Many aircraft models have lights modelled into them rather than added on as effects. This is why the "lights" section of many config files is so sparce. In the case of landing lights, shockwave lights can be added over the top of modelled in lights. The neat thing about shockwave landing lights is they are "volumetric" rather than just being a bright spot on your airplane. When you see it you'll understand why people like them. For models with wing flex you cannot use shockwave navs or strobes because they won't move with the wingtips. It sounds to me like you've become a little obssessed with the fact that shockwave includes a gauge to shut off the gear mounted lights. You don't have to install the gauge if you don't want to. In that case the lights will respond to the landing light switch. I don't work for the shockwave folks and am not an expert in all aspects of them. If you want more people to respond you should start a new thread with a title like "Why Should I Install Shockwave Lights?" or "How Does One Install Shockwave Lights?"

The reason the gear mounted landing lights automatically switch off (assuming one installed the effect and gauge) is because the light effect does not move with the gear as it retracts. If it did not switch off you would have lights flying formation with your plane after the gear retracts. Wing or fuselage mounted landing lights can stay on as long as you like. As for installing the lights - yes, you must edit your config files yourself. AFAIK there is no auto-install mode. The premade file enties you found will help you set up those planes; for others you are on your own. In most cases you can use the existing locations and simply substitute the shockwave effects. In some cases the lights will look better if slightly adjusted. One reason for the saved files being offered is because some of the effects come in a variety of sizes so some trial and error is needed to find the best match for a given airplane. There is no need to update every plane in your hanger all at once. If this all sounds too daunting you may be better off to leave things as they are.

The Shockwave lights are nice, even in daytime. For me the major selling point is the landing light effects. They are very cool 3d looking effects. I've added them to most of my aircraft. I seldom fly at night myself, but the effects look great even in daylight.

You might try adjusting the [pitot_static] entries in your config file. [pitot_static] vertical_speed_time_constant= x.x //Increasing this value will cause a more instantaneous reaction in the VSI pitot_heat=1.000000 Sometimes decreasing the value will reduce 'hunting' in altitude hold. PF

Thanks for the tip. I'm a bit of a technophobe, so everything that happens inside this box under my desk is magic to me.

The way I read their announcement is that they are releasing FSX to Steam in its original form (possibly fixing multiplayer) and then using the FLIGHT engine to develope a new game. Maybe I read it wrong?

I found two files here in the library: ffg_lear35a_n388pd.zip ffg_c21_usaf.zip

I can't believe anyone would think manufacturing and marketing such a device would be a good idea. Any average idiot could have predicted the reception they would get, and the subsequent banning by the airlines.

Not trying to sound like a monday morning quarterback here, but I'm still curious about that throttle pumping. My actual flying experience is limited and pretty dated, but I remember that the carbs on the aircraft I flew did not have accelerator pumps so pumping the throttle would not add any fuel to the airstream unlike in my old cars. Maybe aircraft carbs are different now? Was he trying to dislodge possible ice on the butterfly? Just curious, and I agree that his landing speed looked a little hot.

That article reads much more like a sensational hit piece intended to pump up USA Today's bottom line than a serious attempt to inform the public. Even if the aircraft and equipment producers were all heartless and unconcerned with the health and welfare of those using their products, they are businessmen. It's bad for business when you kill off your customers. Just because you can get a jury to award damages does not mean the aircraft design was actually at fault. The lawyers always go after the deep pockets. The grieving widow or injured survivor is always a sympathetic figure. I worked for years in GA maintenance and a large part of our work was complying with Airworthiness Directives and Service Bulletins to correct identified defects in aircraft and equipment.

When I heard about the Oculus system the first thing I thought of was vertigo when used it in flight simulation. I think I'd get "airsick" for sure using it. I think I'd like it better for something like driving/racing sims or maybe an FPS.

I've been simming almost thirty years now, but I'm really not a "serious" simmer. I just do it for the experience of flying and to exercise my inner Walter Mitty. I fly mostly GA and helicopters so detailed scenery is something I enjoy. I have often explored by car and boat. The idea of being able to fly to an airport, then get in a helicopter, car, or boat and travel to a location away from the airport over plausible high resolution scenery seems like it would be fun to me. This is one of the things that makes Outerra seem interesting to me, it looks like you could build a "world sim" based on that. Not sure I need missions though.

When I was stationed in Germany in the seventies I visited an automotive museum where they had a turbine car prototype. I have no idea now what it was or how old it was, but in typical European fashion it was much smaller than that Chrysler.

I guess it would be fair to say that the flight modelling still needs work. I'm sure at this point aircraft in Outerra are just technolgy demonstrators, allowing people to explore the scenery and see some of the possibilities.

You put some entries in the wrong place, that's why your panel "disappeared" Try this config file, this format should work. It's your panel rearranged. // This Panel.cfg file created by CfgEdit // Built Thursday, November 27, 2003 at 20:55 Build:16518 [Window Titles] Window00=Main-Panel Window01=GPS Window02=Yoke Window03=Posky_Debug Window04=Posky_Util Fixed Window30=Forward Right Fixed Window31=Right Fixed Window32=Rear Right Fixed Window33=Rear left Fixed Window34=Left Fixed Window35=Forward Left [VIEWS] view_forward_WINDOWS=MAIN_PANEL,RADIO_STACK_PANEL VIEW_FORWARD_RIGHT_WINDOWS=30 VIEW_RIGHT_WINDOWS=31 VIEW_REAR_RIGHT_WINDOWS=32 VIEW_REAR_RIGHT_ZOOM=1.0 VIEW_REAR_RIGHT_EYE=0.0, -0.0, -23.5 VIEW_REAR_RIGHT_DIR=1.5, 0.0, 90.0 VIEW_REAR_WINDOWS=33 VIEW_REAR_ZOOM=1.0 VIEW_REAR_EYE=1.9, -0.1, -30.0 VIEW_REAR_DIR=1.0, 0.0, 295.0 VIEW_REAR_LEFT_WINDOWS=34 VIEW_REAR_LEFT_ZOOM=1.0 VIEW_REAR_LEFT_EYE=1.2, -0.0, -23.5 VIEW_REAR_LEFT_DIR=1.5, 0.0, 270.0 VIEW_LEFT_WINDOWS=35 VIEW_FORWARD_LEFT_WINDOWS=36 VIEW_UP_WINDOWS=37 VIEW_UP_DIR=5.0, 0.0, 130.0 [Window00] file=757main.bmp size_mm=1320,1007 window_size_ratio=1.00 position=7 visible=1 ident=0 window_size= 1.000, 1.017 window_pos= 0.000, 0.000 gauge00=rptimer!rp733_timer, 775,711,93,91 gauge01=ca727asi!rp732_asi_fs2k, 208,551,126,130 gauge02=Boeing747-400!Autopilot Heading Window, 975,314,80,25 gauge03=737-400!Flaps Ext, 1287,474,33,23 gauge04=Boeing747-400!Multi-Function Display, 353,696,236,261 gauge05=rp733_adi_efiss!rp733_adi_efis, 350,480,241,228 gauge06=cessna208!ATC-Display-Toggle, 878,546,25,14 gauge07=cessna208!Map-Display-Toggle, 878,585,25,15 gauge08=FPDA_Gear_Wind!FPDA_Gear_Wind, 0,0,10,8 gauge09=cessna208!GPS-Display-Toggle, 878,567,25,14 gauge10=ca727ra!test, 589,760,129,130 gauge11=FuelTotAirbKg!FuelTot777Kg, 1080,605,196,26 gauge12=Boeing777-300!Master_Caution, 559,336,35,31 gauge13=757grab.flever!Lever, 1257,935,57,90 gauge14=ndk700_stdbyatt, 770, 491 ,87,84 gauge15=lear_45!Left Gear Light, 1224,533,19,18 gauge16=lear_45!Nose Gear Light, 1244,533,19,18 gauge17=lear_45!Right Gear Light, 1266,533,19,18 gauge18=BOEING767-300!Nav GPS Switch, 72,696,33,32 gauge19=cessna182s!Autopilot_Switch, 695,357,30,29 gauge20=Autothr_Sw!Autothr_Sw, 842,306,29,35 gauge21=A2-radio.1!Lear-45.Radio, 828,882,158,122 gauge22=ca727alti!rp733_alt, 597,507,120,118 gauge23=OMR737Combi!FPDA_737_Combi, 773,600,97,101 gauge24=ID_767_CentrEICASqz!ID_767_CentrEICASqz, 885,639,90,74 gauge25=767ee5.flaps!, 1223,633,62,60 gauge26=ca727vsi!Carp707_vsi, 595,636,122,121 gauge27=700SIGNS!Signs by Gauge Master, 952,-11,113,67 gauge28=sound.ac!AIRCOND, 891,7,24,20 gauge29=00.767-reverse2.ca!reverse, 1024,451,63,11 gauge30=00.767-reverse1.ca!reverse, 1119,451,63,11 gauge31=00.747-COMPASS.ca!Extra-300.Wiskey-Compass, 1091,75,72,58 gauge32=737-400!Flaps Transit, 1287,501,33,21 gauge33=mooney_bravo!Navigation Lights, 75,738,27,31 gauge34=mooney_bravo!Strobe Lights, 75,771,27,31 gauge35=Mooney_Bravo!Recognition Lights, 75,812,27,31 gauge36=Mooney_Bravo!Rotating Beacon, 75,849,27,31 gauge37=FD_Sw!FD_Sw, 809,342,30,33 gauge38=Boeing747-400!Autopilot Altitude Window, 1149,314,83,25 gauge39=Boeing747-400!Autopilot VS Window, 1051,313,83,29 gauge40=ab330Nav2, 719,316,58,25 gauge41=ab330NAV1, 642,316,58,25 gauge42=Boeing747-400!Autopilot Altitude Hold Switch, 1173,374,39,37 gauge43=HM_DASH8_APLVL!aplvl, 1122,378,25,12 gauge44=Boeing747-400!Autopilot Hdg Switch, 995,384,31,29 gauge45=Boeing747-400!Autopilot Nav Switch, 937,303,31,29 gauge46=Boeing747-400!Autopilot Approach Switch, 939,344,33,29 gauge47=ID_767_Oil!ID_767_Oil, 995,674,85,166 gauge48=Boeing747-400!Autopilot Speed Switch, 842,342,32,28 gauge49=Boeing747-400!Autopilot IAS-Mach Switch, 845,378,29,27 gauge50=Boeing747-400!Autopilot IAS-Mach Window, 874,314,60,25 gauge51=BOEING777-300!Autostart, 732,787,29,33 gauge52=ID_767_EICAS1!ID_767_EICAS1, 1063,474,140,139 gauge53=ID_767_EICAS2v2!ID_767_EICAS2v2, 1071,669,135,111 gauge54=BOEING777-300!Fuel_Selector, 734,870,31,29 gauge55=757grab.Throttles!757grab.Throttles, 1054,852,190,255 gauge56=757grab.slever!Lever, 960,872,64,192 gauge57=rp733_autobrake!rp733_autobrake, 887,769,93,79 gauge58=ID_767_Brk_Hdl!ID_767_Brk_Hdl, 749,940,110,120 gauge59=00.gearl.ca, 1265,560,80,120 gauge60=A2-elevator.trim!Lear_45.Elevator-Trim, 1079,775,54,65 gauge61=pg.a310.grab.surf!Lear_45.Control_Surfaces, 1137,783,59,50 gauge62=Gauge001, 197,694,154,202 gauge63=ML_ND!Nav Display Switch, 137,824,59,59 gauge64=757_altalert, 634,464,54,26 gauge65=757_OMI, 877,471,26,70 gauge66=B757!Landing Outboard Lights Switch, 1061,34,53,50 gauge67=B757!Landing Inboard Lights Switch, 1117,34,52,51 gauge68=B757!Taxi Lights Switch, 1172,36,56,50 gauge69=B757!Autopilot IAS-Mach Selector, 880,357,63,60 gauge70=Boeing747-400!Autopilot Heading Selector, 975,336,88,57 gauge71=B757!Autopilot Altitude Selector, 1162,339,56,57 gauge72=ID_AP_Disc_Bar!ID_AP_Disc_Bar, 1264,388,56,41 gauge73=Cessna208!Nav-GPS-Switch, 29,429,20,22 [Window01] Background_color=16,16,16 size_mm=456,378 window_size_ratio=1.00 position=8 visible=0 ident=GPS_PANEL window_pos= 0.6300, 0.588 window_size= 0.379, 0.397 gauge00=fs9gps!gps_500, 0,0 [Window02] file=757Yoke.bmp size_mm=1320,1007 window_size_ratio=1.00 position=7 visible=0 ident=31 window_size= 1.000, 1.017 window_pos= 0.000, 0.000 [Window03] VISIBLE=0 position=2 size_mm=350,200 child_3d=0 background_color=0,0,0 ident=POSKYDEBUG gauge00=Posky777!POSKYDEBUG, 0, 0 gauge01=Posky777!POSKYDEBUG2, 0, 100 [Window04] VISIBLE=0 position=2 size_mm=204,80 child_3d=0 background_color=0,0,0 ident=Posky Utility gauge00=Pky_Util!Pky_Init, 0, 0 gauge01=Pky_Util!Pky_Timer, 0, 0 gauge02=Pky_util!Pky_Util, 0, 0 [Fixed Window30] file=757_right_front.bmp position=7 visible=0 ident=30 render_3d_window=1 nomenu=1 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 [Fixed Window31] file=757_right_side.bmp position=7 visible=0 ident=31 render_3d_window=1 nomenu=1 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 [Fixed Window32] file=757_right_aft.bmp position=7 visible=0 ident=32 render_3d_window=1 nomenu=1 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 [Fixed Window33] file=757_left_aft.bmp position=7 visible=0 ident=34 render_3d_window=1 nomenu=1 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 [Fixed Window34] file=757_left_side.bmp position=7 visible=0 ident=35 render_3d_window=1 nomenu=1 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 [Fixed Window35] file=757_left_front.bmp position=7 visible=0 ident=36 render_3d_window=1 nomenu=1 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 //----------------------SkySpirit VC entries------------------ [Vcockpit01] VISIBLE=0 position=2 size_mm=350,300 child_3d=0 background_color=0,0,0 ident=POSKYDEBUG gauge00=Posky763!POSKYDEBUG, 0, 0 gauge01=Posky763!POSKYDEBUG2, 0, 100 gauge02=Posky763!POSKYDEBUG3, 0, 200 [Vcockpit02] VISIBLE=0 position=2 size_mm=204,80 child_3d=0 background_color=0,0,0 ident=Posky Utility gauge00=Pky_Util!Pky_Init, 0, 0 gauge01=Pky_Util!Pky_Timer, 0, 0 gauge02=Pky_util!Pky_Util, 0, 0 Day=255,255,255 Night=130,75,75 Luminous=160,100,100 [Default View] X=0 Y=0 SIZE_X=8191 SIZE_Y=2650

Sounds like you must have installed Bill Lyons' Grumman Goose package at some point. He included the "invisible" Flight 19 avengers so you would hear them talking to ATC, but not be able to locate them visually. Just like the real Flight 19.

Are you sure you're flying a Huey? Sure looks like a Black Hawk to me.