Jump to content

okbob

Registered Users
  • Posts

    109
  • Joined

Personal Information

  • Location
    Edmond, Oklahoma USA
  • Occupation
    Environmental Attorney

Interest

  • Interests
    IFR flying

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

okbob's Achievements

Community Guru

Community Guru (4/7)

  • Dedicated Rare
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter Rare

Recent Badges

10

Reputation

  1. Thanks guys. I don't know how I missed that. Happy Saturday, Bob
  2. My apologies if this has already been asked, as I've not found an answer anywhere. Many thanks, Bob Kellogg
  3. If you took the screenshot, you have the copyright, not the model producer. But if you took the model-producer's photo and published that yourself, you would be in technical violation of copyright law. And a work is deemed copyrighted when published. Period. Proof of copyright is made easier if one also files with the copyright office and includes the c in a circle.
  4. Peter, the install tips has a small section about how to open the xml file and how easy it is to edit. Could be a nice learning experiment for you. Bob
  5. Peter, I think you could edit the xml to use (>K:AP_PANEL_SPEED_HOLD, bool). I do not know how well it works. Bob
  6. I'm 75, a private pilot single-engine-land, and still use FSX to practice and write gauges. I also have MSFS, but only use it for the eye candy of flying the C152 around my local area (OKC). For more serious work, its FSX.
  7. Very nice. Thanks for the credit, guys. Bob Kellogg
  8. I have both. I use FSX for serious simming. Plus I can easily customize the gauges, panels and cockpits to look exactly like what I fly, or want to fly. On the other hand, I use MSFS for pretty jaunts around the patch in their stock Cessna 152. And boy, does my city landscape look real!! However, I cannot customize the panel to look like the ones that I rent, nor can I adjust the flight characteristics. But I expect that they will simplify/expand/explain the SDK sometime in the not-too-distant future to where I can figure out how to do those things that I can do in FSX. Until then, I'll happily fly both. Cool beans, okBob
  9. Like Larry says, there's a few of us
  10. You might try adding: Background_Color=0,0,1
  11. Let me suggest that moving from a single-engine airplane to a twin is a large step-up in emergency preparedness training. in addition to retractable gear and constant speed props (which you can learn in a Mooney, for example), you must also learn what to do when one of the engines quits. There will be adverse yaw (due to asymmetric thrust created by just one engine working) and new minimum speeds to learn (such as minimum single engine speed, below which you don't have enough rudder to correct the yaw). Plus identifying which engine quit, and whether it is the one with the most adverse yaw. Other than that, the only big difference is the speeds at which they fly, and the altitudes they can achieve. You might try googling POH for the model plane you're interested in. POH is short for pilot's operating handbook. If you look, you can find a free pdf for just about any aircraft. Also, google flight review for the plane, and you can read about flying it in magazines such as Flying, AOPA Pilot, etc. As for the speeds, I make an index card for each of the airplanes that I fly: on it I list clean and dirty stall speeds; best angle/rate of climb; maneuvering speed; gear/flaps speeds; and blue line speed for twins. Plus any quirks. Cool beans and good luck.
×
×
  • Create New...